triage: Rafiki roadmap queue for next swarm

[WalksWithASwagger]

Goal

Refresh the Rafiki roadmap queue and identify the next safe swarm lanes.

Existing handles to classify

• Epic: Epic: retire alex-samuel studio into Rafiki (value-first) #268
• Track issues: Track 1: Floyo video pipeline (value-first) #263, Track 4: Audio surface (Suno ingest/management) #264, Track 5a: Production-knowledge indexing (importer extension) #265, Track 5b: Canonical gitignored media home + corpus migration #266, Track 6: Retirement cutover + verification #267, Track 2: LoRA lite slice (film LoRAs only) #270, Track 3: Clips review surface in the portal #271, Track 7: gorgeous-ghost carve-out (work repo) #274
• Related blocked/human-gated issues: Verify Notion signed upload against live workspace #69, Validate Curriculum Atlas story rail with real review sessions #200, Add Curriculum Atlas presentation/export controls #201
• Current PR gate to account for: feat: add dark-crystal signature style (order + chaos poles) #305

Scope

Triage only. Do not implement roadmap work in this issue.

Classify each issue as:

• agent-ready
• blocked
• needs-human validation
• stale/rewrite needed
• ready for PR review

Acceptance criteria

• One queue table with issue number, title, status, recommended next action, and stop rule.
• Identify 2-4 highest-leverage swarm lanes for the next work session.
• Separate provider-key/live-generation work from dry-run/docs/test work.
• Confirm no local output/media artifacts need to be committed.

Tests / verification

• gh issue list --repo WalksWithASwagger/rafiki --state open --limit 100
• gh pr list --repo WalksWithASwagger/rafiki --state open --limit 50
• Read README.md, docs/ROADMAP.md, and package scripts before recommending lanes.

Hard stops

• No live provider calls.
• No generated image output commits.
• No PR merges or issue closures.