v0.9.0 — Live Mode v1: push straight into Final Cut Pro

v0.9.0 — Live Mode v1: push straight into Final Cut Pro

The dual-mode roadmap goes live. This server can now drive a running Final Cut Pro, not just edit XML offline — using Apple's officially-supported surfaces only (no patched binary, no private APIs, no accessibility scripting). Both tools were verified end-to-end against Final Cut Pro 12.2 (generated a timeline, pushed it, confirmed the library/event/project landed in FCP and on disk).

New tools

• push_to_fcp — send an FCPXML file into the running FCP with zero clicks via the Open Document Apple event. Injects <import-options> (library location, copy/link assets, suppress warnings), launches FCP if needed, and never mutates your original (flat files get an options-injected copy through the same write sandbox as every other tool).
• list_fcp_libraries — enumerate FCP's open libraries → events → projects via Apple's read-only AppleScript dictionary.

Hard-won, live-verified notes

• Pass a .fcpbundle library location for true zero-click import — a new path is auto-created. Omitting it (or using .fcplibrary/a bare path) makes FCP raise a modal Open Library picker, a required choice that suppress warnings doesn't cover, which blocks the Apple event. push_to_fcp normalizes the location to .fcpbundle.
• Apple offers no programmatic export — the read-back leg of an edit loop still needs File > Export XML. Live mode pushes; round-trips come back through the XML tools. The tool says so in its output.
• Re-importing a project whose media already exists in the target library fails on a media-identity collision — push into a fresh library.

First use triggers a one-time macOS Automation permission prompt for your terminal/MCP host.

Tests: 942 → 955 across 22 suites. The full control-surface map and the optional SpliceKit / CommandPost bridges planned for v1.0 are in docs/CAPABILITY-AUDIT-2026-06.md.

🤖 Generated with Claude Code