From 0874927cfcf7bf615eadf58c92b9f43741724eb8 Mon Sep 17 00:00:00 2001 From: Timothy Date: Fri, 14 Aug 2026 17:56:45 +0200 Subject: [PATCH] =?UTF-8?q?docs(781):=20re-measure=20=C2=A75.3=20from=20a?= =?UTF-8?q?=20DERIVED=20population=20=E2=80=94=20the=20zeros=20split=20fou?= =?UTF-8?q?r=20ways?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- docs/defect-shapes-773.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/docs/defect-shapes-773.md b/docs/defect-shapes-773.md index 8095eec08..9bcfcfd9c 100644 --- a/docs/defect-shapes-773.md +++ b/docs/defect-shapes-773.md @@ -468,6 +468,36 @@ and 5,102 `Read` calls over the same corpus, so the search was demonstrably capa **Re-derive it with that positive control**, not on its own — `rg -c` over multiple files prints `path:count`, so the obvious way to total it sums the paths and returns zero for everything. +**Re-measured 2026-08-14 (#781), and the table above needs two corrections plus seven additions.** +The population here was assembled **by hand**; deriving it from the config files instead +(`~/.claude/settings.json` `enabledPlugins`, `~/.claude.json` `mcpServers`, the project `.mcp.json`, +`.claude/settings.local.json`) surfaces **seven enabled plugins the table omits** — `serena`, +`code-review`, `code-simplifier`, `commit-commands`, `claude-md-management`, `skill-creator`, +`frontend-design`. An audit whose completeness rests on remembering every entry is exactly the +failure `testing.guard-derives-population-from-source` exists to prevent, applied to an audit. + +The corpus is also larger than counted: **964** transcripts via `rglob`, not 811 — a top-level-only +glob sees 209 here and manufactures false zeros. Positive control on the same query: 24,762 `Bash`, +5,275 `Read`, 4,037 `Edit`. + +| Row above | Re-measured | +|---|---| +| `mempalace` "last hit 2026-07-25 (19 days)" | **31 calls, last seen 2026-08-14.** In active use; the gap was a snapshot artifact, not disuse. | +| `codex` "0 skill invocations" | **113 `codex exec` calls across 17 sessions** — the third-heaviest tool in the corpus. The caveat was right; this is the number. | +| `LSP` "0 calls" | Not zero. The handful of calls are from sessions *testing whether the LSP works* — including §5.1's own probes. | +| `gitea` "duplicate, identical values" | Duplicated but **not identical** — the user-scope entry carries `"type": "stdio"`. **Resolved:** the *project* copy was removed, not the user one, because `server-management` and `homelab-docs` have no `.mcp.json` and depend on user scope. | +| *(absent)* `serena` | Enabled; starts and initializes standalone (Serena 1.28.1) but its tools never appear in a session and `ToolSearch` cannot resolve them. Cause unproven → **#799**. | +| *(absent)* six further plugins | Three (`claude-md-management`, `skill-creator`, `frontend-design`) were enabled **on 2026-08-14**, so their zeros mean "not yet tried". The rest are reachable and simply unused. | + +**The issue's framing does not survive the measurement, and that is the finding.** "Retire what is +enabled and never invoked" treats a zero as evidence of uselessness. These zeros split **four** ways: +**broken** (`csharp-lsp` MCP and two LSP servers — #777), **unreachable** (`serena`), **just enabled** +(three plugins), 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 +actually wrong was **duplication** and **breakage**, not excess. The one entry still reading as +coverage it does not provide is `nuget`, which names the same dead `/usr/local/share/dotnet` path +#777 fixed elsewhere; it is inert only because it is explicitly disabled. + **Hooks are the good news.** All 13 scripts in `.claude/hooks/` are wired from either `.claude/settings.json` or `.husky/*`, and no settings entry points at a missing path — there are **no dead hook scripts**, contrary to the issue's suspicion. Husky hooks have genuine fired-output -- 2.47.3