feat(server): make rollback recovery durable - #232
Merged
Conversation
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
rynfar
force-pushed
the
feat/durable-rollback-saga
branch
from
September 2, 2026 23:47
67cda03 to
8d909b2
Compare
rynfar
marked this pull request as ready for review
September 2, 2026 23:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Checkpoint revert was best-effort. A process crash or partial provider/workspace failure could leave Git state, the Pylon projection, and the provider conversation at different turns without a durable recovery owner.
Durable rollback behavior
This adds a provider-neutral, target-absolute rollback saga with:
All built-in production adapters remain unsupported. This PR does not enable a rollback UI, provider-specific process work, or Prime navigation. It does not add relative rollback or queued auto-run behavior.
The three foundation commits are rebased onto
faf581e6d(merged #256). The rebase preserves the server performance/coalescing work and the ownership changes from #250, #255, and #256.DurableRollbackSagasis migration 051, after pending stop 049 and the Prime recovery ledger 050; no 052 source epoch is introduced.Verification
vp test run <14 focused files>— 14 files, 214 tests passedvp run --fail-if-no-match --filter t3 test— 323 files and 4,107 tests passed; 5 files and 15 tests skippedvp run --fail-if-no-match --concurrency-limit 2 --filter t3 --filter @t3tools/contracts --filter @t3tools/client-runtime --filter @t3tools/web --filter @t3tools/mobile typecheckvp lint --report-unused-disable-directives <34 changed TypeScript files>— 0 warnings, 0 errorsvp fmt --check <36 changed files>node scripts/release-smoke.tsgit diff --check origin/pylon..HEADgit range-diff c908bb200..67cda0373 origin/pylon..8d909b20aThe focused coverage includes saga persistence and migration 051, exact decider/projector transitions, reactor restart reconciliation, rollback status snapshots, fault injection at persisted saga and side-effect boundaries, leases/fences, projection CAS compensation, cleanup retry, privacy canaries, linked worktrees, and real-Git restoration of tracked, staged, unstaged, untracked, renamed, deleted, symlinked, ignored-target, index, HEAD, and checkpoint-ref state.
No screenshots are included because the affordance remains hidden.
Refs #200
Implemented with OpenAI Codex GPT-5.6 Sol using the Prime Agent harness.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.