CI watching, CI-fix Repair and the Repair cap #9

Parent

#2

What to build

CI watching, CI-fix Repair, and the Repair cap: the spec's Repair loop in full.

• After each push, wait up to the grace period (default 60 seconds, overridable through an environment variable for tests) for any check or status on the head commit. None → no CI, which counts as passing.
• Checks appeared → watch until done. Green → success. Red → a CI-fix Repair session with the spec's prompt, listing each failed check's name and details URL. Then push and go back to the merge step, since the Base branch may have moved.
• At most 3 Repairs per run, conflict and CI-fix combined. Needing a 4th → Failed run with reason repairs exhausted: <conflict|CI red>, which converts the PR to a draft.
• Before exiting 0, re-check that the PR is open, ready, and mergeable.

Acceptance criteria

• No checks within the grace period → success, exit 0
• Checks pending then green → success
• Red, then the CI-fix Repair pushes a fix, then green → success; the Repair prompt lists the failed checks
• Red after 3 Repairs → Failed run with reason repairs exhausted: CI red, the PR converted to a draft, exit non-zero
• A mix of conflict and CI-fix Repairs counts toward the same cap of 3
• After each Repair the loop merges the Base branch again before watching CI
• Final check: a PR that ended up closed or unmergeable → Failed run, not exit 0

Blocked by

• The Failed run path #5
• Keeping the PR mergeable: merge the Base branch and conflict Repair #8