`stores/warp-engine-desktop-store` és `stores/ttg-desktop-store` törölve: a motor a
`warp-engine-client`be került (2.0.0), tehát nincs mit letölteni, és a 2.2.0 óta nincs mit
konfigurálni sem kívülről — a registry-rekord csak név + katalógus, a store-onkénti
szeparáció pedig almappa, amit a kliens a katalógus-hostból képzett slugból állít elő.
A `repos.list` és a `WIKI_CONNECTION.md` táblája követi (két sorral kevesebb), a
`REPO_REFACT.md` repófája a jelen állapotot mutatja, a történeti bejegyzések pedig
maradtak — azok arról szólnak, ami akkor történt —, datált lezáró jegyzettel.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Three entries in REPO_REFACT.md: the repository is stores/warp-engine-client (Gitea keeps
the redirect, releases and tags moved with it); a store config repository is optional
because the engine's defaults cover everything but identity; and the client has its own
Woodpecker pipeline rather than the /build/config extension, which serves game platforms
publishing into the catalog.
repos.list, WIKI_CONNECTION.md, ECOSYSTEM_PLAN.md and MORE_STORES.md follow the new name;
check-repos.sh is green with 52 repos.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
A new store is a database row on the site now, not a release of the client: the
`Store` model and the public /api/stores endpoint live in the host app, and the
Electron client reads them.
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 `tools` definition — "one person installs and runs it for themselves" — stopped
describing the store engines: they are products other people can build on. So the
four store repositories left `tools` for a `stores` org of their own, and the org
map, the clone list, the wiki table and the ecosystem plan follow. `check-repos.sh`
is green at 49.
Worth writing down for the next org change: `tea` has no transfer subcommand, but
`tea api` makes authenticated calls with tea's own credentials, which is enough for
all of it — POST /orgs, POST /orgs/{org}/teams, PUT /teams/{id}/members/{user},
POST /repos/{owner}/{repo}/transfer. And the transfer keeps Gitea's redirect: the
old `tools/...` raw URLs answer 301, so the installers on already-configured boxes
did not break. That is why this was a transfer and not a migrate-and-delete.
`warpstore` stayed in `engines`: it is a library other repos depend on, which is
what that org is for. The launcher gap moved out of the tools chapter of
ECOSYSTEM_PLAN into the new stores one, where it belongs.
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