hyperframes-qualitylisted

# HyperFrames quality gate Review the exact source project and exact candidate render. Do not treat a successful render command as quality evidence. Read `hyperframes-cli` first; then read `hyperframes-core`, `hyperframes-creative`, `hyperframes-animation`, or `hyperframes-keyframes` only when their area is in scope. ## Run the gate 1. **Validate the source.** Run `hyperframes check`. Resolve structural, deterministic-timeline, layout, and contrast findings before continuing. Use `hyperframes inspect --json` for dense compositions or targeted timestamps; inspect every major text/data moment, scene transition, and the ending. 2. **Review rendered evidence.** Render a draft when no candidate render exists. Extract a contact sheet and representative frames from that rendered MP4, including opening, scene midpoints, dense text/data moments, transitions, and ending. For multi-composition projects, prefer rendered-MP4 frame extraction over snapshot-only evidence; it is the delivery truth. 3. **Critique craft.** Compare the evidence with `BRIEF.md`, `STORYBOARD.md`, `SCRIPT.md`, and `frame.md` when present. Check: - message clarity by scene two and evidence/claim fidelity; - safe areas, typography, contrast, hierarchy, and readable playback-speed copy; - transitions, pacing, continuity, and whether motion explains rather than decorates; - seek-safe timing, no stale frames, clipping, blank states, or unintended repeated/frozen frames; - design-system adherence and a