[sergo] Sergo Report: Registry Delta 43→45 + Exact-Type-Param Vein Closeout - 2026-07-13

[github-actions[bot]]

Executive summary

Run R61 on github/gh-aw. The analyzer registry grew 43 → 45 since R60. My prior finding sg60a1 landed as #44187 — verified fixed in code (writebytestring now guards with isExactString). Pre-run reconciliation showed exactly one open sergo issue (#45037). I deep-audited the two newest linters, closed out the exact-type-param assignability vein, and filed 2 focused issues.

Metric	Value
Serena LSP tools	23 (stable)
Registered analyzers	45 (main.go)
Registry delta since R60	+2 (bytescomparestring 44th, stringscountcontains 45th)
Open sergo issues (pre-run)	1 (#45037)
Findings	8
Issues filed	2
Success score	8/10

References: §29224842172

Tool / registry updates

• LSP: 23 Serena tools, unchanged.
• Registry: grep -cE '^\t\t[a-z]+\.Analyzer,' cmd/linters/main.go = 45 (was 43 at R60). Note: bare grep -c Analyzer over-counts — the anchored form is now the canonical detector.
• New since R60: bytescomparestring (44th; premise/import already tracked in bytescomparestring (new 44th linter): the "allocates" premise is inaccurate under gc — string(a) == string(b) does NOT allocate [Content truncated due to length] #44484, Autofix import robustness: sprintfint/writebytestring/bytescomparestring key import-presence on the path but emit a hardcoded pa [Content truncated due to length] #45037) and stringscountcontains (45th; unaudited by any issue → primary new-exploration target this run).
• sg60a1 → writebytestring (new 43rd linter): autofix emits non-compiling io.WriteString(w, s) for named string types + missing RunWithSugg [Content truncated due to length] #44187 (LANDED): writebytestring now has isExactString (:117, :179) — the named-string/io.WriteString non-compiling-autofix bug is fixed in code.

Strategy split (50 / 50)

Cached reuse (proven veins): re-ran the exact-type-param vs Underlying()-match assignability probe (the #44187 class) and the enforce-readiness pattern (accepted precedent: #42644, #42416, #39324).

New exploration: first full audit of the 44th/45th linters (bytescomparestring, stringscountcontains) plus a parity re-check of the sibling stringsindexcontains.

Findings

1. Exact-type-param vein is now CLOSED. Every linter whose autofix calls an exact-typed stdlib API was checked:

Linter	Emitted call	Guard	Verdict
writebytestring	io.WriteString(w, s) (exact string)	isExactString	fixed (#44187)
sprintfint	strconv.Itoa(x) (exact int)	argType != types.Typ[types.Int] (:87)	correct
bytescomparestring	bytes.Equal(a, b) ([]byte)	named→unnamed slice assignable	correct
appendbytestring	append(b, s...) (core-type string)	Underlying() match valid for append	correct

2. stringscountcontains (45th) & stringsindexcontains — audited CLEAN. Both: use astutil.IsPkgSelector (no syntactic stdlib-name match), gate the literal through pass.TypesInfo (constant.Int), reuse the actual selector qualifier (countPkgText/indexPkgText → same-package strings.Contains, adds no import, so the #45037 alias/import class does not apply), are RWSF-verified, and honor nolint + test-skip. Empty-substring semantics are consistent in both directions, and the pattern sets are complete for their {0,1}/{-1,0} threshold families while correctly excluding non-presence forms (Count>1, Index>0).

3. Doc drift (→ issue). doc.go header says "44 active analyzers" and lists 44, but 45 are registered — stringscountcontains is undocumented (recurs #40436).

4. Enforce-readiness (→ issue). stringsindexcontains has 0 production violations (clean/RWSF) → enforce now. stringscountcontains has exactly 1 (pkg/cli/compile_update_check.go:302 — strings.Count(core, ".") >= 1, a genuine strings.Contains simplification) → fix, then enforce.

Generated tasks / issues filed

• doc-sync: pkg/linters/doc.go says "44 active analyzers" but 45 are registered — the list omits stringscountcontains #45185 — doc-sync: bump header to 45, add the stringscountcontains bullet (alphabetical, between stringreplaceminusone and stringsindexcontains), and add a len(registered) == doc-count guard to stop recurrence. Effort: trivial.
• Enforce-readiness: strings-contains-family linters are clean — add stringsindexcontains to CI (0 violations); stringscountcontai [Content truncated due to length] #45186 — enforce-readiness: add -stringsindexcontains to cgo.yml LINTER_FLAGS (default + wasm runs); rewrite compile_update_check.go:302 to strings.Contains(core, ".") then add -stringscountcontains. Effort: small.

Skipped (not duplicated): the bytescomparestring import-alias/allocates concerns are already covered by #45037 and #44484.

Metrics & historical context

• Cumulative: 61 runs, 416 findings, 111 tasks, avg success 8.74.
• Vein status: ctx-family FuncLit-boundary — exhausted (R58); syntactic-stdlib-match — swept (R59, Linter precision (regression): the syntactic stdlib-package-match migration never landed — 5 holdouts remain, 3 CI-enforced (#40 [Content truncated due to length] #43934); exact-type-param assignability — closed this run.
• Reconciliation confirmed the team lands/closes sergo issues fast (only Autofix import robustness: sprintfint/writebytestring/bytescomparestring key import-presence on the path but emit a hardcoded pa [Content truncated due to length] #45037 open pre-run).

Recommendations & next-run focus (R62)

1. Watch for the 46th analyzer via the anchored grep -cE detector.
2. Re-verify sg61a1 / sg61a2 landed.
3. Autofix import robustness: sprintfint/writebytestring/bytescomparestring key import-presence on the path but emit a hardcoded pa [Content truncated due to length] #45037 sibling sweep: audit any other import-adding linter that keys import-presence on path only and hardcodes the default package qualifier (same non-compiling-under-alias class).
4. Continue nolint + test-skip parity checks on newly-registered linters; prefer single-file precision (1–2 issues/run).

Generated by 🤖 Sergo - Serena Go Expert · 369.4 AIC · ⌖ 14 AIC · ⊞ 5.8K · ◷

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

[github-actions[bot]]

Smoke bot tap stone. Me test comment here.

Warning

Firewall blocked 6 domains

The following domains were blocked by the firewall during workflow execution:

• accounts.google.com
• android.clients.google.com
• clients2.google.com
• contentautofill.googleapis.com
• safebrowsingohttpgateway.googleapis.com
• www.google.com

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

network:
  allowed:
    - defaults
    - "accounts.google.com"
    - "android.clients.google.com"
    - "clients2.google.com"
    - "contentautofill.googleapis.com"
    - "safebrowsingohttpgateway.googleapis.com"
    - "www.google.com"

See Network Configuration for more information.

📰 BREAKING: Report filed by Smoke Copilot · 102.3 AIC · ⌖ 5.22 AIC · ⊞ 19.8K · ◷
_{Comment /smoke-copilot to run again
Add label smoke to run again}

[github-actions[bot]]

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

A newer discussion is available at Discussion #45380.