chore(release): bump version to 2.24.0

V2 trust-by-default media analysis: host-chat vision protocol with
commit_vision, control panel review surface (Phase B), correction tools,
and analysis memory layer. See CHANGELOG.md for the full summary.

Author: samuelgursky

AGENTS.md

@@ -9,12 +9,35 @@ kernel-action counts, release notes, or long reference tables here.
 Never modify, transcode, convert, proxy, relink, replace, or create derivatives
 of source media unless the user explicitly asks for that exact operation.
 
-Analysis workflows may read source media, but outputs must go to sidecar files,
-session scratch space, or the configured `davinci-resolve-mcp-analysis` project
-root. Preserve the chain from camera original to final delivery.
+Analysis workflows may read source media, but file outputs must go to sidecar
+files, session scratch space, or the configured
+`davinci-resolve-mcp-analysis` project root. Resolve-target analysis should run
+visual analysis, transcription, metadata writeback, and Media Pool marker
+writeback by default unless the user opts out; those writes are Resolve project
+database changes, not source-media changes. Preserve the chain from camera
+original to final delivery.
 
 See `docs/guides/media-analysis-guide.md` for the full source-safe workflow.
 
+## Media Analysis Defaults Are Mandatory
+
+Do not translate source-safe into underpowered, read-only, no-writeback analysis.
+When the user asks to analyze Resolve media, run the requested analysis directly
+with visual analysis, transcription, persisted artifacts, metadata writeback, and
+Media Pool marker writeback enabled by default. Do not add
+`include_visuals=false`, `include_transcription=false`,
+`publish_metadata=false`, `timed_markers=no`, `session_only=true`, or
+`dry_run=true` unless the user explicitly asks for that opt-out, the target is a
+raw file path that cannot receive Resolve project writeback. Vision uses
+`host_chat_paths` by default — analyze actions return a deferred payload with
+absolute `frame_paths` and a JSON schema; the host chat must read those frames
+as local images, produce JSON per the schema, and call
+`media_analysis(action="commit_vision", params={clip_id, visual, vision_token})`
+to merge the result and trigger metadata + Media Pool clip-marker writeback.
+Not completing `commit_vision` leaves the analysis in
+`pending_host_vision_analysis` — that is a failure mode, not a success. Users
+must explicitly opt out with `include_visuals=false` for a technical-only run.
+
 ## Frame-Referenced Color Work
 
 Before applying a grade, look, shot match, LUT, CDL, DRX, or copied grade to an

CHANGELOG.md

@@ -2,6 +2,105 @@
 
 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.24.0
+
+**Host-chat vision protocol (V2)** — `analyze_*` actions now use
+`vision.provider="host_chat_paths"` by default. The analyze response is a
+deferred payload with absolute `frame_paths`, a per-shot `shot_table`, and a
+JSON schema; the host chat reads each frame as a local image, produces JSON per
+the schema, and calls `media_analysis(action="commit_vision", params={clip_id,
+visual, vision_token})` to finalize. `commit_vision` merges the visual report,
+rebuilds Media Pool clip markers, publishes metadata to Resolve, and preserves
+human corrections via `corrections.json`. Skipping the commit leaves the run in
+`pending_host_vision_analysis` — surfaced explicitly rather than silently
+downgraded. The legacy `chat_context`/`mcp_sampling` providers still resolve to
+the same host-chat path.
+
+**Trust-by-default analysis defaults** — `analyze_media` defaults to
+`include_transcription=true`, `persist=true`, `publish_metadata=true`, and
+`timed_markers="ask"` so source-safe no longer means underpowered. Agents that
+need a technical-only or read-only run must explicitly pass
+`include_visuals=false`, `include_transcription=false`, `publish_metadata=false`,
+`timed_markers="no"`, `session_only=true`, or `dry_run=true`. The
+`analyze_media` prompt and SKILL.md spell out the anti-regression rule.
+
+**Control panel: Review surface (Phase B)** — The local browser control panel
+gains a Review tab backed by new endpoints: `/api/clips`, `/api/clips/<id>`,
+`/api/clips/<id>/shots`, `/api/clips/<id>/shots/<index>`,
+`/api/clips/<id>/frames/<n>`, `/api/clips/<id>/transcript`,
+`/api/clips/<id>/corrections`, `/api/clips/combined`, `/api/clips/export`,
+`/api/panel_state`, `/api/update/status`, `/api/update/apply`, and
+`/api/resolve/open_clip`. The UI ships a bin grid with thumbnails, a clip
+detail with shot strip, a shot detail with grouped V2 fields + frame grid,
+inline correction editors per subjective field, transcript correction +
+regeneration, an Open-in-Resolve bridge, and 2-second chat ↔ panel state
+polling.
+
+**Control panel MCP actions** — `resolve_control.open_control_panel`,
+`control_panel_status`, and `close_control_panel` manage the local panel
+subprocess via a pidfile. `save_state` / `restore_state` snapshot and restore
+Resolve playhead + selection state. `get_panel_state`, `set_panel_state`, and
+`session_start_context` share panel focus between chat and the UI through
+`panel_state.json`.
+
+**Correction tools** — New `media_analysis` actions for editing analysis
+without re-running it: `update_shot_field`, `update_clip_field`,
+`get_field_history`, `revert_field`, `list_corrections`. Writes land in
+`{clip_dir}/corrections.json` with append-only changelog + provenance
+(mirrors the V2 DB schema). `commit_vision` merges corrections on top of the
+fresh visual report so human edits survive re-analysis.
+
+**Media Pool item open-in-viewer** — `media_pool_item.open_in_viewer` selects
+a clip on the Media page and loads it into the source viewer, optionally
+setting mark in/out and bringing Resolve to the foreground via OS-level
+window activation. Useful for chat → Resolve hand-off.
+
+**Source-trust prompt grading** — `source_trust` parameter
+(`auto`/`filename`/`low`/`medium`/`high`) on analyze actions tunes the vision
+prompt to hedge identity/intent/value for archival or thin-evidence clips.
+
+**Analysis memory layer** — New `src/utils/analysis_memory.py` introduces
+per-project memory + heartbeat + bin summary + soul scaffolding under the
+analysis root. `regenerate_bin_summary_from_manifest` aggregates per-clip
+fields (primary use, select potential, style, energy arc, top tags/locations)
+into a bin briefing. Auto-initialized on analyze.
+
+**Control-panel polish** — Diagnostics + Overview restyled with a status-pill
+design system, navbar dropdowns fixed so top-level buttons no longer navigate
+on their own, Preferences consolidated (Dashboard Convenience + Storage pages
+removed), summary-style enum renamed to `full`/`concise`/`creative`/
+`technical` with backwards compat, navbar version badge + update modal,
+source-trust dropdown wired through.
+
+**Server-side bug fixes** — `commit_vision` auto-publish now reflects per-row
+status correctly (no silent-lie pending), compact analyze responses by default
+(`verbose: true` for the full manifest), `resolve_output_root` skips slug
+append when the configured base already terminates in the slug, frame sampler
+reserves per-shot budget so shot starts aren't starved by flash candidates,
+and machine markers are no longer written to Resolve (V2 architecture).
+
+**Path hardening for GUI launches** — `media_analysis` now augments `PATH`
+with the standard tool dirs (`/opt/homebrew/bin`, `/usr/local/bin`, etc.) so
+ffprobe/ffmpeg resolve even when the MCP server is launched by a GUI app
+(Claude.app, Dock/Spotlight) that inherits launchd's bare PATH.
+
+**Documentation** — `AGENTS.md` adds the "Media Analysis Defaults Are
+Mandatory" section. `docs/SKILL.md` rewrites the `analyze_media` prompt
+guidance for the host-chat-paths protocol and adds the anti-regression rule.
+`docs/guides/media-analysis-guide.md` covers the deferred vision payload and
+commit step. New design docs under `docs/design/`:
+`v2-control-panel-design.md`, `v2-db-schema.sql`,
+`v2-implementation-gameplan.md`, `v2-shot-schema-spec.md`,
+`control-panel-polish-gameplan.md`.
+
+**Validation**: static import checks, API parity audit, focused
+media-analysis + marker/range/v232/v233 unit tests, npm CLI smoke,
+`npm pack --dry-run`, and `git diff --check` all passed. No source media was
+modified. Resolve scripting behavior is additive (new actions; existing
+actions unchanged); live Resolve validation covered the control-panel +
+open_in_viewer + commit_vision auto-publish + corrections-merge paths during
+the V2 push sessions logged in MEMORY.md.
+
 ## What's New in v2.23.1
 
 **Control panel navigation fixes** — The local browser control panel now keeps

README.md

@@ -1,6 +1,6 @@
 # DaVinci Resolve MCP Server
 
-[![Version](https://img.shields.io/badge/version-2.23.1-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
+[![Version](https://img.shields.io/badge/version-2.24.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-32%20(329%20full)-blue.svg)](#server-modes)
@@ -74,7 +74,7 @@ The compound server is recommended unless you specifically need the granular one
 |------|-----------------------------------|
 | App and project control | Launch/reconnect, page switching, project CRUD, project folders, databases, cloud project wrappers, settings, presets, archives |
 | Media pool and ingest | Safe import, image sequences, multicam prep timelines, bin organization, metadata normalization, metadata field inventory, marks, annotations, relink/proxy/full-resolution guards |
-| Media analysis | Source-safe file/clip/bin/project analysis, 2-pop/slate-clap sync-event detection, confirmed Resolve metadata publishing, session-only defaults, existing-report reuse, chat-context visual analysis by default in `analyze_media` with opt-out, optional transcription |
+| Media analysis | Source-safe file/clip/bin/project analysis, 2-pop/slate-clap sync-event detection, default Resolve metadata and Media Pool marker writeback, persisted analysis artifacts, existing-report reuse, host_chat_paths visual analysis (finalized per clip with `commit_vision`, works with any vision-capable MCP client) with opt-out, transcription with opt-out |
 | Timeline editing and conform | Track/item probing, title text key scans/writes, copy/move/duplicate helpers, range operations, gaps/overlaps, source ranges, checked interchange exports/imports |
 | Review annotations | Timeline/item/clip markers, custom data, flags, clip color, copy/move/sync cleanup, review reports, marker thumbnail review |
 | Color and grading | Node graph probing, CDL validation, grade copy, DRX/LUT helpers, versions, Gallery stills, color groups |
@@ -104,7 +104,7 @@ The default server is a local stdio process launched by your MCP client; it does
 
 For method-by-method status, see [API Coverage and Test Results](docs/reference/api-coverage.md). For current workflow support, see [Kernel Action Coverage](docs/kernels/README.md).
 
-`analyze_media` uses in-chat visual analysis by default when the MCP client supports sampling/image messages. Pass `include_visuals=false` for technical-only or privacy-sensitive runs. If in-chat vision is unavailable, analysis continues with local technical/motion evidence and reports the skipped visual layer. `media_analysis.publish_clip_metadata` can publish confirmed analysis summaries, comments, keywords, people, and high-confidence slate fields back to Resolve clip metadata while preserving existing human-entered fields by default.
+`analyze_media` executes directly by default, persists inspectable reports/artifacts under the analysis root, requests host-chat visual analysis via the `host_chat_paths` protocol (analyze returns absolute frame paths + a JSON schema; the host chat reads each frame as an image and calls `media_analysis(action="commit_vision", ...)` to finalize), runs transcription through the configured local backend, and writes analysis summaries plus source-time Media Pool clip markers back to the Resolve project. Pass `include_visuals=false`, `include_transcription=false`, `publish_metadata=false`, `timed_markers=no`, or `dry_run=true` only when you want to opt out of those default behaviors. Skipping `commit_vision` leaves the run in `pending_host_vision_analysis` — surfaced as a failure mode, not silently downgraded.
 
 ## Documentation