docs(781): re-measure §5.3 from a derived population — the zeros split four ways #800
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user