[Code Quality] Sync doc.go analyzer count with actual registry count (44 documented vs 48 registered)

[github-actions]

Description

The custom analyzer registry has grown to 48 analyzers but the doc.go header still says "44 active analyzers". This stale count is misleading for contributors reading the documentation. While low-priority in isolation, this drift tends to compound (already drifted by 4 in one cycle) and will cause confusion when reviewing or onboarding.

Additionally, the new logfatallibrary analyzer is a strict subset of the already-CI-enforced rawloginlib. Both target the same Fatal/Fatalf/Fatalln functions from log package in the same file paths. This causes:

• Zero added lint coverage
• Double-reporting if both are enforced
• Dual //nolint directives needed at every site

See issue #45379 for the partitioning fix. This issue tracks the doc.go count update as a prerequisite cleanup.

Suggested Changes

1. Update doc.go analyzer count from 44 → 48 (current registry count)
2. After resolving logfatallibrary duplicates the already-CI-enforced rawloginlib — its entire detection surface (log.Fatal/Fatalf/Fatalln in libra [Content truncated due to length] #45379 (logfatallibrary/rawloginlib partition), re-sync the count
3. Consider adding a CI check: grep -c Analyzer cmd/linters/main.go should equal the documented count in doc.go

Files Affected

• cmd/linters/doc.go (or equivalent header file documenting the analyzer count)
• cmd/linters/main.go (reference count source)

Success Criteria

• doc.go count matches grep -c Analyzer cmd/linters/main.go
• Ideally a CI lint rule enforces this parity going forward

Source

Extracted from Sergo Report: DELTA-43to48 New-Linter Audit — 2026-07-14

Priority

Low — documentation drift, no functional impact

🔍 Task mining by Discussion Task Miner - Code Quality Improvement Agent · 151.8 AIC · ⌖ 7.62 AIC · ⊞ 7K · ◷

• expires on Jul 15, 2026, 5:20 AM UTC-08:00