[automation] Repository drift report

[github-actions]

Canonical delivery-state reconciliation

Generated: 2026-08-28T17:25:26.808Z

• Open PRs: 21
• Total remote branches: 353
• Ready PRs without exactly one canonical issue: 2
• Issues with competing implementation PRs: 0
• Unattached branches older than 14 days: 327

PRs requiring canonical issue

• build(deps): bump @google-cloud/text-to-speech from 6.4.1 to 7.0.0 #1550 — build(deps): bump @google-cloud/text-to-speech from 6.4.1 to 7.0.0
• fix(ci): arm the truth gate only on a real dispatch contract #1409 — fix(ci): arm the truth gate only on a real dispatch contract

Competing PRs

• None

Stale unattached branches

• agent/add-playwright-k6-readiness-gates-12086133390999099551 — 80a0065, last commit 2026-07-24T07:56:45Z
• agent/autonomous-repository-governance-11618302243648674141 — 4117766, last commit 2026-07-23T16:47:16Z
• agent/harden-api-cost-outbox — cc6fe44, last commit 2026-07-27T21:50:46Z
• agent/harden-api-cost-outbox-17376027973963893260 — 3eeb0ea, last commit 2026-07-25T00:27:32Z
• agent/harden-api-cost-outbox-4026591943861956227 — 780118e, last commit 2026-07-23T16:51:12Z
• agent/sop-orchestration-framework-12765657140344224400 — 956cbf3, last commit 2026-07-23T20:23:02Z
• agent/suppress-noop-runs-reporting-5600344477059750791 — 64c525a, last commit 2026-07-23T16:55:04Z
• agent-completiontruth-gate-is-permanently-unsatisfiable-grv-196-8883 — d477f48, last commit 2026-08-04T06:09:43Z
• agent-harden-api-cost-outbox-17376027973963893260 — 5eed87d, last commit 2026-07-24T23:25:10Z
• bolt/fix-batch-query-n1-bottleneck-16664381751066617032 — 065475a, last commit 2026-07-12T17:57:46Z
• bolt/frontend-string-alloc-optimizations-17876779194115511565 — c9560a6, last commit 2026-07-23T18:07:07Z
• bolt/optimize-text-filtering-15414235492514692486 — c59771c, last commit 2026-07-24T23:29:46Z
• bolt/optimize-transcript-filtering-15405883277453463883 — 2e2ef71, last commit 2026-07-23T17:08:23Z
• bolt/optimize-viewbox-computation-16758650612686925146 — b21aef5, last commit 2026-08-05T00:55:16Z
• bolt-agentflow-visualizer-optimize-4496922033576160387 — 56afc6f, last commit 2026-07-25T18:14:39Z
• bolt-fix-database-optimizer-n1-queries-14843617805558882255 — 265ab89, last commit 2026-07-14T14:41:06Z
• bolt-interactive-transcript-search-opt-14916651575670311014 — 0d9dadc, last commit 2026-07-21T17:56:53Z
• bolt-memoize-segment-row-14076716723355865204 — 3755b95, last commit 2026-07-12T00:10:21Z
• bolt-optimize-call-stacks-and-allocations-6836399447387675120 — 6dbb9c7, last commit 2026-07-26T17:16:54Z
• bolt-optimize-interactive-transcript-4719841486477851193-7466394128762780856 — a788d96, last commit 2026-07-23T16:42:37Z
• bolt-optimize-interactive-transcript-4719841486477851193 — f083286, last commit 2026-07-24T12:22:09Z
• bolt-optimize-interactive-transcript-5311554956858795087 — 6ad9ada, last commit 2026-07-24T01:19:02Z
• bolt-optimize-interactive-transcript-filtering-12565678381754441902 — 8f841ca, last commit 2026-07-21T07:59:08Z
• bolt-optimize-math-spread-10940801643914955491 — dd3ba20, last commit 2026-08-01T19:44:42Z
• bolt-optimize-tolowercase-17536213582151471881 — 09b6143, last commit 2026-07-21T15:28:28Z
• claude/add-deterministic-agent-completion-truth-gate — eb61c3f, last commit 2026-07-24T23:51:03Z
• claude/agent-login-fix — a45572e, last commit 2026-07-24T23:44:01Z
• claude/clever-heisenberg-3r6hpt — 5887e3c, last commit 2026-08-07T20:57:03Z
• claude/clever-heisenberg-8k227t — 39729d2, last commit 2026-08-07T18:10:48Z
• claude/clever-heisenberg-48a1as — 209f1be, last commit 2026-08-07T21:02:02Z
• claude/clever-heisenberg-6860sr — 1cb1fce, last commit 2026-08-07T20:55:05Z
• claude/clever-heisenberg-a0dh4r — 7358509, last commit 2026-08-07T21:10:30Z
• claude/clever-heisenberg-ctwlue — 5baae24, last commit 2026-08-07T21:03:50Z
• claude/clever-heisenberg-eh4att — cec9453, last commit 2026-08-07T21:03:59Z
• claude/clever-heisenberg-eleejm — 855dcec, last commit 2026-08-05T09:59:44Z
• claude/clever-heisenberg-i502mb — 36645ad, last commit 2026-08-05T10:14:22Z
• claude/clever-heisenberg-j1yx9l — 3646a90, last commit 2026-08-07T21:12:21Z
• claude/clever-heisenberg-klf4fu — 1853285, last commit 2026-08-07T17:16:07Z
• claude/clever-heisenberg-kltzfb — 618a604, last commit 2026-08-07T21:09:51Z
• claude/clever-heisenberg-rndqcq — a095dc6, last commit 2026-08-07T21:16:00Z
• claude/clever-heisenberg-s5uqf5 — 2ed25f8, last commit 2026-08-07T20:49:43Z
• claude/clever-heisenberg-spk8wk — 468537d, last commit 2026-08-07T20:58:21Z
• claude/clever-heisenberg-sz2wl8 — 020fad8, last commit 2026-08-07T18:04:42Z
• claude/clever-heisenberg-th9bml — 1fa4f18, last commit 2026-08-07T21:07:14Z
• claude/clever-heisenberg-yqkmys — f622e53, last commit 2026-08-07T21:19:32Z
• claude/dazzling-edison-95u1m4 — f6f083a, last commit 2026-07-17T09:47:19Z
• claude/dazzling-edison-ymkr67 — f024fd7, last commit 2026-07-17T09:13:23Z
• claude/determined-maxwell-0ium0k — a57f50e, last commit 2026-07-27T21:54:44Z
• claude/determined-maxwell-0n3r27 — ddae32f, last commit 2026-08-01T20:34:13Z
• claude/determined-maxwell-1y1im5 — 5d491a0, last commit 2026-07-18T02:48:59Z
• claude/determined-maxwell-2frkmc — c375307, last commit 2026-08-01T23:17:29Z
• claude/determined-maxwell-03lus6 — b269555, last commit 2026-08-02T12:27:19Z
• claude/determined-maxwell-3vgs17 — 9d52047, last commit 2026-07-09T05:59:01Z
• claude/determined-maxwell-3z56dm — 13ce226, last commit 2026-07-07T03:27:39Z
• claude/determined-maxwell-4dxv0e — a395c9c, last commit 2026-07-07T03:21:31Z
• claude/determined-maxwell-4gzjlq — 6632f75, last commit 2026-08-04T01:53:22Z
• claude/determined-maxwell-4k7sox — 1ba9cd4, last commit 2026-07-31T07:26:57Z
• claude/determined-maxwell-4ky0tz — c42776d, last commit 2026-07-14T14:25:40Z
• claude/determined-maxwell-4l1ghl — 1d5ace8, last commit 2026-07-17T02:22:03Z
• claude/determined-maxwell-4nb64a — dddb4db, last commit 2026-07-02T07:02:52Z
• claude/determined-maxwell-4thx4d — 1d5aa56, last commit 2026-07-10T18:46:42Z
• claude/determined-maxwell-5c11cx — 1e32f53, last commit 2026-07-07T04:48:27Z
• claude/determined-maxwell-5k80n4 — da0291d, last commit 2026-07-21T04:35:31Z
• claude/determined-maxwell-5t91o2 — 0283540, last commit 2026-08-02T13:23:26Z
• claude/determined-maxwell-06popt — 70f6db6, last commit 2026-06-29T22:25:32Z
• claude/determined-maxwell-6q4s34 — d88875d, last commit 2026-08-02T18:29:33Z
• claude/determined-maxwell-6rg53d — 78331cd, last commit 2026-07-09T06:45:21Z
• claude/determined-maxwell-6ssl0l — 0f06027, last commit 2026-07-27T21:38:06Z
• claude/determined-maxwell-7c9b1r — d6cdaa5, last commit 2026-08-01T22:33:10Z
• claude/determined-maxwell-7l7uv0 — 9ea44c3, last commit 2026-07-23T19:57:21Z
• claude/determined-maxwell-7ljegg — 8f4fc36, last commit 2026-08-03T21:23:58Z
• claude/determined-maxwell-7p4us0 — e5e91a3, last commit 2026-08-01T18:35:48Z
• claude/determined-maxwell-7vrh8v — 850a796, last commit 2026-06-28T23:07:41Z
• claude/determined-maxwell-7wu0ng — cfe7cd8, last commit 2026-07-17T01:40:51Z
• claude/determined-maxwell-7xje6x — 1a0ce65, last commit 2026-07-28T13:19:24Z
• claude/determined-maxwell-8p5n7u — d9d12cd, last commit 2026-07-17T02:36:20Z
• claude/determined-maxwell-9cogca — 7e0d6a5, last commit 2026-08-01T18:26:45Z
• claude/determined-maxwell-9erquc — e3c0238, last commit 2026-07-18T03:37:17Z
• claude/determined-maxwell-9ld7rc — d39c63d, last commit 2026-07-15T03:45:23Z
• claude/determined-maxwell-9qcq2r — bb98a67, last commit 2026-07-06T23:43:16Z
• claude/determined-maxwell-9qx6ue — 4f5e59f, last commit 2026-07-07T03:22:01Z
• claude/determined-maxwell-9t5kou — a124bde, last commit 2026-08-02T17:39:02Z
• claude/determined-maxwell-9wecpk — 16be441, last commit 2026-07-12T02:10:48Z
• claude/determined-maxwell-11jydn — 471a705, last commit 2026-07-12T02:19:35Z
• claude/determined-maxwell-13gas7 — 72751ee, last commit 2026-07-21T00:02:55Z
• claude/determined-maxwell-14jgh5 — b3bad4c, last commit 2026-07-14T13:49:01Z
• claude/determined-maxwell-33gxdg — 67ec149, last commit 2026-08-04T02:12:21Z
• claude/determined-maxwell-56ir7p — 5f5300d, last commit 2026-08-02T18:06:06Z
• claude/determined-maxwell-61nzcv — 5e90d0a, last commit 2026-07-12T04:09:08Z
• claude/determined-maxwell-70t6tf — 85b70ec, last commit 2026-08-03T21:08:30Z
• claude/determined-maxwell-81rne1 — 17958ac, last commit 2026-07-07T03:07:30Z
• claude/determined-maxwell-82cm3w — ea43337, last commit 2026-08-01T19:59:03Z
• claude/determined-maxwell-1419pg — 15653c1, last commit 2026-08-01T20:15:08Z
• claude/determined-maxwell-5593h9 — baf93b2, last commit 2026-07-02T21:38:19Z
• claude/determined-maxwell-92049h — e6ad8b6, last commit 2026-07-07T00:20:43Z
• claude/determined-maxwell-a6apnm — 18cb319, last commit 2026-07-03T20:50:31Z
• claude/determined-maxwell-a9n93o — b981053, last commit 2026-08-04T06:20:09Z
• claude/determined-maxwell-aacju9 — c4cd028, last commit 2026-07-04T05:08:30Z
• claude/determined-maxwell-ayuxew — 365f94b, last commit 2026-07-14T17:18:08Z
• claude/determined-maxwell-b1npnt — 9ee059c, last commit 2026-08-02T18:46:53Z

This report is intentionally non-destructive. Branch deletion requires a merged PR or an explicit retention decision.

Canonical governance: #898

[linear-code]

GRV-314

[coderabbitai]

🔗 Related PRs

#222 - docs: branch-cleanup assessment + reproducible fail-test harness [merged]
#277 - Vercel remediation complete: waitUntil adoption + active middleware + @vercel/functions package (resolves three user-defined outcomes; 16-agent verification-gate consolidated PASS on full matrix) [closed]
#404 - fix(web): sync package-lock with @vercel/functions (unblocks #277 auto-merge) [merged]
#1061 - revert: remove unauthorized broad #1057 merge [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[coderabbitai]

Coding Plan

Summary

• Respond to the drift report with one dated, non-destructive docs/runbook/ triage document that classifies every flagged PR, issue, and branch. This follows established repository precedent.
• Reconcile the two flagged PRs: attach or defer PR #1356, and exempt automated dependency bumps like PR #1171 at the pr-governance.yml and repository-reconciliation.yml layer to stop recurrence.
• Resolve the four competing PR groups by selecting the green, reviewed PR as canonical and staging closure of the superseded PR. Halt any all-draft or all-red group for human choice.
• Clear the 181 stale branches through the existing branch-cleanup fail-test harness and archive-first branch-cleanup-delete.sh, generated in dry-run mode and left for the maintainer to execute.

Design Choices

Design Choice 1: How to satisfy the canonical-issue requirement for the dependency-bump PR `#1171`

Options Considered:

1. Attach a canonical child issue to #1171 by editing its body to add Closes #<new-issue>, mirroring every other PR.
2. Add a scoped exemption in pr-governance.yml and repository-reconciliation.yml for automated dependency-bump PRs (for example, PRs authored by the dependency bot or matching the build(deps) title prefix), so they no longer require a canonical issue.

Chosen Option: 2

Rationale: A recurring class of automated PRs should not require per-PR manual issue authoring. A scoped, bot-only exemption fixes the drift at its source and stops recurrence. This choice matches the precedent of fixing the governance machinery when the report reveals a systemic gap.

Design Choice 2: How to select the canonical PR within each competing pair

Options Considered:

1. Select the PR with green functional CI plus review approval as canonical. Mark the other PR DEFERRED(duplicate of #N) for a human to close.
2. Always keep the newest PR number as canonical.

Chosen Option: 1

Rationale: The documented repository pattern selects the greener, reviewed PR as canonical. It defers the losing PR with an explicit "duplicate of #N" annotation. PR number alone is not a reliable quality signal.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Phase 1: Produce the reconciliation triage report

This phase creates the single authoritative response artifact. It follows the established runbook format and stays non-destructive. All later phases record their decisions inside this document.

Task 1: Create the dated drift-remediation report

Create the report that classifies every flagged item and anchors it to governance #898.

• Create a new dated markdown file under docs/runbook/ (for example docs/runbook/drift-remediation-2026-08-04.md), matching the section structure of docs/runbook/pr-remediation-report-2026-08-04.md.
• Include a header block with run date, source issue title [automation] Repository drift report, scope, and the Canonical governance: [PROGRAM][OWNER:Codex] Autonomous EventRelay delivery control plane #898`` anchor.
• Include a Definition of Done statement that restates the non-destructive rule: no merge, close, or branch delete runs without a human decision.
• Add three top-level sections that mirror the report: PRs requiring canonical issue, Competing PRs, and Stale unattached branches.
• State explicitly that PRs #1356, #1171 and PR numbers #1364/fix(deploy): repair one-click-deploy.sh prechecks and frontend probe paths #1363/fix(cloud): authenticate task requests before payload validation #1361/fix(security): raise brace-expansion override floors above the OOM backport #1226 have no local history and require live GitHub inspection (title, body, CI state, review state) before disposition.

Task 2: Gather live state for each flagged PR and branch

Collect the evidence the report needs, because local docs stop at PR #1156.

• For each PR (#1356, #1171, #1364, #1154, #1363, #1155, #1361, #1132, #1226, #1117): record author, head SHA, draft state, combined CI status, pr-governance Check result, merge-conflict state, and canonical-issue references from the PR body.
• For each competing issue (#1130, #1127, #1134, #1115): record which of its two PRs is green and reviewed, and which is a draft or red.
• For each stale branch: confirm it has no open same-repo PR head and that its last-commit age exceeds 14 days, reusing the detection logic already in repository-reconciliation.yml.

🤖 Prompt for AI agents

Build the single authoritative triage report that drives every later decision in
this plan. Follow the established runbook format exactly and keep the report
non-destructive.

- Create a new dated markdown file under `docs/runbook/` (for example
`docs/runbook/drift-remediation-2026-08-04.md`). Match the section structure of
`docs/runbook/pr-remediation-report-2026-08-04.md`.
- Add a header block with the run date, the source issue title `[automation]
Repository drift report`, the scope, and the `Canonical governance: `#898``
anchor.
- Add a Definition of Done statement that restates the non-destructive rule: no
merge, close, or branch delete runs without a human decision.
- Add three top-level sections that mirror the drift report: `PRs requiring
canonical issue`, `Competing PRs`, and `Stale unattached branches`.
- State explicitly that PRs `#1356`, `#1171`, and PR numbers `#1364/`#1363/#1361/#1226
have no local history. State that they require live GitHub inspection (title,
body, CI state, review state) before disposition.
- Gather live state for each flagged PR (`#1356`, `#1171`, `#1364`, `#1154`, `#1363`,
`#1155`, `#1361`, `#1132`, `#1226`, `#1117`): record author, head SHA, draft state,
combined CI status, `pr-governance` Check result, merge-conflict state, and
canonical-issue references from the PR body.
- For each competing issue (`#1130`, `#1127`, `#1134`, `#1115`), record which of its two
PRs is green and reviewed, and which one is a draft or red.
- For each stale branch, confirm it has no open same-repo PR head and that its
last-commit age exceeds 14 days. Reuse the detection logic already in
`repository-reconciliation.yml`.

Phase 2: Reconcile ready PRs to canonical issues

This phase clears the PRs requiring canonical issue section. It attaches a canonical issue where a PR is legitimate and exempts automated dependency bumps at the governance layer.

Task 1: Attach or reconcile the canonical issue for PR `#1356`

Give the Claude-authored PR exactly one valid canonical issue, or defer it.

• If PR #1356 delivers real, wanted work: file a focused child issue under #898, then stage a gh pr edit 1356 --body command that adds a single Closes #<new-issue> reference plus the required delivery-evidence sections that pr-governance.yml enforces (## Canonical issue, ## Outcome, ## Risk, ## Verification, ## Production evidence).
• If PR #1356 is obsolete or superseded: stage a gh pr close 1356 command with a superseded/obsolete reason.
• Record the chosen disposition and rationale in the report from Task 1.1. Do not execute the command.

Task 2: Exempt automated dependency-bump PRs from the canonical-issue requirement

Fix the recurring cause that flags PR #1171 and future bumps.

• Update .github/workflows/pr-governance.yml to skip the exactly-one-canonical-issue enforcement and the delivery-evidence enforcement for automated dependency-bump PRs. Detect them by PR author (the dependency bot login) and/or a build(deps) title prefix.
• Update .github/workflows/repository-reconciliation.yml to apply the same exemption in its "ready PR missing canonical issue" classification, so the daily report no longer lists dependency-bump PRs.
• Keep the exemption narrow. Do not exempt any human- or general-agent-authored PR.
• File this governance change as a focused child issue under #898 and reference it as the canonical issue of the PR that lands the change, per the contract in .github/pull_request_template.md.

🤖 Prompt for AI agents

Clear the `PRs requiring canonical issue` section by resolving PR `#1356` and by
fixing the systemic gap that flags dependency-bump PRs like `#1171`.

- For PR `#1356`: if it delivers real, wanted work, file a focused child issue
under `#898`, then stage (do not run) a `gh pr edit 1356 --body` command that adds
a single `Closes #<new-issue>` reference plus the delivery-evidence sections
that `pr-governance.yml` enforces (`## Canonical issue`, `## Outcome`, `##
Risk`, `## Verification`, `## Production evidence`). If PR `#1356` is obsolete or
superseded, stage a `gh pr close 1356` command with a `superseded`/`obsolete`
reason instead.
- Record the chosen disposition and rationale for PR `#1356` in the report created
in Phase 1. Do not execute the staged command.
- Update `.github/workflows/pr-governance.yml` to skip the
exactly-one-canonical-issue enforcement and the delivery-evidence enforcement
for automated dependency-bump PRs. Detect these PRs by author (the dependency
bot login) and/or a `build(deps)` title prefix.
- Update `.github/workflows/repository-reconciliation.yml` to apply the
identical exemption logic to its "ready PR missing canonical issue"
classification, so the daily drift report stops listing dependency-bump PRs.
- Keep the exemption scope narrow: it must apply only to automated
dependency-bump PRs, never to any human- or general-agent-authored PR.
- File this governance-workflow change as a focused child issue under `#898`.
Reference that issue as the canonical issue of the PR that lands this change,
per the contract in `.github/pull_request_template.md`.

Phase 3: Resolve competing implementation PRs

This phase clears the Competing PRs section. For each of the four issues it selects one canonical PR and stages closure of the other. It never auto-closes.

Task 1: Classify each competing pair and select the canonical PR

Apply the documented selection rule to all four groups.

• For each group (#1130: #1364 vs #1154; #1127: #1363 vs #1155; #1134: #1361 vs #1132; #1115: #1226 vs #1117), select the PR with green functional CI and review approval as canonical, using the live state from Task 1.2.
• If both PRs in a group are drafts or both are red, mark the group HALTED(needs human choice) and do not pick a winner.
• Record each decision as a row in the report: issue, canonical PR, superseded PR, evidence, terminal state.

Task 2: Stage closure of the superseded PRs

Prepare, but do not run, the closing actions.

• For each resolved group, stage a gh pr close <superseded-PR> command with an explicit DEFERRED(duplicate of #<canonical-PR>) comment body.
• For each HALTED group, stage no close command and instead list the exact question the maintainer must answer.
• Confirm each surviving canonical PR still carries exactly one valid Closes #<issue> reference; stage a body edit if it does not.

🤖 Prompt for AI agents

Clear the `Competing PRs` section by selecting exactly one canonical PR per
issue and staging closure of the other. Never close any PR automatically.

- For each of the four competing groups (`#1130`: `#1364` vs `#1154`; `#1127`: `#1363` vs
`#1155`; `#1134`: `#1361` vs `#1132`; `#1115`: `#1226` vs `#1117`), select the PR with green
functional CI and review approval as canonical. Use the live state gathered in
Phase 1.
- If both PRs in a group are drafts, or both are red, mark that group
`HALTED(needs human choice)` and do not pick a winner.
- Record each decision as a row in the report: issue, canonical PR, superseded
PR, evidence, terminal state.
- For each resolved group, stage (do not run) a `gh pr close <superseded-PR>`
command with an explicit `DEFERRED(duplicate of #<canonical-PR>)` comment body.
- For each `HALTED` group, stage no close command. Instead, list the exact
question the maintainer must answer to resolve it.
- Confirm each surviving canonical PR still carries exactly one valid `Closes
#<issue>` reference. If it does not, stage a body edit to fix it.

Phase 4: Stage safe cleanup of stale unattached branches

This phase clears the Stale unattached branches section. It uses the existing branch-cleanup harness and its archive-first safety rule. It generates, but does not run, deletions.

Task 1: Run the branch-cleanup fail-test harness and emit a decision matrix

Score every stale branch and produce the KEEP/CLOSE verdicts.

• Run the 6-gate fail-test harness described in .claude/skills/branch-cleanup/SKILL.md against the 181 stale branches (the report lists the bolt/*, bolt-*, claude/dazzling-edison-*, claude/determined-maxwell-*, and claude/* topic branches).
• Emit the decision matrix to docs/branch-cleanup-matrix.md (and .csv), scoring each branch on PR-state, redundancy, merge-cleanliness, unique diff, and staleness.
• Apply the hard safety rules: never mark a branch with an open PR as deletable; assign each branch a verdict of KEEP, CLOSE-SAFE, CLOSE-STALE, or REVIEW.
• Note the two branches with the identical SHA 53fa3fcf (claude/determined-maxwell-udy1ne and claude/determined-maxwell-uybuwc) as a duplicate pair.

Task 2: Generate the archive-and-delete script from the matrix

Produce the executable, dry-run-default cleanup script.

• Regenerate scripts/maintenance/branch-cleanup-delete.sh from the matrix CSV, populating the SAFE_BRANCHES and REVIEW_BRANCHES arrays from the CLOSE-SAFE/CLOSE-STALE and REVIEW verdicts.
• Keep DRY_RUN defaulting to 1 and keep the archive-tag step (git tag -f archive/<branch> then push) before any delete.
• Keep the live open-PR re-check that the prior incident fix (PR #227) added, so no branch with a new open PR is deleted.
• In the report from Task 1.1, record the exact invocation the maintainer runs (scripts/maintenance/branch-cleanup-delete.sh safe, then review) and state that deletion stays non-destructive until run with DRY_RUN=0.

🤖 Prompt for AI agents

Clear the `Stale unattached branches` section by scoring all 181 stale branches
and generating a dry-run-default deletion script. Do not run any deletion.

- Run the 6-gate fail-test harness described in
`.claude/skills/branch-cleanup/SKILL.md` against the 181 stale branches. These
include the `bolt/*`, `bolt-*`, `claude/dazzling-edison-*`,
`claude/determined-maxwell-*`, and `claude/*` topic branches listed in the
report.
- Emit the decision matrix to `docs/branch-cleanup-matrix.md` and
`docs/branch-cleanup-matrix.csv`. Score each branch on PR-state, redundancy,
merge-cleanliness, unique diff, and staleness.
- Apply the hard safety rules: never mark a branch with an open PR as deletable.
Assign each branch one verdict: `KEEP`, `CLOSE-SAFE`, `CLOSE-STALE`, or
`REVIEW`.
- Note the duplicate pair with identical SHA `53fa3fcf`:
`claude/determined-maxwell-udy1ne` and `claude/determined-maxwell-uybuwc`.
- Regenerate `scripts/maintenance/branch-cleanup-delete.sh` from the matrix CSV.
Populate the `SAFE_BRANCHES` array from the `CLOSE-SAFE`/`CLOSE-STALE` verdicts
and the `REVIEW_BRANCHES` array from the `REVIEW` verdicts.
- Keep `DRY_RUN` defaulting to `1`. Keep the archive-tag step (`git tag -f
archive/<branch>` then push) before any delete step.
- Keep the live open-PR re-check added by the prior incident fix (PR `#227`), so
the script never deletes a branch that gained a new open PR.
- In the report from Phase 1, record the exact invocation the maintainer must
run (`scripts/maintenance/branch-cleanup-delete.sh safe`, then `review`). State
that deletion stays non-destructive until the maintainer runs it with
`DRY_RUN=0`.

Research

The repository enforces a canonical one-issue-to-one-PR governance model rooted at issue #898. Three code assets implement this governance model:

• .github/pull_request_template.md: the contract.
• .github/workflows/pr-governance.yml: PR-time enforcement Check.
• .github/workflows/repository-reconciliation.yml: the daily detector that upserts the drift report issue.

Remediation of drift is, by established precedent, a documented process. It is not an autonomous action. Prior drift responses exist as dated markdown reports under docs/triage/, docs/pr-remediation/, and docs/runbook/. The most recent report is docs/runbook/pr-remediation-report-2026-08-04.md. Each report classifies items as MERGED, DEFERRED(reason), or HALTED(reason). Each report ends with staged gh commands for a human to run.

Branch cleanup uses the branch-cleanup skill (.claude/skills/branch-cleanup/SKILL.md). This skill is a 6-gate fail-test harness that produces a decision matrix. The cleanup also uses scripts/maintenance/branch-cleanup-delete.sh, which archive-tags every branch before deletion and re-checks live open-PR status. Protected main plus the missing automerge label make the human gate deliberate.

---

🚀 Next Steps

🤖 All AI agent prompts combined

Task: 1

Build the single authoritative triage report that drives every later decision in
this plan. Follow the established runbook format exactly and keep the report
non-destructive.

- Create a new dated markdown file under `docs/runbook/` (for example
`docs/runbook/drift-remediation-2026-08-04.md`). Match the section structure of
`docs/runbook/pr-remediation-report-2026-08-04.md`.
- Add a header block with the run date, the source issue title `[automation]
Repository drift report`, the scope, and the `Canonical governance: `#898``
anchor.
- Add a Definition of Done statement that restates the non-destructive rule: no
merge, close, or branch delete runs without a human decision.
- Add three top-level sections that mirror the drift report: `PRs requiring
canonical issue`, `Competing PRs`, and `Stale unattached branches`.
- State explicitly that PRs `#1356`, `#1171`, and PR numbers `#1364/`#1363/#1361/#1226
have no local history. State that they require live GitHub inspection (title,
body, CI state, review state) before disposition.
- Gather live state for each flagged PR (`#1356`, `#1171`, `#1364`, `#1154`, `#1363`,
`#1155`, `#1361`, `#1132`, `#1226`, `#1117`): record author, head SHA, draft state,
combined CI status, `pr-governance` Check result, merge-conflict state, and
canonical-issue references from the PR body.
- For each competing issue (`#1130`, `#1127`, `#1134`, `#1115`), record which of its two
PRs is green and reviewed, and which one is a draft or red.
- For each stale branch, confirm it has no open same-repo PR head and that its
last-commit age exceeds 14 days. Reuse the detection logic already in
`repository-reconciliation.yml`.
===============================================================================

Task: 2

Clear the `PRs requiring canonical issue` section by resolving PR `#1356` and by
fixing the systemic gap that flags dependency-bump PRs like `#1171`.

- For PR `#1356`: if it delivers real, wanted work, file a focused child issue
under `#898`, then stage (do not run) a `gh pr edit 1356 --body` command that adds
a single `Closes #<new-issue>` reference plus the delivery-evidence sections
that `pr-governance.yml` enforces (`## Canonical issue`, `## Outcome`, `##
Risk`, `## Verification`, `## Production evidence`). If PR `#1356` is obsolete or
superseded, stage a `gh pr close 1356` command with a `superseded`/`obsolete`
reason instead.
- Record the chosen disposition and rationale for PR `#1356` in the report created
in Phase 1. Do not execute the staged command.
- Update `.github/workflows/pr-governance.yml` to skip the
exactly-one-canonical-issue enforcement and the delivery-evidence enforcement
for automated dependency-bump PRs. Detect these PRs by author (the dependency
bot login) and/or a `build(deps)` title prefix.
- Update `.github/workflows/repository-reconciliation.yml` to apply the
identical exemption logic to its "ready PR missing canonical issue"
classification, so the daily drift report stops listing dependency-bump PRs.
- Keep the exemption scope narrow: it must apply only to automated
dependency-bump PRs, never to any human- or general-agent-authored PR.
- File this governance-workflow change as a focused child issue under `#898`.
Reference that issue as the canonical issue of the PR that lands this change,
per the contract in `.github/pull_request_template.md`.
===============================================================================

Task: 3

Clear the `Competing PRs` section by selecting exactly one canonical PR per
issue and staging closure of the other. Never close any PR automatically.

- For each of the four competing groups (`#1130`: `#1364` vs `#1154`; `#1127`: `#1363` vs
`#1155`; `#1134`: `#1361` vs `#1132`; `#1115`: `#1226` vs `#1117`), select the PR with green
functional CI and review approval as canonical. Use the live state gathered in
Phase 1.
- If both PRs in a group are drafts, or both are red, mark that group
`HALTED(needs human choice)` and do not pick a winner.
- Record each decision as a row in the report: issue, canonical PR, superseded
PR, evidence, terminal state.
- For each resolved group, stage (do not run) a `gh pr close <superseded-PR>`
command with an explicit `DEFERRED(duplicate of #<canonical-PR>)` comment body.
- For each `HALTED` group, stage no close command. Instead, list the exact
question the maintainer must answer to resolve it.
- Confirm each surviving canonical PR still carries exactly one valid `Closes
#<issue>` reference. If it does not, stage a body edit to fix it.
===============================================================================

Task: 4

Clear the `Stale unattached branches` section by scoring all 181 stale branches
and generating a dry-run-default deletion script. Do not run any deletion.

- Run the 6-gate fail-test harness described in
`.claude/skills/branch-cleanup/SKILL.md` against the 181 stale branches. These
include the `bolt/*`, `bolt-*`, `claude/dazzling-edison-*`,
`claude/determined-maxwell-*`, and `claude/*` topic branches listed in the
report.
- Emit the decision matrix to `docs/branch-cleanup-matrix.md` and
`docs/branch-cleanup-matrix.csv`. Score each branch on PR-state, redundancy,
merge-cleanliness, unique diff, and staleness.
- Apply the hard safety rules: never mark a branch with an open PR as deletable.
Assign each branch one verdict: `KEEP`, `CLOSE-SAFE`, `CLOSE-STALE`, or
`REVIEW`.
- Note the duplicate pair with identical SHA `53fa3fcf`:
`claude/determined-maxwell-udy1ne` and `claude/determined-maxwell-uybuwc`.
- Regenerate `scripts/maintenance/branch-cleanup-delete.sh` from the matrix CSV.
Populate the `SAFE_BRANCHES` array from the `CLOSE-SAFE`/`CLOSE-STALE` verdicts
and the `REVIEW_BRANCHES` array from the `REVIEW` verdicts.
- Keep `DRY_RUN` defaulting to `1`. Keep the archive-tag step (`git tag -f
archive/<branch>` then push) before any delete step.
- Keep the live open-PR re-check added by the prior incident fix (PR `#227`), so
the script never deletes a branch that gained a new open PR.
- In the report from Phase 1, record the exact invocation the maintainer must
run (`scripts/maintenance/branch-cleanup-delete.sh safe`, then `review`). State
that deletion stays non-destructive until the maintainer runs it with
`DRY_RUN=0`.

💡 Iterate on the plan with: `@coderabbitai` <feedback>

Example Feedback
- `@coderabbitai` You can skip phase 3. Add a simple unit test case for phase 2.
- `@coderabbitai` For design choice 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!