Feature: Add CI Workflow for Build/Test/Lint

[Jaydeep869]

Description

Add a CI workflow so pull requests are automatically validated with build, test, and lint checks.

Motivation

Without CI, simple regressions (formatting, lint, compile errors, missing resource cleanup) can land undetected. Automated checks improve code quality and review confidence.

Proposed Solution

Create .github/workflows/ci.yml that:

• Uses actions/setup-go.
• Runs go build ./....
• Runs go test ./....
• Runs golangci-lint.
• Triggers on pull requests and pushes to the default branch.

Alternatives Considered

• Only run tests and build (no lint): faster, but lower static quality checks.
• Local only checks via contributor machines: inconsistent and easy to skip.

Additional Context

• Area: .github/workflows/ (new directory) and .github/workflows/ci.yml (new file)
• This directly helps catch issues like deferred close omissions and style/format defects earlier.

[Jaydeep869]

PR #46 appears to cover the current scope written in this issue: Go setup, build, test, lint, and PR/default-branch triggers.

I think we should keep this issue scoped as the initial CI workflow so the current PR can be reviewed against a stable target.

If we want broader CI after that, I’d suggest a separate follow up issue for CI hardening/enhancements, for example:

• pinning action/tool versions for reproducibility
• confirming PR workflow execution in the upstream repo
• adding extra checks like coverage, type-check, spec/docs verification if maintainers want those in CI
• refining job structure or matrix coverage beyond the initial workflow

That way we avoid changing the acceptance bar mid review while still tracking the stronger CI direction.