Skip to content

fix(lastcode): make checkpoint failures self-reporting - #101

Merged
lastobelus merged 14 commits into
lastcode/mainfrom
lastcode/checkpoint-automation
Aug 27, 2026
Merged

lastobelus merged 14 commits into
lastcode/mainfrom
lastcode/checkpoint-automation

Conversation

@lastobelus

Copy link
Copy Markdown
Owner

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:

  • 49 focused tests across supervisor, service, checkpoint smoke, and affected migrations
  • targeted lint with warnings denied
  • scripts and server typechecks
  • live launch-agent alert delivery and same-incident deduplication

Implemented with GPT-5.6 Codex in T3 Code.

Loading
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