davinci-resolve-mcp 2.44.0 → 2.45.0

package/CHANGELOG.md

@@ -2,6 +2,46 @@
 
 Release history for the DaVinci Resolve MCP Server. The latest release is summarized in the root README; older entries live here to keep the README focused.
 
+## What's New in v2.45.0
+
+The edit engine — Phase E, the final phase of the analysis + edit-engine
+program. Three evidence-driven loops on one shared skeleton: evidence query
+→ dry-run plan with per-decision rationale → confirm token → versioned
+timeline ops → metric readback → brain_edits rows.
+
+- **Added** a new `edit_engine` MCP tool (compound tool count: 34):
+  - `plan_selects` / `execute_selects` — ranks shots by deep-tier
+    `editorial.select_potential` and best moments (clip-level fallback for
+    standard-analyzed clips), story-spine order, duration budget; execution
+    builds a NEW selects timeline from per-shot source ranges. Additive.
+  - `plan_tighten` / `execute_tighten` — dead-air lifts from transcript-gap
+    evidence per timeline item (no transcript → reported in `skipped`,
+    never silently trimmed); execution assembles a tightened VARIANT
+    timeline from keep ranges (true partial trims via the range-copy
+    kernel) — the original timeline is never mutated.
+  - `plan_swap` / `execute_swap` — alternates for a timeline item via the
+    visual-similarity index, filtered to shots that can fill the slot
+    exactly; execution replaces the item in place (lift + positioned
+    append) on the version-archived timeline.
+  - `list_plans` / `get_plan` — plans persist under `memory/edit_plans/`
+    with content fingerprints; a stale or tampered plan refuses to execute.
+- **Added** `src/utils/edit_engine.py` (DB-only planning/evidence layer) and
+  `tests/live_edit_engine_validation.py` (disposable-project live harness).
+  execute_* actions are confirm-token gated and registered with the
+  version-on-mutate hook (archive + brain_edits come from the same
+  machinery as every other destructive op).
+- **Fixed** frame→shot mapping in the analysis store: frames now fall back
+  to time-containment when a report's shots don't record
+  `frame_indices_used` (commit paths that omit it previously produced no
+  shot-level visual vectors).
+- **Validation**: full offline suite (1118 tests; 13 new). Live pilot on a
+  disposable synthetic-media Resolve project (ffmpeg + spoken audio):
+  20/20 checks — selects timeline assembled (2 decisions), tighten variant
+  removed exactly the 15.2s of transcript dead air while keeping the
+  spoken 4.8s (original untouched), swap replaced the item with a 0.92
+  cosine alternate, brain_edits rationale rows present for all three
+  loops, timeline versions archived.
+
 ## What's New in v2.44.0
 
 Cross-clip entities + bin briefing v2 — Phase D of the analysis +

package/README.md

@@ -1,9 +1,9 @@
 # DaVinci Resolve MCP Server
 
-[![Version](https://img.shields.io/badge/version-2.44.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-2.45.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
 [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
 [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
-[![Tools](https://img.shields.io/badge/MCP%20Tools-33%20(341%20full)-blue.svg)](#server-modes)
+[![Tools](https://img.shields.io/badge/MCP%20Tools-34%20(341%20full)-blue.svg)](#server-modes)
 [![Tested](https://img.shields.io/badge/Live%20Tested-98.5%25-green.svg)](docs/reference/api-coverage.md#test-results)
 [![DaVinci Resolve](https://img.shields.io/badge/DaVinci%20Resolve-18.5+-darkred.svg)](https://www.blackmagicdesign.com/products/davinciresolve)
 [![Python](https://img.shields.io/badge/python-3.10+-green.svg)](https://www.python.org/downloads/)
@@ -49,7 +49,7 @@ The command starts a localhost server and opens the control panel in your browse
 
 | Mode | Entry point | Tools | Best for |
 |------|-------------|-------|----------|
-| Compound | `src/server.py` | 33 | Default mode for most assistants. Related Resolve operations are grouped behind action parameters to keep context usage low. |
+| Compound | `src/server.py` | 34 | Default mode for most assistants. Related Resolve operations are grouped behind action parameters to keep context usage low. |
 | Full / granular | `src/server.py --full` or `src/resolve_mcp_server.py` | 341 | Power users who want one MCP tool per Resolve API method. |
 
 The compound server is recommended unless you specifically need the granular one-tool-per-method surface.

package/docs/SKILL.md

@@ -671,6 +671,41 @@ only when that mutation is intentional.
 
 ### Timelines
 
+**`edit_engine`** — Evidence-driven edit loops (v2.45.0+): selects assembly,
+tighten, swap.
+
+Every loop is plan → confirm → execute. plan_* actions are dry-run by
+construction: they query the DB-canonical analysis store and return a
+per-decision rationale plus a stored `plan_id` (plans persist under
+`memory/edit_plans/` with a content fingerprint, so a stale plan cannot run
+against a changed project). execute_* actions require a `confirm_token`, run
+under the version-on-mutate hook, and return before/after duration and
+clip-count readback plus `brain_edits` rationale rows.
+
+- `plan_selects(min_select_potential?, max_duration_seconds?, max_shots?,
+  timeline_name?, analysis_root?)` — ranks shots by deep-tier
+  `editorial.select_potential` / best moments (clip-level fallback for
+  standard-analyzed clips), story-spine order.
+  `execute_selects(plan_id)` creates a NEW selects timeline from the plan's
+  per-shot source ranges — additive; nothing existing is touched.
+- `plan_tighten(timeline_name?, target_ratio?, min_pause_seconds?,
+  handle_seconds?)` — dead-air lifts from transcript-gap evidence for each
+  timeline item (items without transcripts are reported in `skipped`, never
+  silently trimmed). `execute_tighten(plan_id)` assembles a tightened
+  VARIANT timeline from the plan's keep ranges — true partial trims; the
+  original timeline is never mutated.
+- `plan_swap(timeline_start_frame | item_name, kind="visual"|"text",
+  limit?)` — alternates for one timeline item via the similarity index,
+  filtered to shots long enough to fill the slot exactly.
+  `execute_swap(plan_id, alternate_index)` replaces the item in place
+  (lift + positioned append at the same record frame) on the
+  version-archived timeline.
+- `list_plans(limit?)` / `get_plan(plan_id)`.
+
+The engine needs the analysis substrate: analyzed clips in the DB (run
+`db_ingest` on older roots), transcripts for tighten, and visual embeddings
+(`build_embeddings(kinds=['visual'])`) for swap.
+
 **`timeline_versioning`** — Version-on-mutate, archive, rollback, brain-edit history (C6).
 
 Every destructive timeline op (compound, captions, ripple delete, gap close,

package/install.py

@@ -35,7 +35,7 @@ from src.utils.update_check import (
 
 # ─── Version ──────────────────────────────────────────────────────────────────
 
-VERSION = "2.44.0"
+VERSION = "2.45.0"
 # Only hard floor: mcp[cli] requires Python 3.10+. There is no upper bound —
 # Resolve's scripting bridge loads into newer interpreters on recent builds
 # (Python 3.14 verified against Resolve Studio 20.3.2). Older Resolve builds

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "davinci-resolve-mcp",
-  "version": "2.44.0",
+  "version": "2.45.0",
   "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
   "license": "MIT",
   "author": "Samuel Gursky <samgursky@gmail.com>",

package/src/granular/common.py

@@ -80,7 +80,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "2.44.0"
+VERSION = "2.45.0"
 logger = logging.getLogger("davinci-resolve-mcp")
 logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
 logger.info(f"Detected platform: {get_platform()}")