Review-thread triage (Universal)

Name is historical (codex-connector). Apply to every unresolved thread on the PR: Codex, Cursor Bugbot, Copilot, humans.

Unresolved threads block merge on every protected fleet repo even when checks are green.

1. Fetch unresolved threads

OWNER="$(gh repo view --json owner --jq .owner.login)"
REPO="$(gh repo view --json name --jq .name)"
gh api graphql -f query="query { repository(owner:\"$OWNER\", name:\"$REPO\") { pullRequest(number: <N>) { reviewThreads(first: 100) { nodes { id isResolved path line comments(first: 10) { nodes { author { login } body diffHunk } } } } } } }" \
  --jq '.data.repository.pullRequest.reviewThreads.nodes | map(select(.isResolved==false))'

2. Classify against current HEAD

Three buckets only:

• addressed — already fixed on this branch after the comment.
• false_positive — bot misread context, or the rule does not apply here.
• real — valid. For money-path / auth / execution / policy / billing files, have a second agent (or a frontier child) adversarially verify before you change behavior.

Do not classify from the stale diff hunk. Read the file at HEAD.

3. Fix reals in one batch

One commit with a regression test per behavior change. Push before resolving any thread (race in step 5).

4. Reply, then resolve

Do not resolve without a reply.

gh api graphql -f query='mutation($t:ID!,$b:String!){addPullRequestReviewThreadReply(input:{pullRequestReviewThreadId:$t,body:$b}){comment{id}}}' -F t=<threadId> -f b=<text>

gh api graphql -f query='mutation($t:ID!){resolveReviewThread(input:{threadId:$t}){thread{isResolved}}}' -F t=<threadId>

Reply shape (review-thread replies are PR text: a real U+00A0 plus a space between sentences, converted with the perl recipe in sentence-gap; since the 2026-10-23 owner ruling, prose files take the same U+00A0 plus a space, and code never does):

• Real: Fixed in <short-sha>. <function>. Test: test/foo.test.ts.
• False positive: why the rule does not apply, then resolve.
• Addressed already: cite the SHA that landed the fix.

Never blind-resolve to force a merge. The gate exists because some findings are real (commit-author, licenses, money-path).

5. Auto-merge race

The instant the last thread resolves and CI is green, auto-merge fires. Bots re-review every push and often never converge.

• Resolving the last thread is merging the PR. Triple-check first.
• Round-2 comments often land on an already-merged PR. Before resolving as "fixed," confirm the fix reached main:

git fetch origin
git merge-base --is-ancestor <fix-sha> origin/main && echo "on main" || echo "NOT on main"

If NOT on main, open a follow-up PR from the same branch. Expect squash-merge conflicts — merge main in; this branch's newer rounds win in its own files.

6. Per-PR stop rule (rounds 1–2, then accepted risk)

Kody and similar bots re-review the whole diff on every push. Zero-unresolved threads is not a terminating merge bar — each fix push can open a fresh batch (BF-1997).

Round 1: classify all unresolved threads against HEAD; batch-fix real items; reply + resolve addressed and false positives. Push before resolving (section 5).

Round 2: only for threads opened on the round-1 head (group by comments.nodes[0].commit.oid). Same batch-fix discipline.

Stop: after round 2, do not chase convergence. For each remaining thread, either merge with an explicit accepted risk note (why the finding is deferred, already mitigated elsewhere, or out of scope) or escalate money-path / release-path items to the owner. Post accepted-risk summaries on the PR and, for fleet work, THE BOARD or Linear (BF-1997 canon).

Kody findings are advisory — verify against HEAD; adversarially check critical paths before changing behavior (section 2). Later rounds on an already-merged PR are mostly noise: triage genuine hazards; surface the rest via Apple Notes + board comment.

Full decision: docs/decisions/2026-10-15-kody-review-stop-rule.md.

Canon

• /Users/jay/apps/FLEET-PROTOCOL.md — Merge requirements
• App AGENTS.md — Kody Review Rules; Pre-Commit / Handoff
• docs/decisions/2026-10-15-kody-review-stop-rule.md — stop rule evidence
• Skills: unstick-pr, land-lane