1.3.0-rc.5 — macOS sweep and resume repair

macOS preparation, retained-campaign storage, and resume repair. Protocol 7.1, frozen clips, full warmups/repetitions, and the pinned encoding runtime are unchanged.

• Prepare each frozen clip once instead of once per recipe, with visible progress and cancellation.
• A saved campaign's retained files no longer consume another campaign's allowance. Publication accounts for the active campaign's originals and upload staging, with a physical free-space guard.
• Guided Large sweeps use an appropriate retention allowance; resumed campaigns preserve their policy and honor explicit limits. Continue restores the full plan's attempt cap and continues checkpoints automatically.
• Completed groups upload at checkpoints; only verified warmups and server-accepted artifacts release local bytes. Failed, interrupted, and paused runs are reported truthfully.
• A running collector is identified before a second collection starts. Existing campaign journals remain resumable.

Native acceptance of this exact macOS package: the normal guided Small sweep ran against the real default queue retaining over 2 GB from a Large campaign. It completed 20 genuine encodes and submitted 14 measurements, with zero queued, skipped, or failed submissions and exit 0, in 3m 25s. All 14 were independently verified on the production API as ACCEPTED, RETAINED, with COMPLETE quality analyses. Timing-stability eligibility remains enforced separately; no measurements or scores were fabricated.

Source and verification: macOS binary from clean commit b0607f0; publication merged at 1a16417. Full client tests, additional resume regressions, frontend tests/lint/typecheck, mounted executable/signature verification, and release preflight passed. See PR #21.

Windows GUI and console are byte-identical to the verified rc.4 repair binaries from 5d379c7. Linux retains its original accepted rc.2-era build. They are not relabeled as newly rebuilt platform clients.

macOS requires Apple Silicon and macOS 27 or later; the app remains ad-hoc signed, not Developer ID signed or notarized. Verify SHA256SUMS and follow INSTALL.md. Earlier release assets are preserved.