[lint-monster] LintMonster: handle ignored errors and discarded results #67326

Daily custom lint findings

make golint-custom reported 951 findings in this group:

• 785 ignored I/O or cleanup errors, including unchecked fmt write errors, Scanner.Err() omissions, and discarded Close() errors.
• 166 discarded results or reused-buffer findings, including blank-identifier assignments, discarded type-assertion ok values, and builders reused without Reset().

The findings span pkg/workflow/, pkg/cli/, pkg/parser/, pkg/console/, and other packages. High-volume examples include pkg/workflow/drive_memory.go (78), pkg/workflow/cache_memory.go (64), and pkg/workflow/repo_memory.go (52). Scanner diagnostics include pkg/parser/frontmatter_content.go:260 and pkg/parser/include_expander.go:167.

Remediation

• Work only on findings in these categories from this lint run.
• Propagate or handle write, scan, and close errors using each caller's existing error-reporting conventions.
• Inspect blank assignments and type assertions; preserve intentional behavior while checking or safely omitting only values that are truly unnecessary.
• Reset or reinitialize reused builders between independent writes where required.
• Keep edits minimal and scoped. If an analyzer itself needs a narrow correction, add or update focused analysistest coverage rather than suppressing the rule broadly.
• Run make fmt after Go edits, then validate with make golint-custom.

Expected outcome: eliminate these ignored-result and resource-handling diagnostics without hiding failures or changing successful output behavior.

Generated by 🧌 LintMonster · codex · gpt60 · 189.5 AIC · ⌖ 29.5 AIC · ⊞ 15.5K · ◷

• expires on Oct 16, 2026, 6:56 PM UTC-08:00