mirror of
https://github.com/hanzoai/video.git
synced 2026-11-03 04:21:39 +00:00
Separates creative grammar (renderer_family) from technical engine (render_runtime) so HyperFrames can stand alongside Remotion as a first-class runtime instead of masquerading as a Remotion sub-case. Locks runtime choice at proposal stage and enforces it end-to-end: the schemas require it, video_compose routes by it, the reviewer fails closed on silent swaps, and a parametrized contract test walks every pipeline manifest to ensure each planning-stage skill explains the conversation to the user. Adds hyperframes_compose (scaffold/lint/ validate/render/doctor/add_block), a playbook -> CSS style bridge, and vendored HyperFrames Layer 3 skills from commit d291358, pinned via PROVENANCE.md for future re-sync. Final_review now records render_runtime_used and runtime_swap_detected so compose lies are catchable after the fact.
2.6 KiB
2.6 KiB
Provenance — HyperFrames Layer 3 Skills
These skills are vendored from the upstream HyperFrames monorepo. Do not edit them expecting the changes to survive a re-sync — changes need to go upstream, or be recorded in the local-edit log below.
Source
- Repo: https://github.com/heygen-com/hyperframes
- Local clone:
C:\Users\ishan\Documents\hyperframes - Vendored commit:
d291358 - Vendored date:
2026-04-17
Mirrored directories
| OpenMontage path | Upstream path |
|---|---|
.agents/skills/hyperframes/ |
skills/hyperframes/ |
.agents/skills/hyperframes-cli/ |
skills/hyperframes-cli/ |
.agents/skills/hyperframes-registry/ |
skills/hyperframes-registry/ |
.agents/skills/website-to-hyperframes/ |
skills/website-to-hyperframes/ |
The gsap upstream skill is NOT re-vendored — OpenMontage already ships its
own GSAP skill family under .agents/skills/gsap*/.
Local edits
Any divergence from upstream is noted at the top of the edited file as an
HTML comment starting with OpenMontage-local. Current edits:
hyperframes-cli/SKILL.md— addedvalidateto the command list and a dedicated Validation section. Upstream omits it, but the CLI ships it and OpenMontage's HyperFrames runtime path relies onhyperframes validateas a real browser-based contract check before render.
Re-sync procedure
# From the hyperframes clone
cd C:/Users/ishan/Documents/hyperframes
git pull
# From OpenMontage
cd C:/Users/ishan/Documents/OpenMontage
rm -rf .agents/skills/hyperframes .agents/skills/hyperframes-cli \
.agents/skills/hyperframes-registry .agents/skills/website-to-hyperframes
cp -r C:/Users/ishan/Documents/hyperframes/skills/hyperframes .agents/skills/
cp -r C:/Users/ishan/Documents/hyperframes/skills/hyperframes-cli .agents/skills/
cp -r C:/Users/ishan/Documents/hyperframes/skills/hyperframes-registry .agents/skills/
cp -r C:/Users/ishan/Documents/hyperframes/skills/website-to-hyperframes .agents/skills/
# Then re-apply the local edits listed above and bump the vendored commit SHA.
Why we vendor instead of referencing the upstream clone directly
- OpenMontage contributors may not have the HyperFrames monorepo on disk.
- Skills must be readable from the OpenMontage tree for agent discovery.
- We want deterministic knowledge — upstream moves; we control when we pick up changes.