Clone any viral video with AI agents. Not just a script, the whole workflow: swap the face, the words, the B-roll, ship 100 variants in one command, and get your 100M views.
TypeScript agentic-aiaiai-agentsai-videocompilerdslffmpeggenerative-aillmmarkup-languagemonorepoplugin-systemprogramming-languagetext-to-videotypescriptvideovideo-automationvideo-clonevideo-editingvideo-generation
Sync Narratage skill with durable runtime quickstart
rpone5596eadcd523
diff --git a/.agents/skills/narratage/SKILL.md b/.agents/skills/narratage/SKILL.mdindex 41deb321..56ca2e91 100644--- a/.agents/skills/narratage/SKILL.md+++ b/.agents/skills/narratage/SKILL.md@@ -19,15 +19,27 @@ Source, and `svml.runtime.json`/`.ts` Runtime Profile separate.`references/playbooks/svml-mapping.md`, then only the relevant craft/format file.- Reference-video reverse engineering → read `references/reference-vlm.md`; have VLM emit`main.svml`, optional `studio.svs`, and `build.svrun` directly, never a JSON storyboard.-- Execution → `check` first, `plan` before paid work, then `build`; inspect and retrieve durable- outputs afterward.+- Execution, Runtime control, Build inspection, or output retrieval → read+ `references/runtime.md`; diagnose and start the durable Runtime, `check` Author Source, `plan`+ before paid work, then submit, inspect, and retrieve the Build.## Required loop```bash+node --run narratage -- doctor path/to/svml.runtime.json+node --run narratage -- runtime up path/to/svml.runtime.jsonnode --run narratage -- check path/to/main.svml --package-lock path/to/svml.packages.lock --root .node --run narratage -- plan path/to/build.svrun --package-lock path/to/svml.packages.lock --root .+node --run narratage -- build path/to/build.svrun --runtime path/to/svml.runtime.json \+ --package-lock path/to/svml.packages.lock --root . --build-id my-build-001 --follow+node --run narratage -- inspect my-build-001 --runtime path/to/svml.runtime.json+node --run narratage -- get my-build-001 --runtime path/to/svml.runtime.json \+ --name final.video --to path/to/output/final.mp4```+Treat `--follow` as an observer: stopping it does not stop the durable Build. Use `runtime down`+only to stop the Worker and Runtime-owned programs; it does not cancel Builds or remote Provider+work.+Preserve unrelated changes. Keep credentials, generated media, runtime state, and logs out of commits.The repository's docs remain the syntax authority.diff --git a/.agents/skills/narratage/references/environment.md b/.agents/skills/narratage/references/environment.mdindex 20035646..72c056c1 100644--- a/.agents/skills/narratage/references/environment.md+++ b/.agents/skills/narratage/references/environment.md@@ -20,9 +20,14 @@ uv python install 3.13uv sync --project services/whisperx --frozenuv sync --project services/image-opencv --frozenuv run --project services/whisperx --frozen svml-whisperx-prepare-node --run narratage -- services up svml.runtime.jsonnode --run narratage -- doctor svml.runtime.json+node --run narratage -- runtime up svml.runtime.json+node --run narratage -- runtime status svml.runtime.json```+Use `runtime up` for normal Build preparation: it owns the detached durable Worker and the external+programs declared by the Runtime Profile. `services up/status/down` is only the narrow external-+program view and does not manage the Worker. See `references/runtime.md` for the Build lifecycle.+The repository owns skill discovery: `.agents/skills` is canonical, with repository-root`.codex/skills` and `.claude/skills` links. This is checkout layout, not a skill setup operation.diff --git a/.agents/skills/narratage/references/quickstart.md b/.agents/skills/narratage/references/quickstart.mdindex a2582ff7..81508761 100644--- a/.agents/skills/narratage/references/quickstart.md+++ b/.agents/skills/narratage/references/quickstart.md@@ -11,7 +11,7 @@ The repository docs are authoritative:| Speech Spine and SemanticMap | `docs/quickstart/timing.md` || Caption, Media, Text, Audio Tracks | `docs/quickstart/tracks.md` and the `@narratage/audio-track` package README || Film and rendering | `docs/quickstart/composition.md` |-| Run Source and Runtime | `docs/quickstart/run.md` |+| Run Source, durable Runtime, Builds, retrieval, and reuse | `docs/quickstart/run.md` and `references/runtime.md` |Canonical path:@@ -19,3 +19,7 @@ Canonical path:Use explicit imports, exact fonts, Canvas/Frames, ProgramSpace, package locks, Targets, and Runtimeauthority. There is no implicit cache; reuse is explicit with `build-record` + `satisfy`.++For execution, preserve the full lifecycle: diagnose the Profile, start or reuse the durable+Runtime, inspect the frozen plan, submit a named Build, inspect its accepted Records, retrieve+Artifacts, and declare any reuse explicitly in a new Run Source.diff --git a/.agents/skills/narratage/references/runtime.md b/.agents/skills/narratage/references/runtime.mdnew file mode 100644index 00000000..3bbf298b--- /dev/null+++ b/.agents/skills/narratage/references/runtime.md@@ -0,0 +1,55 @@+# Durable Runtime and Build workflow++Read `docs/quickstart/run.md` as the authority for Run Source, Target, fidelity, Runtime Profile,+Build, retrieval, and reuse syntax. Use this file as the operational checklist.++## Execute the lifecycle++```bash+pnpm narratage doctor path/to/svml.runtime.json+pnpm narratage runtime up path/to/svml.runtime.json+pnpm narratage runtime status path/to/svml.runtime.json++pnpm narratage check path/to/main.svml \+ --package-lock path/to/svml.packages.lock --root .+pnpm narratage plan path/to/build.svrun \+ --package-lock path/to/svml.packages.lock --root .++pnpm narratage build path/to/build.svrun \+ --runtime path/to/svml.runtime.json \+ --package-lock path/to/svml.packages.lock \+ --root . --build-id my-build-001 --follow++pnpm narratage inspect my-build-001 --runtime path/to/svml.runtime.json+pnpm narratage get my-build-001 \+ --runtime path/to/svml.runtime.json \+ --name final.video --to path/to/output/final.mp4+```++Use `runtime logs` to diagnose the Worker and managed programs. Use `runtime down` for an orderly+stop. It stops the Worker from claiming more leases and stops Runtime-owned programs, but preserves+durable Builds and does not cancel remote Provider work.++## Preserve durable semantics++- `runtime up` starts or reuses the detached Worker plus declared external programs. A direct+ `build` also ensures the execution domain is running before submission.+- `services up/status/down` manages external programs only. Do not use it as the normal Build+ bootstrap because it does not own the Worker lifecycle.+- A Build continues after durable submission. `--follow` only observes progress; interrupting the+ terminal does not stop the Build.+- `inspect` reads durable Build state and accepted Records. `get` copies an archived Artifact to the+ requested destination.+- There is no implicit cache. Reuse Records only through a new `.svrun` containing `build-record`+ and `satisfy`, with the target accepting the resulting fidelity.++## Keep project and package boundaries distinct++Prefer production projects outside the Narratage checkout. Relative Author Sources and assets stay+inside the Source Workspace, which defaults to the directory containing the entry `.svrun`.++- `--root` deliberately widens the Source Workspace boundary.+- `--package-root` only changes where the Host locates installed packages whose bytes are verified+ by the package lock. It does not widen Source access.+- Do not symlink an external project into the repository to bypass containment; canonical-path+ checks reject that escape.