Release media: Flywheel renders its own explainer and walkthrough at every release

[HarperZ9]

Flywheel joins the media-at-every-release loop (raw-native ADR 0012).

Scenes (docs/media/):

• Which source decides: the Form 1040 example in examples/output-validation.
  • The rate schedule and the tax table are drawn from tax_table.py's own rule. The scene checks its table against the checker program's answer and draws nothing if they disagree.
  • The view zooms from the whole first two brackets into the $50 row at $36,700, where the midpoint rule gives $4,169 against the filed $4,165.50.
  • It ends on the three runs, with the verdicts and exit codes that run_output_check.py prints at the release commit (FAIL 1, PASS 0, UNVERIFIABLE 3).
• First check: a walkthrough of the same three runs, with their recorded output and exit codes.

Facts: every number on screen is read at render time. That covers the answers, the authority the contract names, the brackets and row width, the checker's value, and each run's verdict and exit code. All 17 read on the current main (version 1.5.0).

Workflow: .github/workflows/release-media.yml calls HarperZ9/raw-native/.github/workflows/media.yml@main on release: published, or by dispatch with a tag. It renders on a hosted runner at 960 x 540, with captions and no narration, and attaches the videos, posters and bundles. The narrated 4K render follows on the author's machine.

Depends on HarperZ9/raw-native#32 (step cwd, exit-code and stdin facts, show_exit). Merge that first.

Local render: on Chrome's CPU adapter at 640 x 360 the explainer is 1,667 frames (median 54 ms) and the walkthrough 847 frames (median 167 ms).

🤖 Generated with Claude Code