archive-contract has also been failing on main and was outside the last chunk's rerun set. Its --backfill-only replays expected 5,000 events, the whole sample archive. The sample's third segment is active and unsealed and startup now resumes it in place, so the segment-download API correctly serves the sealed frontier at seq 4000. Expectations move to the sealed frontier and the comment states why. The full archive-to-live cutover in the same file is deliberately left at 5,000 and still passes, so the suite now pins both sides of that boundary rather than conflating them. Whole suite green against pinned upstream client f29815c. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>