[sergo] Sergo Report: Registry Delta 43→55 + Doc-Sync Guard Completeness - 2026-07-22

[github-actions[bot]]

Executive Summary

Run R61 (61st Sergo run; prior R60 was 2026-07-08, 14 days / several missed cadences ago). The linter registry grew +12 (43 → 55 analyzers) in the interim — the largest single-interval delta on record. The team's velocity is exceptional: every one of the +12 new linters is already covered by a closed sergo issue, or was audited clean this run. Zero open sergo issues at start.

One fresh, non-duplicate finding filed: a structural gap in the doc-sync guard suite — the guard added to close #46977 bridged only the code surfaces, leaving the prose docs (doc.go / README.md) in a second, disconnected consistency cluster.

Filed: 1 issue (#47190). Skipped: 0 (no duplicates — the finding is distinct from all prior doc-sync issues, which addressed live count drift rather than the test-topology gap).

Tool & Detector Updates

• Serena LSP tools: 23, STABLE — no tool-set change vs cached snapshot.
• Detector change (important for future runs): the analyzer registry authority moved to pkg/linters/registry.go func All(). cmd/linters/main.go is now a one-liner multichecker.Main(linters.All()...). The historical grep -c 'Analyzer' cmd/linters/main.go new-linter detector is dead; use grep -c '.Analyzer,' pkg/linters/registry.go (= 55) instead.

Strategy (50/50 split)

Cached reuse (proven veins) + New exploration

Cached (50%) — proven bug-pattern lenses applied to new linters:

• Autofix compile-correctness / named-type assignability trap (writebytestring writebytestring (new 43rd linter): autofix emits non-compiling io.WriteString(w, s) for named string types + missing RunWithSugg [Content truncated due to length] #44187, sprintfint sprintfint autofix omits the strconv import and orphans fmt — non-compiling fix for single-use files; the RWSF golden masks it #44864, bytescomparestring).
• Autofix import robustness (Autofix import robustness: sprintfint/writebytestring/bytescomparestring key import-presence on the path but emit a hardcoded pa [Content truncated due to length] #45037, writebytestring autofix references io.WriteString but never adds the "io" import — non-compiling fix when the file doesn't alrea [Content truncated due to length] #44653).
• RunWithSuggestedFixes golden parity (Autofix verification-parity gap: 3 of 9 SuggestedFix linters (stringsindexcontains, sprintfint, stringreplaceminusone) have zero [Content truncated due to length] #43313).
• Doc-sync drift (the single most recurring class: doc-sync: pkg/linters/doc.go says "29 active analyzers" but 30 are registered — list omits hardcodedfilepath and sprintferrdot #40436, doc-sync: pkg/linters/doc.go says "44 active analyzers" but 45 are registered — the list omits stringscountcontains #45185, doc-sync: pkg/linters/doc.go says "45 active analyzers" but 51 are registered — 6 newest linters omitted #46131, doc-sync: pkg/linters/doc.go says "52 active analyzers" but 53 are registered — trimleftright is omitted #46527, doc-sync: pkg/linters/doc.go says "53 active analyzers" but 54 are registered — timenowsub is omitted #46707, doc-sync guards never cross-check the analyzer registry — sprintfbool (55th, registered) is undocumented in doc.go/README/spec_t [Content truncated due to length] #46977).

New exploration (50%) — batch audit of the +12 newly-added linters for the above veins, cross-validated against source + tests.

Success criteria: ≥1 distinct non-duplicate finding; no false positives; every claim source-anchored to file:line.

Findings

New linters audited — all CLEAN / thoughtfully-designed:

Linter	Verdict	Evidence
appendoneelement	Clean	Uses RunWithSuggestedFixes (golden). Spread form append(s, []T{x}...) requires T identical to s's element type, so the → append(s, x) rewrite is type-safe. Guards nested untyped composite lits (.go:115) and key-value elems.
bytesbufferstring	Clean	Deliberately excludes *bytes.Buffer (.go:126-134) because string(buf.Bytes()) panics on a nil pointer while buf.String() returns "<nil>" — non-semantics-preserving. Only matches value receivers.
ioutildeprecated	Advisory-only	No SuggestedFix; ioutil.ReadDir → os.ReadDir type-change is a recommendation, not an autofix, so no non-compiling output. Low value.
sprintfbool	Exemplary	Adds strconv import, removes orphaned fmt, handles shadowing/dot-import/comment-overlap, and gates on exact types.Typ[types.Bool] (.go:112) — correctly avoiding the writebytestring named-type non-compiling trap.

Filed finding — #47190 (doc-sync guard incomplete):

The doc-sync test suite enforces two disjoint components with no bridge between them:

• Cluster A (code): linters.All() = documentedAnalyzers() — via TestRegistryMatchesDocumentation (spec_test.go:249, added to close doc-sync guards never cross-check the analyzer registry — sprintfbool (55th, registered) is undocumented in doc.go/README/spec_t [Content truncated due to length] #46977).
• Cluster B (prose): doc.go bullets = README.md table — via TestDocGo_AnalyzersMatchREADME (doc_sync_test.go:54).

No test compares A against B. A linter added to registry.go + documentedAnalyzers() but omitted from doc.go + README.md passes all tests (56==56 and 55==55). Additionally, TestRegistryMatchesDocumentation compares d.analyzer.Name, never d.label, so the README-derived label strings are validated against nothing. Fix: assert the already-parsed doc.go/README slug sets equal linters.All() names, collapsing the two clusters into one total invariant.

Generated Task

1. Complete the doc-sync invariant — add a single test bridging code↔prose surfaces (reuse existing docBulletRe/readmeTableRe parsers vs linters.All(); add label validation). Small, test-only, no production change. → #47190

Metrics

Metric	Value
Registry delta	43 → 55 (+12)
New linters audited clean	4 deep + 8 team-covered
Findings	8
Issues filed	1 (#47190)
Duplicates skipped	0
Open sergo issues (pre-run)	0
Success score	8 / 10

Historical Context

60 prior runs · 416 cumulative findings · avg success 8.74. Doc-sync is the most-reinforced guard (6 prior fixes) — this run extends that lineage by finding the structural gap the count-based fixes left open. The named-type autofix vein (writebytestring R60) is now demonstrably closed in newer linters (sprintfbool gets it right).

Recommendations & Next-Run Focus (R62)

• Watch for the 56th linter via grep -c '.Analyzer,' pkg/linters/registry.go.
• Re-verify #47190 landed.
• Probe any new autofix linter for named-type/import-emission bugs (proven vein).
• Consider enforce-readiness issues for appendoneelement / bytesbufferstring (both clean) once 0 production violations are confirmed.

References:

• §29891960163

Generated by 🤖 Sergo - Serena Go Expert · age00 304.1 AIC · ⌖ 13.7 AIC · ⊞ 5.7K · ◷

• expires on Jul 22, 2026, 9:00 PM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by Sergo - Serena Go Expert.

A newer discussion is available at Discussion #47468.