@hybridlabor-api/aos 4.2.0 → 4.4.0

package/mcps/davinci-resolve-mcp/docs/kernels/render-deliver-kernel.md

@@ -1,92 +0,0 @@
-# Render / Deliver Kernel
-
-The Render / Deliver kernel adds a safer planning and validation layer over
-Resolve's render queue, render settings, format/codec discovery, presets, and
-Quick Export APIs.
-
-Live probes use disposable `_mcp_...` projects, generated synthetic media, and
-temporary output directories only. They may render derivatives of generated
-fixtures, but never render, transcode, proxy, or overwrite user source media.
-
-## New Compound Actions
-
-All actions are under `render(action=...)`.
-
-| Action | Status | Purpose |
-| --- | --- | --- |
-| `render_capabilities` | Supported | Reports render method availability, formats, presets, quick-export presets, setting keys, and safety guards. |
-| `probe_render_matrix` | Supported | Builds a format/codec/resolution compatibility matrix. |
-| `probe_render_settings` | Supported with readback boundary | Captures current format/codec, mode, jobs, render state, and settings when Resolve exposes settings readback. |
-| `validate_render_settings` | Supported | Validates supported setting keys, value types, frame ranges, and optional temp-target requirements. |
-| `safe_set_render_settings` | Supported | Validates settings before `SetRenderSettings`, reports post-set readback/coercion when available, and supports dry-run. |
-| `prepare_render_job` | Supported | Validates target directory/settings, optionally sets format/codec, applies settings, and adds a render job without starting it. |
-| `render_job_lifecycle_probe` | Supported | Adds a job, reads status, and deletes the job to validate queue lifecycle safely. |
-| `quick_export_capabilities` | Supported | Lists Quick Export presets and enforced safety guards. |
-| `safe_quick_export` | Supported dry-run | Validates temp target, forces `EnableUpload=False`, and requires `allow_render=True` before actual Quick Export execution. |
-| `export_render_boundary_report` | Supported | Combines capabilities, settings snapshot, format matrix, and Quick Export capabilities. |
-
-## Supported Boundaries
-
-- Format discovery through `GetRenderFormats`.
-- Codec discovery for every returned format through `GetRenderCodecs`.
-- Resolution discovery for every format/codec pair through
-  `GetRenderResolutions`.
-- Current format/codec set and readback.
-- Current render mode get/set.
-- Render preset list, save, and delete for temporary MCP-named presets.
-- Render setting validation for documented `SetRenderSettings` keys.
-- Safe render job preparation into a temp target directory.
-- Job queue lifecycle: add, status, delete.
-- Actual synthetic render start/completion for a two-second generated timeline.
-- Quick Export preset discovery and guarded dry-run planning.
-
-## Version Or Page Dependent Boundaries
-
-- `GetRenderSettings` is documented, but in the final Resolve Studio 20.3.2.9
-  live probe the project attribute was not callable. The kernel treats settings
-  readback as version/page dependent and still validates and applies settings
-  through `SetRenderSettings`.
-- Render format and codec availability is machine, OS, license, and plugin
-  dependent. The final live probe found 23 formats and 99 format/codec pairs.
-- Some settings may be accepted but not readable for coercion checks on builds
-  where `GetRenderSettings` is unavailable.
-- Quick Export actual execution is intentionally gated behind
-  `allow_render=True`, because it starts rendering immediately and can involve
-  upload-capable presets. The safe helper always forces `EnableUpload=False`.
-
-## Unsupported Or Guarded
-
-- Render lifecycle helpers require temp output directories by default. Passing
-  real delivery paths requires explicit lower-level actions or disabling the
-  temp guard.
-- Upload-enabled Quick Export is not allowed through `safe_quick_export`.
-- Import/export of render and burn-in preset files remains exposed through the
-  existing `render_presets` tool, but the live kernel probe does not fabricate
-  arbitrary preset files.
-
-## 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_render_deliver_validation.py \
-  --output-dir /private/tmp/render-deliver-probe-20260509-release
-```
-
-Result:
-
-- `supported`: 23
-- `version_or_page_dependent`: 1
-- `unsupported`: 0
-- `partially_supported`: 0
-- `write_only_unverifiable`: 0
-- `read_only`: 0
-- `not_applicable`: 0
-- `error`: 0
-
-The live harness created and deleted a disposable project named
-`_mcp_render_deliver_probe_1778342107`, generated synthetic media, probed 23
-formats and 99 format/codec pairs, rendered one tiny synthetic output, wrote
-JSON and Markdown reports, and removed the generated media and render output
-directories after the report was written.

package/mcps/davinci-resolve-mcp/docs/kernels/review-annotation-kernel.md

@@ -1,110 +0,0 @@
-# Review Annotation Kernel
-
-The Review Annotation kernel expands `timeline_markers` into a scope-aware
-annotation layer for timeline markers, timeline item markers, media pool item
-markers, flags, clip colors, and read-only review reports.
-
-Live validation was run against DaVinci Resolve Studio 20.3.2.9 with a
-disposable `_mcp_review_annotation_probe_*` project and generated synthetic
-video/audio media. Final release probe counts:
-
-| Status | Count |
-| --- | ---: |
-| `supported` | 44 |
-| `unsupported` | 1 |
-| `partially_supported` | 0 |
-| `version_or_page_dependent` | 0 |
-| `error` | 0 |
-
-The single `unsupported` result is the expected invalid marker color boundary
-for `color="Invisible"`.
-
-## Added Actions
-
-All actions are exposed through `timeline_markers`.
-
-| Action | Purpose |
-| --- | --- |
-| `annotation_capabilities` | Return supported scopes, colors, aliases, and known boundaries. |
-| `probe_annotations` | Snapshot markers, flags, clip color, ids, and names for one scope or the current timeline context. |
-| `normalize_marker_payload` | Normalize frame aliases, timecode, color, name/label, note/comment, duration, and custom data aliases. |
-| `copy_annotations` | Copy markers between annotation scopes, optionally carrying flags and clip color. |
-| `move_annotations` | Copy markers, then clear source markers when the source exposes marker deletion. |
-| `sync_marker_custom_data` | Update marker custom data for timeline, timeline item, or media pool item scope. |
-| `clear_annotations_by_scope` | Clear markers by color/custom data and optionally clear flags and clip color. |
-| `export_review_report` | Return a read-only annotation report with optional capability metadata. |
-| `annotation_boundary_report` | Return capabilities plus a live annotation snapshot. |
-
-## Scope Matrix
-
-| Scope | Markers | Custom Data | Flags | Clip Color | Frame Space |
-| --- | --- | --- | --- | --- | --- |
-| `timeline` | Supported | Supported | Not exposed | Not exposed | Timeline frame id or timeline timecode. |
-| `timeline_item` | Supported | Supported | Supported | Supported | Timeline item marker frames. |
-| `media_pool_item` | Supported | Supported | Supported | Supported | Source/media pool item frames. |
-
-## Marker Payloads
-
-The kernel accepts these frame inputs:
-
-- `frame`
-- `frame_id`
-- `frameId`
-- `frame_num`
-- `frameNum`
-- `timecode`
-- `tc`
-
-The kernel accepts `custom_data` and `customData`, plus `label` as an alias for
-`name` and `comment` as an alias for `note`.
-
-Validated marker colors:
-
-`Blue`, `Cyan`, `Green`, `Yellow`, `Red`, `Pink`, `Purple`, `Fuchsia`, `Rose`,
-`Lavender`, `Sky`, `Mint`, `Lemon`, `Sand`, `Cocoa`, `Cream`.
-
-## Supported Findings
-
-- Timeline marker add/get/update/custom-data readback works with frame,
-  `frame_id`, `frameId`, explicit timecode, and current-playhead insertion.
-- All documented marker colors were accepted in the live Resolve build.
-- Timeline item markers support marker copy and custom data updates.
-- Timeline item flags and clip color support add/read/set/clear.
-- Media pool item markers, flags, and clip color support add/set/read/clear
-  through the existing MCP wrappers and the new copy/move kernel helpers.
-- `copy_annotations` successfully copied 21 timeline markers to a timeline
-  item in the live probe.
-- `move_annotations` successfully copied a media pool item marker to the
-  timeline and cleared the source marker.
-- `clear_annotations_by_scope` supports Resolve's `"All"` color sentinel for
-  marker cleanup on timeline and timeline item scopes.
-- `export_review_report` and `annotation_boundary_report` are read-only
-  summaries over current annotation state.
-
-## Boundaries
-
-- Timeline, timeline item, and media pool item frame spaces are not equivalent.
-  `copy_annotations` uses direct frame numbers; callers must map frames when
-  moving between source, item-local, and timeline coordinate systems.
-- Current-playhead marker insertion depends on a current timeline and readable
-  current timecode.
-- `probe_annotations` only includes timeline item and media pool item scopes
-  when Resolve can resolve a current video item at the playhead.
-- Flags and clip colors are review metadata, but they are not marker records.
-  They are copied only when both source and target expose compatible methods.
-- Invalid marker colors are rejected before calling Resolve.
-
-## Live Probe
-
-Run the live boundary probe with:
-
-```bash
-python3.11 tests/live_review_annotation_validation.py --output-dir /tmp/review-annotation-probe
-```
-
-The harness creates a disposable project, generates a short synthetic video
-with audio, imports it, creates a timeline, probes annotation operations, writes
-JSON and Markdown reports, 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/timeline-conform-interchange-kernel.md

@@ -1,102 +0,0 @@
-# Timeline Conform / Interchange Kernel
-
-The Timeline Conform / Interchange kernel expands `timeline` into a safer
-structure, source-range, gap/overlap, interchange, comparison, missing-media,
-and relink-planning layer.
-
-Live validation was run against DaVinci Resolve Studio 20.3.2.9 with a
-disposable `_mcp_timeline_conform_probe_*` project and generated synthetic
-video/audio media. Final release probe counts:
-
-| Status | Count |
-| --- | ---: |
-| `supported` | 17 |
-| `partially_supported` | 1 |
-| `unsupported` | 0 |
-| `version_or_page_dependent` | 0 |
-| `not_applicable` | 0 |
-| `error` | 0 |
-
-The partially supported result was FCPXML round-trip survival: export and import
-both worked, but the imported timeline did not preserve MediaPoolItem-name
-linkage in the comparison snapshot. DRT round-trip matched exactly.
-
-## Added Actions
-
-All actions are exposed through `timeline`.
-
-| Action | Purpose |
-| --- | --- |
-| `conform_capabilities` | Return structure, analysis, interchange, relink-planning, and source-media safety boundaries. |
-| `probe_timeline_structure` | Snapshot timeline identity, track counts, items, source ranges, media file paths, markers, and optional clip properties. |
-| `detect_gaps_overlaps` | Report same-track gaps and overlaps from the current timeline snapshot. |
-| `source_range_report` | Group source frame ranges by MediaPoolItem/file path, with optional handles and merging. |
-| `export_timeline_checked` | Resolve export aliases and guard timeline export paths to temp locations by default. |
-| `import_timeline_checked` | Guard timeline imports from temp locations and normalize import options. |
-| `compare_timelines` | Compare current timeline to another timeline or two supplied snapshots. |
-| `probe_interchange_roundtrip` | Export, import, compare, and optionally delete the imported timeline. |
-| `detect_missing_media` | Detect missing/offline media using Resolve status fields and file-path existence, with a sanitized diagnosis block for mounted-volume/folder/file failure modes. |
-| `build_relink_plan` | Read-only, bounded search-root scan for relink candidates by missing file basename. Skips broad scans by default when the source volume is not mounted. |
-| `conform_boundary_report` | Return capabilities, timeline structure, gaps/overlaps, source ranges, and missing-media summary. |
-
-## Interchange Matrix
-
-| Format Alias | Export | Round Trip | Notes |
-| --- | --- | --- | --- |
-| `drt` | Supported | Supported | DRT export/import compared with zero differences in the live probe. |
-| `fcpxml` | Supported | Partially supported | Resolve exported a folder containing `Info.fcpxml`; import worked after resolving the primary file, but MediaPoolItem-name linkage was not preserved. |
-| `edl` | Supported | Not forced in release probe | Export succeeded to temp path. EDL round trips can be lossy by design. |
-| `aaf` | Supported | Not forced in release probe | Export succeeded to temp path. AAF options and media relink behavior are build/content dependent. |
-| `otio` | Supported | Not forced in release probe | Export succeeded to temp path. |
-
-Supported aliases include `aaf`, `drt`, `edl`, `edl_cdl`, `edl_sdl`,
-`edl_missing_clips`, `fcp7xml`, `fcpxml`, `fcpxml_1_8`, `fcpxml_1_9`,
-`fcpxml_1_10`, and `otio`.
-
-## Supported Findings
-
-- Timeline structure snapshots worked across video, audio, and subtitle track
-  categories.
-- Same-track gap detection found the deliberate 24-frame video gap in the
-  generated timeline.
-- Source range reporting grouped generated media paths with requested handles.
-- Guarded exports succeeded for FCPXML, DRT, EDL, AAF, and OTIO.
-- FCPXML directory-style exports are normalized with a `primary_file` path.
-- DRT export/import/compare round-trip succeeded and cleaned up the imported
-  timeline.
-- Synthetic-only unlink, missing-media detection, relink candidate planning,
-  and safe relink all worked through generated media.
-
-## Boundaries
-
-- Interchange formats are not semantically equivalent. DRT is the strongest
-  project-native round-trip path; EDL and FCPXML can lose Resolve-specific
-  relationships.
-- The public API exposes timeline items, source ranges, markers, and some media
-  references, but not full transition/effect/retime semantics for every format.
-- `build_relink_plan` is intentionally read-only. It deduplicates missing
-  basenames, supports `max_depth`, `max_seconds`, and `max_files_scanned`, and
-  skips broad scans by default when a source volume such as a camera card is not
-  mounted. Execute relinks through `media_pool.safe_relink` only with synthetic
-  or explicitly approved paths.
-- Missing-media status fields vary by Resolve build. The kernel combines status
-  text with local file existence when a file path is available.
-- Export and import helpers require temp paths by default because they write
-  interchange artifacts.
-
-## Live Probe
-
-Run the live boundary probe with:
-
-```bash
-python3.11 tests/live_timeline_conform_validation.py --output-dir /tmp/timeline-conform-probe
-```
-
-The harness creates a disposable project, generates synthetic media, builds a
-gapped timeline, probes structure, source ranges, gap/overlap detection,
-interchange export/import/round-trip behavior, synthetic missing-media relink
-planning, writes JSON and Markdown reports, 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/timeline-edit-kernel.md

@@ -1,189 +0,0 @@
-# Timeline Edit Kernel Boundary
-
-The timeline edit kernel is the supported MCP layer for clip duplication,
-range-copy workflows, and timeline-item state copying. It is built only on
-DaVinci Resolve's public scripting API and preserves source media integrity:
-it references existing Media Pool items and never transcodes, renders, proxies,
-or creates derivatives of source media.
-
-## Live Probe Summary
-
-The current boundary was validated on DaVinci Resolve Studio 20.3.2.9 with
-disposable projects and generated synthetic media.
-
-Final exhaustive probe result from May 9, 2026:
-
-| Status | Count |
-| --- | ---: |
-| Supported | 255 |
-| Partially supported | 4 |
-| Unsupported | 138 |
-| Version/page dependent | 4 |
-| Errors | 0 |
-
-The probe first runs the live duplicate/range validation harness, then creates
-a separate disposable project to inspect runtime method availability, timeline
-operations, item properties, keyframes, metadata, cache/voice/take/Fusion/grade
-surfaces, and known API boundaries.
-
-Run it with:
-
-```bash
-python3.11 tests/live_duplicate_clips_validation.py --output-dir /tmp/timeline-kernel-probe
-```
-
-The output directory receives both JSON and Markdown reports. Reports are
-generated artifacts and should not be committed.
-
-## Supported Kernel Features
-
-### Clip duplication
-
-`timeline(action="duplicate_clips")` duplicates existing video timeline items
-by re-appending the same Media Pool item with the same source trim through
-`MediaPool.AppendToTimeline([{clipInfo}])`.
-
-Supported placement modes:
-
-- `same_time`
-- `offset`
-- `at_playhead`
-- `track_above`
-- `after_source`
-- `next_gap`
-
-Supported placement controls:
-
-- `clip_ids` from timeline item unique IDs
-- `selected=True` when Resolve exposes selected/current item state
-- `target_track_index`
-- `track_offset`
-- `record_frame`
-- `record_frame_offset`
-
-`copy_clips` is an alias for duplication. `move_clips` duplicates successfully
-first, then deletes the original source items.
-
-### Linked audio
-
-`include_linked=True` duplicates linked audio items alongside the source video
-item when Resolve exposes linked item handles. The kernel restores the
-video/audio link state on the duplicated items.
-
-### Range operations
-
-The range tools build exact append operations from overlapping source segments:
-
-- `copy_range`
-- `duplicate_range`
-- `overwrite_range`
-- `lift_range`
-
-`copy_range` and `duplicate_range` copy exact video/audio source segments from
-explicit `start_frame`/`end_frame` values or the current mark in/out. The
-destination uses `record_frame` and optional track targeting.
-
-`overwrite_range` deletes whole destination items that overlap the destination
-range, then appends the copied range.
-
-`lift_range` deletes whole timeline items in a range. Partial overlaps are
-blocked by default because Resolve does not expose a public razor/split
-primitive. Passing `allow_partial_item_delete=True` confirms deletion of whole
-overlapping items; it does not perform a partial trim.
-
-### Copyable item state
-
-The kernel can copy these state groups when Resolve exposes readable/writable
-item APIs for the current item type and page state:
-
-- `transform`
-- `crop`
-- `composite`
-- `audio`
-- `retime`
-- `dynamic_zoom`
-- `scaling`
-- `stabilization`
-- `clip_color`
-- `markers`
-- `flags`
-- `enabled`
-- `cache`
-- `voice_isolation`
-- `fusion`
-- `grades`
-- `takes`
-- `keyframes`
-
-`copy_properties=True` copies all supported groups. A list or comma-separated
-string can scope copying to specific groups. `copy_keyframes=True` adds the
-`keyframes` group.
-
-### Capability reporting
-
-`timeline(action="edit_kernel_capabilities")` returns the maintained support
-map for supported, partially supported, and unsupported behavior.
-
-`timeline(action="probe_edit_kernel_item")` is a read-only item probe. It
-reports method availability, `GetProperty()` output, known property values,
-keyframe counts, and linked item summaries.
-
-`timeline(action="title_property_scan")` inspects undocumented title and
-generator `TimelineItem.GetProperty()` keys for the selected item scope.
-`set_title_text` and `bulk_set_title_text` use explicit or scanned keys when a
-Resolve build accepts `SetProperty()` writes for title text payloads.
-
-## Partial Support
-
-The probe classifies a feature as partially supported when Resolve exposes a
-public API surface, but success can vary by item type, page, build, or current
-UI state.
-
-Current partial areas:
-
-- Audio properties: some timeline audio `SetProperty` calls return false on
-  Resolve Studio 20.3.2.9.
-- Dynamic zoom, scaling, and stabilization: copied through exposed
-  `TimelineItem.GetProperty`/`SetProperty` keys when the build accepts writes.
-- Edit-page title and generator text: `title_property_scan` can expose
-  undocumented Text+ keys, but key names and write acceptance vary by item type,
-  page, and Resolve build.
-- Cache and voice isolation: copied only when item-level read/write APIs are
-  callable for the item.
-- Keyframes: copied for exposed properties, but Resolve does not expose enough
-  interpolation detail for full-fidelity readback in every case.
-
-## Unsupported Boundaries
-
-These are blocked by Resolve's public scripting API, not by MCP plumbing:
-
-- Transition cloning: no public timeline-item transition clone/read/write API.
-- Razor/split edits: no direct public timeline split primitive.
-- True partial lift: no safe partial-item delete without a split primitive.
-- Source-less item cloning through append: titles, generators, Fusion
-  compositions, and subtitles can exist on the timeline, but source-less items
-  do not provide a Media Pool item that `AppendToTimeline([{clipInfo}])` can
-  clone.
-- Deep speed-ramp semantics: exposed retime properties and supported keyframes
-  can be copied, but opaque speed-ramp curves are not independently inspectable.
-
-## Version/Page Dependent Behavior
-
-Some behavior depends on Resolve's current page or bridge state:
-
-- `selected=True` can fail to resolve selected/current timeline items when
-  Resolve does not expose selection state to the scripting bridge.
-- After inserting or probing source-less items, some Resolve bridge states lose
-  a callable `Project.SetCurrentTimeline`; the probe reports this as
-  version/page dependent rather than a kernel failure.
-- `probe_edit_kernel_item` is stable when the project has a current timeline;
-  if Resolve loses current timeline state, the harness records the bridge
-  condition separately.
-
-## Development Guardrails
-
-- Use disposable projects and synthetic media for live validation.
-- Never write to, transcode, render, proxy, or create derivatives of source
-  media while testing timeline-kernel behavior.
-- Treat generated probe reports as local artifacts.
-- Add new API experiments to the live probe when expanding the boundary map.

package/mcps/davinci-resolve-mcp/docs/notes/codec-plugin-notes.md

@@ -1,136 +0,0 @@
-# DaVinci Resolve Codec Plugin Notes
-
-Blackmagic's CodecPlugin README documents the DaVinci Resolve IO Encode Plugin
-SDK. These plugins extend Resolve Studio's Deliver page with additional render
-containers/codecs. They are native encode plugins, not a Python scripting API
-surface.
-
-The SDK is encode-focused: it enables additional codecs and container formats
-that can be rendered directly from Resolve. It does not describe a decoder or
-Media Pool import plugin API. Blackmagic notes that only CPU-based plugins are
-currently supported.
-
-## Current MCP Surface
-
-The MCP cannot build, install, load, or configure codec plugins directly.
-Relevant existing render actions are:
-
-- `render(action="get_formats")` wraps `Project.GetRenderFormats()`.
-- `render(action="get_codecs", params={"format": "..."})` wraps
-  `Project.GetRenderCodecs(renderFormat)`.
-- `render(action="set_format_and_codec", params={"format": "...", "codec": "..."})`
-  wraps `Project.SetCurrentRenderFormatAndCodec(format, codec)`.
-- `render(action="get_format_and_codec")` wraps
-  `Project.GetCurrentRenderFormatAndCodec()`.
-- `render(action="get_resolutions", params={"format": "...", "codec": "..."})`
-  wraps `Project.GetRenderResolutions(format, codec)`.
-- `render(action="set_settings")`, `render(action="add_job")`, and
-  `render(action="start")` run the normal render pipeline once Resolve exposes
-  the desired format/codec.
-
-After an IO encode plugin is installed and Resolve is restarted, plugin-provided
-formats and codecs should appear through the same format/codec query actions.
-There is no documented Resolve scripting method to list codec plugin bundles or
-distinguish built-in codecs from plugin-provided codecs.
-
-## Plugin Packaging
-
-Codec plugins are native binaries:
-
-| Platform | Binary type |
-|---|---|
-| macOS | 64-bit dynamic library |
-| Linux | 64-bit shared object |
-| Windows | 64-bit DLL |
-
-Plugins are packaged as `.dvcp.bundle` folders:
-
-```text
-PLUGIN.dvcp.bundle
-  Contents/
-    ARCH_1/
-      PLUGIN.dvcp
-    ARCH_2/
-      PLUGIN.dvcp
-```
-
-The plugin name must match in both the bundle name and binary name.
-
-Supported architecture folder names:
-
-| Platform | Architecture folder |
-|---|---|
-| macOS | `MacOS` for Universal2 or Arm64 |
-| macOS Intel | `MacOS-x86-64`, checked before `MacOS` on Intel-only machines |
-| Linux | `Linux-x86-64` |
-| Windows | `Win64` |
-
-## Install Locations
-
-Install the `.dvcp.bundle` into Resolve's `IOPlugins` folder:
-
-| Platform | IOPlugins folder |
-|---|---|
-| macOS | `/Library/Application Support/Blackmagic Design/DaVinci Resolve/IOPlugins` |
-| macOS App Store | `~/Library/Containers/com.blackmagic-design.DaVinciResolveAppStore/Data/Library/Application Support/IOPlugins` |
-| Linux | `/opt/resolve/IOPlugins` |
-| Windows | `%ProgramData%\Blackmagic Design\DaVinci Resolve\Support\IOPlugins` |
-
-System-wide install paths may require administrator privileges. Installing or
-replacing native codec plugins should remain an explicit user request.
-
-## Sample Plugin
-
-The developer package includes `Examples/x264_encoder_plugin`, which wraps the
-x264 encoder. The sample flow is:
-
-1. Build/install x264 from source.
-2. Point `.mk.defs` on macOS/Linux or `plugin2015.vcxproj` on Windows at the
-   x264 install path.
-3. Build with `make` on macOS/Linux or Visual Studio on Windows.
-4. Package the resulting binary into a `.dvcp.bundle` architecture folder.
-5. Copy the bundle to `IOPlugins`.
-6. Restart Resolve.
-
-Once loaded, the plugin's supported containers should appear in the Deliver page
-format list. If a plugin-supported container, or QuickTime, is selected, the
-plugin's codecs should appear in the codec list and expose any plugin-specific
-render-settings UI.
-
-## Practical Failure Checks
-
-If a custom codec is missing from `render.get_formats` or `render.get_codecs`:
-
-- Confirm Resolve Studio supports the plugin and has been restarted after
-  installation.
-- Confirm the bundle suffix is `.dvcp.bundle`.
-- Confirm the bundle and binary names match exactly.
-- Confirm the architecture folder matches the current platform and CPU.
-- Confirm the plugin binary is in `Contents/<ARCH>/PLUGIN.dvcp`.
-- Confirm the plugin is an encode plugin for Deliver, not an import/decode
-  extension.
-- Confirm any external codec library dependencies, such as x264, can be found by
-  the plugin at runtime.
-- Query formats first, then codecs for the selected format. A codec may only
-  appear for specific containers.
-
-## Useful Future Additions
-
-Good repo additions, if codec-plugin troubleshooting becomes common:
-
-1. A read-only IOPlugins inventory helper that scans known plugin folders and
-   reports `.dvcp.bundle` structure, architecture folders, and matching binary
-   names.
-2. Better `render.set_format_and_codec` failure text that suggests checking
-   `render.get_formats`, `render.get_codecs`, plugin install paths, and restart
-   requirements.
-3. A developer checklist for packaging `.dvcp.bundle` outputs from the bundled
-   x264 sample.
-4. No automatic native build/install flow by default. Codec plugins are native
-   executable code in system/plugin directories and should stay opt-in.
-
-## Source Media Integrity
-
-Codec plugins affect render output from Resolve. They should not be used as a
-reason to transcode, proxy, or replace source media unless the user explicitly
-asks for that derivative workflow.