Record stopped sweep checkpoint

Author: flemming-n-larsen

changes/CH-012-sweep-failure-fixes/tasks.md

@@ -11,5 +11,5 @@ title: Tasks
 - [x] Reproduce `cs.Nene` startup battlefield access and `davidalves.net.DuelistNano` callback state access with focused conformance probes; serves `M-006`.
 - [x] Repair the owning lifecycle boundary without guessing game setup or changing participant jars; serves `M-006`.
 - [x] Add focused positive and negative regression evidence for startup and callback state access; serves `M-006`.
-- [ ] Run bridge unit tests and focused conformance checks, then resume the sweep from its checkpoint; serves `M-006`.
+- [x] Run bridge unit tests and focused conformance checks, then resume the sweep from its checkpoint; serves `M-006`. The sweep was intentionally stopped after checkpointing 296 rows at the user's direction.
 - [ ] Update durable documentation and plan bookkeeping with evidence, then complete the digest.

changes/CH-012-sweep-failure-fixes/verification.md

@@ -16,6 +16,6 @@ The Tank Royale conformance runner completed `cs.Nene` for 35 rounds with no err
 
 The Tank Royale conformance runner completed `davidalves.net.DuelistNano` for 35 rounds with no errors after stale callback tick exceptions were contained at the bridge boundary.
 
-The resumable 50-round sweep was restarted from `compat-test/test_progress.json` and remains in progress; its checkpoint is the durable continuation point.
+The resumable 50-round sweep was restarted from `compat-test/test_progress.json` and intentionally stopped after 296 completed rows at the user's direction; that checkpoint remains the durable continuation point.
 
 No permanent architecture document changed: the fix preserves the existing bridge boundary and only changes when the generated wrapper attaches the peer and how a terminated callback's stale tick exception is contained.