davinci-resolve-mcp 2.224.0 → 2.224.2

package/CHANGELOG.md

@@ -2,6 +2,108 @@
 
 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.224.2 — offline authoring works on Windows
+
+Contributed by @Dev-next-gen (#221), found and verified on Windows.
+
+### Fixed
+
+- **`timeline(action="author_offline")` failed for every target on Windows
+  before writing anything.** The authoring bridge,
+  `scripts/author_interchange.mjs`, handed a filesystem path straight to a
+  dynamic `import()`. On macOS and Linux that is harmless; on Windows the path
+  is `C:\...`, and Node's ESM loader reads the drive letter as a URL scheme
+  `c:` and refuses it with `ERR_UNSUPPORTED_ESM_URL_SCHEME`. Because the import
+  runs before target validation, even the bridge's own error for an unknown
+  target never appeared. The path is now wrapped in `pathToFileURL(...).href`.
+  Nothing changes on macOS or Linux.
+- This is the second time the same bug has shipped: the launcher hit it first
+  and was fixed the same way in 06d5bd6 (2026-07-15), and the authoring bridge,
+  added later, repeated it. CI runs only on Linux, which cannot see it, so it
+  stayed green both times.
+
+### Added
+
+- **A static guard so it cannot ship a third time.** A new test fails if any
+  dynamic `import()` in `scripts/*.mjs` or `bin/*.mjs` is given anything other
+  than a string literal or `pathToFileURL(...)`. Checked statically precisely
+  because no Linux run can observe the failure. Verified here that it earns its
+  place: run against the unfixed bridge it fails naming exactly
+  `scripts/author_interchange.mjs:45`, and passes with the fix.
+
+### Validation
+
+- Full suite green: 3,485 passed, 1 skipped.
+- A repo-wide scan for non-literal dynamic imports, including
+  `resolve-advanced/server/` which the new guard does not cover, found only the
+  two launcher imports already fixed in 06d5bd6 and the one fixed here — so the
+  fix is complete, not a first instance of several.
+- **Not verified on Windows hardware by this project — there is none here.**
+  The Windows failure and the fix were measured by @Dev-next-gen on Python 3.12
+  and Node 25: two failures and four errors on main, all eight passing with the
+  change. The `.drt` authoring cases additionally need `jszip` from the
+  `resolve-advanced` install, which that machine did not have; they now get
+  past the import — the only part this touches — and stop at the missing
+  module instead.
+
+## What's New in v2.224.1 — the bridge installer explains the outcome it was built to detect
+
+Reported by @hemna (#219). No behaviour changed; the installer writes exactly
+what it wrote before and says considerably more about it.
+
+### Fixed
+
+- **The canary-only outcome had no printed guidance at all.** Seeing
+  `resolve_bridge_canary` in Workspace ▸ Scripts while `resolve_bridge_probe`
+  is absent is not a failed install — it is the single most informative thing
+  the installer can tell you, and the exact signal the Lua canary exists to
+  produce. But the printed steps were a fixed four-line list that assumed the
+  Python probe had listed, so a user in this case followed step 3 to a menu
+  entry that cannot exist. The explanation was written down the whole time —
+  inside the canary's own Lua comments, which nobody has any reason to open.
+  There is now a real branch for it that says the install worked, says not to
+  re-run it, and explains what the missing probe means.
+- **Duplicate canary entries are now expected rather than alarming.** The
+  installer writes into every Scripts/Utility folder Resolve scans, giving the
+  canary the same filename in each, so Resolve lists it once per folder with no
+  way to tell them apart. The reporter saw two and reasonably read it as a
+  broken install; a real run on the maintainer's machine produces **four**. The
+  guidance now names the number and says running any one of them is the same as
+  running any other. The count is derived from what was actually installed, and
+  the filename now has a single definition shared by the writer and the
+  counter — those two disagreeing would produce guidance promising entries that
+  are not there.
+- **The Console is named.** The canary reports through `print()`, which lands in
+  Workspace ▸ Console and nowhere else. The installer had never mentioned the
+  Console — the string does not appear in it — so running the canary with no
+  Console open looks exactly like nothing happening, which is what was
+  reported.
+
+### Changed
+
+- The canary-only explanation is **split by edition instead of asserting a
+  single cause**. The canary's own text predates Resolve 21.1 and blames Python
+  discovery — `PYTHON3HOME`, then `/usr/local/bin/python3`, and nowhere else.
+  That is still right on Studio and on 21.0.x and earlier, but on **free 21.1
+  it is wrong**: Python scripting moved to the Studio edition (#203), so `.py`
+  files do not list there whatever Python is installed, and the older advice
+  would send a user chasing a setting that cannot fix their problem. Both
+  branches are now stated, newer cause first.
+
+### Validation
+
+- Full suite green: 3,484 passed, 1 skipped. Six new tests cover the duplicate
+  count and its wording, the absence of that wording for a single canary, the
+  canary-only branch, the Console pointer, both edition branches with the
+  newer one ordered first, and the single-definition guarantee on the canary
+  filename.
+- Verified by running the installer for real on this machine, which is where
+  the four-entry figure comes from.
+- **Still open in #219**: the canary's own embedded remediation text carries
+  the pre-21.1 single-cause diagnosis. Correcting what it says to a specific
+  user needs their edition, which has been asked for; the printed guidance
+  above no longer depends on that answer.
+
 ## What's New in v2.224.0 — native Resolve 21.1 DCTL encryption
 
 Contributed by @legionsound (#216), live-validated on Studio 21.1.0.14.

package/README.md

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

package/install.py

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

package/scripts/install_resolve_bridge.py

@@ -281,6 +281,11 @@ _FRAMEWORK_PYTHON_ROOTS = (
 #: PYTHON3HOME is unset. This is the one python.org's installer creates.
 _FALLBACK_PYTHON3 = Path("/usr/local/bin/python3")
 
+#: Filename of the Lua enumeration canary. Named once: the installer writes it
+#: and the post-install guidance counts it, and those two disagreeing is how a
+#: user ends up told to expect entries that are not there.
+_CANARY_NAME = "resolve_bridge_canary.lua"
+
 _LUA_CANARY = """-- Installed by davinci-resolve-mcp as an enumeration canary.
 -- If THIS appears under Workspace > Scripts but resolve_bridge_probe does not,
 -- Resolve is listing Lua and silently skipping Python: it cannot find a Python 3.
@@ -650,7 +655,7 @@ def _install_to(target: Path, *, probe_only: bool, installed: list[str]) -> None
         installed.append(str(target / probe))
     # Lua always enumerates; Python only with a framework install. The canary
     # makes "Python not detected" distinguishable from "wrong folder".
-    canary = target / "resolve_bridge_canary.lua"
+    canary = target / _CANARY_NAME
     canary.write_text(_LUA_CANARY, encoding="utf-8")
     installed.append(str(canary))
     if probe_only:
@@ -686,6 +691,65 @@ def _install_to(target: Path, *, probe_only: bool, installed: list[str]) -> None
     installed.append(str(launcher_path))
 
 
+def canary_count(result: dict) -> int:
+    """How many identical `resolve_bridge_canary` entries Resolve will list.
+
+    One per Scripts/Utility folder installed into, all with the same filename,
+    so they are indistinguishable in the menu. Reported in issue #219 by a user
+    who reasonably read two identical entries as a broken install.
+    """
+    return sum(1 for path in result.get("installed", [])
+               if str(path).endswith(_CANARY_NAME))
+
+
+def next_steps(result: dict) -> list:
+    """The post-install instructions, as lines.
+
+    Built rather than printed inline so the canary-only branch is testable: it
+    is the single most likely outcome on macOS and, until issue #219, the only
+    one the installer had no words for. The user followed step 3 to a menu
+    entry that cannot exist, and the explanation was sitting in a Lua comment
+    they had no reason to open.
+    """
+    lines = [
+        "Next:",
+        "  1. Restart DaVinci Resolve so it re-scans the Scripts folders.",
+        "  2. Open a saved project (the Scripts menu is empty in Project Manager).",
+        "  3. Workspace > Scripts > resolve_bridge_probe  — run it TWICE.",
+        # The probe runs INSIDE Resolve, which never sees the shell's
+        # DAVINCI_RESOLVE_BRIDGE_CONFIG — it always writes to the fixed default
+        # directory, so the guidance must not follow the override.
+        "  4. Read ~/.config/davinci-resolve-mcp/host-model-probe.json",
+    ]
+    count = canary_count(result)
+    if count > 1:
+        lines += [
+            "",
+            f"Expect {count} identical 'resolve_bridge_canary' entries — one per Scripts",
+            "folder this installed into. That is normal, not a double install; running",
+            "any one of them is the same as running any other.",
+        ]
+    lines += [
+        "",
+        "If step 3 shows no 'resolve_bridge_probe' and you can only see",
+        "'resolve_bridge_canary':",
+        "  - The install worked. Do not re-run it. That is the canary doing its job:",
+        "    Resolve is enumerating scripts, listing Lua, and skipping Python.",
+        "  - Run 'resolve_bridge_canary' and read its output in Workspace > Console.",
+        "    It reports with print(), not a dialog, so with no Console open it looks",
+        "    like nothing happened.",
+        "  - What it means depends on your edition:",
+        "      * Resolve 21.1+ FREE — Python scripting moved to the Studio edition,",
+        "        so .py files no longer list there at all and no Python setting will",
+        "        change that. See issue #203.",
+        "      * Studio, or 21.0.x and earlier — Resolve cannot find a Python 3. It",
+        "        looks at PYTHON3HOME and then /usr/local/bin/python3 and nowhere",
+        "        else, which is why Homebrew, pyenv, uv and conda builds go unseen.",
+        "        The canary's own output carries the fix.",
+    ]
+    return lines
+
+
 def main() -> int:
     parser = argparse.ArgumentParser(description=__doc__)
     parser.add_argument("--probe-only", action="store_true",
@@ -709,14 +773,8 @@ def main() -> int:
         print("WARNING: " + warning)
         print("!" * 72)
         print()
-    print("Next:")
-    print("  1. Restart DaVinci Resolve so it re-scans the Scripts folders.")
-    print("  2. Open a saved project (the Scripts menu is empty in Project Manager).")
-    print("  3. Workspace > Scripts > resolve_bridge_probe  — run it TWICE.")
-    # The probe runs INSIDE Resolve, which never sees the shell's
-    # DAVINCI_RESOLVE_BRIDGE_CONFIG — it always writes to the fixed default
-    # directory, so the guidance must not follow the override.
-    print("  4. Read ~/.config/davinci-resolve-mcp/host-model-probe.json")
+    for line in next_steps(result):
+        print(line)
     return 0
 
 

package/src/granular/common.py

@@ -87,7 +87,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "2.224.0"
+VERSION = "2.224.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 377-tool granular server instead
 """
 
-VERSION = "2.224.0"
+VERSION = "2.224.2"
 
 import base64
 import os