Repository navigation
docs: make the exact-head live-gate status the live-evidence record - #121
Conversation
AGENTS.md and the PR template drop the draft-until-evidence rule. The live-gate commit status on the exact head, linking its evidence comment, is the record, and Mergify already refuses to queue without it. PRs may be reviewed before their live test, and every new head needs a fresh one. The factory loop in the triage plan follows the same order. Decided in the PR #111 step-back (2026-10-03). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Live evidence: Open PstackPinned PR #121: |
Merge Protections🔴 1 of 2 protections blocking · waiting on 🙋 you
🔴 🚦 Auto-queueWaiting for
This rule is failing.When all merge protections are satisfied and these conditions match, this pull request will be queued automatically.
Show 1 satisfied protection🟢 Queue ready pull requestsAutomatically queue non-draft pull requests targeting main after verify, Unfret, and live-gate pass on the head.
|
|
✅ No blocking findingsWalkthroughThis docs-only change makes the
Advisories (1)
Since the last review
Details
Reviewed the whole pull request. @unfret review · @unfret status · @unfret help |
There was a problem hiding this comment.
🛑 1 blocking finding
🔵 Low · A3 skill spec left stale: still says write the PR template evidence block
Check
| 7. Unfret reviews the ready PR. The builder fixes the findings. Each new head needs a fresh `live-gate` status, because the status is bound to the head SHA. | ||
| 5. Build runs on the Factory branch. Before opening the PR, the builder runs the checks AGENTS.md requires: Bun tests, strict typecheck, static invariants, and plugin validation. Then it opens the PR, ready for review. If the build host lacks Bun, as the triage sandbox did, fix the host before the first run. Don't skip the checks. | ||
| 6. Unfret reviews the PR. The builder fixes the findings until Unfret passes. | ||
| 7. Claude runs the live gate (A3) on that final head. The verifier posts one evidence comment and the `live-gate` status on that exact head, and changes nothing else on the PR. Any later head, including a queue-created head, needs a fresh run. |
There was a problem hiding this comment.
🔵 Low · A3 skill spec left stale: still says write the PR template evidence block
Changed step 7 delegates the live gate to the A3 spec ("Claude runs the live gate (A3)"). It says the verifier posts one evidence comment plus the live-gate status and "changes nothing else on the PR", and section 7 (line 171) repeats this. The A3 row it points to (line 13, unchanged) still tells the #90 skill to "write the PR template's evidence block". This diff deletes that block from the template (-Live evidence:). The A3 row also never mentions posting the status or the comment. Scenario: the #90 builder implements from the A3 row. The skill then finds no block to write, or it edits the PR body, which section 7 says produced new review findings. It may also omit the live-gate status Mergify requires. The plan contradicts itself on the verifier contract.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Live evidence: Open PstackPinned PR #121: |
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 12 seconds in the queue, including 2 seconds running CI. Required conditions to merge
|
What changed
The exact-head
live-gatestatus, linking its evidence comment, becomes the live-evidence record. It replaces the PR-template block and the "remains a draft" rule:AGENTS.mdline 9: the record is thelive-gatestatus on that exact head, linking an evidence comment with the installed version, surface, action, and observed result. Mergify doesn't queue without it. A PR may be ready for review before its live test, and every new head, including a queue-created head, needs its own.Why.
.mergify.ymlalready requirescheck-success=live-gateon the head before queueing (#107), so draft state is no longer a merge control. In the PR #111 step-back (2026-10-03), every way the verifier changed draft, ready, or body state produced new Unfret findings. Requiring the live test before review also forced a new live proof for every fix head. Decided by the maintainer on 2026-10-03.Per the
/run-theserule forAGENTS.mdedits, this merges before PR #111 goes back to review. It changes.github/pull_request_template.md, so Mergify won't auto-queue it, and the operator queues it by hand.Verification
verifycovers the tests and static invariants.live-gateis posted by the operator as "no runtime change".🤖 Generated with Claude Code