2026-09-09 roadmap grooming

Reviewed: ~/.claude/state/studio/queue.md (298 lines), rounds.md/escalations.md tails, charter §2 (2026-08-31, amended 09-04), gh pr list --repo RayDataCo/scribble-works --state all --limit 40, and content/*/meta.yaml on origin/release for age-band counts.

Findings

1. PR #132 (merged 2026-09-08T21:09Z) confirmed on release; queue.md:294's RESOLVED line under the Vaughn item is accurate — closed, no further action.
2. Catalog verified: who-plays-what (PR #131, merged) is status: pending-review, not live — the stated 3_4=15/5_6=7/7_8=7/9_10=6 count holds. 9-10 is the live thin lane.
3. queue.md:103's "NEXT ROUND BIAS" (set 2026-09-01) targets a generic "7-10" lane and cites treasure-boxes/snack-shop-sums as the only 2 games — both stale by ~8 days of shipped rounds (7-8 is now at 7, matching 5-6). It no longer describes reality and will mislead anyone skimming for current priority.
4. queue.md:296-298's pointer to "line 264" (admin review queue, spec-first) is broken: that item asked whether to spec the review portal — it was specced, built, and has been live in daily use since PR #108 (2026-09-07), with real founder decisions logged through PR #116/#117. Line 264 itself was never marked done.
5. Lines 1-102 of queue.md (2026-08-31/09-01 rulings) are ~95% completed work (wordmark PR #7, mobile-nav PR #33, footer/bubbles PR #44, playset builder PR #4, etc., all confirmed merged) sitting undifferentiated among still-open items — pure roadmap noise now.
6. Tonight's 9-10 lane build (cut_paste, maze) hit the same Fable 5.1 429 spend-limit wall already logged in escalations.md by sw-product — an account-level cap, not a content gate. Confirms this is a recurring cross-cutting infra risk (also hit on 09-06), not a one-off; worth carrying as context for any future 9-10 dispatch until the founder rules on the cap.

Proposed queue.md diff

• Retire queue.md:103 ("NEXT ROUND BIAS... 7-10 ONLY...") → replace with: "9-10 lane bias stands (6 live, thinnest); cut_paste + maze briefs remain queued as-is per escalations.md 2026-09-09, blocked only on the Fable spend cap."
• queue.md:264-265 (admin review queue spec ask) → mark RESOLVED: "Built and live via PR #108/#112/#113/#115/#116/#117; superseded, do not re-dequeue."
• queue.md:296-298 → drop the "(line 264)" pointer; it now points at a resolved item.
• Archive queue.md:1-102 to a dated queue-archive-2026-08-31.md (or fold to a one-line "shipped" summary), keeping only R1-R3/still-open items live in queue.md.

Decisions needed (founder)

• Fable 5.1 spend cap: raise it or authorize a standing model override for sw-builder — unresolved since 09-06, blocked tonight's build again.
• OK to archive queue.md:1-102 as proposed, or keep full history inline?