davinci-resolve-mcp 2.97.4 → 2.97.6

package/CHANGELOG.md

@@ -2,6 +2,96 @@
 
 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.97.6
+
+**On Windows the server could not see the Resolve it was driving.** Reported in
+[#150](https://github.com/samuelgursky/davinci-resolve-mcp/issues/150) with the
+root cause traced, the fix proposed, and a case table — all of it correct.
+
+### Fixed
+
+- **`runtime_mode` reported `running: false, instances: 0` on every stock
+  Windows install.** WMIC wraps a command line in double quotes when the
+  executable path contains spaces, which the default install path always does
+  (`"C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe"`). The
+  line therefore *ends* with `"`, and `_is_resolve_command()` required it to end
+  with `Resolve.exe`. The trailing-flag stripper above the test did not help: it
+  removes ` -flag` tokens and leaves the closing quote as the final character.
+  A leading quote is now read for what it is — the executable is what sits
+  inside the first quoted span, and everything after the closing quote is
+  arguments. That also tightens rejection: `"…\cmd.exe" /c start … Resolve.exe`
+  is a launcher, not an instance.
+
+  The reading was the visible half. The consequential half is that
+  `get_resolve()` asks this same question before auto-launching, precisely so a
+  failed connect to a live Resolve does not open a second application — the
+  guard whose comment records being "reported three times before it was
+  traced". On Windows its input was a permanent `False`, so the path it exists
+  to block was open: connect fails (modal dialog, mid-launch, scripting toggled
+  off) → "nothing is running" → launch a second Resolve. `_not_connected_error()`
+  reads the same signal, so a Windows user whose Resolve *was* running got the
+  "not running, auto-launch failed, check your Studio install" text instead of
+  the preference or bridge fix that actually applied. `headless` was
+  unreachable too — it is only computed once something is found running, so
+  `-nogui` instances were indistinguishable on Windows.
+
+- **A successful install ended in a traceback under a redirected stdout.** The
+  installer prints box-drawing and check-mark glyphs. A Windows console carries
+  them, but redirecting stdout falls back to the locale code page — cp1252 by
+  default — and `print(f"  {'─' * 50}")` in the summary raised
+  `UnicodeEncodeError` after every client had already been configured, so a
+  working run looked like a failed one
+  (`npx davinci-resolve-mcp setup --clients manual 2>&1 | tail`). Streams that
+  cannot encode those glyphs are now reconfigured to UTF-8 with
+  `errors="replace"`; a console that can already carry them is left alone
+  rather than re-encoded underneath the user.
+
+### Added
+
+- `tests.test_headless_runtime` covers the quoted Windows command line —
+  bare, trailing-whitespace (what WMIC actually prints), and `-nogui` — plus
+  the quoted-launcher line that must still be rejected, so the fix cannot
+  become a substring test by another route. `tests.test_cdl_and_install_config`
+  gains `ConsoleEncodingTests`, including a child interpreter run with
+  `PYTHONIOENCODING=cp1252` and a piped stdout: the exact shape of the reported
+  failure. Both suites fail on the pre-fix code.
+
+## What's New in v2.97.5
+
+**`npm ci` was failing outright, and nothing in the release path noticed.**
+No server behavior changed; this is packaging and release-process hardening.
+
+### Fixed
+
+- **`package-lock.json` was seven releases stale.** It still carried
+  `2.90.0`, and — the part that actually broke things — two
+  `optionalDependencies` added since then, `js-yaml` and `pg`, were never
+  locked. `npm ci` refuses to install at all when the lockfile and
+  `package.json` disagree, so every reproducible install path failed with
+  `EUSAGE — Missing: js-yaml@4.3.1 from lock file` (plus `pg` and its nine
+  transitive deps). CI, fresh contributor clones, and container builds all hit
+  it. `npm install` and `npm publish` resolve independently of the lockfile
+  and stayed green throughout, which is why it survived seven releases.
+  Regenerated with `npm install --package-lock-only`; `npm ci` now installs
+  175 packages clean.
+
+### Added
+
+- **`tests.test_import::test_package_lock_in_sync`** — asserts both version
+  fields in the lockfile match `package.json`, and that the root
+  `dependencies` / `devDependencies` / `optionalDependencies` blocks match
+  exactly. The second half is the one that matters: the version fields being
+  right is not evidence `npm ci` works, and dependency drift is what actually
+  breaks it. Verified to fail on each drift mode independently.
+
+### Changed
+
+- `docs/process/release-process.md` lists `package-lock.json` under "Files To
+  Update" with the regeneration command, and Required Validation now
+  regenerates the lockfile before `test_import` reads it. The lockfile was
+  never on the checklist, which is why the drift was never a step anyone
+  skipped — it was a step that did not exist.
+
 ## What's New in v2.97.4
 
 **Drift is caught at the edit, not at publish time.** Tooling and docs only —

package/README.md

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

package/docs/process/release-process.md

@@ -26,6 +26,14 @@ Every release bump must update all version surfaces:
 - `src/granular/common.py`
 - `install.py`
 - `package.json`
+- `package-lock.json` — regenerate with `npm install --package-lock-only`, do
+  not hand-edit the version. It carries the version in two places and, more
+  importantly, the resolved dependency tree. When it disagrees with
+  `package.json`, **`npm ci` refuses to install at all** (`EUSAGE — Missing: X
+  from lock file`), which breaks CI, fresh clones, and container builds while
+  `npm install` and `npm publish` stay green and hide it. The
+  `tests.test_import` guard `test_package_lock_in_sync` fails the suite on
+  either drift.
 - README version badge
 - README current stats or latest-release summary when they changed
 - `README.zh-CN.md` — the Simplified Chinese translation. Update its version
@@ -62,6 +70,7 @@ Always run static checks before release:
 
 ```bash
 venv/bin/python tests/test_import.py
+npm install --package-lock-only --no-audit --no-fund   # re-stage package-lock.json if it moved
 venv/bin/python scripts/audit_api_parity.py
 venv/bin/python scripts/gen_api_limitations.py --check
 node scripts/agent-rules/generate.mjs --check
@@ -72,6 +81,13 @@ npm pack --dry-run
 git diff --check
 ```
 
+`test_import` carries `test_package_lock_in_sync`, which is the actual gate on the
+lockfile: it asserts both version fields and the root dependency blocks match
+`package.json`. Run the `npm install --package-lock-only` line above first so the
+regeneration is in the working tree when the test reads it — that ordering is why
+the check is a regeneration followed by a test, not a `git diff --exit-code`,
+which would fire on the release bump's own legitimate change.
+
 `test_duplicate_definitions` asserts no module-level name is defined twice under
 `src/`. A second `def foo` silently replaces the first, and in a module the size
 of `src/server.py` the two can be thousands of lines apart with different

package/install.py

@@ -37,7 +37,7 @@ from src.utils.update_check import (
 
 # ─── Version ──────────────────────────────────────────────────────────────────
 
-VERSION = "2.97.4"
+VERSION = "2.97.6"
 # 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
@@ -46,6 +46,42 @@ VERSION = "2.97.4"
 SUPPORTED_PYTHON_MIN = (3, 10)
 PYTHON_ABI_RISK_MIN = (3, 13)
 
+# ─── Console encoding ─────────────────────────────────────────────────────────
+# This installer prints box-drawing and check-mark glyphs. On Windows a console
+# stdout carries them fine, but a *redirected* stdout falls back to the locale
+# code page — cp1252 on a default Windows install — and the first '─' raises
+# UnicodeEncodeError. It fires at the summary, after every client is already
+# configured, so a successful install ends in a traceback and reads as a failed
+# run. Reported in #150 against
+# `npx davinci-resolve-mcp setup --clients manual 2>&1 | tail`.
+#
+# Only streams that cannot already carry the glyphs are touched, so a correctly
+# configured console keeps its own encoding. 'replace' is belt-and-braces: no
+# output path is worth a traceback.
+
+_GLYPH_PROBE = "─→✓⊘•"
+
+def _ensure_glyph_capable_stdio():
+    for stream in (sys.stdout, sys.stderr):
+        reconfigure = getattr(stream, "reconfigure", None)
+        encoding = getattr(stream, "encoding", None)
+        if reconfigure is None or not encoding:
+            continue
+        try:
+            _GLYPH_PROBE.encode(encoding)
+            continue
+        except (LookupError, UnicodeEncodeError):
+            pass
+        try:
+            reconfigure(encoding="utf-8", errors="replace")
+        except Exception:
+            try:
+                reconfigure(errors="replace")
+            except Exception:
+                pass
+
+_ensure_glyph_capable_stdio()
+
 # ─── Colors (disabled on Windows cmd without ANSI support) ────────────────────
 
 def _supports_color():

package/package.json

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

package/src/granular/common.py

@@ -87,7 +87,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "2.97.4"
+VERSION = "2.97.6"
 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.97.4"
+VERSION = "2.97.6"
 
 import base64
 import os

package/src/utils/resolve_runtime.py

@@ -83,8 +83,13 @@ def _process_lines() -> Optional[List[str]]:
         return None
 
 
+def _matches_pattern(executable: str) -> bool:
+    """Does this bare executable path name a Resolve application?"""
+    return any(executable.endswith(pattern) for pattern in RESOLVE_PROCESS_PATTERNS)
+
+
 def _is_resolve_command(line: str) -> bool:
-    """Is this command line a Resolve *executable*, not merely a mention of one?
+    r"""Is this command line a Resolve *executable*, not merely a mention of one?
 
     A plain substring test matches any process whose command line happens to
     contain the path — including a shell running a script that references it.
@@ -96,8 +101,22 @@ def _is_resolve_command(line: str) -> bool:
     flags. So strip trailing flag tokens and require what remains to *end* with
     the pattern. That survives the spaces in "DaVinci Resolve.app" (no splitting
     on whitespace) while rejecting a path buried mid-command.
+
+    Windows quotes that path. WMIC prints the executable wrapped in double
+    quotes whenever it contains spaces, which the default install path always
+    does (`"C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe"`),
+    so the line ends in `"` and `endswith("Resolve.exe")` was false on every
+    stock Windows machine — `runtime_mode` reported nothing running while the
+    same server was driving that very instance, and the second-instance guard
+    in `get_resolve()` lost its input. Reported in #150. A leading quote means
+    the executable is exactly what sits inside the first quoted span; anything
+    after the closing quote is arguments, and the flag loop never sees it.
     """
     text = line.strip()
+    if text.startswith('"'):
+        close = text.find('"', 1)
+        if close > 1:
+            return _matches_pattern(text[1:close])
     while True:
         stripped = text.rstrip()
         cut = stripped.rfind(" -")
@@ -109,7 +128,7 @@ def _is_resolve_command(line: str) -> bool:
         if not candidate:
             break
         text = candidate
-    return any(text.endswith(pattern) for pattern in RESOLVE_PROCESS_PATTERNS)
+    return _matches_pattern(text)
 
 
 def resolve_processes() -> Optional[List[str]]: