[sergo] Sergo Report: Gap-Recovery Reconcile + Registry Delta (43→67) + Comment-Guard Audit - 2026-09-02

[github-actions[bot]]

Overview

R61 (gap-recovery run). The memory branch's sergo-strategies.jsonl/sergo-stats.json were frozen at R60 (2026-07-08) despite roughly two months of continued daily runs — GitHub issues remained the durable source of truth throughout. This run reconciled prior open findings, detected a silent registry-tracking heuristic drift, and completed a fresh audit. Strategy: 50% cached (reconcile 5 open sergo issues via direct code read) / 50% new exploration (8 never-audited linters).

11 findings, 1 issue filed, success score 9/10.

Tool & registry updates

• Serena LSP: 23 tools, stable, no change.
• Registry tracking moved: analyzers are no longer listed in cmd/linters/main.go (it now just calls linters.All()); the canonical list is pkg/linters/registry.go:84-151 (allAnalyzers). The old detector (grep -c Analyzer cmd/linters/main.go) is now silently wrong and must be retired.
• Delta since last real snapshot: 43 → 67 analyzers (+24). pkg/linters/doc.go:3 ("67 active analyzers") is in sync — no doc drift this run.
• CI enforcement: .github/workflows/cgo.yml — 56 of 67 linters enforced natively (line 1460); the wasm build's flag list (line 1463) can silently drift from native (confirmed still true for contextcancelnotdeferred, see contextcancelnotdeferred is enforced on native CI but absent from wasm LINTER_FLAGS - the registry-drift guard cannot detect it #55932 below).

Findings

50% cached — reconciliation of 5 previously-open sergo issues (all still present)

Issue	Linter	Gap (re-confirmed by direct code read)
#57606	generatedyamlheredoc	Quoted-string false heredoc detection
#57340	stringsconcatloop	Map-index/selector ASSIGN-form miss (selfReferentialConcatLHS requires bare *ast.Ident LHS)
#57339	sprintferrdot	Only %s/%v treated as redundant; %q/%x/%X missed
#56533	errorfwrapv	*ast.BasicLit-only format check skips concatenated format strings
#55932	contextcancelnotdeferred	cgo.yml:1460 (native) carries the flag, :1463 (wasm) omits it — self-verified again this run

None auto-closed; all confirmed still unfixed by reading current source, not just issue state.

50% new — fresh audit of 8 never-before-audited linters

Clean (type-resolved, no bare-ident pkg-match, no FuncLit-boundary issues): fmterrorfnoverbs, ioutildeprecated, sprintfbool, mapdeletecheck.

New finding — filed as issue, temp id aw_sg61a1: 5 linters (appendoneelement, timenowsub, stringsjoinone, stringscountcontains, stringsindexcontains) emit analysis.SuggestedFix TextEdits that unconditionally replace the whole matched expression via astutil.NodeText/astutil.BuildContainsFix — neither checks astutil.HasOverlappingComment first, so -fix silently deletes any comment inside the replaced span. The guard already exists and is wired up correctly in 3 sibling linters (sprintfbool, mapdeletecheck, mapclearloop); this run traced the root cause to one shared helper (astutil.go:660-676, BuildContainsFix) plus 3 direct call sites. All 5 affected linters are CI-enforced on production code. Concrete before/after code examples and a recommended 3-step fix are in the filed issue body.

Generated tasks / issues

• 1 issue filed: aw_sg61a1 — comment-deletion via unguarded SuggestedFix (5 linters + 1 shared helper).
• No duplicate issues filed — all 5 reconciled issues were already open and still valid.

Metrics

Metric	Value
Findings	11
Tasks/issues created	1
Success score	9/10
Open sergo issues after this run	6 (5 reconciled + 1 new)
Registry size	67 (was 43 at last real snapshot)

Historical context

The strategy/stats memory files had not been updated since R60 (2026-07-08) even though work clearly continued (issues filed through 2026-09-01, registry grew 43→67). This gap has been recorded in memory (sergo-stats.json.memory_gap_R61) so future runs don't mistake total_runs/total_findings for true lifetime totals — GitHub issue history, not the memory branch, is the authoritative record for that period.

Recommendations

1. Land aw_sg61a1's fix in astutil.BuildContainsFix first — it fixes 2 of the 5 affected linters from one place.
2. Add the same HasOverlappingComment guard directly to appendoneelement.go, timenowsub.go, stringsjoinone.go.
3. Add comment-overlap golden testdata to all 5, since RunWithSuggestedFixes currently never exercises this path for any of them.

Next-run focus (R62 candidates)

• Re-verify aw_sg61a1 landed, and re-check all 5 reconciled issues for movement.
• Sweep the remaining ~16 of 24 SuggestedFix-emitting linters (only 3/24 currently wire the comment guard) for the same gap.
• Watch for a 68th linter via pkg/linters/registry.go's allAnalyzers count vs. doc.go's header — this is now the canonical drift detector, not cmd/linters/main.go.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• api.anthropic.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.anthropic.com"

See Network Configuration for more information.

Generated by 🤖 Sergo - Serena Go Expert · claude · agent · 580.9 AIC · ⌖ 12 AIC · ⊞ 6.8K · ◷

• expires on Sep 2, 2026, 8:10 PM UTC-08:00