The wiki is something running on our server, not part of the server
environment itself, so `wiki-pages` belongs in `services` by the org
taxonomy. Transferred on the forge, and the workspace folder and the
remote followed. Gitea's redirect keeps the old `infra/wiki-pages`
paths resolving, so the deployed checkout and existing links still
work.
The clone list, the wiki file paths in the table and the folder tree
in the README follow.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
MORE_STORES item 2 is done: stores/warp-engine-desktop-store and
stores/ttg-desktop-store. The write-up records what the implementation changed
about the plan — chiefly that the `html` asset is not a downloadable archive but a
hosted directory, so a browser title becomes a menu entry that opens its page
rather than an offline install.
Separately: `check-repos.sh` reported `infra/wiki-pages` as STALE while the repo
was plainly there. Gitea caps a page at 50 items whatever `--limit` says, so
`tea repo list --limit 1000` had been quietly returning the first 50 — invisible
until today, when the estate reached 51 repos. The check now pages through, and
fails loudly if the server returns nothing at all rather than declaring the whole
workspace stale.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The README's layout block was two reorganisations out of date: it still had
`tools_bbs/`, `tools_build/`, `tools_libs/`, an `archive/`, and the public site
and wiki at the workspace root. Since 2026-08-16 every folder is a Gitea org,
one to one — which is the reason a path in `repos.list` is just `<org>/<name>` —
so the block now says that, names the exceptions (`devarea` itself, plus `media/`
and `memory/`, which are not repos), and includes `stores/`.
`clone-repos.sh` needed no change: it makes the parent of each path, so a fresh
machine gets the org folders from the list alone.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
MORE_STORES.md asks which further host platforms could get a store like
the Batocera one, and starts from a measurement: the catalog ships html
for 11 of 15 titles and desktop binaries for 8, while the Batocera store
consumes only cartridge — 7. The gap is not the number of stores but
that the existing one leaves half the catalog untouched.
Also records that the ARM64 asset kind is the prerequisite for the
retro-handheld direction, and closes the internal-org item in
REPO_REFACT.md now that all eight builder images live under build/.
The Woodpecker note is corrected against what the CLI actually reports:
19 repos registered and active, not the 10 the pipelines table shows.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Both were written into the workspace root, which is not a git repo, so
they were versioned nowhere: one `rm` and they were gone, and nobody
else on the team could see them. They belong next to WIKI_CONNECTION.md
— all three describe the estate rather than any single repo.
The references in the ttg-ops skills follow in the marketplace repo.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
mr.zeroandClaude Opus 5