review-wave-8 — the pre-release gate passes: one contract-observable divergence found and fixed (pg's negative-seed GREATEST clamp + offsets CHECK contradicted ADR-023 §2's stored-checkpoint annotation; raw seed now, window open until first publish); the close-out's registered suite-duty follow-up discharged (negative heartbeat(extend) leg in job_handle_validity_predicate, negative save_offset seed leg in receiver_close_and_save_arms — stamped, uniform, green on all three columns vs the live harness server); the class-1 termination of record landed in ADR-017 §2 (no undisposed candidate remains; the window closes permanently at the first cargo publish); release-facing spec set flipped stable with dated gate annotations (core-contract, overview, queues, deployment current, the architecture README — Current State through wave 8, engine-mem's table row corrected); implementation.md records updated; N-1/Findings 2–3/flake/publish-prep audits recorded; all gates re-run green incl. fuzz replay, wasm32, doc gate

docs/plans/implementation.md

@@ -1,10 +1,9 @@
 ---
 status: draft
-last_updated: "2026-10-10 (wave 8 decomposed — the release-readiness
-task set: seven independent entry tasks incl. the frontmatter cleanup
-and the renumber sweep, then matrix → README → publish prep → gate.
-Waves 1–7 implemented + reviewed; Findings 2–3, the fired flake-watch
-trigger, and the class-1 window's last dispositions ride wave 8.)"
+last_updated: "2026-10-11 (wave 8 implemented + reviewed — the release
+gate passed: the class-1 window's dispositions complete, the suite's
+registered boundary-legs follow-up landed, all gates re-run green;
+implementation complete pending the user's manual `cargo publish`.)"
 ---
 
 # alkstore — Implementation plan
@@ -50,7 +49,7 @@ readiness is wave 8.
 | 5 | [Contract suite](#wave-5--contract-suite): the cross-engine equivalence properties (core-contract.md §Verification backlog), version-stamped per ADR-017 | waves 3 + 4 | implemented + reviewed (2026-10-10) |
 | 6 | [Mem engine](#wave-6--mem-engine): separate `alkstore-mem` crate, full contract v1 over in-memory mechanisms (tx overlay, queue/scheduler/streams/locks/wakes), the suite's third factory column (born pinned), wasm32 compile-clean acceptance | waves 1 + 5 | implemented + reviewed (2026-10-10) |
 | [7](#wave-7--fuzzing) | [Fuzzing](#wave-7--fuzzing): the `fuzz/` sidecar workspace (cargo-fuzz targets over the payload codec, the three `@every` parsers, name validation), committed seed corpora + the corpus-replay gate, detached campaigns | wave 6 | implemented + reviewed (2026-10-10) |
-| [8](#wave-8--release-readiness) | [Release readiness](#wave-8--release-readiness): crate docs, deployment matrix final pass, README (written last, honestly), publish prep | wave 7 | decomposed (2026-10-10) |
+| [8](#wave-8--release-readiness) | [Release readiness](#wave-8--release-readiness): crate docs, deployment matrix final pass, README (written last, honestly), publish prep | wave 7 | implemented + reviewed (2026-10-11) |
 
 ## Wave 1 — Foundations
 
@@ -757,4 +756,34 @@ decomposes. Specific gates:
   recommendation: **wave 5 decomposes after the two HIGH fixes land**
   (the suite's wake-driven rows would otherwise inherit a hang-shaped
   false failure); 3–7 may trail into wave 5's window if the
-  fix-batch gate judges them wake-independent.
+  fix-batch gate judges them wake-independent.- **Wave-8 review gate** (`review-wave-8`, 2026-10-11) — the
+  pre-release gate passed: the docs honesty audit clean (README trace
+  list spot-read true, the deployment matrix's rows read true as
+  implemented, crate-doc posture claims consistent with the matrix,
+  the env-boundary grep re-run current); the contract-window closure
+  audited — all five wave-6 dispositions verified landed with dated
+  citations, **the class-1 termination of record landed in ADR-017
+  §2** (the window closes permanently at the first `cargo publish` of
+  `alkstore`; no undisposed class-1 candidate remains); the
+  close-out's registered suite-duty follow-up audited and **landed at
+  the gate** — one divergence found: pg's negative-seed clamp
+  (`GREATEST(offset, 0)` + the offsets-table `CHECK`) contradicted
+  ADR-023 §2's "a negative is stored as the checkpoint" annotation on
+  `get_offset`, fixed engine-side (raw seed, no CHECK), with the
+  negative-`heartbeat(extend)` and negative-`save_offset` suite legs
+  landed in `job_handle_validity_predicate` /
+  `receiver_close_and_save_arms` (stamped, uniform, green on all
+  three columns); N-1's conscious acceptance and Findings 2–3's
+  landed/parked dispositions audited as decisions of record; the
+  flake outcome audited (lock row root-caused harness-model,
+  test-side fixed, watch retired; the trim row and the new
+  stream-ordering observation stay watch-flagged — no live engine
+  bug, not blocking); publish-prep evidence re-verified this gate
+  session (fresh package listing + exclusion re-run, no leakage); the
+  frontmatter sweep + renumber spot-checks re-run green; all gates
+  re-run green including the fuzz replay, wasm32, and the doc gate;
+  the release-facing spec set (core-contract.md, overview.md,
+  queues.md, deployment.md, the architecture README) flipped
+  `stable`. Implementation complete pending the user's manual
+  `cargo publish` (the checklist of record is in
+  `tasks/release-publish-prep.md`).