davinci-resolve-mcp 4.8.19 → 4.8.21

package/CHANGELOG.md

@@ -2,6 +2,83 @@
 
 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 v4.8.21 — timeline duration no longer overcounts by one frame
+
+### Fixed
+
+- **Two timeline-duration readers reported one frame too many.** ([#269](https://github.com/samuelgursky/davinci-resolve-mcp/pull/269), @Dev-next-gen)
+  The granular `get_current_timeline` and `get_project_info`'s per-timeline
+  `duration` computed `GetEndFrame() - GetStartFrame() + 1`, while the compound
+  server, `brain_edits` and `render_stress` all use `GetEndFrame() - GetStartFrame()`
+  for the same timeline. `GetEndFrame()` is one past the last frame, so the `+ 1`
+  counted a frame that does not exist: a 600-frame timeline read back as 601. Both
+  readers now agree with the rest of the server.
+
+### Documentation
+
+- **`api_truth` records `Timeline.GetEndFrame` as an exclusive bound.** Measured
+  live on Studio 19.1.3.7 while reviewing #269: a timeline whose only full-length
+  item is a 32742-frame clip reads start 0 / end 32742, and the item's
+  `GetEnd()` is also 32742. The entry sits beside the existing
+  `AppendToTimeline clipInfo endFrame` entry, which documents the same half-open
+  convention on the write side, so the frame-count rule is now findable from
+  either direction.
+
+### Tests
+
+- `tests/test_timeline_duration.py` (from the PR): both readers return
+  `end - start` for a stubbed 86400..87000 timeline; fails on v4.8.20 with 601.
+- `tests/test_api_truth.py`: the new ledger entry is findable by `GetEndFrame`,
+  carries the `off-by-one` tag, and states the `end - start` rule.
+
+## What's New in v4.8.20 — every boolean param honours `"false"`
+
+### Fixed
+
+- **Boolean tool params read with bare truthiness, file-wide.** The last four
+  releases fixed this one key at a time (`background`, `create_missing`, `dry_run`,
+  `include_*`). This release sweeps the rest: 126 `p.get("k", True|False)` /
+  `bool(p.get(...))` reads and 36 bare `if p.get("k"):` tests of flag params in
+  `src/server.py`, plus 9 reads in `src/utils` (multicam setup, Fuse/DCTL template
+  options, the batch-analysis `auto_build_index`). A caller sending `"false"` (or
+  `"no"`, `"0"`, `"off"`) got the opposite of what they asked for. The cases that
+  mattered:
+  - `override_governance="false"` skipped AI-governance enforcement in `enforce` mode.
+  - `project_manager(action="close", stop_render="false")` stopped a running render
+    and closed the project instead of refusing.
+  - `timeline_item_color(action="propose_grade", execute="false")` took the execute path.
+  - `timeline_markers(action="clear_annotations_by_scope", clear_flags="false" /
+    clear_clip_color="false")` cleared them, and `media_pool_item(action="open_in_viewer",
+    clear_marks="false")` cleared the clip's mark in/out.
+  - `timeline_item_color(action="apply_trace_plan", allow_timeline_mismatch="false")` allowed a mismatched timeline.
+  - The extension lifecycle probes installed on `install="false"` and removed the
+    install on `cleanup="false"`; `grab_and_export` deleted the grabbed still from the
+    Gallery album on `delete_after="false"` and discarded its staging files on
+    `cleanup="false"`; the export round-trip deleted the
+    imported timeline on `cleanup_imported="false"`.
+  Every read keeps its default when the key is omitted, `None`, or an unrecognized
+  string. One change for explicit `null`: a key whose default is `True` (e.g.
+  `overwrite` in the lifecycle probes, `require_temp_path`) now reads `null` as that
+  default instead of as false.
+- **Correction to an earlier claim.** `allow_non_mcp_name="false"` and
+  `overwrite="false"` were *not* bypasses: `_require_disposable_project_name`,
+  `_extension_safe_name` and the `fuse_plugin`/`dctl` install actions already coerce at
+  the point of use. Their handler reads are coerced now for consistency, and tests pin
+  that a real `False` reaches the next layer.
+- Left as-is on purpose: `from_preset` (a preset name), `reference_movie` (a path), the
+  server-set `_setup_defaults_applied` marker, and `generate_speech`'s
+  `AddToTimeline`, which is passed verbatim to Resolve.
+
+### Tests
+
+- `tests/test_bool_param_coercion.py`: behavioural guards for governance override,
+  close-during-render, `propose_grade` execute, annotation clearing, the Fuse probe's
+  install/cleanup, Fuse/DCTL template flags, and the `allow_non_mcp_name` /
+  `overwrite` contracts. 47 subtests fail on the previous code.
+- Two AST ratchets on `src/server.py`: every `x.get("k", True|False)` sits inside a
+  coercer (fallback chains included), and a key coerced anywhere in the file is never
+  tested with bare truthiness on caller input.
+
 ## What's New in v4.8.19 — generated OFX nodes bind their params on Resolve 21.0
 
 ### Fixed

package/README.md

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

package/README.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](README.md) | 简体中文
 
-[![Version](https://img.shields.io/badge/version-4.8.19-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-4.8.21-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-37%20(389%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)
 
-> 本翻译对应 v4.8.19 版 README。如与英文原版有出入，以 [英文原版](README.md) 为准。
+> 本翻译对应 v4.8.21 版 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 = "4.8.19"
+VERSION = "4.8.21"
 # 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": "4.8.19",
+  "version": "4.8.21",
   "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
   "license": "MIT",
   "author": "Samuel Gursky <samgursky@gmail.com>",

package/src/granular/common.py

@@ -93,7 +93,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "4.8.19"
+VERSION = "4.8.21"
 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/granular/timeline.py

@@ -65,7 +65,7 @@ def get_current_timeline() -> Dict[str, Any]:
             "width": current_timeline.GetSetting("timelineResolutionWidth"),
             "height": current_timeline.GetSetting("timelineResolutionHeight")
         },
-        "duration": current_timeline.GetEndFrame() - current_timeline.GetStartFrame() + 1
+        "duration": current_timeline.GetEndFrame() - current_timeline.GetStartFrame()
     }
     
     return result