Skip to content

docs(audit): refresh the ledger PR column — every cluster now has a PR - #2442

Closed
noahgift wants to merge 3 commits into
mainfrom
docs/ledger-refresh-pr-column
Closed

docs(audit): refresh the ledger PR column — every cluster now has a PR#2442
noahgift wants to merge 3 commits into
mainfrom
docs/ledger-refresh-pr-column

Conversation

@noahgift

Copy link
Copy Markdown
Contributor

The ledger's Fixed by column was written before waves 3 and 4 and showed 30 findings covered. Regenerated from the live issue→PR map: 166 rows updated, 57 findings now carry a merged fix.

All 37 clusters have at least one PR. Several are deliberately partial and say so in their own bodies — Refs #2374 (partial) — remaining: 4, 9, 10, 12 — rather than claiming a clean sweep. That's why merged PRs outnumber closed issues: an issue closes when its last finding is covered.

Also added a short key for the column, and recorded which fixes have been verified against binaries built from main and SHA-matched via apr --version: --offline, validate, SSE streaming, rosetta, the native serve routes plus the remote abort, and MCP apr.serve.

That SHA match is not ceremony. The workspace target dir is shared across every worktree, so an "after" binary can silently be another worktree's concurrent build — one fix agent hit exactly that and measured a binary carrying neither of its own commits.

Docs only.

Audit epic: #2373

🤖 Generated with Claude Code

noahgift and others added 2 commits August 10, 2026 22:24
The PR column was written before waves 3 and 4 and showed 30 findings covered.
Regenerated from the live issue-to-PR map: 166 rows updated, 57 findings now
carry a merged fix.

All 37 clusters have at least one PR. Several are deliberately partial and say
so in their own bodies - "Refs #2374 (partial) - remaining: 4, 9, 10, 12" -
rather than claiming a clean sweep, which is why merged PRs outnumber closed
issues: an issue closes when its LAST finding is covered.

Added a short key for the column, and recorded which fixes have been verified
against binaries built from main and SHA-matched via `apr --version`. That
matching matters here: the workspace target dir is shared across every
worktree, so an "after" binary can silently be another worktree's build - one
fix agent hit exactly that and measured a binary carrying neither of its
commits.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Explains the #NNNN / checkmark notation, records that all 37 clusters have a
PR with several deliberately partial, and lists which fixes were verified on
SHA-matched main builds.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@noahgift

Copy link
Copy Markdown
Contributor Author

Parking to let the merge queue drain — branch untouched, this will be reopened.

Six PRs are in the merge queue and their merge_group check runs have been starved for hours: 16 runners, and every open PR keeps re-triggering its own workspace-test alongside them. Cancelling those runs does not hold (new ones replace them within a minute) and drafting does not stop CI on this repo, so closing is the only lever that frees the fleet.

The queue is the only path by which anything actually merges, so it gets the runners until it is empty. Reopening immediately afterwards.

@noahgift noahgift closed this Aug 10, 2026
@noahgift noahgift reopened this Aug 11, 2026
Conflict was the whole ledger file: #2430 landed the "How this count is kept
honest" methodology section on main while this branch was rewriting the same
table's PR column. Rather than hand-merge two rewrites of one table, took
main's file wholesale as the base and re-ran the column derivation against the
live issue-to-PR map on top of it. Both changes survive, and the column now
reflects everything merged to date rather than the snapshot this branch was cut
from.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@noahgift

Copy link
Copy Markdown
Contributor Author

Parking again to hold the CI host under its limit — branch untouched, will be reopened.

Nine audit PRs in flight took the shared runner box to 84% disk and a load average of 112. At that level workspace-test starts timing out at 75 minutes and PRs get silently evicted from the merge queue — which cost this audit about seven hours earlier today. Each PR carries ~49 GB of per-run scratch, so roughly six in flight is the real ceiling.

Reopening as the queue drains. This is pacing, not a problem with the change.

@noahgift noahgift closed this Aug 11, 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