davinci-resolve-mcp 4.6.2 → 4.6.4

package/CHANGELOG.md

@@ -2,6 +2,44 @@
 
 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.6.4 — `ripple="false"` no longer ripples
+
+### Fixed
+
+- **`timeline` `delete_clips`, `lift_range`, and the delete step of `move_clips` read
+  `ripple` with a bare `bool()`, so a client sending `ripple="false"` got a ripple
+  delete.** ([#236](https://github.com/samuelgursky/davinci-resolve-mcp/pull/236), @Dev-next-gen)
+  The gap closed and everything downstream shifted, which is exactly what the caller
+  declined. The guards around it read the flag the same way — the pending-confirm
+  check, `destructive_hook.is_strict_required`, and the blast-radius branch of the
+  risk classifier — so with confirm tokens on the user was asked to confirm a ripple
+  delete they never requested, and once confirmed it ran as one. All six readings now
+  go through `coerce_bool` (the helper #218 added for `dry_run`). Real booleans and
+  `"true"`/`"false"`/`"1"`/`"0"` behave exactly as before; a string `coerce_bool`
+  does not recognise now falls to non-ripple instead of ripple, the safe direction
+  for a destructive flag. Guard test: `tests/test_delete_clips_ripple_string.py`,
+  which fails three of four on the previous code.
+
+## What's New in v4.6.3 — the publish workflow keeps npm `latest` on the highest version
+
+Release-process hardening only. No tool, action, or Resolve behaviour changed.
+
+### Fixed
+
+- **Three release tags pushed in one command left npm `latest` on the oldest of
+  them.** The `Publish npm package` runs for v4.6.0, v4.6.1 and v4.6.2 executed in
+  parallel and finished in the order 4.6.1, 4.6.2, 4.6.0; npm points `latest` at
+  whichever publish lands last, so `npm install davinci-resolve-mcp` resolved to
+  4.6.0 while v4.6.2 was the GitHub Release marked latest. The workflow now ends with
+  a step that compares `dist-tags.latest` against the highest published version
+  (always counting the version the run itself carries, because `npm view` can serve
+  a document minutes stale right after a publish) and re-points `latest` when it
+  lags. It never fails the job; if the trusted-publishing token cannot edit
+  dist-tags it logs the `npm dist-tag add` command for a maintainer. This release's
+  own publish is what puts `latest` back on the newest version.
+- `docs/process/release-process.md`: push one release tag at a time and wait for its
+  publish run before pushing the next; the workflow step is a backstop, not the plan.
+
 ## What's New in v4.6.2 — the granular server's macOS temp-path redirect matches the compound server's
 
 ### Fixed

package/README.md

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

package/docs/process/release-process.md

@@ -204,7 +204,16 @@ should say that no behavior changed.
    ```
 
 6. Push `main`.
-7. Create and push the annotated tag:
+7. Create and push the annotated tag. **Push one release tag at a time and wait
+   for its `Publish npm package` run to finish before pushing the next.** Runs for
+   tags pushed together execute in parallel, and npm points `latest` at whichever
+   publish finishes *last*: on 2026-09-15 v4.6.0–v4.6.2 pushed in one command
+   finished in the order 4.6.1, 4.6.2, 4.6.0, and `latest` landed on 4.6.0. The
+   workflow's final step now re-points `latest` at the highest published version
+   when it lags, but it is a backstop, not the plan — the trusted-publishing token
+   may not be allowed to edit dist-tags, in which case the fix is
+   `npm dist-tag add davinci-resolve-mcp@X.Y.Z latest` by a logged-in maintainer,
+   or simply the next release's publish, which sets `latest` itself.
 
    ```bash
    git tag -a v2.4.1 -m "v2.4.1"

package/install.py

@@ -37,7 +37,7 @@ from src.utils.update_check import (
 
 # ─── Version ──────────────────────────────────────────────────────────────────
 
-VERSION = "4.6.2"
+VERSION = "4.6.4"
 # 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.6.2",
+  "version": "4.6.4",
   "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.6.2"
+VERSION = "4.6.4"
 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 = "4.6.2"
+VERSION = "4.6.4"
 
 import base64
 import os
@@ -73,7 +73,7 @@ from src.utils.proc import safe_run
 from src.utils.readback import verify_by_readback, verification_stats as _verification_stats
 from src.utils import operation_result as _operation_result
 from src.utils import operation_log as _operation_log
-from src.utils.bool_params import explicit_bool_param as _explicit_bool_param
+from src.utils.bool_params import coerce_bool as _coerce_bool, explicit_bool_param as _explicit_bool_param
 from src.utils.confirm_tokens import (
     ConfirmTokenStore as _ConfirmTokenStore,
     gate_required_from as _gate_required_from,
@@ -1365,7 +1365,7 @@ def _action_will_gate_pending_confirm(
         tool_name == "timeline"
         and action == "delete_clips"
         and isinstance(params, dict)
-        and bool(params.get("ripple"))
+        and _coerce_bool(params.get("ripple"))
     ):
         return True
     return False
@@ -4982,7 +4982,7 @@ def _timeline_duplicate_clips_impl(proj, tl, p: Dict[str, Any], *, delete_source
                 seen_delete_ids.add(item_id)
         if delete_items:
             try:
-                out["deleted_sources"] = _timeline_delete_clips_verified(tl, delete_items, bool(p.get("ripple", False)), resolve=resolve)
+                out["deleted_sources"] = _timeline_delete_clips_verified(tl, delete_items, _coerce_bool(p.get("ripple")), resolve=resolve)
                 out["deleted_source_ids"] = _timeline_item_ids(delete_items)
             except Exception as exc:
                 out["deleted_sources"] = False
@@ -5614,7 +5614,7 @@ def _timeline_lift_range_impl(tl, p: Dict[str, Any], *, resolve=None):
         return {"success": True, "deleted": 0, "range": {"start": start, "end": end}}
     deleted_ids = _timeline_item_ids(delete_items)
     return {
-        "success": _timeline_delete_clips_verified(tl, delete_items, bool(p.get("ripple", False)), resolve=resolve),
+        "success": _timeline_delete_clips_verified(tl, delete_items, _coerce_bool(p.get("ripple")), resolve=resolve),
         "deleted": len(delete_items),
         "deleted_ids": deleted_ids,
         "range": {"start": start, "end": end},
@@ -25619,7 +25619,7 @@ def timeline(action: str, params: Optional[Dict[str, Any]] = None) -> Dict[str,
                     if it.GetUniqueId() in ids_set:
                         found.append(it)
         # B2 — ripple=True is catastrophic; require confirmation.
-        ripple = bool(p.get("ripple", False))
+        ripple = _coerce_bool(p.get("ripple"))
         if ripple:
             if "confirm_token" not in p and "confirmToken" not in p and _confirm_token_required():
                 return _issue_confirm_token(

package/src/utils/destructive_hook.py

@@ -493,7 +493,7 @@ def is_strict_required(tool_name: str, action: str, params: Optional[Dict[str, A
         tool_name == "timeline"
         and action == "delete_clips"
         and isinstance(params, dict)
-        and bool(params.get("ripple"))
+        and coerce_bool(params.get("ripple"))
     ):
         return True
     return False

package/src/utils/execution_lifecycle.py

@@ -25,6 +25,7 @@ from dataclasses import dataclass, field
 from typing import Any, Callable, Dict, List, Optional, Set, Tuple
 
 from src.utils import operation_log
+from src.utils.bool_params import coerce_bool
 
 logger = logging.getLogger("resolve-mcp.execution-lifecycle")
 
@@ -407,7 +408,7 @@ class RiskClassificationHook(LifecycleHook):
         ):
             level = RiskLevel.HIGH
             destructive = True
-            if params.get("ripple", False):
+            if coerce_bool(params.get("ripple")):
                 radius = BlastRadius.TIMELINE
                 reasons.append("Ripple mode alters downstream timeline synchronization")
             elif tool_name == "graph":