davinci-resolve-mcp 2.98.0 → 2.98.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,55 @@
2
2
 
3
3
  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.
4
4
 
5
+ ## What's New in v2.98.1
6
+
7
+ **The Bash guard could be walked past with a newline.** Reported and fixed in
8
+ [#152](https://github.com/samuelgursky/davinci-resolve-mcp/pull/152) by
9
+ @fitfam, who found both holes by executing payloads against the hook rather
10
+ than reading it.
11
+
12
+ ### Fixed
13
+
14
+ - **`split_commands()` did not split on newlines.** It knew `&&`, `||`, `;` and
15
+ `|`, so a multi-line block was a single segment: `argv0` came from the first
16
+ line, and a non-mutating first line returned before anything under it was
17
+ looked at. `mkdir -p footage/_superseded` then a newline then
18
+ `mv footage/clip.mp4 footage/_superseded/` passed, while the same two commands
19
+ joined by `;` denied. Either answer is defensible on its own; giving two
20
+ different answers to what a shell treats as the same command is what made the
21
+ guard trainable around.
22
+
23
+ - **The ffmpeg branch exempted an output that equalled an input.** The output
24
+ operand was dropped when it matched a `-i` value — which is exactly
25
+ `ffmpeg -i master.mp4 master.mp4`, the in-place overwrite the hook's own deny
26
+ message calls unrecoverable. Independent of the first hole: the single-line
27
+ form was allowed too.
28
+
29
+ ### Changed
30
+
31
+ - The trailing operand is no longer read as an output when it is the value of a
32
+ `-i` immediately before it. `ffmpeg -i master.mov` prints stream info and
33
+ writes nothing, and denying a read is how a guard teaches an agent to route
34
+ around it. `ffmpeg -i x.mp4 x.mp4` still denies — the token there is not
35
+ preceded by `-i`.
36
+
37
+ ### Added
38
+
39
+ - **`tests.test_source_media_guard`** — the hook had no tests, which is why two
40
+ holes in it needed a payload matrix to find. It runs the hook the way the
41
+ harness does, a PreToolUse payload on stdin and a decision on stdout, and
42
+ fails on exactly the four rows this release fixes. The newline/`;` pair is
43
+ asserted as a pair: not that either answer is right, but that the guard cannot
44
+ give two.
45
+
46
+ ### Note
47
+
48
+ - Splitting on newlines means multi-line text carried *inside* a command — a
49
+ heredoc body, a commit message — is now read as commands too, so text that
50
+ merely quotes `rm camera.mov` is denied. That is the right way round for a
51
+ tripwire; write the text to a file first. #152 was itself blocked this way on
52
+ its first attempt, by the fix it was proposing.
53
+
5
54
  ## What's New in v2.98.0
6
55
 
7
56
  **The control panel could be driven by any web page you visited.** Reported
@@ -117,6 +166,13 @@ state file and panel pidfile move out of shared locations at the same time.
117
166
  response, so an unrelated document sitting in the export folder could reach an
118
167
  assistant's context. Only staged files are read now.
119
168
 
169
+ Live-verified after release on Studio 19.1.3.7 (macOS, Color page, Gallery
170
+ panel open): Resolve's `ExportStills` writes into the staging subdirectory — a
171
+ 257 KB JPEG and its 28 KB `.drx` came back inlined — a bystander file in the
172
+ same folder survived untouched, the folder itself was kept, and
173
+ `cleanup: false` moved both files up into it. That subdirectory write was the
174
+ one claim the offline fixtures could not make.
175
+
120
176
  ### Added
121
177
 
122
178
  - `tests.test_gallery_still_export_cleanup` runs the action against a real temp
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  English | [简体中文](README.zh-CN.md)
4
4
 
5
- [![Version](https://img.shields.io/badge/version-2.98.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
5
+ [![Version](https://img.shields.io/badge/version-2.98.1-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
6
6
  [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
7
7
  [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
8
8
  [![Tools](https://img.shields.io/badge/MCP%20Tools-35%20(353%20full)-blue.svg)](#server-modes)
package/README.zh-CN.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  [English](README.md) | 简体中文
4
4
 
5
- [![Version](https://img.shields.io/badge/version-2.98.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
5
+ [![Version](https://img.shields.io/badge/version-2.98.1-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
6
6
  [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
7
7
  [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
8
8
  [![Tools](https://img.shields.io/badge/MCP%20Tools-35%20(353%20full)-blue.svg)](#服务器模式)
@@ -12,7 +12,7 @@
12
12
  [![Python](https://img.shields.io/badge/python-3.10+-green.svg)](https://www.python.org/downloads/)
13
13
  [![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
14
14
 
15
- > 本翻译对应 v2.98.0 版 README。如与英文原版有出入,以 [英文原版](README.md) 为准。
15
+ > 本翻译对应 v2.98.1 版 README。如与英文原版有出入,以 [英文原版](README.md) 为准。
16
16
 
17
17
  一个 Model Context Protocol (MCP) 服务器,让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio(达芬奇)。它提供完整的 API 覆盖,外加带护栏的工作流助手,涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发,以及不碰源媒体的媒体分析。
18
18
 
package/install.py CHANGED
@@ -37,7 +37,7 @@ from src.utils.update_check import (
37
37
 
38
38
  # ─── Version ──────────────────────────────────────────────────────────────────
39
39
 
40
- VERSION = "2.98.0"
40
+ VERSION = "2.98.1"
41
41
  # Only hard floor: mcp[cli] requires Python 3.10+. There is no upper bound —
42
42
  # Resolve's scripting bridge loads into newer interpreters on recent builds
43
43
  # (Python 3.14 verified against Resolve Studio 20.3.2). Older Resolve builds
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "davinci-resolve-mcp",
3
- "version": "2.98.0",
3
+ "version": "2.98.1",
4
4
  "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
5
5
  "license": "MIT",
6
6
  "author": "Samuel Gursky <samgursky@gmail.com>",
@@ -87,7 +87,7 @@ if not logging.getLogger().handlers:
87
87
  handlers=[logging.StreamHandler()],
88
88
  )
89
89
 
90
- VERSION = "2.98.0"
90
+ VERSION = "2.98.1"
91
91
  logger = logging.getLogger("davinci-resolve-mcp")
92
92
  logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
93
93
  logger.info(f"Detected platform: {get_platform()}")
package/src/server.py CHANGED
@@ -11,7 +11,7 @@ Usage:
11
11
  python src/server.py --full # Start the 353-tool granular server instead
12
12
  """
13
13
 
14
- VERSION = "2.98.0"
14
+ VERSION = "2.98.1"
15
15
 
16
16
  import base64
17
17
  import os