Description\n\nThe nilctxpassed linter was added to the registry (linter #49 of 51) and is confirmed production-ready — it uses TypesInfo for type-safe detection, catches real anti-patterns (nil context values passed to functions expecting context.Context), and has zero production violations in the repo today.\n\nHowever, it is not yet in the CI enforce set. Its sibling linters mapdeletecheck and mapclearloop are CI-enforced; nilctxpassed should be added alongside them.\n\n## Suggested Changes\n\n- Add -nilctxpassed to the LINTER_FLAGS variable in .github/workflows/cgo.yml at both the prod gate (:1208) and wasm gate (:1211) lines, next to -mapdeletecheck.\n\n## Files Affected\n\n- .github/workflows/cgo.yml (lines ~1208 and ~1211)\n\n## Success Criteria\n\n- nilctxpassed appears in the CI enforce set alongside -mapdeletecheck\n- make golint-custom passes with no new findings\n- Existing tests continue to pass\n\n## Source\n\nExtracted from Sergo Report #46342 (2026-07-18).\n\n## Priority\n\nHigh — zero-finding linter with confirmed type-safety; enables enforcement with no breaking risk.
🔍 Task mining by Discussion Task Miner - Code Quality Improvement Agent · 75.7 AIC · ⌖ 7.67 AIC · ⊞ 7K · ◷
Description\n\nThe
nilctxpassedlinter was added to the registry (linter #49 of 51) and is confirmed production-ready — it usesTypesInfofor type-safe detection, catches real anti-patterns (nil context values passed to functions expectingcontext.Context), and has zero production violations in the repo today.\n\nHowever, it is not yet in the CI enforce set. Its sibling lintersmapdeletecheckandmapclearloopare CI-enforced;nilctxpassedshould be added alongside them.\n\n## Suggested Changes\n\n- Add-nilctxpassedto theLINTER_FLAGSvariable in.github/workflows/cgo.ymlat both the prod gate (:1208) and wasm gate (:1211) lines, next to-mapdeletecheck.\n\n## Files Affected\n\n-.github/workflows/cgo.yml(lines ~1208 and ~1211)\n\n## Success Criteria\n\n-nilctxpassedappears in the CI enforce set alongside-mapdeletecheck\n-make golint-custompasses with no new findings\n- Existing tests continue to pass\n\n## Source\n\nExtracted from Sergo Report #46342 (2026-07-18).\n\n## Priority\n\nHigh — zero-finding linter with confirmed type-safety; enables enforcement with no breaking risk.