Resolve Delivery / Deliverable QC

Bridges delivery craft to this repo's tools.

• Craft / specs, the global deliverables-knowledge, post-supervisor, and quality-control / qc-domain skills (distributor specs, mastering, QC discipline). Use for what the spec should be, not tool mechanics.
• Live tool mechanics, docs/kernels/render-deliver-kernel.md (the render planning/validation boundary + Quick Export).
• Offline deliverable QC, resolve-advanced/README.md → deliverable, media, provenance.

Two servers

Job	Server	Tools
Plan / validate / run renders in a running Resolve	davinci-resolve (Python, live)	render, render_presets
QC a finished render vs spec, verify ingest, build manifests/provenance with no Resolve open	davinci-resolve-advanced (Node)	deliverable, media, provenance

Delivery targets (the short path)

Named render intents. list_delivery_targets → prepare_delivery_job(target, target_dir). Ask for prores422hq_master, dnxhr_hqx_master, h264_1080p_web, or an alias (youtube, tiktok, avid, stems). One definition emits BOTH the Resolve render settings and the deliverable_qc spec, so the returned qc_spec is what you QC the finished file against, do not hand-write a second spec.

• Format/codec resolve against the live matrix. A target this machine or license cannot render fails with the available lists; it never silently substitutes. Use check_availability: true to see what this install supports.
• Image-sequence targets return qc_spec: null, deliverable_qc probes one file, a sequence is many. That is expected, not a gap.
• Bitrate is deliberately unset (Resolve has no bitrate key). Pin quality yourself via settings if a spec demands it.