# Changelog All notable changes to `capcut-cli-david` are documented here. Format follows [Keep a Changelog 1.1](https://keepachangelog.com/en/1.1.0/); this project adheres to [SemVer 2.0.0](https://semver.org/spec/v2.0.0.html). Fork-specific sub-sections (*Synced from upstream*, *Compatibility*) are added per [`RELEASE.md`](./RELEASE.md) §4. ## [Unreleased] ### Planned - `1.x` — see [`release-notes/1.0.0.md`](./release-notes/1.0.0.md) §Roadmap for the non-binding 1.x backlog. ## [1.14.1] — 2026-06-09 Patch release. Bugfix for `sync-timelines`: it now reconciles the guid's `draft_info.json` — the mirror CapCut reads on the **first open** of a CLI-built draft — so audio and captions added after the build are no longer silently dropped. ### Fixed - **`sync-timelines` now reconciles `Timelines//draft_info.json`.** A draft built in the CLI and never opened in CapCut keeps its timeline mirror in the guid's `draft_info.json`; CapCut only materialises `Timelines//draft_content.json` on first open. Because `saveDraft` writes **only** the root `draft_content.json`, audio/captions added post-build never reached the file CapCut reads first → they were lost on open (CapCut then rewrote the root video-only on close). `draft_info.json` was an **oversight** in `MIRROR_FILES`, not a deliberate exclusion (only `.bak` + the patch journals `mini_draft.json`/`patch.json` are excluded). Root cause confirmed by filesystem repro. - **Scope = the guid's `draft_info.json` only.** `MIRROR_FILES` feeds the per-guid loop, so the **root** `draft_info.json` (an inert legacy sibling — CapCut does not read it as authority) is **never** touched. The root-siblings pass (root `template-2.tmp` only) is unchanged. - **Data-loss transparency extended:** the stderr `WARNING` for a divergent overwrite now also fires when the guid's `draft_info.json` is overwritten (previously only `draft_content.json`). - Unchanged safety net: timestamped `.synced-.bak` before overwrite, skip-if-absent, skip-when-byte-identical, per-guid isolation, root draft read-only. - **464 tests** (+6). Typecheck clean; changed files lint-clean. ## [1.14.0] — 2026-06-07 Minor release. New read-only `make-preset` — the generation cousin of `query`. Given a font name, it scans the CapCut drafts library and emits a ready-to-use **bare-font** `restyle` preset (font identity only), so you never hand-craft a preset JSON again. ### Added - **`make-preset --font [--out ] [--drafts ] [--human]`** — read-only preset generator. Scans every draft under the projects root (default `defaultProjectsRoot()`, override `--drafts`), finds the font, and emits a preset that feeds straight into `restyle --preset`. - **Match:** `--font` is a **case-insensitive substring** on the catalogue title; if the value is **purely numeric** it is matched as an **exact `resource_id`** instead. - **Source = drafts library (zero new deps).** The complete font block (`font_path`, `font_resource_id`, `fonts[]` incl. `title`, `source_platform`) already lives in any draft that uses the font — no SQLite / CapCut-cache reading. (A catalogue font is, by definition, one you've applied at least once, which writes it into a draft.) - **Dedupe + tie-break:** by `resource_id`; on collision prefers the **catalogue-grade** entry (`source_platform == 1`, non-empty `title`, `.ttf` under `/effect//`) over a bare local fallback, so the same font seen as both local and catalogue collapses to the catalogue truth. - **Bare-font preset:** carries ONLY the font identity — `text_material.{font_path,font_resource_id,font_title,font_source_platform,fonts[]}` + `content_template.styles[0].font {path,id}` + `segment {}`. No stroke/shadow/size decoration. The `fonts[]` entry is copied **verbatim from the draft** (path normalized, `request_id` cleared) so the CapCut dropdown resolves the name (the S1649 #8 correctness detail). - **`--out `** writes the bare preset (ready for `restyle --preset`); without it the preset rides in the JSON envelope. `-H/--human` prints a one-line summary / candidate list. - **Envelope:** `capcut-david/make-preset@1` (`{type, ok, font, ambiguous, candidates[], written, preset}`). - **Exit codes:** `0` for success, no-match (`ok:false`), and ambiguous (lists candidates, no silent pick); `2` if the drafts root is missing, every draft is unreadable, or the matched font is **local-only** (no `resource_id` → can't build a catalogue preset); `1` for usage errors (missing `--font`). - **458 tests** (+25). Typecheck clean; `make-preset.ts` lint-clean. ## [1.13.0] — 2026-06-06 Minor release. New read-only `query` — a catalogue lookup that searches the CapCut drafts library for effects, filters, transitions and fonts by name and returns their `resource_id`. No writes; complements the validate→fixer family. ### Added - **`query [--kind effect|filter|transition|font] [--drafts ]`** — read-only catalogue search. Scans every draft under the projects root (default `defaultProjectsRoot()`, override `--drafts`), indexes 4 kinds and matches `` as a **case-insensitive substring on the item name**, returning each item's `resource_id`/`effect_id`. - **Kinds:** effects (`materials.effects` where `type != "filter"` + `materials.video_effects`), filters (`materials.effects` where `type == "filter"`), transitions (`materials.transitions`), fonts (`materials.texts[].fonts[].title`, or `deriveFontName(font_path)` for local `.ttf` with no resource_id → `resource_id: null`). - **Dedupe:** by `resource_id` (local fonts by `name`+`font_path`); each result lists `from_drafts[]`. - **Envelope:** `capcut-david/query@1` (flat `{type, results[]}`, no `next`). `-H/--human` renders a table. - **Exit codes:** `0` for any valid query incl. zero matches and an empty library; `2` if the drafts root is missing or every draft is unreadable; `1` for usage errors (missing ``, invalid `--kind`). - **433 tests** (+34). Typecheck clean; `query.ts` lint-clean. ## [1.12.0] — 2026-06-06 Minor release. New `validate --fix` — the umbrella auto-fixer that completes the validate→fixer family: it maps each fixable finding to its command-backed fixer and runs them in dependency order. **Dry-run by default**; `--apply` required to write. ### Added - **`validate --fix [--apply]`** — aggregate auto-fixer. Runs `validate`, maps each fixable finding to its fixer, and either **previews** the plan (default, zero writes) or **applies** the fixers in dependency order, then re-validates and reports the residual. - **Finding → fixer mapping:** `materials.orphan_text`/`materials.orphan_media` → `gc` (destructive), `meta.missing` → `init-meta`, `meta.unregistered` → `register`, `timelines.divergence` → `sync-timelines`. - **Fixed run order** `gc → init-meta → register → sync-timelines`. Forced by two dependencies: `register` needs the sidecar `init-meta` writes (so init-meta runs first), and `sync-timelines` copies the **root** `draft_content.json` into the `Timelines/` mirror — so it must run **strictly last**, after `gc` has mutated and saved the root. - **Dry-run by default (D1).** `--fix` alone previews the aggregated plan and writes zero bytes; `--apply` is required to mutate. This intentionally inverts `gc`/`sync-timelines` (apply-by-default), because the umbrella aggregates a destructive `gc` removal across many findings in one pass. `--fix --apply --dry-run` is rejected (mutually exclusive). - **Reuses `--id`/`--skip` (D3)** for selective fixing — a fixer runs iff at least one of its owning finding-ids survives the filter (`gc` owns two, so skipping one alone doesn't drop it). **Re-validates from fresh disk state after applying (D4)** and exits on the residual. **`duration.under/overrun` are reported but excluded** (fixable but no dedicated command, D2). - **Blocking-error refusal.** On a `dangling_ref`/`duplicate_id` draft, `--fix --apply` refuses the whole run (exit 2, zero writes) — `gc`'s id-filter is only sound once duplicates are excluded. Dry-run still shows the plan, flagged `blocked`. - **Conditional CapCut guard.** `validate` stays OUT of `WRITE_COMMANDS` (read-only `validate` and dry-run `--fix` run with CapCut open); `assertCapCutClosed` fires only inside the `--apply` write path. `--force`/`CAPCUT_DAVID_FORCE` bypass. - **Exit codes:** dry-run → always `0`; `--apply` → `reportExitCode(residual)` (`0`/`2`); blocking-error refusal → `2`; `sync-timelines` failure or any tool error → `1`. *Note:* orphan findings are `info`-severity, so the exit code is **not** the success signal for `gc` — `fix.results[].wrote` is. - **Envelope** extends `capcut-david/validate@1` with an additive `fix` key (present only with `--fix`); a plain `validate` envelope is unchanged. No `next` field. ### Changed - **`init-meta`:** the sidecar write is extracted into an exported `applyInitMeta(plan, metaPath)` (the bak-first branch + the compact `writeFileSync`) so `validate --fix` can write the sidecar without re-parsing or re-emitting an envelope. `cmdInitMeta`'s behavior and full envelope are byte-identical (regression-locked). ### Notes - No existing command changes behavior (the `applyInitMeta` extraction is byte-identical — `init-meta`'s tests stay green). `validate --fix` adds 24 tests (399 total). Typecheck clean; `validate-fix.ts` lint-clean. ### Compatibility - CapCut ≥ 5.x desktop (Windows + macOS) — unchanged. Node `>= 18` — unchanged. Runtime dependencies: zero — unchanged. ## [1.11.0] — 2026-06-05 Minor release. New `init-meta` command — generates the missing `draft_meta_info.json` sidecar that v1.8.0 `validate`'s `meta.missing` detects. Completes the validate→fixer family (`timelines.divergence`→`sync-timelines`, `orphan_*`→`gc`, `meta.missing`→`init-meta`). ### Added - **`init-meta `** — generates the canonical `draft_meta_info.json` next to a draft's `draft_content.json` when it is missing. Without that sidecar a draft is invisible in the CapCut UI and `register` fails. - **Refuse-to-clobber (the INVERSE posture of `sync-timelines`/`gc`).** An existing `draft_meta_info.json` is presumed **authoritative** (it carries the real `draft_id`, `tm_draft_*` timestamps and cloud refs), and `meta.missing` only fires when the file is *absent* — so `init-meta` **refuses** (exit 1, zero bytes, sidecar untouched) when one already exists, unless `--force` (which writes a `.bak` of the original first and warns on stderr). - **Writes ONLY `draft_meta_info.json`.** Never `draft_info.json` (a stale one could shadow `draft_content.json` in `findDraft`), never `root_meta_info.json` — except the opt-in `--register` substep, which chains `register` and is explicitly CapCut-open-guarded (`init-meta` itself is not in `WRITE_COMMANDS`). `draft_content.json` is never touched. - **Field sourcing** matches `register`'s disk-identity rules: `draft_id` from the draft's `id` (or a fresh UUID + an stderr note that `register` will reconcile), `draft_name` = the dir basename, `draft_root_path` = the **parent** of the draft dir, `tm_*` in microseconds. The canonical ~40-field shape is built by `buildDraftMetaInfo`, **extracted verbatim from `psycho-build`** into `src/utils/draft-meta.ts` and shared, so both emit a byte-identical sidecar (locked by an exact key-set/order test). - **Flags:** `--force`, `--register`, `--projects-root` (forwarded only to `register`), `--dry-run` (writes nothing), `-q`, `-H`. **Exit codes:** `0` = created (or dry-run / register OK), `1` = tool failure (not found, resolved file ≠ `draft_content.json`, sidecar already present without `--force`, write/register failure). No exit 2. - `validate`'s `meta.missing` `fix_hint` now names `capcut-david init-meta `. ### Notes - No existing command changes behavior. The `buildDraftMetaInfo` extraction is byte-identical (`psycho-build`'s 45 tests stay green). `init-meta` adds 13 tests (375 total); `init-meta.js` coverage is 97.8% lines / 100% functions. ### Compatibility - CapCut ≥ 5.x desktop (Windows + macOS) — unchanged. Node `>= 18` — unchanged. Runtime dependencies: zero — unchanged. ## [1.10.0] — 2026-06-05 Minor release. New `gc` command — the WRITE verb that removes the orphan materials v1.8.0's read-only `validate` reports (`materials.orphan_text` / `materials.orphan_media`). Completes the validate→fixer trio alongside v1.9.0 `sync-timelines`. ### Added - **`gc `** — deletes the **segment-orphan text/video/audio materials** that `validate` flags as info (e.g. the leftover text materials `import-captions`/`restyle` leave behind on every re-injection), by mutating `draft.materials` in place and re-serialising via `saveDraft`. - **Scope is the data-safety guarantee.** gc removes **only** from `materials.texts` / `materials.videos` / `materials.audios` — never any other slot. For those three slots, segment-reachability is *total* reachability: a cross-material id scan over all 9 fixtures (1283 materials) found **zero material→material references**, so a segment-orphan there has no inbound edge. It is an *orphan media/text GC, not a full GC* (it leaves the now-doubly-orphan companion bundle of a deleted text — benign, and validate ignores those by design). - **JSON-only.** gc **never** deletes a file under `Resources/` (a media `path` may be shared by another live material) and writes no file but `draft_content.json` (+ its `.bak` via `saveDraft`). - **Refuses on a broken draft.** If `validate` would report an error (`materials.dangling_ref` or `materials.duplicate_id`), gc exits 1 and writes nothing — a dangling ref means the draft is already inconsistent; a duplicate id makes "the orphan with id X" ambiguous. - **Defensive cross-ref skip.** A text whose `text_to_audio_ids` is non-empty (the one documented field that can name other-material ids; empty in every fixture) is **skipped** (reported under `skipped_cross_ref`), never deleted. - **No-op never writes.** When nothing is orphaned, gc calls no `saveDraft` — the `.bak` and mtime are untouched (`wrote:false`), so it is idempotent and the previous edit's rollback is preserved. (After a real removal gc cannot promise byte-identity — the deletions are re-serialised — so the byte-identity guarantee is the no-op path only.) - **Apply-by-default + `--dry-run`**; in `WRITE_COMMANDS` (the "CapCut is open" guard refuses while CapCut runs, `--force` bypass); a stderr WARNING on real removal names the `.bak` and reminds you to run `sync-timelines` afterwards (the root now diverges from any `Timelines/` mirrors). **Exit codes:** `0` = success incl. nothing-to-gc, `1` = tool failure. No exit 2. - `validate` now exports `collectOrphans` (the shared per-slot orphan definition gc deletes against) and `hasBlockingErrors`; its `materials.orphan_text` / `materials.orphan_media` findings' `fix_hint` now names `capcut-david gc `. ### Notes - No existing command changes behavior. `gc` adds 24 tests (363 total); `gc.js` coverage is 100% lines / 100% functions. ### Compatibility - CapCut ≥ 5.x desktop (Windows + macOS) — unchanged. Node `>= 18` — unchanged. Runtime dependencies: zero — unchanged. ## [1.9.0] — 2026-06-05 Minor release. New `sync-timelines` command — the WRITE verb that repairs the stale-timeline-mirror corruption that v1.8.0's read-only `validate` detects (`timelines.divergence`). Once CapCut opens a draft it treats `/Timelines//draft_content.json` as its own timeline source of truth; a later CLI re-patch of the root leaves that mirror stale and CapCut renders the old state (fonts/captions missing). This automates the documented manual recovery. ### Added - **`sync-timelines `** — copies the root `draft_content.json` (RAW bytes, never re-serialised) into every `Timelines//draft_content.json` + `template-2.tmp`, so root and mirrors agree again. Direction is **always root → mirror**, never inferred from mtime. It is the fixer for `validate`'s `timelines.divergence` finding. - **Data-loss safety (apply-by-default + nets):** in `WRITE_COMMANDS` → the "CapCut is open" guard refuses while CapCut runs (`--force` bypass); **timestamped, non-clobbering** per-file backups (`…synced-.bak`) before every overwrite; **skip-when-byte-identical** (a converged draft writes zero bytes, mtime unchanged); a **stderr WARNING** on each divergent-mirror overwrite reminding you to confirm CapCut has been closed since the draft was *modified*. The dangerous "mirror is newer than root" case (edited in CapCut, closed, then synced) is recoverable from the timestamped backup. - **Never touched:** the root `draft_content.json` itself (read-only source), the root `draft_content.json.bak` (`saveDraft`'s own rollback), the patch journals (`attachment/patch/mini_draft.json` / `patch.json`), `draft_meta_info.json` / `root_meta_info.json`, `key_value.json`, `Resources/`. - **Robustness:** per-guid isolation — a locked/unwritable mirror degrades to an error (exit 1) without aborting the other guids, and a backup created for a write that then fails is cleaned up (no orphan). No `Timelines/` folder ⇒ no-op success (the dir is never fabricated). - **Flags:** `--dry-run` (report without writing a byte), `-q`, `-H`, `--force`. **Exit codes:** `0` = synced or nothing to sync, `1` = tool failure. No exit 2. - Shared `listTimelineDirs()` util (`src/utils/timelines.ts`) — single source of the `Timelines/` walk, now used by `mirror.ts`, `validate.ts` and `sync-timelines.ts`. `validate.ts` exports `draftSignature`; its `timelines.divergence` `fix_hint` now names `sync-timelines`. ### Notes - No existing command changes behavior. `sync-timelines` adds 31 tests (350 total); `sync-timelines.js` coverage is 98.6% lines / 100% functions. The `mirror.ts` / `validate.ts` refactor to the shared walk is behaviour-preserving (all prior tests green). ### Compatibility - CapCut ≥ 5.x desktop (Windows + macOS) — unchanged. Node `>= 18` — unchanged. Runtime dependencies: zero — unchanged. ## [1.8.0] — 2026-06-05 Minor release. New `validate` command — a strictly read-only linter that detects draft corruption and broken invariants **before** you open CapCut. It is the diagnostic backbone the future fix verbs (`--fix`, `gc`, `sync-timelines`, `relink`) will graft onto: every detector is a pure, exported `CHECKS` function emitting a stable finding schema (`id` / `severity` / `fixable` / `fix_hint`). ### Added - **`validate `** — runs a battery of checks over `draft_content.json` and prints a versioned JSON report (`schema: "capcut-david/validate@1"`) or, with `-H`, a human table grouped by severity. **Never writes a byte** (no `saveDraft`, no `.bak`, no `mkdir` — locked by a byte-identity test) and is deliberately **not** in `WRITE_COMMANDS`, so it runs fine while CapCut is open. Each detector is wrapped so a throw degrades into a diagnostic rather than crashing the run; an unparseable draft is a single clean `{"error":…}` (exit 1). - **Exit codes:** `0` = ran clean (or only info/warnings without `--strict`), `2` = `error` findings present (or warnings under `--strict`), `1` = tool failure (bad args / project not found / unreadable JSON). So *finding problems* never collapses to a tool error. - **Checks (always-on, CI-safe — pure graph):** `materials.dangling_ref` (error; resolves `segment.material_id` against an **exact** id Set, never the prefix-matching `findMaterialGlobal`), `materials.duplicate_id` (error; global across all ~54 material slots), `companions.missing` (warning; each *present* `extra_material_refs` entry must resolve — the slot bundle is polymorphic/positional), `segments.zero_duration` (error on video/audio/text tracks, warning elsewhere), `duration.underrun` (warning) / `duration.overrun` (info) with a µs epsilon, `segments.overlap` (warning; video/audio only — text/effect/overlay stack legitimately), `materials.orphan_text` / `materials.orphan_media` (info; scoped to the typed slots so per-segment companions never cry wolf — and the leftovers `import-captions`/`restyle` create by design stay info), `canvas.config_sanity` (warning; `fps` is read at the draft root). - **Checks (filesystem):** `meta.missing` (error), `meta.unregistered` (warning), `meta.duplicate_draft_id` (warning) run automatically when a **directory** is passed (a bare `draft_content.json` file → these report *skipped*, never error); they read `root_meta_info.json` from `--projects-root` or `defaultProjectsRoot()` and degrade quietly if it is absent. `assets.missing_file` (`--check-assets`) and `timelines.divergence` (`--check-timelines`, a cheap duration/segment-count signal — never a deep-equal) are **opt-in**. - **Flags:** `-H/--human`, `-q/--quiet` (exit code only — CI gate), `--strict`, `--id ` / `--skip ` (repeatable), `--check-assets`, `--check-timelines`, `--projects-root `. ### Notes - `effect.bind_dangling` is intentionally **not** in the MVP: video FX bind via `material_id` on an `effect` track while a filter material's `bind_segment_id` is legitimately empty (`""` = track-wide); shipping it without handling both routing modes would cry wolf. It returns to a later minor once the fix verbs need it. - No existing command changes behavior. `validate` adds 52 tests (331 total); `validate.js` coverage is 97.6% lines / 100% functions. ### Compatibility - CapCut ≥ 5.x desktop (Windows + macOS) — unchanged. Node `>= 18` — unchanged. Runtime dependencies: zero — unchanged. ## [1.7.0] — 2026-06-05 Minor release. Hardens the engine against the two most expensive CLI footguns documented in the CapCut skills: absolute source paths breaking on Windows, and writing a draft while CapCut is open (silent loss to CapCut's on-close overwrite). ### Fixed - **Absolute source paths on Windows.** `add-audio` / `add-video` resolved paths with `path.startsWith("/")`, which on Windows misclassifies an absolute path (`C:\…` / `C:/…`) as relative and joins it onto the cwd → `ENOENT` (or the asset silently not copied into `assets/`). Now uses `path.resolve()` (correct on Windows + POSIX) for the source, and `path.basename()` (was `split("/").pop()`, which returns the whole string for a backslash path) for the asset filename. A relative input that already worked produces a **byte-identical** draft (locked by test); an absolute input that previously failed now copies the source into `/assets//` and references it there. ### Added - **"CapCut is open" preflight guard.** Every draft-writing command (`add-*`, `set-text`, `shift`/`shift-all`, `speed`, `volume`, `trim`, `opacity`, `import-captions`, `restyle`, `add-keyframe`, `ken-burns`, `apply-template`, `batch`, `cut`, `psycho-build`, `register`) now refuses to run while CapCut is detected running, with a clear error (`CapCut is running — close it before writing (or pass --force)`). CapCut holds `draft_content.json` / `root_meta_info.json` in memory and rewrites them on close, silently discarding CLI edits — this is gotcha #1 in every CapCut skill and Iron Law #4 of the build pipeline. Detection: `tasklist` (Windows) / `pgrep` (macOS/Linux); **fail-open** — if the probe is absent or finds nothing (e.g. CI), the command proceeds. Read-only commands and `init` (creates a brand-new draft) are not guarded. - `--force` flag (and `CAPCUT_DAVID_FORCE` env var) to bypass the guard for automation. ### Notes - The guard runs one process-list probe per write command (~tens of ms); library functions (`addText`, `importCaptions`, `applyCaptionStyle`, …) are never touched, so programmatic/batched use is unaffected. - `add-text` / `import-captions` / `restyle` output is unchanged — no new behavior on existing paths beyond the absolute-path fix. ### Compatibility - CapCut ≥ 5.x desktop (Windows + macOS) — unchanged. Node `>= 18` — unchanged. Runtime dependencies: zero — unchanged. - 279 tracked tests pass (265 prior + 3 absolute-path + 11 guard). The absolute-path fix's Windows regression value is host-OS-specific (POSIX absolute paths already started with `/`); it was watched fail→pass on Windows. ## [1.6.0] — 2026-06-05 Minor release. New `restyle` command ports the CapCut-CaptionStyling font-mirroring patchers (`restyle.py` + `fix_fonts_full.py` + `fix_content_styles_font.py` + `fix_key_value.py`) into the engine, so that skill becomes pure orchestration. It applies a caption style preset (font / stroke / shadow / size) to every caption, **span-aware**: multi-span keyword-highlight captions keep each span's color + range while the font / stroke / shadow change on all spans (the inverse of `--clone-style`). ### Added - `restyle --preset [--track-name ]` — apply a caption style preset to every caption on the target text track(s) (default: **all** text tracks; `--track-name` scopes to one). Reuses the `preset_captions_style.json` schema (`text_material` + `content_template` + `segment`). Each span keeps its `fill` (keyword color) + `range`; `font` / `strokes` / `shadows` / `size` / `bold` come from the preset. Material-level font fields are grafted (`font_path`, `font_resource_id`, `fonts[]` with empty `request_id`, `has_shadow`, `shadow_*`, `border_*`); `recognize_task_id` is cleared (else CapCut Auto-Captions regenerate and wipe the style); `base_content` / `recognize_text` are preserved (not blanked from the preset). - Sidecar font-mirroring — writes the new draft to `template-2.tmp` + `draft_content.json.bak`, forces `content.styles[].font.{path,id}` inside `Timelines/*/mini_draft.json` + `patch.json`, and injects the `key_value.json` registry entry keyed by `resource_id`. All targets are skip-if-absent; `key_value.json` is never fabricated. ### Changed - `register` now stamps a fresh `tm_draft_modified` on the add path, so a cloned or engine-generated draft surfaces at the **top** of CapCut's grid instead of inheriting a stale timestamp that buries it at the bottom (present in the index but effectively invisible). ### Notes - Single-span lean captions (legacy `add-text` UTF-16 byte-length range) are promoted to code-unit ranges on restyle, matching CapCut's rich-text convention. - Restyle scopes to materials **reachable from text-track segments**, so orphaned text materials left by `import-captions` are never touched. - `restyle` is a new, separate code path — `add-text` / `import-captions` output stays byte-identical (locked by test). The font dropdown showing "System" for a correctly-rendered preset font is a pre-existing CapCut cosmetic quirk, not a regression. ### Compatibility - CapCut ≥ 5.x desktop (Windows + macOS) — unchanged. Node `>= 18` — unchanged. Runtime dependencies: zero — unchanged. - 265 tracked tests pass (241 prior + restyle / mirror / register). Restyle output validated against a live CapCut render (CC-DerStil preset on a multi-span keyword caption — per-word colors survive the font change). ## [1.5.0] — 2026-06-04 Minor release. `import-captions --clone-style` preserves the existing caption look (font / strokes / shadows / size) from the target track when injecting keyword-highlight captions — font-agnostic, so any font the user set in CapCut (even one not in any preset library) survives, with the highlight color laid on top. This is the last piece needed to fully replace the standalone `inject_word_captions.py` patcher (which cloned the draft's caption style via template copy). ### Added - `import-captions … --clone-style` — before replacing the target track, photocopy the style block (`font`, `strokes`, `shadows`, `size`, `bold`, …) of that track's first existing caption and apply it to every new caption, overriding only `range` + `fill` (solid highlight color). The template material is deep-cloned so material-level fields (`text_color`, `border_*`, `shadow_*`, `line_spacing`, …) are preserved too. In clone mode every card is rich-text (parity with the patcher). Opt-in — default behavior is unchanged from 1.4.0. - `buildRichTextContent(text, fontSize, baseColor, highlights, baseStyle?)` — optional `baseStyle` param; when provided each span is a deep copy of it with `range` + solid `fill` overridden. Without it, the lean default span shape is byte-for-byte unchanged (locked by test). ### Changed - `import-captions` without `--track-name` now targets the **first existing text track** (was: a track literally named `text`). CapCut caption tracks are usually unnamed, so the old default created a stray second track and clone had nothing to read. `add-text` is unaffected; `add-text`/`import-captions` content output is otherwise identical to 1.4.0. ### Notes - `--clone-style` clones from the target track (`--track-name` if given, else the first text track). If that track is empty / its content can't be parsed, it falls back to the default style with a stderr warning — never an error. ### Compatibility - CapCut ≥ 5.x desktop (Windows + macOS) — unchanged. Node `>= 18` — unchanged. Runtime dependencies: zero — unchanged. - 241 tracked tests pass (235 prior + 6 clone-style). Clone output validated against a live CapCut render with a deliberately non-preset font. ## [1.4.0] — 2026-06-04 Minor release. Makes keyword highlight (per-word caption color) a first-class engine feature, replacing the standalone Python `inject_word_captions.py` patcher. CapCut multi-span rich-text is now produced natively, with colors emitted as float32 (`Math.fround`) to match CapCut's internal encoding and `range` offsets in UTF-16 code units. ### Added - `add-text … --keyword | --keyword-range [--keyword-color ]` — color one keyword inside a caption. `--keyword` matches the first substring occurrence (UTF-16 code-unit offsets via native `String.indexOf`/`.length`); `--keyword-range` takes explicit `start,end` offsets and takes precedence. Default color `#FFD600`. A keyword that is not found (or an out-of-bounds range) is a hard error — never a silent no-op. - `import-captions [--highlight-color ] [--track-name ]` — batch word/keyword captions from `[{text,start,end,hl?:[s,e],color?}]`. Replaces the named text track's segments 1:1 with the patcher, leaves prior text materials orphaned (unreferenced ⇒ invisible ⇒ zero deletion risk), supports per-card `color` (falls back to `--highlight-color`), and extends `draft.duration` to the last caption end. - `buildRichTextContent()` — shared core that emits N contiguous, non-overlapping CapCut style spans covering `[0, text.length]` in UTF-16 code units (gaps = base color, ranges = highlight color), `is_rich_text: true` on multi-span materials. ### Changed - `add-text` / `import-captions` share `buildTextMaterial()`. The single-span `buildTextContent` path is **unchanged** — `add-text` without a keyword flag is byte-identical to v1.3.0 (single span, UTF-16 *byte* range, no `is_rich_text`). Locked by test. ### Fixed - `set-text` and `apply-template` now **refuse** to mutate a multi-span (keyword-highlight) caption instead of silently corrupting it (they only re-ranged `styles[0]`, desyncing the remaining keyword spans). Clear error directs the user to rebuild via `add-text --keyword` / `import-captions`. - `test-fixtures/fixtures/animations-draft.json` keyword-highlight oracle: restored the real caption text `"THE EYES ARE WATCHING ME."` (the LOREM anonymizer had replaced it at approximate length while leaving the style ranges, desyncing range↔text). Documented the policy exception in the fixtures README. ### Compatibility - CapCut ≥ 5.x desktop (Windows + macOS) — unchanged. Node `>= 18` — unchanged. Runtime dependencies: zero — unchanged. - 234 tracked tests pass (208 prior + 26 keyword-highlight). Highlight output validated against a live CapCut render. ## [1.3.0] — 2026-05-20 Minor release. Extends the CapCut "Cubic Out" Δ-scaling fix (shipped in v1.2.0 for `cmdKenBurns`) to the incremental path `cmdAddKeyframe`. Both code paths now converge on a single shared segment model (`computeSegmentHandles`). ### Fixed - `cmdAddKeyframe` ease-out wrote `start.right_control.y = -0.47` fixed regardless of Δvalue at the inserted kf — now `round(0.94 × Δvalue, 6)`, coherent with the CapCut "Cubic Out" preset and the `cmdKenBurns` fix shipped in v1.2.0. - `cmdAddKeyframe` did not retro-compute neighbor handles when inserting between two existing kfs — `prev.right_control` and `next.left_control` stayed pinned to obsolete intervals. Now both neighbors are retro-updated: `prev.right` (x AND y), `next.left` (x — y stays 0 for all supported curves). ### Changed - `cmdAddKeyframe` output: - sequence (`add t=0, val=A, ease-out` + `add t=T, val=B, ease-out`) now produces byte-identical output to `cmdKenBurns(A, B, ease-out)` on the `scale_x` container; - insertion between 2 existing kfs now modifies the neighbors as well (cf. Fixed); - solitary kf (neither prev nor next) — both `left_control` AND `right_control` are `{x: 0, y: 0}` (previously `right` carried a "phantom" handle without a destination: `{round(0.32 × segDuration), -0.47}`); - replace of a kf at the same `timeOffset` now retro-updates neighbors using the new `value` (so the new Δ propagates). - The curve specified to `cmdAddKeyframe` now applies to **both adjacent segments** (`prev→new` and `new→next`) — i.e., it overwrites the handles of `prev.right` and `next.left` at insertion. Semantics aligned with CapCut UI where changing a kf's curve affects both surrounding segments. - `CURVE_PROFILES["ease-out"].startRightY`: `-0.47` → `0` (internal cleanup; this field is no longer consumed — the real value comes from the `curve === "ease-out"` gate via `KEN_BURNS_CUBIC_OUT_RIGHT_Y_RATIO`). ### Compatibility - CapCut ≥ 5.x desktop (Windows + macOS), JianYing 6+ unsupported — unchanged. - Node `>= 18` — unchanged. - Runtime dependencies: zero — unchanged. - New tests targeting `cmdAddKeyframe` oracle parity, behavioral coverage, and captured-CapCut-UI byte-identity (208 tracked tests). All tracked tests pass. The new byte-identity oracle (`test-fixtures/oracles/cubic-out-triplet-frame-aligned.json`) locks a formal contract vs CapCut UI: x byte-identical on frame-aligned intervals, ±1μs on non-aligned, ±1e-9 (~1 ULP) on y. - `draft_content.json` output for `add-keyframe --curve ease-out` is **not** byte-identical to 1.2.0 when `Δ ≠ -0.5` (intended correctness fix). `ken-burns` output is byte-identical to 1.2.0. ## [1.2.0] — 2026-05-19 Minor release. Corrects a latent easing bug in `ken-burns`: the start keyframe's outgoing Bezier handle `y` was a fixed absolute (`-0.47`) regardless of the zoom range, so easing was wrong for every range except exactly `to − from = -0.5`. **Not** byte-identical for `Δ ≠ -0.5` (hence minor, not patch) — see **Changed**. ### Fixed - **`ken-burns` ease-out easing** — `cmdKenBurns` wrote `start.right_control.y = -0.47` (the `CURVE_PROFILES["ease-out"]` fixed value) for every zoom, ignoring the value delta. CapCut's "Cubic Out" preset encodes `start.right_control.y = round(0.94 × (toVal − fromVal), 6)`; the `-0.47` was only the `Δ = -0.5` special case (a `1.5 → 1.0` zoom). A zoom-in `1.0 → 1.12` (`Δ = +0.12`) was getting `-0.47` instead of `0.1128` — a grossly wrong curve. Fix: `cmdKenBurns` now derives `y` from `0.94 × Δ` for `ease-out` (other curves keep their profile `y`, all `0`). Validated against the real-capture ground truth (`CapCut-ZoomFX/Tools/tests/fixtures/cubic-out-groundtruth.json`) and the cutcli-fix parity model. The incremental `add-keyframe` / `computeControlPoints` path is intentionally **not** changed (no proven ground truth there) — see release note backlog. ### Changed - `ken-burns` draft output: `start.right_control.y` now varies with the zoom delta (`round(0.94 × (to − from), 6)`). Output is byte-identical to 1.1.1 **only** when `to − from = -0.5` (e.g. `1.5 → 1.0`); for any other range the value changes (from the previously-wrong `-0.47` to the correct Δ-scaled value). `start.right_control.x`, `end.left_control`, the `x` ratios, and all non-`ease-out` curves are unchanged. `cmdAddKeyframe` output is byte-identical. ### Compatibility - CapCut ≥ 5.x desktop (Windows + macOS), JianYing 6+ unsupported — unchanged. - Node `>= 18` — unchanged. - Runtime dependencies: zero — unchanged. - 3 new tests (199 tracked tests). All tracked tests pass (the pre-existing `cmdKenBurns: curve override changes control points` assertion was corrected from `-0.47` to `0.47` — it had encoded the bug). Aggregate coverage stays above the 80% gate. - `draft_content.json` output is **not** byte-identical to 1.1.1 for `ken-burns` with `to − from ≠ -0.5` (intended correctness fix; see **Changed**). ## [1.1.1] — 2026-05-17 Patch fixing Bug #3, found during end-to-end verification of 1.1.0: the standalone `register` command failed on copied or moved drafts. Additive bugfix — no breaking changes, `draft_content.json` output byte-identical. ### Fixed - **Bug #3** — `capcut-david register ` trusted the target's `draft_meta_info.json` for `draft_name` / `draft_fold_path` instead of re-deriving them from the directory argument. A draft generated at path A then copied to CapCut path B kept A's name and path, so the `root_meta_info.json` entry pointed at the wrong location and CapCut couldn't open it. Dedup was also keyed on `draft_id`; a `cp -r` keeps the same id, so `register` returned `{"added": false}` and indexed nothing. Fix: `register` now derives `draft_name` from `basename()` and `draft_fold_path` from the resolved absolute ``, rewrites the sidecar to match, regenerates a fresh `draft_id` when it collides with a *different* folder, and dedups on `draft_fold_path`. The `psycho-build --out --register` one-shot is unaffected (verified — it already writes a correct `--out`-derived sidecar before registering). ### Changed - `register` idempotency key changed from `draft_id` to `draft_fold_path` (supersedes the "Idempotent on `draft_id`" note in [1.1.0]). Re-registering the same directory is still a no-op (`added: false`); registering a different directory that carries a duplicate `draft_id` now succeeds with a freshly generated id instead of being silently skipped. `register` also rewrites the target's `draft_meta_info.json` (`draft_name` / `draft_fold_path` / `draft_id`) so the sidecar stays consistent with the draft's on-disk location. ## [1.1.0] — 2026-05-17 First minor after 1.0 graduation. Closes the two post-1.0 bugs filed against the published surface: `psycho-build` drafts now appear in CapCut's UI (Bug #1), and `init` works out-of-the-box without `--template` (Bug #2). Additive only — no breaking changes. ### Added - `capcut-david register [--projects-root ]` — append a built draft to CapCut's `/root_meta_info.json` `.all_draft_store[]` so it surfaces in the CapCut UI. Idempotent on `draft_id`. Cross-platform default projects-root (Win: `%LOCALAPPDATA%/CapCut/User Data/Projects/com.lveditor.draft`; macOS: `~/Movies/CapCut/User Data/Projects/com.lveditor.draft`; Linux best-effort under `~/.local/share/CapCut/...`). - `--register` flag on `psycho-build` — when passed, runs the equivalent of `register ` after emitting the draft. `--projects-root ` overrides the default. - `psycho-build` now also emits **`draft_meta_info.json`** and **`draft_info.json`** alongside `draft_content.json`. These are the two CapCut sidecar files required for the draft to be indexed; without them the draft existed on disk but was invisible in the CapCut UI. - `src/utils/capcut-paths.ts` — shared helpers `resolveTemplateDir()`, `defaultProjectsRoot()`, `nowUs()`. Replaces the per-module template-path resolution previously duplicated in `pipeline.ts` and shipped broken in `create.ts:cmdInit`. ### Fixed - **Bug #1** — `psycho-build` produced drafts that were invisible in CapCut's UI. The output directory contained `draft_content.json` + `assets/` but was missing `draft_meta_info.json` + `draft_info.json`, and no entry was created in `root_meta_info.json`. Fix: `psycho-build` now always emits the two sidecar metadata files; the `--register` flag handles the root-meta indexing. - **Bug #2** — `capcut-david init` (with no `--template` flag) tried to copy `../CapCutAPI/template`, a path inherited from the upstream Python project that never existed in this fork's distribution. Fix: default template now resolves to the bundled `templates/minimal/` via `resolveTemplateDir()`. Default `--drafts` also became cross-platform (was hard-coded to macOS `~/Movies/CapCut/...`). ### Changed - `PsychoBuildResult` interface (`src/commands/pipeline.ts`) is additive: new fields `metaInfoPath`, `draftInfoPath`, `registered`, `registerRootMetaPath`. CLI output for `psycho-build` likewise gains `meta_info_path`, `draft_info_path`, `registered`, `register_root_meta_path`. - `Flags` interface (`src/utils/cli.ts`) gains `register?: boolean` and `projectsRoot?: string`. - `package.json` — `version` → `1.1.0`. `files`, `bin`, `engines`, deps unchanged. ### Compatibility - CapCut: same as 1.0.0 (≥ 5.x desktop on Windows + macOS). - JianYing 6+: unsupported (encrypted draft) — unchanged from 1.0.0. - Node: `engines.node >= 18` (unchanged). - Runtime deps: zero (unchanged). - 21 new tests (194 total, up from 173). Aggregate coverage on `src/commands/*` + `src/draft.ts` remains above the 80% gate. - All existing CLI commands and on-disk draft shapes are byte-identical to 1.0.0. `draft_content.json` output is unchanged. ## [1.0.0] — 2026-05-12 **Stable release.** Full SemVer 2.0.0 guarantees per [`RELEASE.md`](./RELEASE.md) §1 now in effect. **Code-identical to `0.5.0` and `1.0.0-rc.1`** — what changes is the contract. ### Highlights - The fork graduates after 5 implementation phases (A → E): - `0.1.0` — fork from `renezander030/capcut-cli`, modular `src/` (Phase A) - `0.2.0` — fixture-backed `node:test` harness, ≥80% coverage, full CI matrix (Phase B) - `0.3.0` — creation primitives `add-keyframe` and `ken-burns` (Phase C) - `0.4.0` — `psycho-build` YAML manifest pipeline (Phase D) - `0.5.0` — packaging consolidation: bundled `capcut-david` skill, in-repo schema docs, README rewrite (Phase E) - 27 CLI commands across 6 families. 173 tests, ≥80% coverage. 3000+ lines of in-repo schema reference. Zero runtime deps. Tarball ~110 kB / 52 files. ### Migration from 0.x - Pinned to `0.4.0` or `0.5.0` → `1.0.0`: no change. CLI surface byte-identical between `0.5.0`, `1.0.0-rc.1`, `1.0.0`. Just bump the pin. - Pinned to `0.1.0–0.3.0`: surface is additive across `0.x`; nothing was removed. Review use of inspect family (added `0.1.0`) and creation primitives (added `0.3.0`). - `cut-*` Claude skills users (`cut-audio`, `cut-draft`, `cut-motion`, `cut-storyboard`, `cut-tiktok`): deprecated since `2026-05-12` with `deprecated: true` frontmatter + redirect callouts pointing at the bundled `capcut-david` skill. Install the new skill from `$(npm root -g)/capcut-cli-david/skills/capcut-david/`. ### Changed - `package.json` — `version` → `1.0.0`. Dist-tag `latest` advances to `1.0.0` (was `0.4.0`). - `release-notes/1.0.0.md` — finalised from placeholder to the published GitHub release body (Highlights / Migration / Roadmap / Thanks). ### Deprecated and removed - The 5 legacy `cut-*` Claude skills are deprecated. Migrate to the unified `capcut-david` skill bundled in this package. - Removed nothing else. The full `0.x` CLI surface is preserved. ### Compatibility - CapCut: ≥ 5.x desktop (Windows + macOS); both `cutcli`-shape (`new_version: 167.x`) and CapCut-UI shape (`169.x`) supported. - JianYing 6+: unsupported (encrypted draft) — see [`COMPATIBILITY.md`](./COMPATIBILITY.md) §5. - Node: `engines.node >= 18`. - Runtime deps: zero (Node stdlib only). ### Roadmap (1.x — non-binding) - `1.x.0` — `capcut-david query` (animation / sticker / effect / filter catalogue lookup; recipe-referenced) - `1.x.0` — `capcut-david validate ` (schema-invariant linter) - `1.x.0` — JianYing 6+ research; `psycho-build` dynamic audio ducking ## [1.0.0-rc.1] — 2026-05-12 Release candidate for `1.0.0`. **No CLI / API / schema changes vs `0.5.0`.** Code is identical; this tag is the dress rehearsal for the SemVer 2.0.0 contract taking effect at `1.0.0` per [`RELEASE.md`](./RELEASE.md) §1. ### Changed - `package.json` — `version` → `1.0.0-rc.1`. Published with `--tag next`. ### Cutover (orchestrator-side, outside the npm package) - The 5 legacy `cut-*` Claude skills (`cut-audio`, `cut-draft`, `cut-motion`, `cut-storyboard`, `cut-tiktok`, in the upstream wiki vault) carry `deprecated: true` frontmatter + a redirect callout pointing at the bundled `capcut-david` skill — applied 2026-05-12. - `Wiki_Claude/SKILLS MAP.md` lists `capcut-david` and the five deprecated `cut-*` entries with their migration targets. - Pre-release audit (Explore sub-agent) — verdict **SHIP**: 7/7 Phase E criteria PASS, cross-links resolve, package.json `files` array complete, no v0.1.0 stragglers in repo content. ### Soak checklist (self-validation against this RC) - [x] `npm view capcut-cli-david@1.0.0-rc.1` returns `1.0.0-rc.1`; dist-tag `next` advances to it - [x] `capcut-david --help` prints all command families (Overview / Browse / Detail / Create / Edit / Animate / Pipeline) - [x] `capcut-david psycho-build examples/psycho/manifest.example.yaml --out /tmp/test --seed 42` succeeds end-to-end - [x] Skill loads in Claude Code from `~/.claude/skills/capcut-david/` (copied from `$(npm root -g)/capcut-cli-david/skills/capcut-david/`) - [x] All 7 `docs/draft-schema/` files render on GitHub at `v1.0.0-rc.1` - [x] Tarball contains `skills/`, `docs/`, `release-notes/`, `templates/`, `dist/`, the 7 root meta-docs (`README/CHANGELOG/LICENSE/NOTICE/COMPATIBILITY/UPSTREAM/RELEASE.md`) - [x] CI matrix green on commit (13/13 jobs: Node 18/20/22 × Ubuntu/macOS/Windows + Lint+Typecheck + Coverage + Fixture integrity + CI Pass) If every box stays checked through the soak window, promote to `1.0.0` per [`RELEASE.md`](./RELEASE.md) §1 (`--tag latest`). Otherwise bump to `1.0.0-rc.N+1`. ### Compatibility - Unchanged from `0.5.0`. CapCut ≥ 5.x desktop. JianYing 6+ unsupported. Node ≥ 18. Runtime deps: zero. ## [0.5.0] — 2026-05-12 Phase E packaging consolidation — graduation prep. **No new commands** (feature-frozen per Phase E constraints). The fork ships its own Claude Code skill bundle and an in-repo CapCut draft-schema reference, in service of the imminent `1.0.0` graduation. ### Added - `skills/capcut-david/SKILL.md` — unified Claude Code skill that supersedes `cut-draft`, `cut-storyboard`, `cut-motion`, `cut-audio`, and `cut-tiktok` (the 5 legacy `cut-*` skills). Bundled with the npm package under `skills/`. - `skills/capcut-david/references/recipes-{motion,audio,tiktok,storyboard}.md` — full recipes migrated and consolidated from the 5 source skills, normalised against the `capcut-david` command surface. - `docs/draft-schema/` (7 files, ~3000 lines) — in-repo reverse-engineered reference for CapCut's `draft_content.json` schema: overview, tracks/segments, materials, keyframes & animations, effects/filters/stickers, and version differences. - `docs/README.md` — thin docs index pointing at `draft-schema/` and the existing top-level docs (`RELEASE.md`, `UPSTREAM.md`, `COMPATIBILITY.md`). - `release-notes/` — per-version GitHub release-notes drafts (this directory). Each release tag pulls its body from the matching file. - `COMPATIBILITY.md`, `UPSTREAM.md`, `RELEASE.md` — meta-docs moved from the upstream planning vault into the repo root so README + CHANGELOG cross-links resolve on GitHub and in the npm tarball. ### Changed - `README.md` — full rewrite: tagline + comparison table (vs upstream `cutcli` and `capcut-cli`) + Quickstart + command index + pointers to `skills/capcut-david/SKILL.md` and `docs/draft-schema/`. - `package.json` — `version` → `0.5.0`. `files` array extended to ship `skills/`, `docs/`, `release-notes/`, `CHANGELOG.md`, `COMPATIBILITY.md`, `UPSTREAM.md`, `RELEASE.md` with the npm package alongside the existing `dist/`, `templates/`, `README.md`, `LICENSE`, `NOTICE`. ### Compatibility - CapCut: same as 0.4.0 (≥ 5.x desktop / JianYing 移动剪辑 ≥ 12.x). - Node: `engines.node >= 18` (unchanged). - Runtime deps: still zero. ## [0.4.0] — 2026-05-12 Phase D — the `psycho-build` YAML manifest pipeline. A single command that composes the existing creation primitives (`init` + `add-video` × N + `ken-burns` × N + `add-audio` × 2 + `add-text` × M) into a complete TikTok-format (1080×1920) draft. Zero new draft-writing code lives in the pipeline module — it orchestrates only. ### Added - `capcut-david psycho-build [--out ] [--seed ]` — consumes a YAML manifest describing images (each with optional `ken_burns`), an optional voice track, optional music track (statically ducked via `volume`), and optional SRT-driven captions with a style preset. Produces a draft directory ready to open in CapCut. - `src/commands/pipeline.ts` — hand-rolled YAML subset parser (block + flow mappings/sequences, scalars, quoted strings, comments, line-numbered errors), hand-rolled SRT parser (HH:MM:SS,mmm timing, multi-line text, CRLF tolerant, optional index line), manifest validator with field-level error messages, mulberry32 + FNV-1a seeded UUID generator for deterministic builds (RFC 4122 v4 layout). - `--seed ` global flag — same seed + same manifest → byte-identical draft. Seed may also live in the manifest under `seed:` (the CLI flag wins). - `examples/psycho/manifest.example.yaml` + placeholder assets (`assets/img{1,2,3}.jpg`, `assets/narration.mp3`, `assets/ambient.mp3`, `assets/captions.srt`) + `examples/psycho/README.md` Quickstart. - `templates/minimal/draft_content.json` — bundled empty-draft template for `init`-style operations from the pipeline (shipped via `package.json:files`). - `test/pipeline.test.mjs` — 39 new tests (212 total): YAML parser units (scalars, quoted strings, nested blocks, flow values, comments, errors), SRT parser units (3-entry blocks, multiline text, CRLF, missing index, empty input, malformed timestamps), manifest validator coverage (every required field's specific error message), duration parser, seeded UUID determinism, full E2E build vs the example manifest with structural assertions, determinism check (same seed twice → identical draft modulo volatile path fields), different-seed-different-ids check, and three CLI-level happy/error paths. ### Changed - `--help` adds a new `Pipeline:` section documenting `psycho-build`. - `src/utils/companion.ts` — `setUuidProvider(fn | null)` is new and lets pipeline.ts swap `randomUUID` for a seeded generator without touching any other module. Existing UUID semantics unchanged when no provider is installed. - `package.json` — `files` includes `templates/` so the bundled minimal draft template ships with the npm package. ### Compatibility - CapCut: same as 0.3.0 (≥ 5.x desktop / JianYing 移动剪辑 ≥ 12.x). - Node: `engines.node >= 18` (unchanged). - Runtime deps: still zero. Pipeline is built entirely on Node stdlib. ## [0.3.0] — 2026-05-12 Phase C — creation primitives: keyframes and Ken Burns. Two new commands, zero behavioral change to existing surface. ### Added - `capcut-david add-keyframe