Repository navigation
Verify Beacon state across process restarts - #88
0x00101010 wants to merge 3 commits into
Conversation
Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-01a10d69-00b6-7378-855f-af2b1a148692
|
Local qualification at Review map: independent fixes #77, #78, #79; feature chain #80 → #81 → #82 → #83 → #84 → #85 → #86 → #87 → #88. #84 includes the #77/#78 branches, and #85 includes #79. Each feature PR targets its immediate parent. CI qualification as of October 5, 21:25 UTC: #86 and #87 passed 341 and 345 Anvil tests respectively, with the same five Forge failures seen on the original PRs. Workspace crate checks passed on #86 and #88. The latest five runs had 29 cancellations without acquiring a runner, and #87 Clippy lost its runner during dependency compilation. The unchanged rustls advisory RUSTSEC-2026-0285 also fails cargo-deny. Earlier runs show pre-existing external-fixture dependency/RPC failures; the latest #87 external-fixture job is still running. All other jobs in the latest five runs have finished. Cancelled checks are unverified, not passes. These drafts are not merge-ready. Dependency/CI maintenance needs a separate scope decision; no checks were disabled or manually rerun. The original #75/#76 branches and immutable devnet pin remain unchanged. This qualification does not claim live Base snapshot or Denim acceptance. Comment generated by Amp. |
Amp-Thread-ID: T-01a10d69-00b6-7378-855f-af2b1a148692
Amp-Thread-ID: T-01a10d69-00b6-7378-855f-af2b1a148692
|
CI repairs from #89 are included at This PR is not fully green: the external Convex fixture hit public archive-RPC rate limits, then timed out. Its other eleven external fixtures passed. Reliable external verification needs a CI-approved archive endpoint in the existing The earlier feature review evidence is stack-level, not twelve independently recorded per-parent review cycles. The maintenance changes received their own independent reviews. Comment generated by Amp. |
Why
In-memory load tests cannot prove that graceful shutdown writes a usable checkpoint or that incompatible startup leaves it untouched. Exercise the real CLI across SIGTERM and restart.
What
Notes