Scenes feed: jsDelivr treats scenes@v2 as a semver VERSION and never re-resolves a retag (Games tab stale)

[AlexZ005]

The Games tab in production shows three games; the feed has six

sceneTemplates.js reads https://cdn.jsdelivr.net/gh/theprototype-app/scenes@v2/index.json. The serving ritual retags v2 (git tag -f v2 && git push -f origin v2) and purges — and the retag is never picked up.

Root cause (measured 2026-09-20)

jsDelivr parses v2 as a semver version, not a tag:

$ curl -s https://data.jsdelivr.com/v1/package/gh/theprototype-app/scenes
{ "tags": {}, "versions": ["1", "2"] }

$ curl -sD - https://cdn.jsdelivr.net/gh/theprototype-app/scenes@v2/index.json | grep x-jsd
x-jsd-version: 2
x-jsd-version-type: version        <- cached PERMANENTLY, never re-resolved

Files under a resolved version are immutable on jsDelivr's side; purge.jsdelivr.net reports finished for the path but the version→commit resolution is not refreshed. Result: scenes@v2/index.json is still the copy from before Jam Room (towers, stars-room, football), ~16 h and four purges after the retag, while the new files resolve by path (they were never cached) and scenes@a5ebe8f/index.json is right.

@main resolves as a branch (x-jsd-version-type: branch, cached ≤ 12 h, purgeable) and lists all six games.

Options (a product decision — the pinned-format-tag convention is the user's)

1. Point SCENES_BASE at a non-semver ref. A branch (scenes@main, or a format-2 branch that only moves on the ritual) or a tag whose name jsDelivr cannot parse as a version (format-2). Keeps "new ref per FORMAT bump only". One-line change in sceneTemplates.js (+ the same trap for packs@v1, which has not been retagged yet and will hit this the day it is).
2. Cloud build override today, no core release: VITE_SCENES_BASE=https://cdn.jsdelivr.net/gh/theprototype-app/scenes@main in the cloud .env.deploy — contentBase() exists for exactly this. Production shows the six games on the next deploy.
3. Per-release commit pins (scenes@<sha>): always fresh, but every content change becomes a core release, which the tag convention was chosen to avoid.

Recommended: 2 now (a deploy), then 1 in the next core release, with a note in the scenes repo's ritual that v2 is dead on jsDelivr.

Found while closing roadmap 29 round 2 (lane 29-integrate).

[AlexZ005]

Decision (user, 2026-09-20): option 2 now, option 1 next core release

Half 1 — done, production is fixed. VITE_SCENES_BASE=https://cdn.jsdelivr.net/gh/theprototype-app/scenes@main added to the cloud .env.deploy (gitignored) and the site redeployed from the same v1.15.1 tag — no core release, no PB migration, no Worker change. Cloud c916210 records it in the deploy CHANGELOG.

Verified live rather than assumed:

$ curl -s https://www.theprototype.app/_app/immutable/nodes/2.BVdNSDMl.js \
  | grep -o 'Sx(`[^`]*scenes@[a-z0-9]*`'
Sx(`https://cdn.jsdelivr.net/gh/theprototype-app/scenes@main`

i.e. contentBase(VITE_SCENES_BASE, '…scenes@v2') now takes the override and the v2 literal is only the unused fallback. The feed at that ref lists all six games (towers, stars-room, football, jam-room, dungeon-realms, untangle); scenes@v2 still lists three. Same on pages.dev and the apex.

Half 2 — still open, this issue stays open for it. Core's SCENES_BASE default in src/lib/sceneTemplates.js:31 still ships scenes@v2, so anyone building core from source gets the stale feed. It should move to a ref jsDelivr cannot parse as a version — format-2 keeps the "new ref per FORMAT bump only" convention and is one line:

export const SCENES_BASE = contentBase(import.meta.env.VITE_SCENES_BASE, 'https://cdn.jsdelivr.net/gh/theprototype-app/scenes@format-2');

PACKS_BASE in src/lib/packs.js:21 has the identical trap sitting unexploded — packs@v1 has simply never been retagged. It should move in the same change, and the scenes repo's serving ritual (and the layout notes that quote it) needs the line that v2 is dead on jsDelivr and a retag of a semver-looking ref is a no-op.

Not doing the core half today: it is a core release, and 1.15.1 shipped hours ago. Queued as its own lane.

[AlexZ005]

Core half: #235 (SCENES_BASE → scenes@format-2, PACKS_BASE → packs@format-1). Measured: a plain TAG named format-2 is reported x-jsd-version-type: branch with s-maxage=43200 and lists six games; companion docs theprototype-app/scenes#7, packs#1, cloud#28. The .env.deploy scenes@main override stays until the core release carrying #235 is deployed.