0.5.3 — Scenarios split into two pages

The monolithic scenarios page carried two distinct experiences (interactive cards and the LinkedIn static set) plus the shared data in one folder. They're now two independent, iterable pages over one shared bank — change one without touching the other.

What changed

• New shared bank. The "how long" data moved from the page folder to src/data/scenarios.json — a single source of truth. buildScenarios() in build.js reads that fixed path; any scenarios: true page inlines it.
• scenarios.html — PoC-1, interactive. Now only the branching cards (<rm-scenarios>) and the session record (<rm-scenarios-record>). The static-export code and styles were removed from this page.
• statics.html — PoC-2, the post images. New page. <rm-statics> is a scenario picker plus a stage that renders the selected scenario's four 4:5 artboards, with a Clean view toggle that drops page chrome for edge-to-edge screenshots. Deep-linkable via #<id> or #static=<id|n>.
• Both pages are gated to live scenarios — the same tone gate — so the post images can't get ahead of the vetted card copy. The two renderers share the bank, so the demo and the posts can never drift apart.

Housekeeping

• Rebased onto upstream 0.5.2 (light header on top-level pages, chain-derived smoke, pricing-restore snapshot, old-structure cleanup). The new pages adopt the 0.5.2 light-header design tokens — one look everywhere.
• Removed the orphan v0/v0.5/v0.5.0/index.html build output (0.5.0 is a chain intermediate, not a switcher target under the current manifest).
• Smoke suite extended: page-list parity now includes Scenarios + Statics, with new groups driving one card end-to-end (refuse → deflect → reveal → interval → record) and the static picker (four frames, switch scenario, still four).
• Frozen version outputs re-pinned: adding two HEAD pages changes only the inlined RM.data.pages fallback line in each snapshot (verified diff).

The consented survey capture (PoC-3) remains out of code — it needs the consent design and the Ambassador/AppSec review called for in the GRC plan.