v2.10.13

v2.10.13

Fixes

• Vast collection teardown no longer destroys a rental while a job bound to it is still collecting. The lease guard now consults every bound job's collection state (status, final_collected and the final-collection anchors) and defers the destroy within the bounded grace window, so a stop/deadline cancel can no longer win the race against the final collection.
• Persist the first collection-teardown allowance for jobs that entered collecting without a Stop RPC; status writes and supervisor restarts cannot renew its 240-second limit.
• Enable Pareto delta transfers only for explicitly verified published image digests. Existing pinned images retain full snapshot transfers until the shared rental-protocol candidate from PR #511 is built, verified and published.

Changed

• Prepare multi-day Vast rental support across API validation, single-job approvals, calibration watches, rental start, deadline/budget controls and the rental form. Budget, transfer reserve, finite-number validation and cleanup ownership remain enforced. Legacy images retain their 24-hour ceiling.
• Add an unpublished rental-protocol v3 worker-image candidate, based on the current immutable PB8 image, with independent multi-day guard deadlines and Pareto delta snapshots. Include a source-bound offline image verifier. The active image and published feature allowlist remain unchanged until the candidate is built, verified and published; multi-day requests on older images fail before rental.
• Preserve the published worker's PB8 fixes in the rental-protocol candidate: inherit the immutable fresh-population image and require its GPU backend hash, Rust fingerprint, compiled source stamp, seed and checkpoint checks during the image build.
• Build the rental-protocol v3 worker candidate locally and verify it in a separate network-disabled container. Confirm unchanged PB8 base layers, patched GPU backend hash, Rust fingerprint, seeds/checkpoint behavior, a 120-hour guard deadline and Pareto delta snapshots. Registry publication, activation, GPU hardware validation and a real optimizer run remain pending.
• Support guard protocol 3 in Queue rental controls, bound Loop controls and automatic transfer-reserve rebalancing. Share the reserve-aware budget deadline calculation so multi-day Loop budget changes retain their approved duration; legacy image limits and worker acknowledgement remain enforced.
• Reject unsupported rental durations at API validation and expose the active image's duration limit to the rental form. Cancel unsupported persisted performance-test watches before offer search, report insufficient Loop transfer reserves accurately, and verify quota bypass in the GPU-replacement Stop collection tests.
• Update the real-menu Vast browser regression to expect the current JavaScript asset version (181).