davinci-resolve-mcp 4.4.0 → 4.4.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 +50 -0
- package/README.md +1 -1
- package/README.zh-CN.md +2 -2
- package/install.py +1 -1
- package/package.json +1 -1
- package/src/granular/common.py +1 -1
- package/src/server.py +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,56 @@
|
|
|
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 v4.4.1 — the safety ratchet stops scanning only half the project
|
|
6
|
+
|
|
7
|
+
The write-enforcement ratchet read `src/server.py` and nothing else. The granular
|
|
8
|
+
server's 387 tools were covered by no guard at all — not a risk table, not the
|
|
9
|
+
destructive registry, not the ratchet. That is how `ti_copy_grades` reached
|
|
10
|
+
`TimelineItem.CopyGrades`, which replaces a node graph with no recovery version,
|
|
11
|
+
behind nothing. v4.3.0 fixed that one tool by hand; nothing would have caught the
|
|
12
|
+
next one.
|
|
13
|
+
|
|
14
|
+
### Added
|
|
15
|
+
|
|
16
|
+
- **`tests/test_write_enforcement_ratchet.py` now scans both servers.** They are
|
|
17
|
+
built differently, so the granular tests claim different things and the module
|
|
18
|
+
docstring says which is which:
|
|
19
|
+
|
|
20
|
+
- **Enforcement.** A granular tool that calls a symbol the ledger marks
|
|
21
|
+
`destroys_prior_work` must be gated — `acknowledge_trap` plus a confirm token —
|
|
22
|
+
and must be hinted destructive, so a client that refuses destructive tools never
|
|
23
|
+
reaches the confirmation at all. `TRAP_METHODS` is derived from `API_TRUTH`
|
|
24
|
+
rather than written out, so flagging a new entry extends this guard without
|
|
25
|
+
anyone remembering that this file exists.
|
|
26
|
+
- **Visibility.** The other **131** destructive-hinted granular tools are frozen
|
|
27
|
+
in a backlog that can only shrink. This does **not** make them safe: the
|
|
28
|
+
granular server has no enforcement hook — `@_destructive_op` wraps an
|
|
29
|
+
`(action, params)` signature granular tools do not have — so there is no
|
|
30
|
+
archive, no safe-mode refusal and no audit row behind any of them. The backlog
|
|
31
|
+
makes the number known, and makes the 132nd fail the suite.
|
|
32
|
+
|
|
33
|
+
### Fixed
|
|
34
|
+
|
|
35
|
+
- **The first draft of the gate detector could be fooled by dead code.** It looked
|
|
36
|
+
for the string `CONFIRM_TOKENS` in the function body, so deleting the token
|
|
37
|
+
*redemption* while leaving the *issuance* behind still read as gated — and issuing
|
|
38
|
+
a token nobody checks is exactly the regression worth catching. Gating is now
|
|
39
|
+
detected as AST call nodes (`issue` **and** `consume` on `CONFIRM_TOKENS`) plus
|
|
40
|
+
the real `acknowledge_trap` and `confirm_token` parameters.
|
|
41
|
+
|
|
42
|
+
### Validation
|
|
43
|
+
|
|
44
|
+
- Five regressions re-introduced deliberately, each confirming a guard fires rather
|
|
45
|
+
than passing vacuously: delete the redemption, drop `acknowledge_trap`, drop the
|
|
46
|
+
destructive annotation, add a new ungated destructive tool, and gate a tool still
|
|
47
|
+
on the backlog. **Two of the five passed against the first draft** — the dead-code
|
|
48
|
+
hole above, and a probe that silently did nothing because `ast.unparse` drops
|
|
49
|
+
comments. Both the guard and the probes were fixed until all five failed on
|
|
50
|
+
demand and passed on restore.
|
|
51
|
+
- Full offline suite: **3,644 passed, 1 skipped, 0 failed**, 1,269 subtests. All
|
|
52
|
+
release drift guards green.
|
|
53
|
+
- Tests only; no server behaviour changed and no Resolve call was made.
|
|
54
|
+
|
|
5
55
|
## What's New in v4.4.0 — 85 granular tools stop lying to clients about what they do
|
|
6
56
|
|
|
7
57
|
Granular tools infer their MCP safety annotation from the leading verb in the tool
|
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
English | [简体中文](README.zh-CN.md)
|
|
4
4
|
|
|
5
|
-
[](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
|
|
6
6
|
[](https://www.npmjs.com/package/davinci-resolve-mcp)
|
|
7
7
|
[](docs/reference/api-coverage.md)
|
|
8
8
|
[-blue.svg)](#server-modes)
|
package/README.zh-CN.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
[English](README.md) | 简体中文
|
|
4
4
|
|
|
5
|
-
[](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
|
|
6
6
|
[](https://www.npmjs.com/package/davinci-resolve-mcp)
|
|
7
7
|
[](docs/reference/api-coverage.md)
|
|
8
8
|
[-blue.svg)](#服务器模式)
|
|
@@ -12,7 +12,7 @@
|
|
|
12
12
|
[](https://www.python.org/downloads/)
|
|
13
13
|
[](https://opensource.org/licenses/MIT)
|
|
14
14
|
|
|
15
|
-
> 本翻译对应 v4.4.
|
|
15
|
+
> 本翻译对应 v4.4.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 = "4.4.
|
|
40
|
+
VERSION = "4.4.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
package/src/granular/common.py
CHANGED
|
@@ -92,7 +92,7 @@ if not logging.getLogger().handlers:
|
|
|
92
92
|
handlers=[logging.StreamHandler()],
|
|
93
93
|
)
|
|
94
94
|
|
|
95
|
-
VERSION = "4.4.
|
|
95
|
+
VERSION = "4.4.1"
|
|
96
96
|
logger = logging.getLogger("davinci-resolve-mcp")
|
|
97
97
|
logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
|
|
98
98
|
logger.info(f"Detected platform: {get_platform()}")
|