@hybridlabor-api/aos 4.4.1 → 4.4.2-beta.1

package/mcps/davinci-resolve-mcp/CLAUDE.md

@@ -1,15 +0,0 @@
-# Claude Code Instructions
-
-This file is intentionally short. The canonical AI-agent instructions for this
-repository live in `AGENTS.md`.
-
-Claude Code users should follow:
-
-- `AGENTS.md` for repository rules and source media safety
-- `docs/SKILL.md` for DaVinci Resolve MCP operating guidance
-- `docs/process/release-process.md` for version bumps, validation, tags, and
-  GitHub Releases
-- `docs/guides/media-analysis-guide.md` for source-safe media analysis
-
-Do not maintain a separate release checklist, tool-count summary, or changelog
-here. Those details drift; use the docs above as the source of truth.

package/mcps/davinci-resolve-mcp/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2025-2026 DaVinci Resolve MCP Contributors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/mcps/davinci-resolve-mcp/README.md

@@ -1,173 +0,0 @@
-# DaVinci Resolve MCP Server
-
-[![Version](https://img.shields.io/badge/version-2.57.5-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)
-[![Tested](https://img.shields.io/badge/Live%20Tested-98.5%25-green.svg)](docs/reference/api-coverage.md#test-results)
-[![DaVinci Resolve](https://img.shields.io/badge/DaVinci%20Resolve-18.5+-darkred.svg)](https://www.blackmagicdesign.com/products/davinciresolve)
-[![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)
-
-A Model Context Protocol (MCP) server that lets AI assistants control DaVinci Resolve Studio through the official Scripting API. It provides full API coverage plus guarded workflow helpers for editing, media pool organization, render setup, review markers, grading, Fusion, Fairlight, project lifecycle tasks, extension authoring, and source-safe media analysis.
-
-[![Local control panel](docs/images/control-panel/01-overview.png)](docs/guides/control-panel.md)
-
-A local browser control panel ships with the server for inspecting Resolve state, running source-safe analysis, drilling into analyzed clips and shots, and editing analysis output inline. See the [Control Panel Guide](docs/guides/control-panel.md) for the full tour.
-
-## Quick Start
-
-```bash
-npx davinci-resolve-mcp setup
-```
-
-Before connecting, open DaVinci Resolve Studio and set **Preferences > General > External scripting using** to **Local**. The npm launcher installs a managed copy under your user application-data directory, then runs the universal Python installer. The installer creates a virtual environment, detects Resolve paths, and can configure Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Zed, Continue, Cline, Roo Code, OpenCode, and JetBrains IDEs.
-
-For source installs:
-
-```bash
-git clone https://github.com/samuelgursky/davinci-resolve-mcp.git
-cd davinci-resolve-mcp
-python install.py
-```
-
-For platform paths, client-specific config, and manual setup, see [Installation and Configuration](docs/install.md).
-
-The installer and server check the latest GitHub release for MCP updates. Checks are best-effort and throttled; the server never blocks MCP startup for a prompt. The installer can prompt, snooze, ignore a release, disable checks, or apply an opt-in safe auto-update for clean git checkouts.
-
-## Local Control Panel
-
-Launch the single-user local control panel from the repository root:
-
-```bash
-venv/bin/python -m src.control_panel
-```
-
-The command starts a localhost server and opens the control panel in your browser. To have an AI coding agent do this, ask: **"Open the Resolve MCP control panel for this repo."** Agents should use `venv/bin/python -m src.control_panel` unless your Python environment is already active. Persisted analysis jobs refresh the local search index automatically after successful slices; the manual Build Index action is for rebuilding from existing reports.
-
-## Server Modes
-
-| Mode | Entry point | Tools | Best for |
-|------|-------------|-------|----------|
-| Compound | `src/server.py` | 34 | Default mode for most assistants. Related Resolve operations are grouped behind action parameters to keep context usage low. |
-| Full / granular | `src/server.py --full` or `src/resolve_mcp_server.py` | 341 | Power users who want one MCP tool per Resolve API method. |
-
-The compound server is recommended unless you specifically need the granular one-tool-per-method surface.
-
-## What You Can Do
-
-```text
-"List all projects and open the one called 'My Film'"
-"Create a timeline called 'Assembly Cut' from all clips in the current bin"
-"Build a multicam prep timeline from selected camera angles and preserve source media"
-"Detect 2-pops or slate claps and suggest record offsets for sync prep"
-"Publish analysis summaries, keywords, people, and slate hints into Resolve clip metadata"
-"Probe this timeline for gaps, overlaps, missing media, and source frame ranges"
-"Safely import this image sequence, organize it into bins, and normalize clip metadata"
-"Build a ProRes 422 HQ render plan, validate the settings, and queue the job"
-"Copy review markers from the timeline to the selected clip and export a review report"
-"Snapshot this clip's grade, validate a CDL update, and export a temp LUT"
-"Create a Fusion TextPlus overlay on the selected clip and verify graph connections"
-"Report audio channel mappings, voice isolation availability, and subtitle support"
-"Install this MCP-marked DCTL or script, classify refresh/restart needs, then remove it"
-```
-
-## Core Capabilities
-
-| Area | What the compound server supports |
-|------|-----------------------------------|
-| 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, 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 |
-| Fusion | Timeline-item comps, safe tool creation, input writes, port inspection, validated connections, scoped bulk writes |
-| Audio and Fairlight | Track/item probes, source mapping, guarded audio property writes, voice isolation, auto-sync planning, transcription/subtitle probes |
-| Render and deliver | Format/codec matrix probing, render settings validation, queued job lifecycle checks, guarded Quick Export |
-| Extension authoring | Fuse, DCTL, ACES DCTL, and Resolve-page Lua/Python script lifecycle helpers with safe MCP-marked install/remove |
-
-## Source Media Safety
-
-This project treats camera originals and source media as immutable. Analysis tools read source files and write reports only to sidecar, scratch, or project analysis directories; confirmed metadata publishing writes only to Resolve's project database. The server must not modify, transcode, proxy, or create derivatives of source media unless the user explicitly asks for that. See [Media Analysis Guide](docs/guides/media-analysis-guide.md) for the detailed source-safe workflow.
-
-## Security Posture
-
-The default server is a local stdio process launched by your MCP client; it does not expose a network listener or built-in multi-user auth surface. Tool metadata includes MCP client-safety hints for read-only, destructive, idempotent, and external-resource operations. See [Security Policy](SECURITY.md) for operational boundaries, confirmation guidance, and vulnerability reporting.
-
-## Key Stats
-
-| Metric | Value |
-|--------|-------|
-| MCP Tools | **32** compound / **341** granular |
-| Kernel Actions | **136** guarded workflow actions across 9 compound tools |
-| API Methods Covered | **336/336** (100%) |
-| Methods Live Tested | **331/336** (98.5%) |
-| Live Test Pass Rate | **331/331** (100%) |
-| Tested Against | DaVinci Resolve 19.1.3 Studio + Resolve 20.3.2 Studio |
-
-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` 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
-
-| Document | Use it for |
-|----------|------------|
-| [Installation and Configuration](docs/install.md) | Requirements, installer options, supported clients, server modes, manual config |
-| [API Coverage and Test Results](docs/reference/api-coverage.md) | Key stats, API coverage table, live-test status, full method reference |
-| [Kernel Action Coverage](docs/kernels/README.md) | Current guarded workflow action map |
-| [AI Skill Reference](docs/SKILL.md) | Operational context for AI assistants using the compound server |
-| [Control Panel Guide](docs/guides/control-panel.md) | Local browser panel tour: Overview, Review (bin/clip/shot), Analyze, Setup, Preferences |
-| [Media Analysis Guide](docs/guides/media-analysis-guide.md) | Source-safe FFprobe, FFmpeg, Whisper, sidecar, and analysis-root workflows |
-| [Multicam Setup Helper Guide](docs/guides/multicam-setup-guide.md) | Stacked timeline prep, helper/API boundary, and Resolve UI conversion steps |
-| [Editorial Decision Guide](docs/guides/editorial-decision-guide.md) | Project-owned editorial craft guidance for analysis and timeline decisions |
-| [Color Decision Guide](docs/guides/color-decision-guide.md) | Project-owned color correction guidance and Resolve color API boundaries |
-| [Contributing and Project Layout](docs/contributing.md) | Contribution workflow, platform support, security notes, repository structure |
-| [Security Policy](SECURITY.md) | Local stdio trust boundary, tool metadata, confirmation guidance, reporting |
-| [Release Process](docs/process/release-process.md) | Maintainer release checklist, version surfaces, validation, tags, and release notes |
-| [Changelog](CHANGELOG.md) | Historical release notes |
-
-Extension authoring references live in [docs/authoring](docs/authoring/). Resolve developer-package notes live in [docs/notes](docs/notes/) and [docs/integrations](docs/integrations/). Prompt recipes live in [examples](examples/).
-
-## Requirements
-
-- DaVinci Resolve Studio 18.5+ on macOS, Windows, or Linux. The free edition does not support external scripting.
-- Python 3.10+ (3.10-3.12 is the lowest-risk range). Python 3.13/3.14 also work on recent Resolve builds (verified on Studio 20.3.2); older builds may fail to connect on 3.13+, in which case use 3.10-3.12.
-- Resolve external scripting set to **Local**.
-
-Resolve 19.1.3 remains the compatibility baseline. Resolve 20.x scripting calls are additive, version-guarded, and live-tested on 20.3.2. Resolve 21.0 scripting additions (audio classification, speaker-detection transcription, IntelliSearch, slate analysis, motion-deblur, speech generation, session background-task control) are exposed behind runtime capability detection, so they stay inert on older builds and activate automatically on Resolve 21+.
-
-## Development
-
-```bash
-python src/server.py          # Compound server
-python src/server.py --full   # Granular server
-venv/bin/python tests/test_import.py
-venv/bin/python scripts/audit_api_parity.py
-```
-
-Release and validation rules are in [docs/process/release-process.md](docs/process/release-process.md). AI agents working in this repository should start with [AGENTS.md](AGENTS.md); Claude Code users can also read [CLAUDE.md](CLAUDE.md), which points to the same canonical instructions.
-
-## License
-
-MIT
-
-## Author
-
-Samuel Gursky (samgursky@gmail.com)
-- GitHub: [github.com/samuelgursky](https://github.com/samuelgursky)
-
-## Acknowledgments
-
-- Blackmagic Design for DaVinci Resolve and its scripting API
-- The Model Context Protocol team for enabling AI assistant integration
-- Anthropic for Claude Code, used extensively in development and testing
-
-### Community contributions
-
-- [@rgxdev](https://github.com/rgxdev) — configurable Media Pool inventory walk
-  (exclude bins + inventory limit), [#69](https://github.com/samuelgursky/davinci-resolve-mcp/pull/69) (v2.53.0)
-- [@swayll](https://github.com/swayll) — Source Track Selector investigation
-  ([#74](https://github.com/samuelgursky/davinci-resolve-mcp/issues/74)); confirmed
-  + documented API limitation (v2.57.1)

package/mcps/davinci-resolve-mcp/SECURITY.md

@@ -1,53 +0,0 @@
-# Security Policy
-
-## Supported Use
-
-`davinci-resolve-mcp` is a local stdio MCP server for controlling DaVinci
-Resolve Studio through the official Resolve Scripting API. It is intended to run
-under the same local user account that operates Resolve.
-
-The default server does not expose a network listener, HTTP API, remote shell, or
-multi-user authentication surface. Access control is delegated to the MCP client
-that launches the stdio process and to the local operating-system user session.
-
-## Operational Boundaries
-
-- Keep Resolve external scripting set to **Local** unless you have a separate,
-  intentional remote-control deployment plan.
-- Treat the MCP client as the user-confirmation boundary. Clients should ask for
-  confirmation before destructive or high-impact actions such as quitting
-  Resolve, deleting projects, replacing clips, relinking media, deleting markers,
-  changing render/project settings, or installing/removing scripts, Fuses, DCTLs,
-  and presets.
-- Source media is immutable by default. This server must not modify, transcode,
-  proxy, relink, replace, or create derivatives of source media unless the user
-  explicitly asks for that exact operation.
-- Analysis outputs belong in sidecar files, session scratch space, or the
-  configured `davinci-resolve-mcp-analysis` project root.
-
-## Tool Metadata
-
-Tools use MCP `ToolAnnotations` where supported:
-
-- `readOnlyHint` for probe/list/get operations.
-- `destructiveHint` for operations that overwrite, delete, relink, replace,
-  change project state, or can otherwise cause meaningful workflow impact.
-- `idempotentHint` for repeatable state changes such as page switching.
-- `openWorldHint` for operations that touch filesystem paths, media, render
-  output, scripts, Fuses, DCTLs, presets, or other external resources.
-
-Compound tools group multiple actions behind an `action` parameter, so their
-annotation is conservative when any action in the group can mutate state.
-
-## Reporting Vulnerabilities
-
-Please report security issues privately by opening a GitHub security advisory or
-emailing the maintainer listed in the README. Include:
-
-- Affected version or commit.
-- MCP client and operating system.
-- Minimal reproduction steps.
-- Expected and actual impact.
-
-Please do not publish exploit details until there is a coordinated fix or a
-reasonable disclosure window has passed.