Upgrade hyperframes 0.7.60 → 0.7.106 - #25
Merged
Merged
Conversation
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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VL7mRpmEphLAbcH7YmABnV
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Batch 12, stacked on #24. Bumps the pinned render backend: the
packages/toolsdependency, theDEFAULT_HYPERFRAMES_SPECnpx fallback, and the README mentions.Compatibility — verified against everything OSS invokes
OVS_E2E=1suite 287/288 green on 0.7.106, including the real hyperframes render e2e and the draft pipeline.ovs snapshotend-to-end: the frame-naming contract (frame-<NN>-at-<T>s.png, index-ordered join),contact-sheet.jpg, multi---at, and--describe falseall behave exactly as the preview-evidence code assumes.snapshot --at/--describe/--output,render --output/--quality,check --json,lint); thecheck --jsonsection shape is unchanged, so the draft-disposition parser keeps working.The capability probe this upgrade was meant to answer
Trying the upgrade first was the cheap path toward a deterministic DOM-visibility probe. Answer: 0.7.106 does not provide it.
#scene-hook { opacity: 1 !important }overlaying every later scene — the upstreamINACTIVE_SCENE_VISIBLEincident shape) passescheck --jsonwithok: trueand zero findings, exactly as on 0.7.60.inspectis a deprecated overflow checker (aggregate findings only);keyframesis tween-declaration-level;snapshot --describeis Gemini vision — non-deterministic and keyed.So the
INACTIVE_SCENE_VISIBLE-class checks still require a headless-browser DOM sampler (e.g.playwright-coredriving the system Chrome) — a separate dependency decision, deliberately not smuggled into this bump.🤖 Generated with Claude Code
https://claude.ai/code/session_01VL7mRpmEphLAbcH7YmABnV