feat: reconcile running development loops#98
Merged
Conversation
Co-authored-by: Codex (GPT-5) <codex@openai.com>
Co-authored-by: Codex (GPT-5) <codex@openai.com>
Co-authored-by: Codex (GPT-5) <codex@openai.com>
Co-authored-by: Codex (GPT-5) <codex@openai.com>
Co-authored-by: Codex (GPT-5) <codex@openai.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ncolesummers
marked this pull request as ready for review
July 23, 2026 05:14
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.
Summary
Why
Running development-loop records could remain active indefinitely after their durable execution disappeared, stopped making progress, or became superseded by tracker state. The existing run status also could not distinguish timeout, stall, or reconciliation cancellation.
This change adds a deterministic, read-only reconciliation entry point backed by Postgres state. It deliberately injects execution liveness rather than inferring it from step rows, preserving dispatch leases and scheduling for #96.
Behavior
failed/timed_outfailed/stalledReview notes
Two fresh adversarial reviews were run after the first green implementation. Regressions were added for stale health snapshots, future queued-step activity, liveness-provider exceptions, cross-loop selection, cancellation-policy propagation, and compatibility-wrapper reason handling.
Automatic scheduling/calling of reconciliation remains scoped to #96.
Validation
bun run buildbun run validategit diff --check main..HEADCloses #95
Prepared with Codex (GPT-5).