mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-05 22:27:29 +00:00
WaterrrForeverandClaude Opus 5
c1a128a072
Adds `render --require-version X.Y.Z`: refuse to render unless the running renderer is exactly that version. ## Why a pin is not enough `npx hyperframes@X.Y.Z` stops the renderer drifting between runs, but nothing checks the claim afterwards. A project states the version it believes it used and no artifact can contradict it. The provenance tag does not close the gap either. `hyperframes_version` stamped a constant `0.0.0-dev` for twenty published versions (#4365) — measured across 710 tagged mp4s, 710 carry that value, so the tag identifies nothing. #4409 fixes the stamp, which makes drift VISIBLE once a fixed build ships. This makes it ENFORCEABLE at the point it matters, before the encode. ## Three properties 1. **Fails closed on an unresolved version.** If the engine cannot say what it is, the gate cannot verify anything, and passing would hand back exactly the unfalsifiable claim the flag exists to remove — while looking green. It compares against the engine's exported `UNRESOLVED_VERSION` rather than a re-typed literal. 2. **Exact, never a range.** npm already gives the caller ranges. This answers "did the version I named run", and a caret would let the gate pass on a version the caller never named. 3. **Runs before the plan**, so a mismatch costs a startup rather than a full encode. ## Verification `checkRequiredVersion` is a pure function so the guard can be exercised; a guard that cannot be reached is one nobody has checked. 9 tests, extracted and executed: exact match, whitespace, mismatch naming both versions, fail-closed on unresolved, three exactness cases, empty value, and that the sentinel cannot be satisfied by asking for it by name. Two mutations, both red attributably: - drop the fail-closed branch -> exactly the 2 unresolved tests fail - lenient `startsWith` match -> exactly the 2 exactness tests fail The second is the one worth having: a prefix match is the tempting lenient implementation, and it silently passes `--require-version 0.8.7` against a running 0.8.72. I could not run the vitest suite here (no bun/node_modules on this machine), so please let CI confirm the suite itself rather than reading my green as a test run. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>