Release v0.27.0: reliable media edits, compilation, and queued automation

[renezander030]

Drafts can silently retain an older same-name media file, keep stale import links after relinking, or remain partially created after an invalid compile operation. Queued edits can also discard a different job under a reused ID or race through aliases of the same project. This release fixes those paths and prepares v0.27.0.

• Copy the requested replacement bytes with content-aware collision handling and side-effect-free dry runs.
• Refresh changed-media import entries and local IDs in the guarded timeline/sidecar transaction, preserving existing imports.
• Add recursive relinking with ambiguity reports and path-boundary prefix mapping.
• Keep adjacent fractional-second clips contiguous by rounding their start/end boundaries.
• Preflight compile operations through the real builders and remove only the invocation's owned output on failure.
• Bind queue IDs to the effective command payload and execution settings.
• Serialize project aliases and declared explicit destinations through canonical project locks.
• Validate queue inputs/limits and check combined capture size at exit with bounded reads.
• Resolve OTIO local file URLs and media paths relative to the document directory.

Validation: 1,094 tests passed locally (one Windows-only case), and all eight required CI checks passed on this head: Node 18/20/22, Linux/macOS/Windows, lint, and the Wasm component/MCP check. Generated command docs and a fresh-tarball CLI/library smoke also passed. The review guide maps each behavior to its regression coverage and provides reproducible checks: docs/reviews/v0.27.0.md.

Review notes: based on master at 44b35c41551370b871ebcf9856386b96e968706b. Queue locks/IDs apply within one invocation; implicit compile outputs and shared store-index writes need external serialization. Capture limits are polling/exit thresholds, not disk quotas. Existing version guards and desktop-validation evidence limits remain in place. The Python client and Wasm component source are unchanged. Merge and npm/GitHub release publication wait for maintainer review.