docs(781): re-measure §5.3 from a derived population — the zeros split four ways #800
1
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
0874927cfc |
docs(781): re-measure §5.3 from a DERIVED population — the zeros split four ways
PR Gates / CI image pin matches docker/ci (pull_request) Successful in 38s
Build ErsatzTV Image / Delimiter ban (release path) (pull_request) Successful in 44s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Successful in 49s
PR Gates / Docs update reminder (pull_request) Successful in 47s
PR Gates / decisions lifecycle (pull_request) Successful in 1m1s
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (pull_request) Successful in 13s
review-verdict/h10 Exempt: docs-only change (no code, no protected path)
Review verdict / Set review-verdict status (pull_request_target) Successful in 18s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Successful in 8s
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Successful in 5s
Build ErsatzTV Image / Build & test (.NET) (pull_request) Successful in 9s
Build ErsatzTV Image / Build & push image (amd64) (pull_request) Skipped
PR Gates / Script tests (pytest) (pull_request) Successful in 2m55s
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> |