publishing a plugin is pushing a tag

Three mechanisms where there should be one. The catalogue was filled by hand, and each host separately
polled twenty-one repositories with git to work out whether a release existed — a second source of
truth for a fact one place already knew. Shipping photos 2026.09.03.02 correctly and watching alpha
not notice for ten minutes is what started this.

The timer. scripts/marketplace-cron.sh, every minute, on the machine that publishes. Safe now only
because the previous commit made the sync read tags instead of working trees; over the old one this
would have published somebody's afternoon on a schedule. Nothing is written unless the release commit
differs from the one already published, so a tick with nothing to do is one query, one fetch per repo
and no writes — about 2.7s. One timestamped summary line per tick regardless, because a fresh timestamp
is the only thing that separates "nothing to publish" from "the timer died"; a named line only for a
plugin that moved.

The badge. `updateable` now compares the tag at HEAD with the tag the catalogue says is newest —
difference, not ordering, since parsing 2026.08.27.01 works right up until somebody tags v2 and then
fails silently. refreshRemote() and its two-minute window are gone with the polling they existed to
paper over. The git rule stays as the fallback for a plugin the store cannot speak for: an unregistered
checkout, or an unreachable store. That case now reads whatever refs the last pull left, which is the
accepted cost of not making every machine poll every repository forever.

fetchCatalogue()'s cache went from five minutes to one. It only drew tiles before; now the wait for a
release to appear would have been the sync's minute plus its five.

Also: the Update button names its destination whenever a release is known, not only on `new-release`.
An untagged checkout reports `untagged` and used to lose the tag with it, so the button said "Update"
and the owner had to guess where it landed — the marketplace knows, even for a checkout that has never
fetched it.

Verified: forced a stale row, the timer republished it inside 60s and logged one line. Badge decisions
checked against the live catalogue for seven plugins, including the two shapes that matter — at a tag
the store agrees with, and untagged with a release known only to the store. 9 release tests pass, 100%
of release.ts covered, four of them new and all against real repositories.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/marketplace-todo.md

@@ -29,17 +29,21 @@ Ranked by what actually blocks something.
 
 ## Staleness
 
-- [ ] **Nothing refreshes the catalogue automatically.** Publishing a plugin update changes nothing until
-      somebody runs `bun --env-file=.env scripts/marketplace-sync.ts`. A Gitea webhook or a cron is the
-      obvious next step.
+- [x] **Nothing refreshes the catalogue automatically.** Done 2026-09-03: `scripts/marketplace-cron.sh`
+      every minute. A Gitea webhook would make it a second instead, at the price of a public write route
+      on the one process here with no login — not worth it for a minute.
 
-- [ ] **The sync reads local clones, not the remotes.** The machine running it must have every plugin
-      checked out, so the catalogue describes that machine's copies. The version that clones each repo
-      into a temp directory is a small change.
+- [x] **The sync reads local clones, not the remotes.** Done 2026-09-03. Bare mirrors, read at the newest
+      tag, driven by the registry rather than by a directory listing. The catalogue no longer describes
+      any machine's working copies.
 
-- [ ] **`rawUrl()` assumes Gitea and a `main` branch.** A GitHub-hosted plugin, or one whose default branch
-      is `master`, gets a 404 for its icon. The forge belongs in the registry rather than inferred from a
-      URL shape.
+- [ ] **`rawUrl()` assumes Gitea.** A GitHub-hosted plugin gets a 404 for its icon. The forge belongs in
+      the registry rather than inferred from a URL shape. (The `main`-vs-`master` half of this is gone —
+      URLs pin to the release tag now.)
+
+- [ ] **Four plugins have never been tagged**, so the store still shows rows the old sync took from a
+      working tree: av-club, kanban, openseo, fofos-admin. They are frozen until somebody tags them, and
+      the sync names them on every run somebody asks for.
 
 ## Scale