cueframe 0.4.9 → 0.4.10

package/README.md

@@ -77,45 +77,38 @@ npx -y cueframe render <projectId> -o short.mp4 --json
 Both paths converge on `render`; the suggestion on-ramp just authors the
 composition for you instead of you hand-writing it.
 
-## Package a recipe offline
+## Run a template
 
-`cueframe recipe pack` is an authoring command, separate from `recipe run`.
-It validates a prepared project draft and already-bundled component sources,
-calculates their canonical source versions, pins every component placement, and
-writes a portable version-4 `.cueframe` project. It needs no login, network,
-rendering runtime, or separately installed kernel. It does not compile or execute
-component code; preview the result in a compatible CueFrame runtime before publishing.
+A template is one `.cueframe` document: a composition with `{{name}}`
+references, the parameters that fill them, optional presets and brand kits.
+The public catalog lives in `cueframe-ai/cueframe-templates`; your org keeps
+its own under `POST /v1/templates`.
 
 ```bash
-cueframe recipe pack --body @recipe-input.json --out recipe.cueframe --json
-cueframe recipe pack --body @recipe-input.json --out recipe.cueframe --check --json
-# --body @- accepts stdin; --dry-run validates without creating/replacing output.
+cueframe template run yosemite-warp-text --preset granite --media source=sample --values text=CARVED -o carved.mp4
+cueframe template run ./template.cueframe --media source=./clip.mp4 --values title="Journey" --no-render --json
+cueframe template status <jobId> --wait --json       # reconnect to a running preparation
+cueframe template validate ./template.cueframe          # offline: references, presets, mattes
 ```
 
-The versioned input is `{ "version": 1, "project": { ... }, "components": [...] }`:
-
-- `project` is a version-4 project draft: `id`, `name`, explicit `createdAt` and
-  `modifiedAt`, `composition`, `pool`, and `recipe` metadata. No timestamps are invented.
-- `recipe` declares `schemaVersion: 1`, `slug`, one `mediaSlots` entry (the current
-  `recipe run --media` contract), `cloudBrandKit`, and `components` metadata entries
-  with `componentId`, `name`, `category`, and optional `propSchema`.
-- `components` contains self-contained component-v2 source objects:
-  `{ version: 2, componentId, tsxSource, manifest }`. Bundle owned modules with
-  `esbuild` and `packages: 'external'`; the CLI checks remaining imports against
-  the authoritative runtime allowlist and enforces the recipe source-size limit.
-- Omit `authoredComponents`, metadata `sourceVersionId`, and placement
-  `props.componentRef`: the packer generates these consistently. Declare and bind
-  required component assets to matching pool entries before packaging.
-
-This is not an automatic exporter for arbitrary existing projects: authors
-explicitly choose the replaceable media and prepare the recipe metadata. Keep
-the generated artifact under version control; consumers can use it without
-rebuilding or installing the recipe's development dependencies.
-
-Use a recipe with `cueframe recipe run ./recipe.cueframe --media ./input.svg
---no-render --json`. That authenticated workflow uploads media, installs owned
-components, and creates an editable project. Omit `--no-render` for immediate
-rendering, or render the created project after previewing and editing it.
+`run` publishes a local document to your org (a catalog slug is imported on
+first use), uploads each `--media name=<file>`, then starts one preparation job.
+The job imports and processes media, attaches verified template assets, applies
+the composition, and returns the ready project before `run` renders it. The
+`template_job_request` JSON event carries an idempotency key; pass it back with
+`--idempotency-key` if the start request loses its response. Reuse the same
+media IDs from the earlier upload events as `--media name=media:<id>` so the
+retried request has identical inputs. After a `jobId` arrives,
+`template status <jobId> --wait` reconnects without starting another project.
+`--media name=<https url>` imports the
+URL, `--media name=sample` takes the template's own sample. `--values` are
+coerced by the document's parameter types before anything is sent, so an enum
+typo fails here, not on the server.
+
+`validate` needs no account for a file or a catalog slug. It exits 2 with the
+list of problems: undeclared or misplaced references, a preset that does not
+bind, a required media parameter with no sample, a prepared matte at another
+bake version.
 
 ## Wire it into your agents
 

package/dist/analyze-CDC4H53Q.js

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+import{H as a}from"./chunk-QS37SCWN.js";import"./chunk-3QSA3EBY.js";export{a as analyzeCommand};

package/dist/chunk-3QSA3EBY.js

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+var d=Object.defineProperty;var e=(c,a)=>{for(var b in a)d(c,b,{get:a[b],enumerable:!0})};export{e as a};