@hybridlabor-api/aos 4.3.0 → 4.4.0

package/mcps/davinci-resolve-mcp/docs/kernels/color-grade-kernel.md

@@ -1,103 +0,0 @@
-# Color / Grade Kernel
-
-The Color / Grade kernel expands `timeline_item_color` into a safer grade
-inspection, versioning, copy, LUT, DRX, Gallery, and color-group boundary layer.
-
-Live validation was run against DaVinci Resolve Studio 20.3.2.9 with a
-disposable `_mcp_color_grade_probe_*` project and generated synthetic color-bar
-media. Final release probe counts:
-
-| Status | Count |
-| --- | ---: |
-| `supported` | 25 |
-| `version_or_page_dependent` | 2 |
-| `not_applicable` | 1 |
-| `partially_supported` | 0 |
-| `unsupported` | 0 |
-| `error` | 0 |
-
-The version/page-dependent results were Gallery still export and
-`ExportCurrentFrameAsStill(.drx)` in this Resolve/UI state. `safe_apply_drx`
-was marked `not_applicable` because the probe could not produce a DRX file
-through the public API in that run.
-
-## Added Actions
-
-All actions are exposed through `timeline_item_color`.
-
-| Action | Purpose |
-| --- | --- |
-| `grade_capabilities` | Return callable item methods, graph sources, LUT export types, version modes, guards, and known boundaries. |
-| `probe_grade_item` | Snapshot grade versions, item graph, color group, cache states, ids, names, and callable methods. |
-| `probe_node_graph` | Inspect item, timeline, pre-clip group, or post-clip group graph availability and node metadata. |
-| `safe_set_cdl` | Validate and normalize CDL payloads before calling `SetCDL`; supports dry run. |
-| `safe_copy_grade` | Resolve target timeline item IDs before calling `CopyGrades`; supports dry run. |
-| `safe_apply_drx` | Validate DRX file existence and temp-path guard before calling `ApplyGradeFromDRX`. |
-| `safe_export_lut` | Resolve LUT export type aliases and require temp output paths by default. |
-| `grade_version_snapshot` | Read current, local, and remote grade version names. |
-| `grade_version_restore` | Safely load a named local/remote version after verifying it exists. |
-| `color_group_capabilities` | Report color groups and pre/post graph availability. |
-| `gallery_capabilities` | Report Gallery availability, albums, and callable Gallery methods. |
-| `grade_boundary_report` | Return capabilities, current item snapshot, color groups, Gallery, and timeline graph summary. |
-
-## Scope Matrix
-
-| Scope | Probe Support | Mutation Support | Notes |
-| --- | --- | --- | --- |
-| Timeline item graph | Supported | CDL, LUT export, grade copy, DRX apply when file exists | Primary grade entry point. |
-| Timeline graph | Supported | Raw `graph` tool can mutate | Live probe found zero timeline nodes by default. |
-| Color group pre-clip graph | Supported | Raw `graph` tool can mutate | Requires existing `group_name`. |
-| Color group post-clip graph | Supported | Raw `graph` tool can mutate | Requires existing `group_name`. |
-| Gallery albums/stills | Partially environment dependent | Album create and list supported; still export may require UI panel state | Public API can return false if Gallery export is not ready. |
-
-## Supported Findings
-
-- `SetCDL` worked after payload validation and Resolve-specific string
-  normalization.
-- Item graph and timeline graph objects were available; item graph exposed one
-  node in the synthetic clip.
-- Node graph metadata probes worked for node count, LUT, cache mode, label, and
-  tools-in-node where Resolve returned data.
-- Local grade version add, rename, load, restore, and delete worked when the
-  version to delete was not currently loaded.
-- `CopyGrades` worked from the first synthetic timeline item to the second.
-- `ExportLUT` produced a 33-point `.cube` file under the generated temp probe
-  directory.
-- Color group create, assign, capability probe, pre/post graph probe, remove,
-  and delete worked.
-- Gallery capability and album list/create calls worked.
-
-## Boundaries
-
-- Node graph internals are intentionally limited by Resolve's public API. The
-  kernel can inspect high-level node count and a few node attributes, but not
-  every grading control inside a node.
-- `ApplyGradeFromDRX` replaces the target graph. There is no append mode in the
-  public API.
-- `safe_apply_drx` requires an existing DRX path. The live release probe could
-  not produce one because both Gallery still export and
-  `ExportCurrentFrameAsStill(.drx)` were unavailable in the current UI/build
-  state.
-- Gallery still export may require the Color page Gallery panel to be open and
-  ready. The public API returned false in the release probe even after the page
-  was active.
-- LUT export writes files, so `safe_export_lut` requires temp paths by default.
-- Stabilize, Smart Reframe, Magic Mask, and Magic Mask regeneration are exposed
-  as callable methods but are not forced in the boundary report because they can
-  be asynchronous, page dependent, and expensive.
-
-## Live Probe
-
-Run the live boundary probe with:
-
-```bash
-python3.11 tests/live_color_grade_validation.py --output-dir /tmp/color-grade-probe
-```
-
-The harness creates a disposable project, generates synthetic color-bar media,
-builds a two-item timeline, probes grade/node/version/copy/LUT/group/Gallery
-surfaces, writes JSON and Markdown reports, deletes the project, and removes
-generated media and exported probe files.
-
-Use `--keep-open` only when you intentionally want to inspect the disposable
-project by hand.

package/mcps/davinci-resolve-mcp/docs/kernels/extension-authoring-kernel.md

@@ -1,101 +0,0 @@
-# Extension Authoring Kernel
-
-The Extension Authoring kernel turns the existing `fuse_plugin`, `dctl`, and
-`script_plugin` tools into a lifecycle-aware boundary layer for generated
-Resolve extensions.
-
-Kernel actions are exposed through `script_plugin` as the cross-extension
-orchestrator. The raw authoring tools remain available for direct file
-operations.
-
-Live validation was run against DaVinci Resolve Studio 20.3.2.9 with only
-MCP-marked `_mcp_` Fuse, DCTL, ACES DCTL, and Resolve-page script files. Final
-release probe counts:
-
-| Status | Count |
-| --- | ---: |
-| `supported` | 14 |
-| `partially_supported` | 1 |
-| `unsupported` | 1 |
-| `not_applicable` | 0 |
-| `version_or_page_dependent` | 0 |
-| `error` | 0 |
-
-The unsupported result is intentional: safe install rejects provided source that
-does not include the expected MCP marker.
-
-## Added Actions
-
-All kernel actions are exposed through `script_plugin`.
-
-| Action | Purpose |
-| --- | --- |
-| `extension_capabilities` | Report Fuse, DCTL, script paths, template kinds, MCP markers, lifecycle rules, and safety guards. |
-| `probe_fuse_lifecycle` | Generate, validate, optionally install/read/list/remove a Fuse template. |
-| `probe_dctl_lifecycle` | Generate, validate, optionally install/read/list/remove a LUT or ACES DCTL template. |
-| `probe_script_lifecycle` | Generate, validate, optionally install/read/list/execute/remove a Resolve-page script. |
-| `safe_install_extension` | Install Fuse, DCTL, or script source/templates with `_mcp_` name and marker guards. |
-| `safe_remove_extension` | Remove Fuse, DCTL, or script files only when the file is MCP-marked by default. |
-| `refresh_or_restart_required` | Classify whether an extension needs LUT refresh, menu refresh, UI reload, or Resolve restart. |
-| `extension_boundary_report` | Return lifecycle classifications, template validation matrix, and dry-run probes. |
-
-## Lifecycle Map
-
-| Surface | Install Target | Live Pickup | Restart |
-| --- | --- | --- | --- |
-| Fuse | Fusion Fuses directory | Existing Fuses can be UI-reloaded from Inspector; MCP cannot trigger it. | Required for new Fuse registration. |
-| Regular DCTL | LUT directory | `project_settings.refresh_luts` picks it up. | Not required for LUT-category DCTLs. |
-| ACES IDT/ODT DCTL | ACES Transforms IDT/ODT | Not picked up by LUT refresh. | Required. |
-| Resolve-page script | Fusion/Scripts category directory | Workspace Scripts menu refreshes when opened. | Not required. |
-| Inline Python script | Temp file subprocess | Captured synchronously. | Not required. |
-| Inline Lua script | Temp Lua file via `fusion.RunScript` | Captured through Fusion app data bridge. | Not required. |
-
-## Supported Findings
-
-- Fuse template generation, validation, install, read, MCP-managed list, and
-  safe marker-enforced remove worked.
-- Regular LUT DCTL template generation, validation, install into `LUT/MCP`,
-  read, list, `project_settings.refresh_luts`, and safe remove worked.
-- ACES IDT DCTL template generation, install into `ACES Transforms/IDT/MCP`,
-  read, list, and safe remove worked. It remains restart-required before Resolve
-  can use the transform.
-- Python Resolve-page script template generation, install, read, list, execute,
-  stdout/stderr capture, and safe remove worked.
-- `script_plugin.run_inline` worked for Python with stdout capture.
-- `script_plugin.run_inline` worked for Lua with stdout and return-value capture.
-- The template matrix generated and validated every Fuse, DCTL, and script
-  template kind.
-- Safe install rejected unmarked provided source by default.
-
-## Boundaries
-
-- Installed Lua script execution through `fusion.RunScript(path)` returned
-  `success=False` in the release probe, even though install/read/list/remove
-  worked and inline Lua execution worked. Use `run_inline(language="lua")` when
-  captured output/return values matter.
-- New Fuses still require a Resolve restart to appear as registered Fusion
-  tools. The MCP can install/remove files but cannot force Fusion to register a
-  new Fuse in-process.
-- ACES IDT/ODT DCTLs are scanned at Resolve startup. `RefreshLUTList` is only
-  appropriate for LUT-category DCTLs.
-- Template validation is structural/parser-level. It does not prove a Fuse
-  renders correctly after restart or that every DCTL compiles on every GPU
-  backend.
-- Safe remove refuses to delete unmarked extension files unless
-  `require_marker=False` is explicitly passed.
-
-## Live Probe
-
-Run the live boundary probe with:
-
-```bash
-python3.11 tests/live_extension_authoring_validation.py --output-dir /tmp/extension-authoring-probe
-```
-
-The harness creates a disposable `_mcp_` project, installs and removes a
-generated Fuse, regular DCTL, ACES DCTL, Python script, and Lua script, probes
-inline Python/Lua execution, writes JSON and Markdown reports, deletes the
-project, and removes its temp work directory.
-
-Use `--keep-open` only when you intentionally want to inspect the disposable
-project by hand.

package/mcps/davinci-resolve-mcp/docs/kernels/fusion-composition-kernel.md

@@ -1,121 +0,0 @@
-# Fusion Composition Kernel
-
-The Fusion Composition kernel expands `fusion_comp` into a safer graph
-inspection, tool creation, input write, connection, and boundary-report layer
-for timeline item Fusion comps and active Fusion page comps.
-
-Live validation was run against DaVinci Resolve Studio 20.3.2.9 with a
-disposable `_mcp_fusion_composition_probe_*` project and generated synthetic
-video media. Final release probe counts:
-
-| Status | Count |
-| --- | ---: |
-| `supported` | 18 |
-| `partially_supported` | 0 |
-| `unsupported` | 0 |
-| `version_or_page_dependent` | 0 |
-| `not_applicable` | 0 |
-| `error` | 0 |
-
-## Added Actions
-
-All actions are exposed through `fusion_comp`.
-
-| Action | Purpose |
-| --- | --- |
-| `fusion_graph_capabilities` | Return current comp summary, common tool IDs, supported graph operations, and known boundaries. |
-| `probe_fusion_comp` | Snapshot composition attrs, tool count, and tool summaries, optionally including input/output ports. |
-| `probe_fusion_tool` | Inspect one tool by name, including attrs and optional input/output metadata. |
-| `safe_add_tool` | Validate a tool type, add it with optional naming, and return a normalized tool summary; supports dry run. |
-| `safe_set_inputs` | Batch write inputs on one tool with optional readback classification. |
-| `safe_connect_tools` | Validate source/target tools before connecting a source output to a target input. |
-| `fusion_boundary_report` | Return graph capabilities plus a composition snapshot for the selected comp scope. |
-| `bulk_set_expressions` | Batch `SetExpression` across scoped timeline-item Fusion comps. Each op needs `tool_name`, `input_name`, `expression`, plus a timeline scope. Wraps each op in `StartUndo`/`EndUndo` + `comp.Lock`. |
-| `group_settings_export` | Save a named `GroupOperator`'s settings to a `.setting` file via `SaveSettings`, returning a parsed published-input summary. |
-| `group_settings_splice_inputs` | Replace the `Inputs = ordered() { ... }` block of `source_path` with the matching block from `template_path` and write `dest_path`. Read-only against Resolve; pure file operation. |
-| `group_settings_load` | Backup the current group state, then `LoadSettings` from a `.setting` file. Wrapped in `StartUndo`/`EndUndo` + `comp.Lock` so Fusion's Ctrl+Z can reverse it. Backup path is returned alongside any error. |
-| `probe_group_published_inputs` | Read live published `Input1..InputN` slots off a `GroupOperator`, optionally cross-referenced with a `.setting` file summary. |
-
-The pre-existing `bulk_set_inputs` action remains the batch path for applying
-input writes across multiple explicitly scoped timeline-item Fusion comps.
-
-### `group_settings_splice_inputs` notes
-
-The Fusion `.setting` format is a Lua-like nested structure: an InstanceInput
-commonly contains `UserControls = ordered() { Custom = { ... } }` tables, so any
-parsing that uses a flat regex will truncate bodies at the first inner `}`. This
-kernel uses balanced-brace scanning end-to-end. Practical implications:
-
-- The action only swaps the published `Inputs = ordered() { ... }` block. The
-  group's outer name, inner `Tools = ordered() { ... }` section, and surrounding
-  structure are preserved byte-for-byte.
-- You must provide the *new* layout as a real `.setting` file (typically
-  exported from a known-good group via `group_settings_export`). The kernel does
-  not ship hardcoded templates.
-- `template_group_name` is optional when the template file contains a single
-  `GroupOperator`; pass it when the template file contains multiple groups and
-  you want a specific one.
-
-### `group_settings_load` Edit-page caveat
-
-`LoadSettings` may update inner tool wiring but not refresh Edit-page
-`InstanceInput` order until the group is selected in Fusion and reloaded via UI.
-This is a Resolve quirk, not a kernel bug. The action always backs up the group
-to a timestamped sibling of `settings_path` first; the backup path is returned
-in success and in error responses.
-
-## Scope Matrix
-
-| Scope | Probe Support | Mutation Support | Notes |
-| --- | --- | --- | --- |
-| Timeline item Fusion comp | Supported | Tool add, input writes, connections, frame range, comp export | Primary safe automation target. Pass `timeline_item`, `clip_id`, or `timeline_item_id`. |
-| Active Fusion page comp | Supported when a current comp exists | Raw and safe graph helpers work against the active page comp | Page state matters; omit timeline scope only when that is intentional. |
-| Bulk timeline item comps | Supported | `bulk_set_inputs` requires explicit timeline scope per op | Avoids accidentally mutating the active page comp. |
-| Comp import/export | Supported through `timeline_item_fusion` | Export succeeded to a temp `.setting` file in the live probe | Import should use temp or explicitly approved paths. |
-
-## Supported Findings
-
-- Timeline item Fusion comp creation, count, and name listing worked on the
-  generated synthetic clip.
-- `fusion_graph_capabilities` and `fusion_boundary_report` produced stable
-  graph summaries without requiring Fusion page focus.
-- `safe_add_tool` successfully added `Background`, `TextPlus`, `Merge`,
-  `Transform`, and `Blur` tools to a timeline item comp.
-- `safe_set_inputs` wrote and read back text and background color inputs.
-- `probe_fusion_tool` returned normalized attrs plus input/output metadata for
-  the generated `TextPlus` tool.
-- `safe_connect_tools` connected the generated text tool to `MediaOut1`.
-- `bulk_set_inputs` wrote multiple scoped input changes in one request.
-- `set_frame_range` and timeline item comp export succeeded against the
-  disposable timeline item comp.
-
-## Boundaries
-
-- Tool availability varies by Resolve/Fusion build. The kernel reports common
-  tool IDs but does not pretend every Fusion tool is installed everywhere.
-- Fusion inputs are heterogeneous. Some are readable after writes, some coerce
-  values, and some can be effectively write-only depending on the tool.
-- Active Fusion page comps and timeline item comps are different scopes. The
-  safe helpers support both, but bulk mutation requires timeline scope.
-- `fusion_comp.render` is still exposed as the raw API path, but the live kernel
-  probe does not force a render because renderability depends on graph shape,
-  MediaOut state, and page/build behavior.
-- The public API exposes tool attrs and ports, not a semantic model of every
-  effect parameter. Higher-level wrappers should probe before assuming a
-  control exists.
-
-## Live Probe
-
-Run the live boundary probe with:
-
-```bash
-python3.11 tests/live_fusion_composition_validation.py --output-dir /tmp/fusion-composition-probe
-```
-
-The harness creates a disposable project, generates synthetic video media,
-builds a timeline item Fusion comp, probes tool creation, input writes, graph
-inspection, connections, bulk writes, frame range, comp export, and boundary
-reporting, then deletes the project and removes generated media.
-
-Use `--keep-open` only when you intentionally want to inspect the disposable
-project by hand.

package/mcps/davinci-resolve-mcp/docs/kernels/media-pool-ingest-kernel.md

@@ -1,147 +0,0 @@
-# Media Pool / Ingest Kernel
-
-The Media Pool / Ingest kernel expands the raw Resolve Media Storage,
-Media Pool, Folder, MediaPoolItem, and MediaPoolItem marker wrappers into a
-safer agent-facing layer for import, organization, metadata, annotation, and
-link-boundary work.
-
-Source media integrity remains the first rule: these helpers do not transcode,
-render, proxy-generate, overwrite, or mutate source files. They validate paths
-before calling Resolve, and the live harness uses generated synthetic media in
-disposable `_mcp_...` projects only.
-
-## New Compound Actions
-
-All actions are under `media_pool(action=...)`.
-
-| Action | Status | Purpose |
-| --- | --- | --- |
-| `ingest_capabilities` | Supported | Maintained support/partial/unsupported map for ingest workflows. |
-| `probe_media_pool` | Supported | Read-only Media Pool, folder, selected clip, and method availability snapshot. |
-| `probe_ingest_item` | Supported | Read-only metadata/property/annotation/audio snapshot for clip IDs or selected clips. |
-| `safe_import_media` | Supported | Validates existing paths, optionally targets a Media Pool folder, supports dry-run, then calls `ImportMedia(paths)`. |
-| `safe_import_sequence` | Supported | Validates printf-style sequence patterns and frame ranges before calling `ImportMedia([{clipInfo}])`. |
-| `safe_import_folder` | Supported dry-run | Validates folder paths before `ImportFolderFromFile`; dry-run is recommended unless importing Resolve folder exports intentionally. |
-| `setup_multicam_timeline` | Supported setup helper | Creates a stacked multicam prep timeline from Media Pool clips, with one angle per video track and optional matching audio tracks. |
-| `organize_clips` | Supported | Moves clips to an existing or optionally created Media Pool folder. |
-| `copy_metadata` | Supported | Copies Resolve metadata and optional third-party metadata from one clip to target clips. |
-| `normalize_metadata` | Supported | Bulk-writes explicit metadata and third-party metadata to clip IDs or selected clips. |
-| `probe_clip_properties` | Supported | Read-only full and known-key clip property snapshots. |
-| `metadata_field_inventory` | Supported | Read-only metadata, clip-property, and inferred Metadata-panel group inventory for selected or explicit clips. |
-| `safe_relink` | Supported | Validates clip IDs and target directory before `RelinkClips`; supports dry-run. |
-| `safe_unlink` | Supported | Validates clip IDs before `UnlinkClips`; supports dry-run. |
-| `link_proxy_checked` | Supported | Validates clip ID and proxy file path before `LinkProxyMedia`. |
-| `link_full_resolution_checked` | Supported on Resolve 20+ | Version-guards and validates path before `LinkFullResolutionMedia`. |
-| `set_clip_marks` | Supported | Bulk `SetMarkInOut` for clip IDs or selected clips. |
-| `clear_clip_marks` | Supported | Bulk `ClearMarkInOut` for clip IDs or selected clips. |
-| `copy_clip_annotations` | Supported | Copies clip color, flags, and media-pool item markers from one clip to targets. |
-| `media_pool_boundary_report` | Supported | Combines capabilities, Media Pool probe, and optional item probes. |
-
-## Multicam Setup Helper
-
-`setup_multicam_timeline` is intentionally documented as a helper tool rather
-than API coverage. It prepares the timeline structure Resolve's multicam UI can
-consume, while leaving native conversion to Resolve.
-
-Supported planning inputs:
-
-- `clip_ids`: simple one-angle-per-clip setup.
-- `angles`: explicit rows with `clip_id`, `angle_name`, source range, track
-  index, audio track index, source timecode, record frame, or record offset.
-- `sync_mode`: `stack_start`, `source_timecode`, or `record_frame`.
-- `include_audio`: append audio-only rows for each angle.
-- `dry_run`: return the planned append rows without creating a timeline.
-
-After the helper creates the setup timeline, verify sync in Resolve, duplicate
-the timeline if it should remain recoverable, then use the Media Pool context
-menu command "Convert Compound Clips (Timelines) to Multicam Clips." See
-`docs/guides/multicam-setup-guide.md` for examples and the Resolve 20 manual
-reference.
-
-For 2-pop or slate-clap assisted sync, run
-`media_analysis(action="detect_sync_events")` first and pass its suggested
-`record_offset` values into `setup_multicam_timeline(sync_mode="record_frame")`.
-If the detected sync points should become Resolve markers, ask the user first;
-the guarded write step is `media_analysis(action="add_sync_event_markers",
-params={"confirm": true, ...})`.
-
-## Supported Boundaries
-
-- Media Storage browsing: volumes, subfolders, and file listing.
-- Media import through simple paths and image sequence clipInfos.
-- Safe import helpers with path validation and dry-run support.
-- Media Pool organization: folder creation, current folder switching, selected
-  clip get/set, and clip moves.
-- Multicam setup timelines: source-safe placement of existing Media Pool clips
-  on per-angle tracks via `AppendToTimeline([{clipInfo}])`, with stack-start,
-  manual record-frame, or source-timecode planning.
-- Metadata: scalar and dict metadata writes, third-party metadata writes,
-  metadata copy, explicit normalization, and field inventory for mapping
-  analysis writeback targets to Resolve metadata/clip-property surfaces.
-- Clip property probing: full snapshot plus known keys such as `File Path`,
-  `Type`, `FPS`, `Duration`, `Resolution`, `Codec`, and audio fields.
-- Media Pool item annotations: markers, custom marker data, flags, clip color,
-  and mark in/out.
-- Link boundaries: relink/unlink dry-runs, proxy linking, and Resolve 20+
-  full-resolution media linking, with generated media used for live validation.
-- Export metadata to a caller-provided path.
-
-## Partial Or Version-Dependent Areas
-
-- Clip property writes are still key/media/build dependent. The kernel probes
-  properties read-only; raw `media_pool_item.set_clip_property` remains
-  available for explicit writes.
-- Proxy and full-resolution linking may accept paths without deep media
-  compatibility validation. Use checked helpers for path validation, and verify
-  editorial intent before changing real project links.
-- Audio transcription depends on Studio features, installed language
-  components, media type, and Resolve state; it remains exposed on existing
-  `folder` and `media_pool_item` actions, not folded into the ingest live pass.
-- Image sequence import depends on a valid printf-style pattern and Resolve's
-  still/sequence interpretation.
-- `ImportFolderFromFile` is a Resolve folder/project interchange operation, not
-  a general filesystem import. The safe helper validates the folder and supports
-  dry-run to prevent accidental misuse.
-
-## Unsupported Or Intentionally Guarded
-
-- Non-media files are not imported. The final live probe classified a generated
-  `.txt` fixture as `unsupported` because Resolve returned zero imported items
-  without raising an API error.
-- The kernel does not create proxies, transcodes, renders, or derivatives of
-  source media.
-- Destructive replacement APIs (`ReplaceClip`, `ReplaceClipPreserveSubClip`)
-  remain raw explicit clip actions and are not used by the kernel probe.
-- Resolve does not guarantee a stable writable metadata schema across versions
-  or locales.
-- Native multicam clip creation, angle switching, and multicam flattening are
-  not exposed by the public Resolve scripting API. The setup helper prepares a
-  timeline that can be converted to a native multicam clip in Resolve's UI. See
-  the installed DaVinci Resolve 20 Manual, Edit > Chapter 42, "Multicam
-  Editing," for the current UI workflow.
-
-## Live Evidence
-
-Final validation ran on May 9, 2026 with DaVinci Resolve Studio 20.3.2.9 and
-Python 3.11.14.
-
-```
-python3.11 tests/live_media_pool_ingest_validation.py \
-  --output-dir /private/tmp/media-pool-ingest-probe-20260509-release
-```
-
-Result:
-
-- `supported`: 56
-- `unsupported`: 1
-- `partially_supported`: 0
-- `version_or_page_dependent`: 0
-- `write_only_unverifiable`: 0
-- `read_only`: 0
-- `not_applicable`: 0
-- `error`: 0
-
-The live harness created and deleted a disposable project named
-`_mcp_media_pool_ingest_probe_1778341105`, generated synthetic video/audio/still
-fixtures, wrote JSON and Markdown reports, and removed the generated media
-directory after the report was written.

package/mcps/davinci-resolve-mcp/docs/kernels/project-lifecycle-kernel.md

@@ -1,120 +0,0 @@
-# Project / Database / Archive Kernel
-
-The Project / Database / Archive kernel expands `project_manager` into a guarded
-project lifecycle, settings, database, preset, and archive boundary layer.
-
-Live validation was run against DaVinci Resolve Studio 20.3.2.9 with disposable
-`_mcp_project_lifecycle_*` projects only. The probe created an empty timeline,
-saved the disposable project, exported/imported through a temp DRP, exercised
-project folders, layout presets, page switching, database dry-runs, settings
-snapshot/write/restore, and archive guards. Final release probe counts:
-
-| Status | Count |
-| --- | ---: |
-| `supported` | 35 |
-| `partially_supported` | 5 |
-| `unsupported` | 1 |
-| `not_applicable` | 1 |
-| `version_or_page_dependent` | 0 |
-| `error` | 0 |
-
-The unsupported result is intentional: archive calls that request source media,
-render cache, or proxy media are rejected by default unless explicitly opted in.
-
-## Added Actions
-
-All kernel actions are exposed through `project_manager`.
-
-| Action | Purpose |
-| --- | --- |
-| `project_capabilities` | Report ProjectManager, Project, layout preset, render preset, and safety-guard availability. |
-| `probe_project_lifecycle` | Snapshot current project, current folder, project list, folder list, and ProjectManager methods. |
-| `probe_project_settings` | Read candidate project settings and optionally dry-run/write-restore candidates. |
-| `safe_project_create` | Create disposable `_mcp_` projects with optional temp media-location guard. |
-| `safe_project_export` | Export disposable projects to temp DRP paths; stills/LUTs are off by default. |
-| `safe_project_import` | Import temp DRP projects under disposable `_mcp_` names. |
-| `safe_project_archive` | Archive disposable projects with media/cache/proxy flags forced false by default. |
-| `safe_project_restore` | Restore temp project archives or DRPs under disposable `_mcp_` names. |
-| `safe_project_delete` | Delete disposable projects, with explicit `close_current=True` required for the open project. |
-| `safe_set_project_settings` | Validate, write, read back, and restore project settings. |
-| `project_settings_snapshot` | Snapshot project settings, presets, timeline count, current timeline, render presets, and color groups. |
-| `database_capabilities` | Read current database, database list, and switch safety constraints. |
-| `safe_set_current_database` | Dry-run database switches by default because switching closes open projects. |
-| `preset_lifecycle_probe` | Report project, render, quick-export, Fairlight, layout, render-preset, and burn-in preset surfaces. |
-| `project_boundary_report` | Return the full lifecycle, settings, database, preset, and cloud boundary report. |
-
-`project_manager_folders` also now normalizes both documented string folder
-returns and newer folder-object returns.
-
-## Supported Findings
-
-- Disposable project creation, current-project readback, save, and delete worked.
-- Empty timeline creation inside the disposable project worked and gave the
-  project enough structure for DRP export.
-- DRP export and `ImportProject` under a new `_mcp_` name worked.
-- Project folder list/create/open/current/goto-parent/delete worked.
-- Full project settings snapshots worked, including project presets, render
-  presets, quick-export presets, timeline count, current timeline, and color
-  groups.
-- Same-value write/readback/restore worked for `timelineResolutionWidth`.
-- Database current/list probing worked, and guarded database switching correctly
-  dry-ran by default.
-- Layout preset save/update/load/export/import/delete worked with `_mcp_`
-  temp names.
-- All Resolve pages opened successfully through `resolve_control.open_page`.
-- Keyframe mode readback worked.
-- The combined boundary report worked and includes cloud methods as
-  shape-only, infrastructure-dependent capabilities.
-
-## Boundaries
-
-- `ProjectManager.RestoreProject` returned false when pointed at the exported
-  DRP. `ImportProject` is the supported path for temp DRP round-trips in this
-  probe.
-- `ProjectManager.ArchiveProject` returned false for both a `.dra` path and a
-  folder-style path, even with `src_media=False`, `render_cache=False`, and
-  `proxy_media=False`.
-- Archive calls with source media, render cache, or proxy media are blocked by
-  default. This protects source media integrity and avoids large cache/proxy
-  copies.
-- `Resolve.SetKeyframeMode` returned false when setting the current keyframe
-  mode back to itself, though `GetKeyframeMode` worked.
-- `Resolve.ExportRenderPreset` returned false for the first listed render
-  preset in the release probe. Render/quick-export preset listing still worked.
-- `Project.GetRenderSettings` was not present on the live Project object, so
-  render settings remain covered by the Render / Deliver kernel's existing
-  guarded actions.
-- Cloud project create/load/import/restore methods are exposed by the API, but
-  default validation treats them as shape-only because they require Resolve
-  cloud infrastructure and media-location settings.
-
-## Safety Rules
-
-- Safe project create/import/restore/delete actions require names beginning with
-  `_mcp_` unless `allow_non_mcp_name=True`.
-- Safe export/import/archive/restore paths must be under the system temp
-  directory unless `require_temp_path=False`.
-- Safe project delete refuses to delete the currently open project unless
-  `close_current=True`.
-- Safe database switching is a dry-run unless both `allow_switch=True` and
-  `dry_run=False` are provided.
-- Safe archive defaults all media/cache/proxy flags to false and rejects any
-  true flag unless `allow_media_archive=True`.
-
-## Live Probe
-
-Run the live boundary probe with:
-
-```bash
-python3.11 tests/live_project_lifecycle_validation.py --output-dir /tmp/project-lifecycle-probe
-```
-
-The harness creates disposable `_mcp_` projects, creates an empty timeline,
-saves the project, probes DRP export/import, archive/restore boundaries,
-project folder lifecycle, project settings write/restore, database dry-runs,
-layout preset lifecycle, page switching, keyframe mode, preset listings, writes
-JSON and Markdown reports, deletes disposable projects and layout presets, and
-removes temp work files.
-
-Use `--keep-open` only when you intentionally want to inspect the disposable
-projects by hand.