Repository navigation
fix(lastcode): make checkpoint failures self-reporting - #101
Merged
Merged
Conversation
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.
The hourly checkpoint job can keep running while its latest durable record appears frozen: a retained recovery worktree blocks later attempts before they append history, and the old best-effort macOS notification has no acknowledgement, retry, or stable recovery thread. Nightly 1195 also exposed another deployed migration-number collision.
This adds a standalone supervisor with durable incident state, same-thread delivery and retry, deduplication, recovery closure, pinned bootstrap, environment scrubbing, and self-refresh. It also reserves upstream migration 43, shifts LastCode migrations forward, adds idempotent upgrade bridges for existing databases, and expands the checkpoint smoke gate to cover both bridge paths.
Validation:
Implemented with GPT-5.6 Codex in T3 Code.