fix(ai): default analyzer logger to discard when cfg.Logger is nil

[HarshParmar029]

Fixes #126

Problem

NewAnalyzer did not handle cfg.Logger == nil, causing a nil-pointer
panic on any logging call (e.g. a.logger.Debug(...)).

Fix

Added a nil check in NewAnalyzer. When cfg.Logger is nil, it defaults
to slog.New(slog.NewTextHandler(io.Discard, nil)) — a no-op logger that
produces no output but never panics.

Testing

• Existing tests pass
• Added test case for nil logger initialization

[github-actions]

🚀 First PR — welcome aboard!

A few things to expect:

1. CI: every PR runs build + race tests + lint + (eventually) the kernel matrix. If something fails, the log will tell you exactly which gate.
2. DCO: every commit needs Signed-off-by: — git commit -s adds it automatically.
3. Conventional Commits: PR titles like feat(doctor): add new rule or fix(bpf): handle X. We squash-merge by default.
4. Review: a maintainer will review within 72 hours. Suggestions are conversations, not orders — push back if something doesn't fit your context.

If you get stuck, reply here or jump to Discussions. We want this PR to land.

[HarshParmar029]

Hi @btwshivam

All CI checks are now passing — including Lint, Build, Test, and Docker.

This PR fixes the nil-pointer panic in NewAnalyzer when cfg.Logger is nil, by defaulting to a no-op slog logger backed by io.Discard.

Would appreciate a review when you get a chance. Happy to make any changes if needed!

[HarshParmar029]

Hi @btwshivam,

Just a gentle follow-up — all CI checks are green, and this fixes the nil logger panic in NewAnalyzer (ref #126).

Happy to address any feedback or make changes. Thanks for your time!

[btwshivam]

same fix as #162, which also ships a regression test, so we're going with that one. please close this in its favor. thanks for jumping on it.

[btwshivam]

/close