Answers ruling 38. Code cites are at origin/main 46ed046.
Today
- A game is live when
content/games/<slug>/meta.yamlsaysstatus: live(content/games/letter-sound-hunt/meta.yaml:19); prebuild copies it tosrc/data/catalog-status.js:4. - Going live = launch-games: render, R2 upload, manifest refresh, meta.yaml flip, then PR and squash merge (
~/.claude/skills/launch-games/SKILL.md:29-38). - The site already reads D1 (
wrangler.toml:149). On merge,deploy-website.yml:92-113syncs git into D1, but it skips withoutCLOUDFLARE_CATALOG_D1_TOKEN(:109). Result: 4 merged games 404. - The sync still writes
statusfrom git (scripts/catalog-sync.mjs:16). - The daily Worker curates from its bundled catalog unless
CATALOG_SOURCE=d1(workers/daily-playset/src/deliver.js:242). Its release guard rejects any vars change (scripts/deploy/daily.mjs:26).
Target
Tap LIVE in the packet; the game is on the site minutes later and in the next daily email. No PR.
Sequence
- D1 token (you). Sync runs and the 4 404s clear.
- #481 before the first production LIVE tap (phase 4 can build on preview in parallel). Phase 1 (tests only) can start now; phase 2 is the production flip. Otherwise a D1 publish changes the site but not the email (
deliver.js:242,:269-272). - #413 phase 4, amended. Publish endpoint (role, audit row, R2 pre-flight) plus packet LIVE/KILL buttons. Amended: your 10-08 "Go 1" ruling keeps pages pre-built for live games only, so the endpoint must also trigger a rebuild that pre-builds the page. Neither half exists: the build's live set is meta.yaml (
src/lib/games.js:121) and re-releasing the deployed sha is skipped (scripts/deploy/website.mjs:77). - #413 phase 5 (cutover), pulled up next to phase 4. The sync stops writing
status. Otherwise the next merge reverts a packet flip (catalog-sync.mjs:16). launch-games loses its flip/PR phases. - #413 phase 6 cleanup, unchanged.
What stays in the PR workflow: game creation. Game, art and critic, plus, if you take decision 2, the render, R2 upload and manifest. Critic-ACCEPT PRs merge hidden as pending-review (ruling 38). Only publishing (LIVE or KILL) leaves.
Founder-owed blockers
CLOUDFLARE_CATALOG_D1_TOKEN(D1 Edit) as a website-production secret. Open since 10-11 (escalations.md:591).- Nod on the daily Worker production var
CATALOG_SOURCE=d1(#481 phase 2). publisherrole grant + first production flip (#413 phase 4).- Cutover date (#413 phase 5).
- Release-dispatch token (decision 1).
Risks
- List-vs-page window. D1-driven lists show a flipped game before its page is rebuilt (404 meanwhile); the release must pre-build it first.
- D1 outage skips a whole daily tick. There is no fallback (
deliver.js:272), so #481 phase 3 alerting is required. - Drift during dual-run. The parity check has been reporting success while skipped (escalations.md:646).
Decisions for you
- Rebuild trigger. Default: a fine-grained GitHub token,
actions:writeon scribble-works only, stored as a review-portal secret. - PDF moves into the creation PR. The R2 upload and manifest happen at hidden merge, so LIVE is a pure flip. Bear: the bucket is public, so a hidden game's PDF is reachable by URL before LIVE. Default: yes.
- Cutover with phase 4, skipping the 7-day dual-run. Default: yes, once #481 is live. Rollback is
CATALOG_SOURCE=filesplus a status re-export.