Skip to content

engine: safely recover serial frontier staging attempts - #84

Closed
rbtr wants to merge 2 commits into
mainfrom
feat/serial-frontier
Closed

engine: safely recover serial frontier staging attempts#84
rbtr wants to merge 2 commits into
mainfrom
feat/serial-frontier

Conversation

@rbtr

@rbtr rbtr commented Sep 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • Persist active frontier phase metadata in the Bolt-backed queue checkpoint.
  • On restart, treat every in-flight staging attempt as invalid evidence: requeue its PRs for a fresh serial staging run.
  • Delete only staging branches in Shunt's configured namespace, preventing checkpoint data from targeting another branch.
  • Keep restored active candidates ahead of later pending candidates.

PRD alignment

This is the first implementation slice for docs/frontier-prd.md: deterministic serial recovery, durable active-candidate metadata, and safe invalidation across a restart. It does not add speculative fan-out, a Postgres schema change, or deployment-specific behavior.

Validation

  • make lint test build
  • primary LSP diagnostics
  • independent review of the final diff
  • git diff --check and public-copy scrub

@rbtr

rbtr commented Sep 5, 2026

Copy link
Copy Markdown
Owner Author

This PR used the wrong delivery plan. The existing PR stack will receive the required changes.

@rbtr rbtr closed this Sep 5, 2026
@rbtr
rbtr deleted the feat/serial-frontier branch September 5, 2026 06:21
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