@autoaiai/aicut 0.1.11 → 0.1.13

package/skills/erduo-broll-loop-engineering/references/prompt-first-workflow.md

@@ -1,322 +0,0 @@
-# Prompt-first production workflow
-
-## Inputs and output
-
-- Talking-head mode requires a matching edited source video and SRT.
-- Faceless mode requires an SRT.
-- User images, videos, logos, screenshots, ordinary references, and explicit
-  brand restrictions are optional.
-- A separate design file or preset is never required.
-- When the user does not specify a delivery location, create one new
-  timestamped directory beside the SRT using its basename plus
-  `-broll-YYYYMMDD-HHMMSS`, with a unique suffix when needed.
-- Default delivery is an ordered `05-delivery/shots/` directory: one directly
-  rendered H.264 MP4 per Recipe, 3840×2160, 30 fps, plus `shot-media.json`,
-  six-frame semantic check sheets, and `delivery-index.json`.
-- The complete preview is assembled only from those verified shot files. A
-  full-length `master.mp4` is optional.
-- Never overwrite an existing directory, shot, contract, preview, attempt, or
-  master path. `broll-shot-export` is legacy compatibility for pre-v1.0.1
-  master-based runs, not the default shot path.
-
-## Runtime contract
-
-Default runtime intent to `auto`. Read the runtime contract, validate Director
-recipes, then run the deterministic post-Director planner and validator.
-HyperFrames and Remotion are independent production routes; missing targeted
-local readiness is `action-required`. Auto may resolve to one backend or
-hybrid. HyperFrames and Remotion keep separate source; the Parent exchanges
-only independently verified shot files and never nests or translates runtime
-source.
-
-The Director authors one runtime-neutral Shot Recipe per shot. The Assets
-stage preserves runtime-neutral material roles and objective media facts. Each
-Builder owns its planned backend source and one direct render target per
-assigned shot. Parent scripts render, validate, contract, and assemble those
-shots for every route. Normal v1
-production never dispatches a Runtime Planner, Integrator, or Render Agent.
-Describing a recipe is not backend evidence.
-
-The bundled Shotcraft catalog is an optional runtime-neutral technique
-reference, not a second backend or a production gate. Original direction is the
-default; a complete film may use zero queries. Only after independent shot
-logic leaves one named technique question, or the user explicitly requests the
-reference, start with a directed `--search` or category-filtered `--list`, then
-use `--card <id> --style <key>` only for the selected card. Search uses
-whitespace-separated AND terms; retry a zero-result phrase with one or two
-discriminating terms. Never query merely to prove compliance or run an
-unfiltered `--list` during production.
-Do not load `references/shotcraft/catalog.json` or all card bodies into a stage
-context. The catalog excludes upstream TSX, demo media, audio, textures, and
-runtime assets; its entries are not verified HyperFrames components or
-Remotion/HyperFrames parity witnesses.
-
-## Cached production preflight
-
-Installation or upgrade performs deep environment inspection once and writes
-a machine-local readiness cache. Before Direction run the bundled lightweight
-preflight. After runtime planning, run it for only the required backends.
-Normal production dispatches no Onboarding Agent.
-
-The cache binds stable release, machine, Node, installed-Skill, and pinned-tool
-identities only. Production-run, SRT, project/output, runtime-plan, command
-`PATH`, disk-space, and Pexels changes never invalidate it. Per-run preflight
-checks readable input, unused writable output, storage, and requested cached
-backend readiness and returns compact JSON.
-
-Only `next: run-onboarding-diagnostic` launches one inspection-only Onboarding
-Agent scoped to failed stable facts. After grouped authorization, a fresh
-repair Agent applies approved reversible repairs and refreshes the cache.
-`fix-production-input` and `fix-project-runtime` stay with Parent. Pexels is checked by Assets only when
-a real Pexels material need exists.
-
-## Official CLI privacy and network
-
-Every stage follows [shared command execution](safe-execution.md) and consumes
-only its compact result. Executor success does not prove an official Skill load
-or replace command-result review.
-
-Official HyperFrames Skills check and update access the official GitHub Skill
-source. Treat that as declared network access. Skills check is part of
-inspection; Skills update remains an authorized repair.
-
-## Shared film logic
-
-Director, Lead, and Builder receive their short animation charter through
-generated `AGENTS.md`, `CLAUDE.md`, and an injected role prompt. They do not
-reopen the parent Skill, other stage Skills, generic craft references, schemas,
-validators, or catalogs to relearn it. The injected source-authoring anchor and
-compression recovery fields remain fixed. Motion is generated from meaning
-through attention, physical character, causal action, key states, element
-lifecycle, one primary focus, and settled readability before a runtime
-mechanism is chosen.
-
-Use parsed SRT integer milliseconds as the only time truth. Cover continuously
-from zero through the final cue end. Group cues into semantic shots when they
-express one idea; subtitle boundaries do not dictate shot count.
-
-For every shot, decide:
-
-- why it needs a visual and what the audience should understand;
-- which visual logic or deliberate stability fits the content;
-- how attention moves or settles;
-- what visible change, relationship, comparison, or result carries meaning;
-- what must remain readable;
-- the material's semantic and compositional role;
-- how the shot connects to its neighbors;
-- what selective screen copy is useful without reproducing subtitles.
-
-Let sections establish, question, compare, explain, escalate, resolve, return,
-or transition in the form the content needs. Let motifs develop and return with
-changed meaning. Shape density into rises, releases, and recovery moments.
-Avoid accidental repetition without breaking purposeful continuity.
-
-Treat suspicious names, versions, models, brands, and numerical claims as
-low-confidence until confirmed. Use safe generic wording and report the
-uncertainty rather than silently correcting it.
-
-Route primary material in this order:
-
-```text
-user material
-→ controllable generation
-→ Pexels
-→ HyperFrames-native structural support
-```
-
-Make photographic media participate in the composition. Native graphics may
-support typography, relationships, information graphics, emphasis,
-transitions, and local structure, but must not become the default primary
-material across an extended passage.
-
-Use project-local font files with source and license records. Plan title,
-interface, and body roles. Do not rely on remote or system fonts.
-
-Do not burn subtitles into the B-roll or add background music. Keep faceless
-output silent by default. In talking-head mode, preserve the agreed
-source-audio policy.
-
-## 1. Direction
-
-Dispatch a fresh Director Agent. It reads the actual inputs, understands the
-whole film, and writes:
-
-- `creative-brief.md`
-- `visual-direction.md`
-- `film-plan.md`
-- `shot-plan.md`
-- one schema-valid JSON object per shot under `shot-recipes/<shot-id>.json`
-- `motion-map.json`
-- `representative-scenes.json`
-- `material-requests.md`
-- `handoff.md`
-
-The Director completes content-specific visual and motion logic without the
-catalog. Only a justified query may add at most one primary `patternRef` with a
-resolvable card ID, style key, pinned upstream Git commit, semantic reason and
-fallback. No query and no `patternRef` is a complete valid result; do not write
-per-shot no-pattern decisions. Pattern selection never replaces the shot's
-content-specific visual logic.
-
-Every Recipe v3 records a primary focus for each beat, start/turn/result/hold
-states, each element group's destination, and one content-related reason for
-every required capability. `motion-map.json` maps every Recipe exactly once and
-contains only the compact relation/action/composition/entry/rhythm/settle facts
-Lead needs to detect repetition.
-
-The visual direction arises from the current content, audience, goal, and
-optional material. It is not selected from a bundled theme. The shot plan must
-prove continuous time coverage, semantic grouping, whole-film development,
-material intentions, typography roles, density variation, motif development,
-adjacent variation, and safe handling of uncertain terms. The Recipe set uses
-integer milliseconds, validates against the repository schema, maps one-to-one
-to the shot plan, and contains no runtime APIs or component syntax.
-
-## 2. Mandatory material collection
-
-Dispatch a fresh Assets and Pexels Agent on every production run. It must:
-
-1. inspect available user material;
-2. consider suitable controllable generation;
-3. perform real Pexels image and video searches;
-4. evaluate relevance and composition before selection;
-5. download every selected external item locally;
-6. bind every selected item to planned shots and a composition-use plan;
-7. source and freeze licensed project fonts.
-
-A real Pexels search may produce zero selected items. The Agent explains the
-search and rejections instead of forcing weak media. Selected media records its
-subject, focal point, crop, safe overlay area, brightness, color temperature,
-depth, movement, title relationship, source, creator, local path, and shot
-binding.
-
-For a selected pattern, Assets reads only that card and verifies its concrete
-material preconditions. Missing screenshots, UI states, paired states, layers,
-data, masks, or depth inputs invoke the declared fallback or return to the
-Director; they are not replaced with fabricated or unrelated media.
-
-When controllable generation is unavailable, record that fact and continue to
-Pexels. Do not impose a fixed search count, but preserve evidence of real image
-and video searches plus the selection or rejection reasoning.
-
-## 3. Runtime planning and targeted readiness
-
-The Parent first generates the production profile. The default command produces
-H.264 MP4 at 3840×2160, 30 fps, with no audio:
-
-```text
-node scripts/create-production-profile.mjs \
-  --output <broll-production/production-profile.json>
-```
-
-For an explicit vertical 25 fps request, use deterministic flags instead of
-writing JSON:
-
-```text
-node scripts/create-production-profile.mjs \
-  --output <broll-production/production-profile.json> \
-  --width 1080 --height 1920 --fps 25 \
-  --audio silent --master-format h264-mp4
-```
-
-Then the Parent runs:
-
-```text
-node scripts/plan-runtime.mjs \
-  --recipes <broll-production/01-director/shot-recipes> \
-  --selection <runtime-selection.json> \
-  --narrative-envelope <broll-production/01-director/narrative-envelope.json> \
-  --visual-system <broll-production/01-director/visual-system.json> \
-  --representative-scenes <broll-production/01-director/representative-scenes.json> \
-  --motion-map <broll-production/01-director/motion-map.json> \
-  --production-profile <broll-production/production-profile.json> \
-  --production-root <broll-production>
-```
-
-The script validates inputs, writes the immutable plan, and writes one minimal
-assignment packet per authoring unit. The profile identity binds raster, fps,
-audio policy, intermediate media, and final H.264 MP4 policy into the plan and
-every assignment. Do not redirect stdout into a plan, edit generated JSON, or
-dispatch `broll-runtime-plan`. Run targeted cached preflight
-only for the resulting `requiredBackends`; launch Onboarding only when that
-preflight reports a missing or changed backend fact.
-
-## 4. Unit building
-
-Dispatch each generated assignment packet to its named backend Builder.
-The assignment already injects the matching role prompt, a source-authoring
-anchor of at most eight lines, compression recovery fields, exact paths, and one
-standard command. A Lead also receives the whole-film compact motion map but
-only the three representative Recipes; a production Builder receives only its
-unit Recipes and seams.
-
-HyperFrames Builders use the release-pinned runtime. Remotion Builders keep
-source isolated but reuse the production-root toolchain for an identical
-dependency identity. Each Builder returns editable source and one direct
-runtime target per assigned `shotId`, plus a minimal exception-led handoff. It
-does not create capture, trace, lint, screenshot, frame-scan, render, hash,
-probe, decode, manifest, receipt, contract, or proof tooling and does not write
-those machine artifacts by hand.
-
-## 5. Parent direct shot render and checks
-
-After each assignment's source is ready, Parent runs the standard command for
-that assignment:
-
-```text
-node scripts/render-assigned-shots.mjs \
-  --plan <01-runtime-plan/runtime-plan.json> \
-  --assignment <01-runtime-plan/assignments/U001.json> \
-  --recipes <01-director/shot-recipes> \
-  --source-root <03-build/U001/source> \
-  --production-root <broll-production>
-```
-
-The script validates the plan, assignment, source closure, profile, Recipe, and
-runtime target; directly renders each assigned shot; runs FFprobe and complete
-decode; writes one `shot-media.json` per shot; and produces the semantic
-six-frame sheet at Recipe-derived opening, preparation, action-a, action-b,
-result, and settle/tail times. Only a concrete jump, occlusion, boundary,
-unsettled result, complex path/connector, or user requirement may add a short
-continuous diagnostic window. A normal shot never escalates to a full-frame
-sequence. Parent returns only `shotId + time/window + defect + evidence locator`
-for repair; a passing shot needs only a compact summary.
-
-Before assembly, Parent runs the bundled `validate-shot-media.mjs` contract on
-every generated shot record. Missing, duplicate, undecodable, identity-drifted,
-or out-of-order shot media closes the gate instead of being silently repaired by
-cutting a unit or Master.
-
-## 6. Preview and default delivery
-
-Once every shot contract passes, Parent assembles the complete low-cost preview
-only from those verified shot files:
-
-```text
-node scripts/assemble-shot-preview.mjs \
-  --plan <01-runtime-plan/runtime-plan.json> \
-  --recipes <01-director/shot-recipes> \
-  --source-manifest <03-build/U001/source-manifest.json> \
-  --source-manifest <03-build/U002/source-manifest.json> \
-  --production-root <broll-production> \
-  --output <05-delivery/preview.mp4>
-```
-
-`delivery-index.json` is the order truth. Shot count, Recipe count, integer
-millisecond windows, local frame mapping, source/Recipe/profile identities,
-codec, decode, and continuous SRT coverage must close before preview assembly.
-The Director does not watch the complete dynamic preview or write a full-film
-witness. The user judges aesthetics using the three representative scenes,
-per-shot six-frame sheets, and complete preview.
-
-After approval, the ordered high-quality shot directory is the default formal
-delivery. A full-length master is optional and must be assembled from the same
-unchanged verified shots to a new path. Technical verification proves media
-behavior, not visual taste.
-
-## 7. Legacy shot export
-
-`broll-shot-export` is not part of new production. Use it only after an explicit
-request to recover shot files from a verified master created by a legacy run.
-Its outputs are labeled master-derived and must never be presented as
-`direct-runtime-render` shot-native delivery.

package/skills/erduo-broll-loop-engineering/references/remotion-backend.md

@@ -1,334 +0,0 @@
-# Remotion production backend
-
-This is the Parent/tooling reference for an assignment routed to `remotion`.
-It is not a default Builder reread: the generated assignment carries exact
-runtime facts, commands, and at most two selected references. Parent owns
-dependency preparation, typecheck, bundle reuse, direct shot rendering,
-six-frame checks, media contracts, preview assembly, and optional Master
-delivery. No Integrator or Render Agent is authorized.
-
-The v1.0.1 Remotion route is a release-candidate existing-project adapter. A
-real Composition canary covers typecheck, CLI render, FFprobe/full decode, shot
-contract, and preview assembly. The same `179.866` second SRT forced entirely
-through Remotion has not completed, so this document does not claim equal
-production evidence, performance, or stability with HyperFrames.
-
-## Provenance and scope
-
-The backend design is informed by the pinned Apache-2.0
-`Vincentwei1021/video-shotcraft` source at Git commit
-`41ee360d82f4c491ba9d88a24a4add7d8ff1cf8b`. Its useful production ideas are
-native Remotion compositions, frame-owned state, runtime geometry inspection,
-ordered `Sequence` assembly, and render verification. This repository's stage
-contracts and verifier are original. Imported reference TSX remains under
-`references/shotcraft/remotion-sources/` with its own manifest, provenance,
-and license notice.
-
-The imported TSX is auditable reference source, not an installed component
-library. Never import production code from the installed Skill directory.
-For a selected card, query the card first and use only its returned
-`remotionSources` under either `demos/` or `template/src/`, plus required
-shared fixtures. Adapt the motion grammar to
-the actual Shot Recipe, frozen assets, typography, dimensions, and timing.
-Normalize query results beginning with `remotion-sources/` to the full
-Skill-root-relative `references/shotcraft/remotion-sources/...` form before
-recording manifest `referenceFiles`.
-If substantial upstream code is retained, preserve an Apache-2.0 notice in
-the generated source and record the exact upstream paths in build notes.
-
-The imported reference set contains no image, video, audio, or font payloads.
-Replace external-media imports with Assets-stage files. A missing demo is not
-a blocker: implement the Recipe's declared fallback from first principles and
-record why the fallback was used. Never describe a card or demo as a ready
-production component.
-
-## Project-resolved runtime version
-
-Use an existing project-local exact package/lock closure or the release-candidate
-baseline prepared by Parent inside the production directory. Do not install
-packages into the Skill repository or a global prefix. Use Node.js 22 or newer.
-This release deliberately does not pin one global Remotion version.
-
-Every production project still has to be reproducible:
-
-- `remotion` and `@remotion/cli` must be exact semver declarations at the same
-  concrete version;
-- `react` and `react-dom` must also use the same exact version;
-- `@types/react`, `typescript`, and every additional dependency must be exact;
-- `package-lock.json` v3 must close over those declarations using only npm
-  registry HTTPS tarballs with integrity values;
-- the installed packages and project-local `remotion versions` probe exposed
-  through its shared-toolchain link must
-  report the same version recorded in `remotion-project.json`.
-
-For an existing project, preserve its compatible exact lock after the local
-CLI and required feature canaries pass. For a genuinely new project, the
-authorized Onboarding repair Agent reads current stable registry metadata,
-selects one concrete Remotion version for which the same
-`@remotion/cli` version exists, resolves compatible exact React and TypeScript
-packages, records the resolution time and package metadata, and then writes
-the exact project declarations and lock. Never put `latest`, a caret, a tilde,
-or a range into a production project. Never let `npx` choose or download a
-runtime during Build or frozen-unit rendering.
-
-Before installing or invoking Remotion, show the user the official
-[Remotion licensing page](https://www.remotion.dev/docs/licensing) and record
-their confirmation that the intended use is covered. Do not infer commercial
-license eligibility from this Skill or from successful package installation.
-
-Add another package only when the selected native implementation needs it.
-Pin it exactly, resolve it through `https://registry.npmjs.org/`, review its
-license, and record the reason and license in build notes. Generate the lock
-before preparation and inspect it for non-registry sources. Run only binaries
-through the unit's `node_modules` link and checked-in Node entry points;
-do not let a command silently download a different CLI. `package.json` scripts
-may expose the same exact commands for user convenience, but production stages
-must invoke the local Node entry points directly.
-
-## Shared dependency toolchain
-
-Source isolation does not require dependency duplication. Parent runs the
-bundled preparer once for each distinct dependency identity, before creative
-work calls the assignment's standard command:
-
-```text
-node scripts/remotion-toolchain.mjs prepare \
-  --project <unit-project> \
-  --production-root <broll-production> \
-  --receipt <parent-evidence/toolchain.json>
-```
-
-The script derives an identity from the exact dependency declarations, full
-lock closure, Node major, platform, and architecture. The first caller installs
-that identity under `.remotion-toolchains/`; later matching callers reuse it
-and receive a project-root `node_modules` link. A different exact closure gets
-another toolchain. Never run private per-unit `npm ci`, copy `node_modules`, or
-delete an existing private dependency tree automatically; stop and migrate it
-explicitly. The dependency link is the only permitted project symlink and the
-verifier continues to exclude dependency bytes from production identity.
-
-Parent wraps every install, typecheck, browser geometry trace, diagnostic
-render, and direct-shot render:
-
-```text
-node scripts/remotion-toolchain.mjs run-heavy \
-  --production-root <broll-production> \
-  --cwd <unit-project> -- \
-  <direct executable> [arguments...]
-```
-
-The fixed two-slot queue prevents an arbitrary number of Builders from running
-heavy local processes together. Source authoring does not use this queue. Do
-not add automatic CPU/memory tuning; the bounded queue is the complete resource
-rule. A shared npm cache may reduce downloads, but it is not dependency reuse
-and never substitutes for the Parent-generated shared toolchain receipt.
-
-Every command follows [shared command execution](safe-execution.md) and consumes
-only its compact result.
-
-## HTML-in-canvas capability
-
-`effects.dom-pixel-postprocess` is a native Remotion capability for capturing
-a live deterministic DOM subtree into `<HtmlInCanvas>` and post-processing it
-with Canvas 2D or WebGL2. It is an implementation capability inside a Remotion
-shot, not a new runtime and not a bridge to HyperFrames.
-
-Version numbers alone do not prove this experimental browser capability. The
-cached readiness plus the capability-specific preflight must bind the exact local Remotion version,
-browser, and render backend, and must include a real project-local still
-canary whose source imports and mounts `<HtmlInCanvas>`. Require Remotion
-`4.0.455` or newer, confirm `HtmlInCanvas.isSupported()` in the preview
-browser, and render the canary through the same local CLI used for production.
-The current Studio preview floor is Chrome 149 with
-`chrome://flags/#canvas-draw-element` enabled; record the exact browser fact
-rather than assuming a future browser keeps the same experimental API.
-
-The initial production contract supports only:
-
-- `canvas-2d`, using `drawElementImage()` in `onPaint`;
-- `webgl2`, initializing and cleaning GPU resources through `onInit` and
-  drawing the current `elementImage` in `onPaint`;
-- one non-nested capture layer at any point in the rendered component tree;
-- frame-derived effect parameters from `useCurrentFrame()` and the canonical
-  fps, with a real readable hold after any readability-reducing distortion.
-
-WebGPU, nested `<HtmlInCanvas>`, undocumented crop APIs, direct browser API
-use, ambient animation loops, and silent visual fallbacks are outside this
-contract. A failed support check or still canary is `unsupported` for this
-capability, not permission to weaken the Recipe or switch backend.
-
-For WebGL2, freeze either `angle` or `swangle` in the source-identity-bound
-`remotion.config.ts` through
-`Config.setChromiumOpenGlRenderer()`. Use `angle` when the verified render host
-has the required GPU path and `swangle` for a verified software path. Builder
-capture, diagnostics, and frozen-unit render must use the same value.
-
-When this capability appears in any shot, `remotion-project.json` must declare:
-
-```json
-{
-  "runtimeFeatures": {
-    "htmlInCanvas": {
-      "paintBackends": ["canvas-2d"],
-      "nested": false,
-      "chromiumOpenGlRenderer": "browser-default"
-    }
-  }
-}
-```
-
-For WebGL2, use `"paintBackends": ["webgl2"]` or list both actually used
-backends, and set `chromiumOpenGlRenderer` to the frozen `angle` or `swangle`
-value. The verifier rejects a capability/manifest mismatch, an unsupported
-backend, an older Remotion version, missing component/context evidence, or a
-missing GL configuration.
-
-## Canonical frame mapping
-
-The SRT-bound Shot Recipe remains the time truth. At integer `fps`, map every
-absolute millisecond boundary independently with exact half-up rounding:
-
-```text
-frame(ms) = floor((ms * fps + 500) / 1000)
-```
-
-For a shot `[startMs, endMs)`, use:
-
-```text
-startFrame       = frame(startMs)
-endFrame         = frame(endMs)
-durationInFrames = endFrame - startFrame
-sequenceFrom     = startFrame - compositionStartFrame
-```
-
-Use the same conversion for phases and readable holds. Never accumulate
-rounded durations, because that introduces drift. Reject a mapping with a
-non-positive frame duration. At a shared millisecond boundary, the previous
-exclusive `endFrame` must equal the next inclusive `startFrame`; therefore
-adjacent shots have no frame gap or overlap. Record both source milliseconds
-and mapped frames in `remotion-project.json`.
-
-The resulting media duration is the integer-frame representation of the SRT
-end, not a claim that arbitrary milliseconds divide evenly by the frame rate.
-Record boundary quantization in technical verification.
-
-## Project and manifest contract
-
-Each runnable authoring-unit project contains:
-
-- `src/index.ts`, which calls `registerRoot`;
-- `src/Root.tsx`, which registers exactly the declared `Composition`;
-- frame-driven shot source under `src/`;
-- project-local frozen assets under `public/` when needed;
-- `package.json`, `package-lock.json`, and `tsconfig.json`;
-- `remotion-project.json`, conforming to
-  `references/runtime/remotion-project.schema.json`.
-
-List every production input in the manifest's `files` array with a SHA-256.
-The verifier rejects omitted project files, symlinks, path traversal, hash
-mismatches, range dependency versions, non-npm registry lock sources, invalid
-frame mapping, and known ambient-time or CSS-time APIs.
-
-Run from the installed parent Skill root:
-
-```text
-node scripts/remotion-verify.mjs \
-  --project <project-directory> \
-  --manifest <project-directory>/remotion-project.json \
-  --expect block \
-  --json
-```
-
-Parent binds the source manifest and every recorded production file to the
-unit source identity before direct shot rendering. Builder does not hand-write
-the manifest, identity, receipt, or media contract.
-The verifier ignores only root `.git/` and root `node_modules/`; every other
-file under `project/` must appear in the manifest and identity. Put caches,
-stills, logs, and rendered outputs in sibling evidence directories
-outside `project/`, where they never enter the identity.
-
-The schema still reads legacy `kind: master`, `--expect master`,
-`--write-identity`, and `--identity` records so a pre-v0.9 task can be audited.
-Do not use those legacy modes to start or continue a new v0.9 production.
-
-## Deterministic source rules
-
-Reconstruct every visual state from the requested frame. Use
-`useCurrentFrame()`, `interpolate()`, `spring()`, `Sequence`, deterministic
-closed-form math, and fixed-seed helpers. Keep phase and readable-hold
-boundaries derived from the canonical absolute mapping.
-
-Do not use `Date`, `Math.random`, Web Crypto randomness, timers,
-`requestAnimationFrame`, ambient React state/effects, network requests during
-render, CSS `animation`/`transition`, or environment-dependent behavior.
-Precompute remote or asynchronous facts before build and freeze the results as
-licensed local inputs. Media and fonts must resolve from project-local files.
-When source declares a font family, place every font under `public/`, list it
-with role `font`, load it explicitly with `@font-face`, `FontFace`, or a
-deterministic local loader, and use only that declared family. Generic or host
-system fallbacks such as `sans-serif`, `system-ui`, or `-apple-system` are not
-reproducible evidence and are rejected by the verifier. Font shorthand is also
-rejected: declare `fontFamily` or `font-family` explicitly so the local family
-binding can be inspected.
-
-## Executable gates
-
-The Builder authors only its assigned source and runs the exact standard check
-from its assignment. The Parent owns shared-toolchain preparation, one
-project-local TypeScript check, one bundle, direct rendering of every assigned
-Composition ID, Recipe-bound geometry samples, bounded diagnostic windows,
-FFprobe, complete decode, source identity, SHA-256, and one schema-valid
-`shot-media.json` per Recipe. A stable resolved hold is legal and never needs
-invented movement merely to satisfy the lint.
-
-The standard command samples opening, preparation, action-a, action-b, result,
-and settle/tail from Recipe beats and holds. Only a concrete jump, collision,
-occlusion, boundary, unsettled result, or complex path/connector may add a
-bounded diagnostic window. A normal shot never receives a full-frame scan.
-Parent returns only `shotId + time/window + defect + evidence locator`; a pass
-returns one compact summary. Builder does not create or hand-write capture,
-trace, lint, render, hash, probe, decode, manifest, receipt, contract, or proof
-tooling/artifacts.
-
-After every shot passes, the Parent runs `scripts/assemble-shot-preview.mjs`
-with the runtime plan, Recipe directory, verified source manifests, production
-root, and a new output path. `delivery-index.json` is the only assembly-order
-truth. The complete preview is built only from those verified shot files; the
-ordered shot directory is the default formal delivery and a full-length master
-is optional. No Integrator or Render Agent is dispatched.
-
-Parent tooling follows `references/motion-layout-lint.md` for the shared trace
-contract and limits; it is not a default Builder reread. Static source regex cannot establish geometry or easing quality. A
-passing trace suppresses AI frame inspection; findings alone trigger bounded
-diagnostic renders. Code cannot prove perceived weight, meaningful arcs,
-exaggeration, appeal, or story clarity. Representative moving scenes provide
-the early visual-lock decision and the complete moving preview provides the
-final aesthetic decision. There is no default full-film Director video witness.
-
-Invoke `node node_modules/@remotion/cli/remotion-cli.js` with the manifest's
-entry point and each shot Composition ID explicitly for diagnostic stills and each
-direct shot render.
-Never infer a composition ID from file names, use
-`latest`, overwrite an output, treat an exit code alone as evidence, or claim
-visual parity with HyperFrames.
-
-For a faceless or otherwise silent audio policy, pass `--muted` explicitly to
-every diagnostic clip and direct shot render. Do not infer silence from the absence of an
-`Audio` component: Remotion may otherwise emit a near-silent audio stream and
-extend the container beyond the exact frame duration. Verify zero audio
-streams and `durationInFrames / fps` container duration with FFprobe.
-
-## Backend boundary
-
-Remotion and HyperFrames share the Director Recipe, selected pattern intent,
-and frozen Assets handoff. They do not share runtime source. A production run
-uses a validated post-Director runtime plan before build, and every later
-handoff preserves its authoring-unit and shot bindings. The authoring unit is a
-work packet, not a media boundary. Every route exchanges only schema-valid shot
-media at the Parent's assembly boundary. A selected-backend failure returns to
-that backend for repair; do not silently convert it to the other runtime or
-pre-render it merely to disguise a reroute.
-
-Legacy Integrator, Studio-approval, and Render records remain readable only for
-explicit pre-v0.9 recovery. Their stage Skills return read-only recovery
-reports and must not be dispatched for a new production.