davinci-resolve-mcp 2.95.0 → 2.95.2

package/CHANGELOG.md

@@ -2,6 +2,97 @@
 
 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.95.2
+
+Adds the live round-trip harness the offline `.drp` tier never had — the absence
+of which is why three unbacked "verified live" claims survived in its README, one
+reaching a shipped `api_truth` recommendation before being caught.
+
+### Added — `tests/live_drp_roundtrip_verification.py`
+
+Authors a `.drp` per primitive, imports it into a running Resolve, asserts intent
+against structural readback, **and exports the composited frame to assert the
+item is actually visible on screen.**
+
+That last assertion is the whole point. `place_fusion_title` satisfies every
+structural check — right track, frame, duration, `PrettyType`, and correctly
+encoded text — while rendering nothing, so a harness that only diffed
+`GetStart()`/`GetDuration()` would have called it green. Visibility is measured
+with `Project.ExportCurrentFrameAsStill` plus a luma pass: an inert item yields
+`max=0` across the entire frame, a real one does not (the live control returns
+`max=255` with ~16k bright pixels).
+
+**Known-broken cases are declared, not skipped.** `place_fusion_title` is
+recorded as `KNOWN BROKEN`; if it starts working the harness reports `UNEXPECTED
+PASS` and fails, forcing the docs that describe it to be updated.
+
+Current state on Studio 21.0.4.5: **7 passed, 1 known-broken, 0 needing
+attention** — media placement, blade, trim, cross-track move, and generator
+visibility all verified end to end.
+
+### Fixed — the `RESOLVE_VERIFY=1` gate was unrunnable
+
+It ran a single test that threw `TODO — implement once fixtures land`, so the
+flag reported a failing suite and everyone learned to ignore it. A gate nobody
+can run green is worse than no gate. It is now a documented skip pointing at the
+harness above, and `RESOLVE_VERIFY=1 npm test` is clean.
+
+### Changed — release process states the rule
+
+"The file round-trips" and "Resolve honours it" are different claims; only a live
+import establishes the second. Changes to the offline `.drp` tier must run the
+harness, and a doc may not say "verified live" unless a runnable command produced
+that result.
+
+The harness is also robust to `DeleteProject`'s session lock: projects opened in
+a session cannot be deleted until Resolve restarts, so it steps off the current
+project, retries, falls back to run-unique names rather than colliding, and
+reports what it could not remove instead of failing silently.
+
+## What's New in v2.95.1
+
+Withdraws a recommendation this project shipped two releases ago. **`drp
+place_fusion_title` produces a title Resolve never renders**, and v2.93.2/v2.93.3
+told callers to use it.
+
+### Fixed — the offline title is inert
+
+Measured on Studio 21.0.4.5. The placed clip is structurally perfect: right
+track, right frame, right duration, `PrettyType` = `Fusion Title`, and the text
+genuinely is written into the `CompositionBA` — it decodes back. But Resolve
+never instantiates the comp:
+
+| | offline-placed | live-inserted |
+|---|---|---|
+| `GetFusionCompCount()` | 1 | 1 |
+| `GetToolList()` | **`[]`** | `['Template','MediaOut1']` |
+| Inspector Title tab | **blank** | shows `Text+` |
+| Viewer | **black** | renders the text |
+
+Reproduced four ways — alone, inside an edit chain, onto a bundled-template base
+project, and onto a genuine 21.0.4.5 Resolve export. Ruled out: template
+staleness (the bundled clip element is structurally identical to a real one, same
+tags, size differing only by text length) and DbId rewriting (the comp blobs hold
+no DbId references). Root cause open.
+
+It passes every structural readback while being invisible on screen — the exact
+silent-lie shape the `api_truth` ledger exists to catch. The **nested-timeline
+route is unaffected** and remains the working answer.
+
+### Narrowed — it is the Fusion-comp path, not clone-a-template
+
+`place_generator`, built the same way, works: an imported Solid Color shows a
+populated `Generator - Solid Color` Inspector with a live Color parameter. A
+generator's parameters are a protobuf `EffectFiltersBA`, which Resolve reads; a
+title's are a `CompositionBA` Fusion-comp blob, which it does not instantiate.
+
+### Changed — "mapped" no longer implies "Resolve honours it"
+
+The drp-format README's honest-scope section conflated file-level fidelity with
+live behaviour. A blob that survives a write/read cycle has been *encoded*
+correctly; only a live import proves it is *instantiated*. The section now says
+so, and the Fusion-title row carries the warning.
+
 ## What's New in v2.95.0
 
 Compound clips can now be walked into and edited offline — the one capability

package/README.md

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

package/README.zh-CN.md

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

package/docs/process/release-process.md

@@ -113,6 +113,26 @@ Resolve validation before release. Use disposable projects and synthetic media
 only. Never modify, transcode, proxy, or create derivatives of source media
 unless the user explicitly requests it.
 
+**Changes to the offline `.drp` authoring tier must run the round-trip harness,
+and a structural readback is NOT sufficient evidence on its own:**
+
+```bash
+RESOLVE_VERIFY=1 venv/bin/python tests/live_drp_roundtrip_verification.py
+```
+
+It authors a `.drp` per primitive, imports it into Resolve, asserts intent
+against structural readback, **and exports the composited frame to assert the
+item is visible on screen.** That last assertion exists because
+`place_fusion_title` passes every structural check — right track, frame,
+duration, type, and correctly-encoded text — while rendering nothing. Anything
+that only diffs `GetStart()`/`GetDuration()` will call that green. Known-broken
+cases are declared in the harness rather than skipped, so a fix reports
+`UNEXPECTED PASS` and fails until the docs describing it are updated.
+
+The same rule generalises: **"the file round-trips" and "Resolve honours it" are
+different claims.** Only a live import establishes the second one. Do not write
+"verified live" in a doc unless a runnable command produced that result.
+
 Examples:
 
 ```bash

package/docs/reference/api-limitations.md

@@ -67,7 +67,7 @@ equivalent, blocking full automation.
 
 - **Object:** `Timeline`
 - **Behavior:** There is no API to read or set the Source/Auto Track Selector (the Edit-page patch panel that picks the destination track). InsertTitleIntoTimeline, InsertFusionTitleIntoTimeline, InsertGeneratorIntoTimeline, InsertFusionGeneratorIntoTimeline, InsertOFXGeneratorIntoTimeline and InsertFusionCompositionIntoTimeline take no trackIndex and always drop the clip on the selector's current target (V1 in practice). Locking lower video tracks does NOT redirect the insert — verified live on 21.0.0: locking V1 makes the insert FAIL rather than land on V2. Titles/generators also can't be moved afterward (no MediaPoolItem, so AppendToTimeline clipInfo and MoveClips don't apply). RE-MEASURED on Studio 21.0.4.5 (2026-08-12, version read live), one fresh 3-video-track timeline per arm so no insert could fail on a collision: nothing locked -> lands V1; V1 locked via SetTrackLock -> returns None; V1 locked by CLICKING THE PADLOCK IN THE UI -> returns None, IDENTICAL to the API lock. That kills the recurring theory that the GUI lock advances the selector where the API lock does not — it does not, and a revision of resolve-advanced/vendor/drp-format/README.md that claimed otherwise as 'verified live' has been withdrawn as false. WHAT DOES WORK, and it is the whole mechanism: dragging the SOURCE PATCH badge onto V2 in the Edit-page patch panel sends the next insert to V2 (measured, same rig, nothing locked). The destination is the patch panel, never the lock state. In the track header the per-track badge column is the auto-track-selector toggle, while the source patch badge appears only on the patched track and dragging THAT is what re-targets. So THE SELECTOR itself is reachable only by GUI automation, and exposing read/write on the patch panel is a smaller, better-defined API request than adding trackIndex to all six Insert*IntoTimeline methods. Do not read that as 'a title cannot be placed on a chosen track from a script' — it can, without touching the selector at all, by nesting it (see the recommendation). The gap is in these six methods and in selector access, not in the outcome.
-- **Workaround / current handling:** USE THE NESTED-TIMELINE ROUTE — the insert method is a dead end but the goal is not, and this is entirely public API. Measured end to end on Studio 21.0.4.5 (2026-08-12): put the title on its OWN timeline (CreateEmptyTimeline + InsertFusionTitleIntoTimeline; it lands on V1 there and that does not matter), then place THAT timeline's media pool item — Timeline.GetMediaPoolItem(), clip property Type='Timeline' — with AppendToTimeline's clipInfo trackIndex/recordFrame. It lands on the requested track at the requested frame, exactly. The text stays settable afterwards: placedItem.GetMediaPoolItem().GetTimeline() (Resolve 21.0.4+) opens the inner timeline, and the Text+ item there still reports GetFusionCompCount()==1, so GetFusionCompByIndex(1).FindTool('Template').SetInput('StyledText', ...) works and persists across processes. Duration is controllable the same way: duration = endFrame - startFrame, endFrame EXCLUSIVE (verified at 1, 119 and 120 frames). This composes — a PNG plus two titles each placed by trackIndex into one container timeline, and the container placed as a single clip, all elements individually reachable and editable through the nesting. TWO CONSTRAINTS: (a) every placed instance shares ONE media pool item, so a text edit propagates to all of them — use one source timeline per distinct card; (b) placements must not overlap on a track, or the append is silently rejected (see the overlapping-record entry). COMPOUND CLIPS ARE THE TRAP HERE: Timeline.CreateCompoundClip also gives a source-less title a MediaPoolItem and also places correctly, but it SEVERS the text — FusionCompCount drops 1->0 and GetTimeline() returns None for Type='Compound' while working correctly for Type='Timeline', so there is no route back to the Text+. Use a nested timeline, never a compound, when the text must stay editable. For clips that already have a MediaPoolItem, AppendToTimeline clipInfo 'trackIndex' was always the answer (exposed as media_pool append_to_timeline clip_infos). Do NOT reach for track locking in either form — it blocks the insert rather than re-targeting it. GUI automation of the patch panel works but is a last resort and is unverifiable from the API side; if used, read the landing track back with TimelineItem.GetTrackTypeAndIndex() and treat a wrong track as a failure. Offline, the advanced server's drp place_fusion_title places a title by track and frame directly. See issue #74.
+- **Workaround / current handling:** USE THE NESTED-TIMELINE ROUTE — the insert method is a dead end but the goal is not, and this is entirely public API. Measured end to end on Studio 21.0.4.5 (2026-08-12): put the title on its OWN timeline (CreateEmptyTimeline + InsertFusionTitleIntoTimeline; it lands on V1 there and that does not matter), then place THAT timeline's media pool item — Timeline.GetMediaPoolItem(), clip property Type='Timeline' — with AppendToTimeline's clipInfo trackIndex/recordFrame. It lands on the requested track at the requested frame, exactly. The text stays settable afterwards: placedItem.GetMediaPoolItem().GetTimeline() (Resolve 21.0.4+) opens the inner timeline, and the Text+ item there still reports GetFusionCompCount()==1, so GetFusionCompByIndex(1).FindTool('Template').SetInput('StyledText', ...) works and persists across processes. Duration is controllable the same way: duration = endFrame - startFrame, endFrame EXCLUSIVE (verified at 1, 119 and 120 frames). This composes — a PNG plus two titles each placed by trackIndex into one container timeline, and the container placed as a single clip, all elements individually reachable and editable through the nesting. TWO CONSTRAINTS: (a) every placed instance shares ONE media pool item, so a text edit propagates to all of them — use one source timeline per distinct card; (b) placements must not overlap on a track, or the append is silently rejected (see the overlapping-record entry). COMPOUND CLIPS ARE THE TRAP HERE: Timeline.CreateCompoundClip also gives a source-less title a MediaPoolItem and also places correctly, but it SEVERS the text — FusionCompCount drops 1->0 and GetTimeline() returns None for Type='Compound' while working correctly for Type='Timeline', so there is no route back to the Text+. Use a nested timeline, never a compound, when the text must stay editable. For clips that already have a MediaPoolItem, AppendToTimeline clipInfo 'trackIndex' was always the answer (exposed as media_pool append_to_timeline clip_infos). Do NOT reach for track locking in either form — it blocks the insert rather than re-targeting it. GUI automation of the patch panel works but is a last resort and is unverifiable from the API side; if used, read the landing track back with TimelineItem.GetTrackTypeAndIndex() and treat a wrong track as a failure. DO NOT REACH FOR drp place_fusion_title HERE — an earlier revision of this entry recommended it and that recommendation is WITHDRAWN. Measured on Studio 21.0.4.5: it places a Fusion Title that is structurally perfect — right track, right frame, right duration, PrettyType 'Fusion Title', and the text really is written into the CompositionBA, which decodes back correctly — but Resolve never instantiates the comp. The imported item reports GetFusionCompCount()==1 while GetFusionCompByIndex(1).GetToolList() is EMPTY (a live-inserted Text+ returns ['Template','MediaOut1']), the Edit-page Inspector's Title tab is blank, and the viewer renders nothing. Reproduced four ways: placed alone, placed in an edit chain, onto a bundled-template base project, and onto a genuine 21.0.4.5 Resolve export. It therefore passes every structural readback while being invisible on screen — the exact silent-lie shape this ledger exists to catch. The nested-timeline route above is the one that actually works. See issue #74.
 - **Reference:** [issue #74](https://github.com/samuelgursky/davinci-resolve-mcp/issues/74)
 - **Tags:** missing-method, timeline, title, generator, track
 

package/install.py

@@ -36,7 +36,7 @@ from src.utils.update_check import (
 
 # ─── Version ──────────────────────────────────────────────────────────────────
 
-VERSION = "2.95.0"
+VERSION = "2.95.2"
 # 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": "2.95.0",
+  "version": "2.95.2",
   "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
   "license": "MIT",
   "author": "Samuel Gursky <samgursky@gmail.com>",

package/resolve-advanced/vendor/drp-format/README.md

@@ -1,8 +1,24 @@
 # drp-format — offline DaVinci Resolve project authoring & editing
 
 Read, author, and edit **real, importable** DaVinci Resolve 21 projects (`.drp`) and timelines
-(`.drt`) as files — no Resolve required. Everything here is verified by a live round-trip
-(author/edit → `import_project` → `lint`/`clip_where` → re-export decode), not just self-parse.
+(`.drt`) as files — no Resolve required.
+
+> **How to verify a claim in this file.** This README previously said "everything here is verified
+> by a live round-trip". It was not: the gate it referred to threw `TODO — implement once fixtures
+> land`, so nobody ever ran it green, and three unbacked "verified live" claims survived here —
+> one of which reached a shipped `api_truth` recommendation before being caught. The round-trip
+> that actually exists is:
+>
+> ```bash
+> RESOLVE_VERIFY=1 venv/bin/python tests/live_drp_roundtrip_verification.py
+> ```
+>
+> It authors a `.drp` per primitive, imports it into a running Resolve, asserts intent against
+> structural readback, **and exports the composited frame to assert the item is visible on
+> screen.** That last check is the point: `place_fusion_title` satisfies every structural
+> assertion — correct track, frame, duration, type, and text encoded in the blob — while
+> rendering nothing. Structure alone cannot tell you a thing works. Known-broken cases are
+> declared in the harness, so a fix reports `UNEXPECTED PASS` and forces the docs to be updated.
 
 Background + the full schema map: `docs/design/drp-drx-drt-closeout-harness/knowledge/resolve21-schema-reconciliation.md`
 and `.../resolve-authoring-completion.md`.
@@ -37,7 +53,7 @@ and `.../resolve-authoring-completion.md`.
 **Place elements (track-targeted — the #74 bypass, offline)**
 | Action | What it does |
 |---|---|
-| `place_fusion_title` | Text+ on a chosen track. Options: `text, font, style, size, vJustify, hJustify, color:{r,g,b}`, `trackIndex`, `startFrame`, `durationFrames` |
+| `place_fusion_title` | ⚠️ **INERT on 21.0.4.5 — placed but not rendered, see below.** Text+ on a chosen track. Options: `text, font, style, size, vJustify, hJustify, color:{r,g,b}`, `trackIndex`, `startFrame`, `durationFrames` |
 | `place_generator` | built-in generator (`generatorName`, e.g. "Solid Color") on a chosen track |
 | `place_transition` | cross-dissolve at an abutting cut (`track`, `atFrame`, `durationFrames`) — clips need handle media |
 
@@ -117,16 +133,40 @@ Selector's current target (V1 in practice), which no API can read or set.
 > locking. Treat it as such: it is not verifiable from the API side, since nothing in the
 > scripting surface can confirm the selector landed where you dragged it.
 
-For export-based workflows, `place_fusion_title` places a title on any track at an exact frame
-offline, with no selector involved.
+> ⚠️ **`place_fusion_title` currently produces an INERT title — do not use it for this.**
+> Measured on Studio 21.0.4.5: the placed clip is structurally perfect (right track, frame and
+> duration, `PrettyType` = `Fusion Title`, and the text really is written into the
+> `CompositionBA` — it decodes back), but **Resolve never instantiates the comp**. The imported
+> item reports `GetFusionCompCount() == 1` while `GetFusionCompByIndex(1).GetToolList()` is
+> **empty** (a live-inserted Text+ returns `['Template','MediaOut1']`), the Inspector's Title tab
+> is blank, and the viewer renders nothing. Reproduced four ways: alone, in an edit chain, onto a
+> bundled-template base, and onto a genuine 21.0.4.5 export. Ruled out so far — template staleness
+> (the bundled clip element is structurally identical to a real one: same tags, size differing
+> only by text length) and DbId rewriting (the comp blobs contain no DbId references). Root cause
+> open. Use the live nested-timeline route until this is fixed.
+>
+> **The defect is specific to the Fusion-comp path, not to clone-a-template.** `place_generator`,
+> built the same way, works: an imported Solid Color shows a populated `Generator - Solid Color`
+> Inspector with a live Color parameter and renders on the timeline. The difference is where the
+> parameters live — a generator's are a protobuf `EffectFiltersBA`, which Resolve reads happily,
+> while a title's are a `CompositionBA` Fusion-comp blob, which it does not instantiate. That is
+> the narrowest place to start looking.
 
 ---
 
 ## What's mapped (honest scope)
 
+> **Read "mapped" as file-level fidelity, not as "Resolve honours it."** Those are different
+> claims and this README conflated them. `place_fusion_title` round-trips byte-for-byte and its
+> text decodes back correctly, yet Resolve builds no comp from it (see the ⚠️ above). A blob that
+> survives a write/read cycle has been *encoded* correctly; only a live import proves it is
+> *instantiated*. Everything below is the first claim. The second is only established where an
+> entry says it was measured against a running Resolve build.
+
 **Fully mapped (read + write, round-trips byte-for-byte):** project packaging; tracks
 (`Sm2TiTrack`+Type+Sequence); clips; source in-points (`<In>`); Fusion titles
-(text/font/style/size/justify/color); generators; transitions; markers; grades (full DRX body);
+(text/font/style/size/justify/color — **encoded correctly but not instantiated by Resolve 21.0.4.5;
+see the ⚠️ above**); generators; transitions; markers; grades (full DRX body);
 media path + resolution + frame-count + fps. **Plus the full Media-Pool metadata layer:** the
 keyed-dict format (`Geometry`/`Time`/`VideoMetadata`/`Proxy`/audio/small `FieldsBlob`) with typed
 values (`keyed-dict.js`); audio config (`TracksBA`/`VirtualAudioTrackBA` → sample-rate/channels/codec

package/resolve-advanced/vendor/drp-format/__tests__/inject-grades.test.js

@@ -18,7 +18,6 @@ const os = require('node:os');
 const JSZip = require('jszip');
 
 const drpFormat = require('..');
-const { resolveVerifyTest } = require('./_resolve-verify');
 
 // A plausible-shaped synthetic body. The injector does not parse the bytes,
 // only substitutes them. Hex characters only.
@@ -229,10 +228,19 @@ test('injectGrades: internals — extractDrxBodyHex throws on missing Body', ()
 // the byte-identical-render check requires Resolve. When the env flag is
 // unset the test skips with a clear marker.
 
-resolveVerifyTest('injectGrades: rendered frame matches direct DRX apply', async () => {
-  // The harness's resolve-verifications.md has the full recipe. The actual
-  // implementation will live here once a captured fixture + a Resolve session
-  // is in flight. Until then it's a placeholder that exists to demonstrate
-  // the resolveVerifyTest gate and to surface in the skip list as a TODO.
-  throw new Error('TODO — implement once fixtures/inject-target.drp + Resolve session land');
-});
+// NOT a throwing placeholder any more. It used to `throw new Error('TODO ...')`,
+// which meant RESOLVE_VERIFY=1 reported a FAILING suite and everyone learned to
+// ignore the flag — which is a large part of why this package carried three
+// unbacked "verified live" claims. A gate nobody can run green is worse than no
+// gate. The live round-trip that DOES exist now lives on the Python side, where
+// the Resolve scripting API is reachable directly:
+//
+//   RESOLVE_VERIFY=1 venv/bin/python tests/live_drp_roundtrip_verification.py
+//
+// It authors a .drp per primitive, imports it into Resolve, asserts intent
+// against structural readback AND exports the composited frame to assert the
+// item is actually VISIBLE — the check that catches place_fusion_title, which
+// passes every structural assertion while rendering nothing.
+test.skip('injectGrades: rendered frame matches direct DRX apply '
+  + '(covered by tests/live_drp_roundtrip_verification.py — grade-render compare still TODO)',
+() => {});

package/src/granular/common.py

@@ -87,7 +87,7 @@ if not logging.getLogger().handlers:
         handlers=[logging.StreamHandler()],
     )
 
-VERSION = "2.95.0"
+VERSION = "2.95.2"
 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 353-tool granular server instead
 """
 
-VERSION = "2.95.0"
+VERSION = "2.95.2"
 
 import base64
 import os

package/src/utils/api_truth.py

@@ -643,9 +643,23 @@ API_TRUTH: List[Dict[str, Any]] = [
                        "works but is a last resort and is unverifiable from the API "
                        "side; if used, read the landing track back with "
                        "TimelineItem.GetTrackTypeAndIndex() and treat a wrong track as "
-                       "a failure. Offline, the advanced server's drp "
-                       "place_fusion_title places a title by track and frame directly. "
-                       "See issue #74.",
+                       "a failure. DO NOT REACH FOR drp place_fusion_title HERE — an "
+                       "earlier revision of this entry recommended it and that "
+                       "recommendation is WITHDRAWN. Measured on Studio 21.0.4.5: it "
+                       "places a Fusion Title that is structurally perfect — right "
+                       "track, right frame, right duration, PrettyType 'Fusion Title', "
+                       "and the text really is written into the CompositionBA, which "
+                       "decodes back correctly — but Resolve never instantiates the "
+                       "comp. The imported item reports GetFusionCompCount()==1 while "
+                       "GetFusionCompByIndex(1).GetToolList() is EMPTY (a live-inserted "
+                       "Text+ returns ['Template','MediaOut1']), the Edit-page "
+                       "Inspector's Title tab is blank, and the viewer renders nothing. "
+                       "Reproduced four ways: placed alone, placed in an edit chain, "
+                       "onto a bundled-template base project, and onto a genuine "
+                       "21.0.4.5 Resolve export. It therefore passes every structural "
+                       "readback while being invisible on screen — the exact silent-lie "
+                       "shape this ledger exists to catch. The nested-timeline route "
+                       "above is the one that actually works. See issue #74.",
         "tags": ["missing-method", "timeline", "title", "generator", "track"],
         "submit": "missing",
         "issue": 74,