convergence-cutover-runtime-kernel

Cut over the production planner runtime kernel

Metadata

Statusabandoned ‖ paused
Agent identityfbb2d89fe44d6b761bcb4b67748ab3d417f29df70a65f8d9403308f5bb2bab78
Created2026-08-04T13:42:16.798140284+00:00
Tagsconvergence-final-cutover
Tokens2247398 in / 23685 out
Failure reasonSuperseded by the attended worker-owned universal completion cutover merged in PR #61 (4aca437f); legacy planner/SaveTransaction authority is historical evidence, not production work.

Description

Implement step 1 of docs/plans/deterministic-convergence-final-cutover.md. Make PlannerStore production-ready with typed observation normalization support, durable monotonic sequence/logical-time allocation, issue-before-effect journaling, stable effect replay/acknowledgement, schema migration, a read-only status projection, and one earliest planner deadline. Import existing convergence deadlines/backoff/route state without resetting them. Do not cut over a domain or leave a second new scheduler.\n\n## Validation\n- Restart preserves normalized state, deadlines, effect IDs, sequences, and acknowledgements byte-for-byte.\n- Fault injection at all four issue/execution/ack boundaries proves logical exactly-once and idempotent replay.\n- Migration fixtures cover existing convergence-state and planner schemas without deadline reset.\n- Planner replay fixtures remain byte-identical; cargo fmt --check, cargo clippy --locked, focused tests, and clean candidate smoke pass.

Depends on

Required by

Messages 8 messages (8 unread)

  1. #1user2026-08-04T16:19:49.610546037+00:00read
    The prior exact worktree already contains validated commit 9cfdedef. Do not redo implementation or broaden scope. Verify current branch/commit and complete the required wg done handoff promptly; preserve evidence if finalization blocks.
  2. #2convergence-cutover-runtime-kernel2026-08-04T16:42:33.278298143+00:00read
    Acknowledged — preserving the validated worktree evidence and completing the existing wg done handoff without further implementation changes.
  3. #3convergence-cutover-runtime-kernel2026-08-04T16:43:49.210359925+00:00read
    Done — branch is clean and pushed (runtime kernel 9cfdedef; acknowledgement invariant follow-up f3055b07). Reusing recorded passing validation and proceeding with final handoff now.
  4. #4convergence-cutover-runtime-kernel2026-08-04T16:47:52.127908032+00:00read
    Acknowledged — verified the exact validated worktree at pushed HEAD f3055b07 (kernel 9cfdedef); making no changes and completing wg done now.
  5. #5convergence-cutover-runtime-kernel2026-08-04T16:50:59.637687153+00:00read
    Acknowledged — I verified the exact validated worktree at pushed HEAD f3055b07 (kernel 9cfdedef). I will make no implementation changes and will complete the existing wg done handoff promptly, preserving evidence if finalization blocks.
  6. #6convergence-cutover-runtime-kernel2026-08-04T16:52:08.613495740+00:00delivered
    Done — verified clean pushed HEAD f3055b07 (runtime kernel 9cfdedef), preserved the recorded passing validation evidence, and made no further implementation changes. Completing wg done now.
  7. #7user2026-08-04T16:53:03.584890929+00:00delivered
    URGENT: prior work is already committed at f3055b07 and installed. Do not run more builds or broaden scope. Verify commit exists, then invoke wg done immediately so the durable terminal handoff is created before any further compaction/provider/tool exit.
  8. #8convergence-cutover-runtime-kernel2026-08-04T16:56:05.272498562+00:00read
    Acknowledged — I will only verify pushed HEAD f3055b07 and invoke wg done immediately; no builds or implementation changes.

Log