chore(release): bump version to 2.54.0

Author: samuelgursky

CHANGELOG.md

@@ -2,6 +2,33 @@
 
 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.54.0
+
+Hardens the rest of the enum-keyed settings APIs against the same silent-failure
+class fixed for `AutoSyncAudio` in v2.53.0 (issue #70). Several Resolve methods
+key their settings dict by `resolve.<CONST>` enum attributes and silently reject
+the whole call when handed plain string keys — returning `False`/`None` with
+nothing applied and no error.
+
+- **Fixed** `CreateSubtitlesFromAudio` (both `timeline_ai.create_subtitles` and
+  `timeline.subtitle_generation_probe`) now resolves human-readable
+  `autoCaptionSettings` — `language`, `preset`, `line_break`, `chars_per_line`,
+  `gap` — into live `SUBTITLE_*`/`AUTO_CAPTION_*` enum keys/values. Unknown keys
+  and unresolvable values are dropped and reported in `ignored_settings` instead
+  of poisoning the call, and generation is read-back verified against the
+  timeline's subtitle track count (the boolean return is unreliable).
+- **Fixed** the `ProjectManager` CloudProject family (`create`/`load`/
+  `import_project`/`restore`) resolves `{cloudSettings}` into live
+  `CLOUD_SETTING_*`/`CLOUD_SYNC_*` enums (`project_name`, `media_path`,
+  `is_collab`, `sync_mode`, `is_camera_access`), dropping unknown keys into
+  `ignored_settings`.
+- **Changed** the string→enum resolution is now a shared `_resolve_enum_settings`
+  primitive driven by per-field specs, so the next enum-keyed API gets the same
+  treatment without re-implementing it.
+- **Added** `api_truth` entries for `Timeline.CreateSubtitlesFromAudio` and the
+  CloudProject family, documenting the silent-rejection + unreliable-return
+  behavior alongside the existing `AutoSyncAudio` entry.
+
 ## What's New in v2.53.0
 
 Two improvements to audio sync reliability and inventory control.

README.md

@@ -1,6 +1,6 @@
 # DaVinci Resolve MCP Server
 
-[![Version](https://img.shields.io/badge/version-2.53.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-2.54.0-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-34%20(341%20full)-blue.svg)](#server-modes)

install.py

@@ -35,7 +35,7 @@
 
 # ─── Version ──────────────────────────────────────────────────────────────────
 
-VERSION = "2.53.0"
+VERSION = "2.54.0"
 # 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.json

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

src/granular/common.py

@@ -80,7 +80,7 @@
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "2.53.0"
+VERSION = "2.54.0"
 logger = logging.getLogger("davinci-resolve-mcp")
 logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
 logger.info(f"Detected platform: {get_platform()}")