@autoaiai/aicut 0.1.11 → 0.1.13

package/skills/erduo-broll-loop-engineering/references/first-run-onboarding.md

@@ -1,107 +0,0 @@
-# First-run and changed-environment onboarding
-
-Use this reference only after `production-preflight.mjs` returns
-`next: run-onboarding-diagnostic`. Normal video production does not dispatch an
-Onboarding Agent.
-
-## Two layers
-
-Installation readiness is machine state. Production readiness is run state.
-Do not bind them together.
-
-The installation/upgrade workflow performs the expensive checks once and
-writes `environment-readiness.json` in the application-owned data directory.
-The cache records only stable facts:
-
-- product version and cache schema;
-- platform, architecture, and a non-secret host identifier;
-- Node major and minimum support result;
-- expected release Skill count and installation-manifest identity;
-- FFmpeg and FFprobe execution results;
-- pinned HyperFrames runtime/official-Skills identities and doctor readiness;
-- backends whose toolchains have real readiness evidence;
-- creation time.
-
-Never bind this cache to a production-run ID, SRT, project or output path,
-runtime-plan identity, command `PATH`, disk free-space value, or Pexels state.
-Those facts vary normally and must not trigger another deep environment audit.
-
-## Production preflight
-
-Before Direction, Parent runs:
-
-```text
-node <release-root>/scripts/production-preflight.mjs \
-  --srt <srt> --output <target> --project <project-root> --json
-```
-
-It performs bounded local checks only:
-
-- readiness cache exists and matches current release/machine/tool identity;
-- current Node remains supported;
-- SRT is a readable regular file;
-- project root exists;
-- output target is unused and its existing parent is writable;
-- available space exceeds a small declared floor.
-
-After the deterministic runtime plan is written, add `--runtime hyperframes`
-and/or `--runtime remotion` for each required backend. A runtime-plan or SRT change
-does not invalidate the cache; it merely selects which cached backend fact is
-needed.
-
-The JSON result has three routing outcomes:
-
-- `status: ready`, `next: continue`: proceed without Onboarding;
-- `next: fix-production-input`: resolve SRT/output/project facts without an
-  environment Agent;
-- `next: fix-project-runtime`: repair the exact project-local Remotion
-  declaration, lock, installation, or CLI identity without Onboarding;
-- `next: run-onboarding-diagnostic`: dispatch one Onboarding Agent scoped to
-  the returned stable fact IDs.
-
-Do not ask an Agent to reread raw command output. The script result is the
-handoff.
-
-## When diagnosis is justified
-
-Run deep diagnosis only for a missing cache, release upgrade/migration,
-machine or architecture change, Node major/support change, install-manifest or
-Skill-set change, pinned tool identity change, a required backend absent from
-the cache, or a real production command failure that identifies an environment
-dependency.
-
-Inspection is read-only and checks only the failed facts. One grouped request
-contains all known repairs and human-only actions. A fresh repair Agent applies
-only explicitly authorized reversible changes and refreshes the cache with:
-
-```text
-node <release-root>/scripts/doctor.mjs --refresh-cache --json
-```
-
-For HyperFrames, the diagnostic loads pinned official Skills and runs the
-official JSON doctor. For Remotion, it verifies exact local dependencies and
-the direct project-local CLI. Optional feature canaries are run only when a
-planned Recipe actually requests that capability.
-
-## Pexels
-
-Pexels is material routing, not environment readiness. Do not read, validate,
-or cache its credential during onboarding or common production preflight.
-When Assets reaches a real Pexels-backed need, that stage checks secure access
-and asks once for a human action if unavailable. No need means no credential
-check.
-
-Never expose the credential in chat, Markdown, logs, file paths, command
-arguments, artifacts, or reports.
-
-## Execution boundary
-
-All commands follow [shared command execution](safe-execution.md). Stages
-consume its compact result and do not duplicate implementation details.
-
-## Handoff
-
-The exception-path handoff contains failed fact IDs, diagnostic scope, compact
-results, repairs proposed/performed, remaining human action, cache refresh
-status, and final status. It excludes production-run bindings, SRT duration,
-output details, Pexels status, full environment dumps, and unrelated software.

package/skills/erduo-broll-loop-engineering/references/handoff-template.md

@@ -1,70 +0,0 @@
-# Compact Agent handoff and Parent script receipt
-
-Use file locators instead of copying plans, JSON, source, logs, screenshots, or
-media facts into prose. Successful defaults need no narration. Keep the handoff
-short enough to scan. Creative Agents do not hand-write receipts, manifests,
-hashes, probes, decode results, media contracts, or proof; Parent scripts own
-those machine artifacts.
-
-```markdown
-# <stage> handoff
-
-- status: complete | action-required | unsupported | blocked
-- owner: <stage>
-- scope: <run, block, or authoring-unit ID and exact ms range>
-- identity: <runtime-selection/runtime-plan/composition aggregate as relevant>
-- artifacts: <primary editable-source or direction locators>
-- standard-command: <exact Parent-owned command or compact result locator>
-- exceptions: none | <only unresolved facts and owning stage>
-- next: <one stage or user preview decision>
-```
-
-## Stage-specific minimums
-
-- **Onboarding:** phase, required backends, bound environment identity, exact
-  version/readiness facts, recorded Pexels state, repairs/human actions, and no
-  secret values. Missing Pexels is `action-required` only for a plan-required
-  Pexels route.
-- **Director:** narrative-envelope, visual-system, shot-plan, Recipe directory,
-  motion-map, representative-scenes, standard validator result, actual material
-  needs/no-need set, and unresolved factual terms.
-  Do not repeat the shared system or catalog bodies.
-- **Parent planning script:** generated plan identity, assignment packet
-  locators, ordered blocks/authoring units, required backends, warnings, and
-  unverified preferences. This is a script receipt, not an Agent handoff.
-- **Assets:** selected inventory/font/provenance locators, actual acquisition
-  routes, asset-fusion bindings, and conditional Pexels facts. When no request
-  reached Pexels, say `pexels: not-invoked (no need)` once.
-- **Lead Builder:** role/phase, three representative Recipe/source locators,
-  runtime-native shared primitive locator, asset/font subset, exact standard
-  command, and only real unresolved issues. Parent creates source identity,
-  rendered media, checks, and visual-lock inputs. Do not include unrelated
-  Recipes or the full film plan beyond `motion-map.json`.
-- **Production Builder:** authoring-unit ID, assigned Recipe/source/direct-render
-  target locators, shared-system locator, selected 0–2 references,
-  material/font bindings, seams, dependency identity when Remotion, exact
-  standard command, and real unresolved issues. Do not include Agent-authored
-  receipt, manifest, hash, probe, decode, media contract, or proof.
-- **Parent direct-shot script:** ordered shot/media-contract locators,
-  six-frame sheet and bounded-failure locators, source/Recipe/profile identities,
-  FFprobe/full-decode facts, and `delivery-index.json`. This is a script receipt,
-  not an Agent handoff.
-- **Parent preview/delivery script:** verified shot closure, preview locator,
-  approval state, default ordered shot-directory locator, and optional unused
-  Master target/facts. A Master is not required for normal delivery.
-- **Visual lock:** three representative selections/reasons, runtime-specific
-  moving-scene and shared-source identities, bound assets/fonts, concrete
-  Director witness, user status (`approved` or explicit `skipped`), skip risk
-  when applicable, validator result, and next production packets.
-- **Legacy Planner/Integrator/Render:** only when the user explicitly asks to
-  inspect or recover a pre-v0.9 task, report the last trustworthy identity,
-  available artifact locators, concrete mismatch, and safest next owner. Do
-  not create new production artifacts or continue the legacy chain.
-- **Legacy Shot Export:** source Master identity, requested windows, explicitly
-  master-derived outputs, FFprobe, and decode facts. Never label them
-  `direct-runtime-render`.
-
-Never include credentials, command arguments containing secrets, full
-environment dumps, home-directory prefixes, raw SRT text not needed for
-identification, complete source, long logs, craft scores, aesthetic checklist
-claims, or assertions that technical checks prove visual quality.

package/skills/erduo-broll-loop-engineering/references/motion-layout-lint.md

@@ -1,122 +0,0 @@
-# Motion and layout lint
-
-Use this reference only in a backend Builder. It replaces routine
-AI inspection of repeated stills. Representative moving scenes provide the
-early visual-lock decision; the identity-bound complete preview provides the
-final human aesthetic decision.
-
-## What the lint can establish
-
-`scripts/motion-layout-lint.mjs` consumes runtime-captured element geometry.
-The normal first pass samples Recipe beat boundaries, readable holds, scene
-cuts, and only the mechanism-specific points needed to prove the declared
-change. It can report:
-
-- discontinuous position, scale, size, or opacity changes;
-- hard transition edges, abrupt acceleration changes, failure to settle, and
-  excessive direction reversals;
-- declared readable holds that are too short or still moving;
-- most elements starting together or too many independent focus groups moving
-  at once;
-- focus-bearing elements outside the shared safe area;
-- wholly off-canvas visible elements and strong unplanned overlap between
-  independent groups;
-- when supplied the validated Shot Recipe directory, whether every planned
-  non-still beat is bound to a non-decorative rendered action and produces an
-  actual rendered geometry, visibility, or captured appearance change;
-- for a Recipe selecting a `diagram-*` craft entry, whether every readable
-  hold includes actual rendered node/connector/connector-label geometry, and
-  whether labels touch paths or nodes, connectors cross unrelated nodes, two
-  connectors share a path, or diagram geometry leaves the canvas.
-
-These are code-checkable projections of slow in/slow out, timing, follow
-through, staging, and readable composition. They are risk signals, not a
-Disney-principle score.
-
-The lint cannot prove anticipation communicates the right idea, perceived
-mass, pleasing arcs, meaningful exaggeration, story clarity, or appeal. The
-user decides those properties from one final moving preview.
-
-## Instrument the actual runtime
-
-Do not manufacture the trace from Recipe prose, keyframe declarations, CSS
-source, or hand-authored estimates. Instrument the rendered composition:
-
-1. mark only meaningful visible elements with stable IDs, one role, one focus
-   group, safe-area policy, optional allowed overlaps, and finite motion
-   windows;
-2. seek the real runtime first to Recipe beat boundaries, readable holds, scene
-   cuts, and the smallest additional samples required by the mechanism;
-3. after layout and paint settle for that requested frame, capture each marked
-   element's canvas-space rectangle and effective opacity;
-4. when geometry cannot express a material-state or attention change, capture
-   a SHA-256 of computed visible styling such as fill, stroke, color, filter,
-   clip, or path state; exclude text content and hand-authored evidence labels;
-5. bind the trace to the exact Builder unit source identity and validate it
-   against `references/runtime/motion-layout-trace.schema.json`;
-6. run `motion-layout-lint.mjs --trace <trace> --recipes <assigned-recipes>` and
-   preserve its compact JSON result outside production source.
-
-When the Recipe's primary craft ID begins with `diagram-`, use trace schema
-`1.1.0` and add one `diagramFrames` entry inside every readable hold. Capture
-node rectangles, connector polylines, and connector-label rectangles from the
-same rendered DOM or scene at that exact frame. Connector labels are separate
-from labels intentionally contained inside nodes. The check rejects contact
-or collision only; it does not prescribe diagonal versus orthogonal lines,
-node shapes, spacing grids, palette, number of nodes, or a house style.
-
-The Recipe directory is mandatory for a Builder pass. The lint maps each
-Recipe beat into its rendered shot window. A non-still beat passes only when a
-primary, secondary, text, or structural element explicitly binds its motion to
-that beat and the captured runtime state actually changes. A progressive
-continuous subject action may fulfill a beat when its end state advances;
-ambient, looping, unbound, or decorative motion cannot. An explicit
-`deliberate-stillness` beat needs no fabricated movement.
-
-Once a non-still beat produces its bound, non-decorative state change, the
-resolved state may remain still for settling or reading. Unchanged duration is
-not a defect and must never trigger dense capture or a request for more motion.
-The lint checks whether the declared change happened, not whether the screen
-keeps changing.
-
-For Remotion, capture DOM geometry from the project-local rendered
-Composition. `getBoundingClientRect()` is acceptable only after the exact
-frame has rendered; normalize transforms into the returned canvas-space box.
-For Canvas/WebGL content, expose scene-owned semantic bounds rather than the
-single canvas rectangle.
-
-For HyperFrames, use rendered DOM geometry when the selected official adapter
-exposes the elements. For Canvas, SVG abstraction, or Three/WebGPU content,
-export semantic scene bounds from the same deterministic frame function. If
-the current official runtime has no truthful geometry hook for an element,
-record it as unmeasured; do not infer it with source regex or claim full lint
-coverage. Standard runtime checks and the final moving preview remain valid,
-but they do not turn the missing geometry into a pass.
-
-## Handle findings
-
-`status: pass` with Recipe evidence requires no still, clip, AI visual analysis,
-or prose QA report.
-Store the one-line result locator in the compact receipt.
-
-`status: attention` returns `diagnosticWindows`. Render only those bounded
-frames or short clips, escalate only those windows to dense or per-frame trace
-when necessary, repair the owning source, recapture the affected trace,
-and rerun the lint. Do not sample unrelated frames. An intentional exception
-must name the finding code, affected element, exact reason, and bounded window;
-never waive an error by calling it aesthetic.
-
-Run the sampled lint once for each Builder assignment before accepting its
-media. Exact connector/path evidence, complex Canvas/WebGL, or an explicit user
-requirement may begin with dense capture. Do not rerun
-an unchanged passing unit trace during Parent assembly or delivery; source and
-media identity comparison is enough. Cross-unit rhythm and seams remain visible
-in the one complete moving preview rather than being claimed by a source lint.
-
-No passing path generates an all-frame PNG sequence. This check rejects a paper
-plan whose declared non-still beat produces no rendered subject change. It does
-not punish a stable result, readable hold, or settled tail, and it never asks a
-Builder to add ambient or continuous movement. It does not prove that a metaphor is
-understandable, a diagram is the right explanation, a rhythm feels right, or
-an animation is beautiful; those remain creative judgments in the final moving
-preview.

package/skills/erduo-broll-loop-engineering/references/parent-review-checklist.md

@@ -1,171 +0,0 @@
-# Parent bounded review
-
-Start from the compact receipt/handoff. Inspect an actual artifact only to
-answer a concrete contract or technical question. The Parent does not perform
-an independent aesthetic review, commission a review Agent, assign craft
-scores, or require extra screenshot evidence. Visual taste has two user gates:
-the three representative scenes for direction and the complete shot-assembled
-preview for the film as a whole.
-
-## Goal and environment
-
-- Output directory and shot/preview/optional-master targets are new and
-  non-overwriting.
-- Runtime selection is validated; new projects default to `auto` and ambiguous
-  existing evidence stops.
-- Cached installation readiness matches this release and host; the lightweight
-  preflight closes the current SRT, project, target and required backend facts.
-- Pexels remains outside readiness and is checked only when Assets reaches a
-  validated Pexels material need.
-- Required official HyperFrames Skills/doctor or exact local Remotion
-  dependencies/CLI evidence is real; FFmpeg, FFprobe, storage, permissions, and
-  paths are usable.
-- Commands used the shared executor and no credential or environment dump
-  appears.
-
-## Direction contracts
-
-- Integer SRT milliseconds cover zero through final cue end continuously and
-  every cue belongs to one semantic shot.
-- `narrative-envelope.json` stores whole-film proposition, sections, context,
-  and terminology once.
-- `visual-system.json` stores the concrete visual world, palette/typography
-  roles, materials/depth, motif semantics, rhythm, safe-area policy, lazy
-  defaults to avoid, and at least three content-appropriate composition
-  families once.
-- Recipe v3 files are schema-valid compact shot deltas: beat-level primary
-  focus, start/turn/result/hold key states, element lifecycles, composition
-  family, hero-frame relationship, visible `microBeats[]`, shot-specific
-  material need, one content-related reason for every required capability,
-  optional locators, neighbor handoff, and readable hold. They do not repeat
-  global rules or contain runtime APIs.
-- A micro-beat changes subject, topology, scale, depth, material state,
-  relationship, or attention; deliberate stillness is explicit. Beat-count
-  heuristics are not a pass/fail score.
-- Every shot records a concrete first-read anchor, visible action, and readable
-  result. A shot normally spans about 5–12 seconds; one over 15 seconds has a
-  content-driven `durationRationale` and real visible development.
-- `representative-scenes.json` names exactly three distinct Recipe shots with
-  `opening`, `information-dense`, and `late` coverage and concerns that
-  collectively test composition, text, material, and motion.
-- `motion-map.json` maps every Recipe once and keeps only content relation,
-  primary action, composition family, entry family, rhythm, and settle time.
-  The three representative shots cover three distinct relations, compositions,
-  and rhythms rather than one template with changed copy.
-- Shotcraft may be unused across the whole film. When a named technique
-  question justified a query, that shot has at most one pattern and its locator
-  resolves progressively; no per-shot no-pattern record is required. Craft
-  never supplies runtime routing evidence.
-- Uncertain facts use safe wording; no copied third-party code, prompt,
-  example, media, or wording enters the artifacts.
-
-## Runtime plan and assignments
-
-- The Parent generated `production-profile.json` with
-  `create-production-profile.mjs`; it did not hand-write output policy JSON.
-- The Parent ran `plan-runtime.mjs` directly with Recipes, selection, narrative
-  envelope, visual system, the three-shot `--representative-scenes` artifact,
-  `--motion-map`,
-  `--production-profile`, and an unused production
-  root. No Runtime Planner Agent was dispatched.
-- The plan and every Builder assignment carry the generated profile's same hash
-  identity.
-- Generated plan and assignment JSON pass bundled validation and were not
-  hand-edited or created by redirecting stdout.
-- Every shot appears exactly once in one backend block and one authoring unit.
-- Blocks remain contiguous runtime/integration boundaries.
-- Authoring units remain inside one block, contain whole adjacent shots,
-  commonly group 5–8 ordinary short shots, and form a closed ordered partition.
-  An ordinary single-backend film around 180 seconds targets 2–3 production
-  Builders, while backend, complexity, exclusive-state, and
-  `authoring.continuityGroup` constraints override the target. No unit crosses a
-  backend or non-contiguous time, no shot crosses units, and no live transition
-  is split merely to hit a count.
-- Decisions cite capability or exact backend evidence, never semantic keywords
-  or craft choice. Unverified Remotion preferences remain marked unverified.
-
-## Conditional Assets
-
-- The Assets stage inspected supplied material and closed project-local fonts,
-  licenses, hashes, and provenance even when external acquisition was unused.
-- Empty/native-MG material needs produced a compact no-search decision; they
-  did not invoke generation or Pexels.
-- Non-empty needs followed only suitable routes: user material, authorized
-  controllable generation, Pexels for suitable stock, then runtime-native
-  structural support. Fact/brand/logo/web/UI needs used an appropriate factual
-  source rather than stock substitution.
-- Any Pexels search was real, credential-scoped, need-bound, and preserved
-  selection/rejection facts. A missing key blocked only a Pexels-routed need.
-- Every selected file exists locally and records source, rights, objective
-  media facts, shot binding, focal/crop/safe regions, and an asset-fusion plan.
-
-## Each focused Builder
-
-- Each required backend's Lead packet passed the deterministic assignment gate,
-  built only its assigned representative Recipes, and returned moving scenes
-  plus directly importable runtime-native shared source and identity.
-- `04-visual-lock/visual-lock.json` binds the three scenes, representative
-  reasons, source identities, assets/fonts, and the user's approved or explicit
-  skipped decision. Every production packet passed the gate against that
-  unchanged contract; no full-film Director witness is required.
-- Hybrid shares only runtime-neutral visual tokens. HyperFrames and Remotion
-  have separate source locators and identities.
-
-- The assignment injects the matching generated role charter, a source-authoring
-  anchor of at most eight lines, and fixed compression recovery fields. The
-  Agent did not reread parent/other stage Skills, generic craft references,
-  schemas, validators, or catalogs.
-- The fresh Agent owns one validated authoring unit only and read only its unit
-  Recipes, immediate seam summaries, shared narrative/visual-system locators,
-  frozen assets/fonts, and 0–2 selected references.
-- It did not load all film Recipes, full catalogs, or unrelated references.
-- The Agent did not create capture, trace, lint, screenshot, frame-scan,
-  render, hash, probe, decode, manifest, contract, receipt, or proof tooling.
-  It ran only the assignment's standard command and repaired only its concrete
-  shot/window findings.
-- The maximum visible hero frame was authored first, then attention, causal
-  action, dependent follow-through, settle, and readable hold. This created no
-  approval artifact or aesthetic checklist.
-- Each shot uses one primary craft grammar, preserves Recipe timing and
-  micro-beats, is deterministic/seekable, and records runtime implementation
-  decisions and faithful variances.
-- Ordinary media drives geometry, crop, mask, path, annotation, palette,
-  depth, or state; it is not a generic thumbnail/card/title background.
-- Every assigned `shotId` has editable source and its own direct runtime render
-  target. Source, fonts, dependencies, and unit seams close technically; the
-  Agent handoff is locator-only and exception-led.
-- Remotion source directories remain isolated, while identical dependency
-  identities name one shared toolchain receipt. No unit contains a private
-  dependency copy, and every install/typecheck/browser/render command used the
-  fixed two-slot heavy queue.
-
-## Scripted shot rendering, preview, and delivery
-
-- Parent ran `render-assigned-shots.mjs` for each assignment. Every planned
-  Recipe appears exactly once as an independently probed and fully decoded
-  H.264 file with `renderTarget.mode: direct-runtime-render`; no shot was cut
-  from a unit or Master.
-- Every shot has a schema-valid `shot-media.json`, source/Recipe/profile
-  identity, and an opening/preparation/action-a/action-b/result/settle-tail
-  six-frame semantic sheet. Only concrete risk windows added bounded frames;
-  normal shots produced no full-frame sequence.
-- `delivery-index.json` closes shot count, Recipe order, absolute SRT windows,
-  local frame mapping, neighbors, seams, and continuous coverage.
-- Parent ran `assemble-shot-preview.mjs` only from the verified shot files and
-  fully decoded the complete preview. No Integrator or Render Agent was
-  dispatched.
-- After approval, the ordered high-quality shot directory is the default
-  delivery. Any requested Master is newly assembled from those same unchanged
-  shots to an unused path; it is optional and never copied from preview.
-- The representative scenes are the user's early visual-direction stop and the
-  complete composition preview is the final aesthetic stop. There is no default
-  full-film Director witness, and script checks do not claim aesthetic approval.
-- Every delivered shot passes FFprobe and complete decode. An optional Master,
-  when requested, also passes them. Technical facts are not aesthetic approval.
-
-## Final report
-
-Report ordered shot and index locators, preview locator, objective media facts,
-continuous coverage, material/font sources, optional Master or legacy-export
-locators, and honest limitations. Do not add a post-render aesthetic review or
-ask the user to approve a second time.