0.12.0

resolve 0.12.0: board notes read when the node says they changed, not every 15 s (#26)

0.11.0

resolve 0.11.0: references as {id, name} (node 0.4.0) (#25)

v0.10.0

Moves to Pointman's typed extension protocol (#24). Needs a Pointman node 0.2.0 or later.

v0.9.0

Versions (PFE-12, PR #21): resolve.version applies a plan to a copy of the timeline for the person to A/B (with their ok) and puts them back on their timeline, page and playhead; the A/B shadow renders (their timeline above, the version below) are posted with it; resolve.drop_version deletes an unedited copy. The marker watcher and the follow watcher both skip version timelines.

v0.8.0

The follow watcher (PFE-13, PR #22): when the person pauses and the cut has changed, it checks the agents' tracks (cutout/loft sync with the voice, desktops without a cutout, orphan cues, scraps, cuts showing through a transition, chapter cards removed) and posts what's new to the project's agent with a dry-run plan for the mechanical fixes. resolve.watch runs it on demand. Opt-in per project through the routes.toml follow table.

v0.7.0

Edit plans (PFE-11, PR #9): dry run → preview → apply → verify, with one undo. Includes the fixes from the scratch-project live check (PR #23): the playhead goes back after every lay and after insert_gap (by what actually moved), undoing a colour back to none clears it, undoing a graded join restores every piece's grade, and a re-apply after an undo starts with fresh warnings.

v0.6.13

resolve.insert_gap {at, frames}: a pause on every track at once. Resolve's API has no insert, but SetSpeed with RippleTimeline moves every item and marker after the changed clip, so a temporary 1-frame clip on a temporary track is stretched and removed. Nothing is re-laid, so grades and transitions stay. A negative frames closes a gap. It checks every clip's place afterwards; on any failure it says how far the timeline moved and how to undo it; it journals at and frames. resolve-rules.md: 'Inserting time'. Asked for by James (Spacesheep v1, marker 11:30.60). Reviewed by @resolvedoc.

v0.6.12

The shadow renderer (and with it resolve_frame_check, QC's never-seen check and suspects) takes Crop as timeline pixels before the zoom, 2 a unit on 1080p, whatever the source's shape. Pan and Tilt stay shares of the fitted image. Measured on a 1728x1116 recording at zoom 1.478: CropRight 471.7 put Resolve's edge at x 780, not 960. resolve-rules.md and the README say so. Reviewed by @resolvedoc.

v0.6.11

SKILLS: working as a team. Only the editor changes the timeline. Briefs for the FX artist need no asking back. Deliveries fit their slot (ProRes 4444 alpha, frame count checked, stills, -v2 kept for undo). Timing travels as manifest data. Options come before polish. The slot can change under a graphic, and cue sounds come off with a removed card. skills/team.md has the full loop, briefs, deliveries and manifests. Asked for by James (thread 13661). Written by @cairn from how the editor and sheepgfx run Spacesheep v1; reviewed by @editor.

v0.6.10

SKILLS: a transition (flip, glitch, full-screen card wiping in or out) must cover the cuts beneath it, confirmed frame by frame with resolve_frame_check. Each cut goes under the transition's opaque frames, not its first or last see-through frame, and not just before or after it. The clip itself must cover the frame too (Opacity 100, Normal, full-frame). resolve-rules.md has the four-step check. Asked for by James (Spacesheep v1, marker 6:24.88). Reviewed by @resolvedoc.