Launch Asset Checklist (tracking from README)

[driver727-pixel]

This issue extracts and tracks the launch-blocking asset tasks from the README for visibility and easier collaboration.

Required before launch

• Upload and register all rarity frame files in /public/assets/frames/
• Audit district backgrounds so each live forge district has both print and small variants
• Review card/share/download flows and replace remaining generated stable layers with static assets where possible

Future content decisions (locked in but optional)

• Treat The Roads as a corridor gameplay layer where route events spawn, not as a forgeable district or standalone mission

Nice-to-have immersion uploads

• District ambience loops
• Mission success/failure/fork-choice audio
• Battle queue/draw/result audio
• Trade sent/accepted/declined audio
• Launch promo/social share art

Known follow-ups

• Refactor or retire the BoardComposite pipeline as appropriate
• Keep The Roads as an event layer rather than a district selector

Edit this issue as tasks are completed or revised. See README.md for latest context.