chore(chatarchive): add golangci-lint configuration for chatarchive package

[CodeMonkeyCybersecurity]

Problem

The chat-archive package doesn't have linting wired into the pre-commit or CI pipelines. Issue #84 tracks the broader golangci-lint v2 migration, but the chatarchive package should have lint coverage regardless.

Proposed fix

1. Add golangci-lint run ./pkg/chatarchive/... to the CI script
2. Ensure errcheck linter is enabled (per OWASP A10 / SECURITY.md)
3. Add to pre-commit hook (fast: <2s for a single package)

References

• SECURITY.md §SAST: "gosec and staticcheck must run on every push"
• WORKFLOW.md §CI Pipeline: Stage 1 includes language-specific linter
• Issue fix(lint): update .golangci.yml for golangci-lint v2 (removed gosimple, exportloopref) #84: broader golangci-lint v2 migration

Acceptance criteria

• golangci-lint run ./pkg/chatarchive/... passes clean
• Wired into scripts/chatarchive-ci.sh
• No new lint violations introduced

[CodeMonkeyCybersecurity]

SOAPIER session note (2026-03-20)

Objective assessment

• Reviewed scripts/chatarchive-ci.sh. The script currently runs unit, integration, race, compile, and e2e smoke checks for chatarchive, but it does not invoke golangci-lint for ./pkg/chatarchive/....

Analysis

• This is a clean CI hygiene follow-up and should stay aligned with the broader golangci-lint v2 cleanup tracked in fix(lint): update .golangci.yml for golangci-lint v2 (removed gosimple, exportloopref) #84.

Related

• Sibling follow-ups: fix(lint): update .golangci.yml for golangci-lint v2 (removed gosimple, exportloopref) #84, feat(chatarchive): add --format flag for machine-readable output (JSON) #92, feat(chatarchive): add incremental archive with file modification time tracking #93.