Skip to content

Make passive checkpoints verifiable and recoverable - #3

Draft
iammedved wants to merge 1 commit into
mainfrom
astra-integration/2026-09-05
Draft

Make passive checkpoints verifiable and recoverable#3
iammedved wants to merge 1 commit into
mainfrom
astra-integration/2026-09-05

Conversation

@iammedved

Copy link
Copy Markdown
Owner

Passive checkpoint verification previously accepted an empty workspace and a repeated checkpoint could hide a damaged journal. Verification now distinguishes missing, current, stale, foreign, and invalid state, validates the checkpoint/journal binding, and checks saved data before returning unchanged.

A versioned metadata transaction supports explicit recovery after an interrupted pair write. Recovery requires both Pinmind source hashes to remain unchanged and never re-executes the user's action. Passive doctor no longer requires a separate Codex CLI; explicit controller diagnostics remain available.

Validation: baseline and final verification suites pass; new regressions cover corruption, interruption/recovery, changed source state, active-run ownership, locks, and legacy checkpoint compatibility. An independent review found and verified the source-hash recovery fix.

Draft because live plugin loading, hook trust, and behavior in new Codex/Work sessions remain unverified. This working branch is intended for a locally verified disabled installation; no merge, release, or package publication is requested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant