davinci-resolve-mcp 2.95.1 → 2.95.2

package/CHANGELOG.md

@@ -2,6 +2,53 @@
 
 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.95.2
+
+Adds the live round-trip harness the offline `.drp` tier never had — the absence
+of which is why three unbacked "verified live" claims survived in its README, one
+reaching a shipped `api_truth` recommendation before being caught.
+
+### Added — `tests/live_drp_roundtrip_verification.py`
+
+Authors a `.drp` per primitive, imports it into a running Resolve, asserts intent
+against structural readback, **and exports the composited frame to assert the
+item is actually visible on screen.**
+
+That last assertion is the whole point. `place_fusion_title` satisfies every
+structural check — right track, frame, duration, `PrettyType`, and correctly
+encoded text — while rendering nothing, so a harness that only diffed
+`GetStart()`/`GetDuration()` would have called it green. Visibility is measured
+with `Project.ExportCurrentFrameAsStill` plus a luma pass: an inert item yields
+`max=0` across the entire frame, a real one does not (the live control returns
+`max=255` with ~16k bright pixels).
+
+**Known-broken cases are declared, not skipped.** `place_fusion_title` is
+recorded as `KNOWN BROKEN`; if it starts working the harness reports `UNEXPECTED
+PASS` and fails, forcing the docs that describe it to be updated.
+
+Current state on Studio 21.0.4.5: **7 passed, 1 known-broken, 0 needing
+attention** — media placement, blade, trim, cross-track move, and generator
+visibility all verified end to end.
+
+### Fixed — the `RESOLVE_VERIFY=1` gate was unrunnable
+
+It ran a single test that threw `TODO — implement once fixtures land`, so the
+flag reported a failing suite and everyone learned to ignore it. A gate nobody
+can run green is worse than no gate. It is now a documented skip pointing at the
+harness above, and `RESOLVE_VERIFY=1 npm test` is clean.
+
+### Changed — release process states the rule
+
+"The file round-trips" and "Resolve honours it" are different claims; only a live
+import establishes the second. Changes to the offline `.drp` tier must run the
+harness, and a doc may not say "verified live" unless a runnable command produced
+that result.
+
+The harness is also robust to `DeleteProject`'s session lock: projects opened in
+a session cannot be deleted until Resolve restarts, so it steps off the current
+project, retries, falls back to run-unique names rather than colliding, and
+reports what it could not remove instead of failing silently.
+
 ## What's New in v2.95.1
 
 Withdraws a recommendation this project shipped two releases ago. **`drp

package/README.md

@@ -2,7 +2,7 @@
 
 English | [简体中文](README.zh-CN.md)
 
-[![Version](https://img.shields.io/badge/version-2.95.1-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-2.95.2-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-34%20(353%20full)-blue.svg)](#server-modes)

package/README.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](README.md) | 简体中文
 
-[![Version](https://img.shields.io/badge/version-2.95.1-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-2.95.2-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-34%20(353%20full)-blue.svg)](#服务器模式)
@@ -12,7 +12,7 @@
 [![Python](https://img.shields.io/badge/python-3.10+-green.svg)](https://www.python.org/downloads/)
 [![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
-> 本翻译对应 v2.95.1 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
+> 本翻译对应 v2.95.2 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
 
 一个 Model Context Protocol (MCP) 服务器，让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio（达芬奇）。它提供完整的 API 覆盖，外加带护栏的工作流助手，涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发，以及不碰源媒体的媒体分析。
 

package/docs/process/release-process.md

@@ -113,6 +113,26 @@ Resolve validation before release. Use disposable projects and synthetic media
 only. Never modify, transcode, proxy, or create derivatives of source media
 unless the user explicitly requests it.
 
+**Changes to the offline `.drp` authoring tier must run the round-trip harness,
+and a structural readback is NOT sufficient evidence on its own:**
+
+```bash
+RESOLVE_VERIFY=1 venv/bin/python tests/live_drp_roundtrip_verification.py
+```
+
+It authors a `.drp` per primitive, imports it into Resolve, asserts intent
+against structural readback, **and exports the composited frame to assert the
+item is visible on screen.** That last assertion exists because
+`place_fusion_title` passes every structural check — right track, frame,
+duration, type, and correctly-encoded text — while rendering nothing. Anything
+that only diffs `GetStart()`/`GetDuration()` will call that green. Known-broken
+cases are declared in the harness rather than skipped, so a fix reports
+`UNEXPECTED PASS` and fails until the docs describing it are updated.
+
+The same rule generalises: **"the file round-trips" and "Resolve honours it" are
+different claims.** Only a live import establishes the second one. Do not write
+"verified live" in a doc unless a runnable command produced that result.
+
 Examples:
 
 ```bash

package/install.py

@@ -36,7 +36,7 @@ from src.utils.update_check import (
 
 # ─── Version ──────────────────────────────────────────────────────────────────
 
-VERSION = "2.95.1"
+VERSION = "2.95.2"
 # 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.95.1",
+  "version": "2.95.2",
   "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
   "license": "MIT",
   "author": "Samuel Gursky <samgursky@gmail.com>",

package/resolve-advanced/vendor/drp-format/README.md

@@ -1,8 +1,24 @@
 # drp-format — offline DaVinci Resolve project authoring & editing
 
 Read, author, and edit **real, importable** DaVinci Resolve 21 projects (`.drp`) and timelines
-(`.drt`) as files — no Resolve required. Everything here is verified by a live round-trip
-(author/edit → `import_project` → `lint`/`clip_where` → re-export decode), not just self-parse.
+(`.drt`) as files — no Resolve required.
+
+> **How to verify a claim in this file.** This README previously said "everything here is verified
+> by a live round-trip". It was not: the gate it referred to threw `TODO — implement once fixtures
+> land`, so nobody ever ran it green, and three unbacked "verified live" claims survived here —
+> one of which reached a shipped `api_truth` recommendation before being caught. The round-trip
+> that actually exists is:
+>
+> ```bash
+> RESOLVE_VERIFY=1 venv/bin/python tests/live_drp_roundtrip_verification.py
+> ```
+>
+> It authors a `.drp` per primitive, imports it into a running Resolve, asserts intent against
+> structural readback, **and exports the composited frame to assert the item is visible on
+> screen.** That last check is the point: `place_fusion_title` satisfies every structural
+> assertion — correct track, frame, duration, type, and text encoded in the blob — while
+> rendering nothing. Structure alone cannot tell you a thing works. Known-broken cases are
+> declared in the harness, so a fix reports `UNEXPECTED PASS` and forces the docs to be updated.
 
 Background + the full schema map: `docs/design/drp-drx-drt-closeout-harness/knowledge/resolve21-schema-reconciliation.md`
 and `.../resolve-authoring-completion.md`.

package/resolve-advanced/vendor/drp-format/__tests__/inject-grades.test.js

@@ -18,7 +18,6 @@ const os = require('node:os');
 const JSZip = require('jszip');
 
 const drpFormat = require('..');
-const { resolveVerifyTest } = require('./_resolve-verify');
 
 // A plausible-shaped synthetic body. The injector does not parse the bytes,
 // only substitutes them. Hex characters only.
@@ -229,10 +228,19 @@ test('injectGrades: internals — extractDrxBodyHex throws on missing Body', ()
 // the byte-identical-render check requires Resolve. When the env flag is
 // unset the test skips with a clear marker.
 
-resolveVerifyTest('injectGrades: rendered frame matches direct DRX apply', async () => {
-  // The harness's resolve-verifications.md has the full recipe. The actual
-  // implementation will live here once a captured fixture + a Resolve session
-  // is in flight. Until then it's a placeholder that exists to demonstrate
-  // the resolveVerifyTest gate and to surface in the skip list as a TODO.
-  throw new Error('TODO — implement once fixtures/inject-target.drp + Resolve session land');
-});
+// NOT a throwing placeholder any more. It used to `throw new Error('TODO ...')`,
+// which meant RESOLVE_VERIFY=1 reported a FAILING suite and everyone learned to
+// ignore the flag — which is a large part of why this package carried three
+// unbacked "verified live" claims. A gate nobody can run green is worse than no
+// gate. The live round-trip that DOES exist now lives on the Python side, where
+// the Resolve scripting API is reachable directly:
+//
+//   RESOLVE_VERIFY=1 venv/bin/python tests/live_drp_roundtrip_verification.py
+//
+// It authors a .drp per primitive, imports it into Resolve, asserts intent
+// against structural readback AND exports the composited frame to assert the
+// item is actually VISIBLE — the check that catches place_fusion_title, which
+// passes every structural assertion while rendering nothing.
+test.skip('injectGrades: rendered frame matches direct DRX apply '
+  + '(covered by tests/live_drp_roundtrip_verification.py — grade-render compare still TODO)',
+() => {});

package/src/granular/common.py

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

package/src/server.py

@@ -11,7 +11,7 @@ Usage:
     python src/server.py --full       # Start the 353-tool granular server instead
 """
 
-VERSION = "2.95.1"
+VERSION = "2.95.2"
 
 import base64
 import os