01-projects/printables-product

Scribble Works - publish new games without a PR (build plan)

2026-10-28·plan·status: proposed (verify-strategic-output ITERATE -> 4 fixes applied + trimmed, 2026-10-28); founder "Defaults" 2026-10-28 09:01 ET (ruling 39)
scribble-workscatalogd1publishinglaunch-games

Answers ruling 38. Code cites are at origin/main 46ed046.

Today

Target

Tap LIVE in the packet; the game is on the site minutes later and in the next daily email. No PR.

Sequence

  1. D1 token (you). Sync runs and the 4 404s clear.
  2. #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).
  3. #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).
  4. #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.
  5. #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

  1. CLOUDFLARE_CATALOG_D1_TOKEN (D1 Edit) as a website-production secret. Open since 10-11 (escalations.md:591).
  2. Nod on the daily Worker production var CATALOG_SOURCE=d1 (#481 phase 2).
  3. publisher role grant + first production flip (#413 phase 4).
  4. Cutover date (#413 phase 5).
  5. Release-dispatch token (decision 1).

Risks

Decisions for you

  1. Rebuild trigger. Default: a fine-grained GitHub token, actions:write on scribble-works only, stored as a review-portal secret.
  2. 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.
  3. Cutover with phase 4, skipping the 7-day dual-run. Default: yes, once #481 is live. Rollback is CATALOG_SOURCE=files plus a status re-export.