Skip to content

docs: make the exact-head live-gate status the live-evidence record - #121

Merged
mergify[bot] merged 2 commits into
mainfrom
docs/live-gate-record
Oct 4, 2026
Merged

mergify[bot] merged 2 commits into
mainfrom
docs/live-gate-record

Conversation

@ericlitman

Copy link
Copy Markdown
Owner

What changed

The exact-head live-gate status, linking its evidence comment, becomes the live-evidence record. It replaces the PR-template block and the "remains a draft" rule:

  • AGENTS.md line 9: the record is the live-gate status 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.
  • PR template: the last checkbox and footer now match.
  • Triage plan: the factory loop runs review first and the live gate on the final head. New section 7 records the change and why.

Why. .mergify.yml already requires check-success=live-gate on 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-these rule for AGENTS.md edits, 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

  • Docs only. No skill, runner, manifest, or test file changes, so no plugin runtime behavior changed. CI verify covers the tests and static invariants.
  • No affected harness, so there's no installed-candidate run. live-gate is posted by the operator as "no runtime change".

🤖 Generated with Claude Code

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>
@ericlitman

Copy link
Copy Markdown
Owner Author

Live evidence: Open Pstack

Pinned PR #121: c4b55bd47a53873d83bc55faa34af607338bfe30.
Result: no runtime change. The diff touches only AGENTS.md, .github/pull_request_template.md, and docs/plans/2026-10-01-triage-and-roadmap.md. No plugin skill, runner, manifest, or shipped asset changed, so no harness is affected.
Posted by hand by the operator, because the verifier (#90 / PR #111) isn't merged yet.

@mergify

mergify Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

Merge Protections

🔴 1 of 2 protections blocking · waiting on 🙋 you

Protection Waiting on
🔴 🚦 Auto-queue 🙋 you
🟢 Queue ready pull requests —

🔴 🚦 Auto-queue

Waiting for

  • -files~=^\.github/
This rule is failing.

When all merge protections are satisfied and these conditions match, this pull request will be queued automatically.

  • -files~=^\.github/
  • base = main

Show 1 satisfied protection

🟢 Queue ready pull requests

Automatically queue non-draft pull requests targeting main after verify, Unfret, and live-gate pass on the head.

  • -draft
  • check-success=Unfret
  • check-success=live-gate
  • check-success=verify

@greptile-apps

greptile-apps Bot commented Oct 4, 2026 •

Copy link
Copy Markdown

RetriggerConfidence Score: 5/5

[Low risk] Updates documentation of the pull request process.

The PR appears safe to merge; the existing queue rule still holds PRs until the live gate passes.

What we checked:

  • Review finishes before the live test: No. Mergify requires live-gate on the PR head before it queues the PR.

Summary

This docs-only PR makes the exact-head live-gate status and its linked evidence comment the live-evidence record. It moves live testing until after review, so a pull request can be reviewed before its live test.

  • Replaces the PR-body evidence block with an exact-head status and linked comment.
  • Updates the triage steps to run review and fixes before the live gate.
  • Keeps Mergify’s queue requirement tied to live-gate on the final head.
Diagram
%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Open PR ready for review] --> B[Review and fix findings]
  B --> C[Live test final head]
  C --> D[Post evidence comment and live-gate status]
  D --> E[Mergify checks the head before queueing]
Loading

Reviews (1) · Last reviewed commit: "docs: make the exact-head live-gate stat..."

@unfret-eal

unfret-eal Bot commented Oct 4, 2026 •

Copy link
Copy Markdown

✅ No blocking findings

Walkthrough

This docs-only change makes the `live-gate` commit status on a pull request's exact head the official record of live-test evidence. That status links an evidence comment naming the installed version, surface, action, and observed result. It replaces both the PR template's evidence block and the rule that a PR without evidence stays a draft. AGENTS.md now says a PR can be ready for review before its live test, Mergify won't queue it without `live-gate`, and every new head needs its own status, including queue-created heads. The PR template checkbox and footer are updated to match. The triage plan reorders the factory loop so review runs first and the live gate runs on the final head, and a new section 7 explains why. No runtime code changes. The author reports that `live-gate` is posted by hand as "no runtime change".

Area What changes
AGENTS.md gate rule The live-evidence record moves from the PR template and draft state to the exact-head `live-gate` status and its linked comment. PRs may be ready for review before the live test, and each new head needs a fresh status.
PR template The evidence block and the "remains a draft" footer are removed. The last checkbox now points to the `live-gate` status on the final head, and the footer says Mergify won't queue without it.
Triage plan The factory loop now opens PRs ready for review, runs Unfret first, and runs the live gate on the final head. The verifier posts only the comment and the status. A new section 7 records the decision.
Advisories (1)
  • Live-gate checkbox has no completion step
    Not blocking because: The checklist can remain incomplete after successful verification, but the evidence comment and exact-head status are authoritative. Mergify checks live-gate rather than checkbox state, so this presentation defect neither obstructs nor weakens the gate.
Since the last review
  • Withdrawn: A3 skill spec left stale: still says write the PR template evidence block. Why: The carried repair is satisfied at the current head. The A3 row now explicitly requires posting one evidence comment and the exact-SHA live-gate status, changing nothing else on the PR, and references section 7. It no longer instructs the skill to write the removed template evidence block and now agrees with execution step 7. The specific contradictory implementation contract reported previously is absent; this is a completed repair, not a reversal of prior guidance.
Details
Lane / stage Model Effort Outcome Duration
broad-gpt-5.6-sol-xhigh / review openai/gpt-5.6-sol (reported model unavailable) xhigh succeeded 28 s
broad-opus-5.5-max / review anthropic/claude-opus-5-5 (reported model unavailable) max succeeded 4 min 28 s
focal-gpt-6.1-sol-xhigh / review openai/gpt-6.1-sol (reported model unavailable) xhigh succeeded 3 min 1 s
broad-gpt-5.6-sol-xhigh / reread openai/gpt-5.6-sol (reported model unavailable) xhigh succeeded 56 s
broad-opus-5.5-max / reread anthropic/claude-opus-5-5 (reported model unavailable) max succeeded 4 min 48 s
focal-gpt-6.1-sol-xhigh / reread openai/gpt-6.1-sol (reported model unavailable) xhigh succeeded 3 min 59 s
judge / judge openai/gpt-6-astra (reported model unavailable) high succeeded 1 min 54 s

Reviewed the whole pull request.
3 reviewers finished.
Commit 71bc986.
Check run.
Run: GET /unfret/run/panel:71bc986b50e144b837aa28aca8fd7d75490da60f:Jg-qGpQ2yMM:6g29ZmqHDh0.

@unfret review · @unfret status · @unfret help

@unfret-eal unfret-eal Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛑 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.

@unfret-eal unfret-eal Bot Oct 4, 2026 •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 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.

Withdrawn in the latest review.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ericlitman

Copy link
Copy Markdown
Owner Author

Live evidence: Open Pstack

Pinned PR #121: 71bc986b50e144b837aa28aca8fd7d75490da60f.
Result: no runtime change. This is a docs-only head; it edits the A3 row in docs/plans/2026-10-01-triage-and-roadmap.md to address the Unfret finding. No harness is affected. Posted by hand by the operator, because the verifier (#90) isn't merged yet.

@unfret-eal unfret-eal Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No blocking findings
Check

@ericlitman

Copy link
Copy Markdown
Owner Author

@Mergifyio queue

@mergify

mergify Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • ✅ Entered queue — 2026-10-04 01:39 UTC · Rule: default · triggered by @ericlitman with the @mergifyio queue command
  • ✅ Checks skipped · PR is already up-to-date
  • ✅ Merged — 2026-10-04 01:39 UTC · at be66d68e33fd7aeb4d8fe5aa39b4838bab3f208c · merge

This pull request spent 12 seconds in the queue, including 2 seconds running CI.

Required conditions to merge

@mergify mergify Bot added the queued label Oct 4, 2026
@mergify
mergify Bot merged commit be66d68 into main Oct 4, 2026
5 checks passed
@mergify mergify Bot removed the queued label Oct 4, 2026
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