Files
cxwandClaude Fable 5 475abfeaed chore(deps): upgrade hyperframes 0.7.60 -> 0.7.106
Bumps the pinned render backend (packages/tools dependency, the npx
fallback spec in DEFAULT_HYPERFRAMES_SPEC, and the README mentions).

Compatibility verified against everything OSS actually invokes:
- Full OVS_E2E=1 suite 287/288 green, including the real hyperframes
  render e2e and the draft pipeline.
- Real `ovs snapshot` end-to-end on 0.7.106: the frame naming contract
  (`frame-<NN>-at-<T>s.png`, index-ordered), contact-sheet.jpg, multi
  `--at`, and `--describe false` all behave as the preview-evidence
  code assumes.
- Every flag OSS passes still exists (snapshot --at/--describe/
  --output, render --output/--quality, check --json, lint); the
  check --json section shape is unchanged, so the draft disposition
  parser keeps working.

Capability probe (the reason this upgrade was tried first): 0.7.106
still exposes NO deterministic per-element visibility evidence. The
pinned-scene fixture (`#scene-hook{opacity:1!important}` overlaying
every later scene) passes `check --json` with ok:true and zero
findings, exactly as on 0.7.60; `inspect` is a deprecated overflow
checker; `snapshot --describe` remains Gemini-vision (non-deterministic,
needs GEMINI_API_KEY). Building the INACTIVE_SCENE_VISIBLE-class
checks therefore still requires a headless-browser DOM sampler — a
separate dependency decision, not part of this bump.

Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01VL7mRpmEphLAbcH7YmABnV
2026-08-12 12:01:07 +08:00
..