Docs-only. Appends a re-measured block to docs/defect-shapes-773.md §5.3, keeping the dated 2026-08-13 table rather than overwriting it.
What the re-measurement found
Original claim
Re-measured 2026-08-14
population = the listed tools
Seven enabled plugins were omitted, incl. serena — the table was hand-written
811 transcripts
964 via rglob (a top-level glob sees 209 and manufactures false zeros)
mempalace dead 19 days
31 calls, last seen 2026-08-14 — active; the gap was a snapshot artifact
codex 0 skill invocations
113 codex exec calls / 17 sessions — third-heaviest tool in the corpus
LSP 0 calls
Not zero — the calls are from sessions testing whether the LSP works, incl. §5.1's own probes
gitea "identical values"
Not identical (user scope has "type": "stdio")
Positive control on the same query: 24,762 Bash, 5,275 Read, 4,037 Edit.
Why this is a PARTIAL, deliberately
#781's Done-when asks that every configured plugin/MCP server be "demonstrably used or removed". The evidence argues against the removals. These zeros split four ways:
broken — csharp-lsp MCP + two LSP servers (fixed in #777)
unreachable — serena: starts standalone at v1.28.1, tools never reach a session → #799
just enabled — three plugins turned on the same day; their zeros mean "not yet tried"
wrong surface measured — codex, which is in fact the corpus's third-heaviest tool
Ticking that box would mean deleting things whose zero I have just shown is not evidence of uselessness. fixes-trailer-closes-issues-that-are-not-done is the record for exactly that. So this PR lands the audit and the one supported change, and the issue stays open pending #799 and a later re-measure.
The gitea de-duplication, and why it went the other way
Resolved in gitignored local config, so it shows here only as a recorded outcome. The naive move — keep the more specific project entry — would have broken two other repos: server-management and homelab-docs have no .mcp.json and depend on the user-scope copy. The project copy was removed instead, and the survivor was smoke-tested (starts, 54 tools) rather than assumed.
refs #781 (partial — see below)
Docs-only. Appends a re-measured block to `docs/defect-shapes-773.md` §5.3, keeping the dated 2026-08-13 table rather than overwriting it.
## What the re-measurement found
| Original claim | Re-measured 2026-08-14 |
|---|---|
| population = the listed tools | **Seven enabled plugins were omitted**, incl. `serena` — the table was hand-written |
| 811 transcripts | **964** via `rglob` (a top-level glob sees 209 and manufactures false zeros) |
| `mempalace` dead 19 days | **31 calls, last seen 2026-08-14** — active; the gap was a snapshot artifact |
| `codex` 0 skill invocations | **113 `codex exec` calls / 17 sessions** — third-heaviest tool in the corpus |
| `LSP` 0 calls | Not zero — the calls are from sessions testing whether the LSP works, incl. §5.1's own probes |
| `gitea` "identical values" | Not identical (user scope has `"type": "stdio"`) |
Positive control on the same query: 24,762 `Bash`, 5,275 `Read`, 4,037 `Edit`.
## Why this is a PARTIAL, deliberately
#781's Done-when asks that every configured plugin/MCP server be "demonstrably used or removed". **The evidence argues against the removals.** These zeros split four ways:
- **broken** — `csharp-lsp` MCP + two LSP servers (fixed in #777)
- **unreachable** — `serena`: starts standalone at v1.28.1, tools never reach a session → **#799**
- **just enabled** — three plugins turned on the same day; their zeros mean "not yet tried"
- **wrong surface measured** — `codex`, which is in fact the corpus's third-heaviest tool
Ticking that box would mean deleting things whose zero I have just shown is not evidence of uselessness. `fixes-trailer-closes-issues-that-are-not-done` is the record for exactly that. So this PR lands the audit and the one supported change, and the issue stays open pending #799 and a later re-measure.
## The `gitea` de-duplication, and why it went the other way
Resolved in gitignored local config, so it shows here only as a recorded outcome. The naive move — keep the more specific project entry — **would have broken two other repos**: `server-management` and `homelab-docs` have no `.mcp.json` and depend on the user-scope copy. The project copy was removed instead, and the survivor was smoke-tested (starts, 54 tools) rather than assumed.
The §5.3 table was assembled by hand. Deriving the population from the config files
instead surfaces seven enabled plugins it omits, including `serena`. An audit whose
completeness rests on remembering every entry is the failure
`testing.guard-derives-population-from-source` exists to prevent, applied to an audit
rather than to a guard.
The corpus was also undercounted: 964 transcripts via rglob, not 811 — a top-level
glob sees 209 here and manufactures false zeros. Positive control: 24,762 Bash.
Two corrections to existing rows. `mempalace` is not dead — 31 calls, last seen
2026-08-14; the 19-day gap was a snapshot artifact. `codex` is the third-heaviest
tool in the corpus at 113 `codex exec` calls across 17 sessions; the table's caveat
was right and this is the number.
The conclusion the issue expected does not survive. "Retire what is enabled and never
invoked" reads a zero as uselessness, but these zeros split four ways: broken
(csharp-lsp MCP and two LSP servers, #777), unreachable (serena, #799), just enabled
(three plugins turned on that same day), and measured on the wrong surface (codex).
Establishing WHY a counter is zero is a precondition for acting on it, and on this
evidence almost nothing should be removed. What was wrong was duplication and
breakage, not excess.
The one removal the evidence supports is `gitea`, and it went the opposite way from
the obvious choice: the PROJECT copy was dropped, not the "more specific" one, because
server-management and homelab-docs have no .mcp.json of their own and depend on the
user-scope entry. The survivor was smoke-tested afterwards (starts, 54 tools) rather
than assumed. That change is to gitignored local config, so it appears here only as
the recorded outcome.
The 2026-08-13 table is kept rather than overwritten: it is a dated measurement, and
the re-measurement is stated against it so a reader can see what moved.
refs #781
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
refs #781 (partial — see below)
Docs-only. Appends a re-measured block to
docs/defect-shapes-773.md§5.3, keeping the dated 2026-08-13 table rather than overwriting it.What the re-measurement found
serena— the table was hand-writtenrglob(a top-level glob sees 209 and manufactures false zeros)mempalacedead 19 dayscodex0 skill invocationscodex execcalls / 17 sessions — third-heaviest tool in the corpusLSP0 callsgitea"identical values""type": "stdio")Positive control on the same query: 24,762
Bash, 5,275Read, 4,037Edit.Why this is a PARTIAL, deliberately
#781's Done-when asks that every configured plugin/MCP server be "demonstrably used or removed". The evidence argues against the removals. These zeros split four ways:
csharp-lspMCP + two LSP servers (fixed in #777)serena: starts standalone at v1.28.1, tools never reach a session → #799codex, which is in fact the corpus's third-heaviest toolTicking that box would mean deleting things whose zero I have just shown is not evidence of uselessness.
fixes-trailer-closes-issues-that-are-not-doneis the record for exactly that. So this PR lands the audit and the one supported change, and the issue stays open pending #799 and a later re-measure.The
giteade-duplication, and why it went the other wayResolved in gitignored local config, so it shows here only as a recorded outcome. The naive move — keep the more specific project entry — would have broken two other repos:
server-managementandhomelab-docshave no.mcp.jsonand depend on the user-scope copy. The project copy was removed instead, and the survivor was smoke-tested (starts, 54 tools) rather than assumed.0d792329cfto0874927cfc