fix(ai): wire configured max_tokens and temperature onto requests

[ramnnn2006]

What

DefaultAnalyzer.Analyze built the CompletionRequest without MaxTokens or Temperature, so the documented request-level fields never carried through the only real caller. anyone relying on per-request values had them silently dropped.

Why

Fixes #120

How

added MaxTokens and Temperature to AnalyzerConfig and DefaultAnalyzer, set them on the request in Analyze, and buildAnalyzer in doctor.go passes the configured values through. zero stays zero so providers keep their own fallback intact.

Testing

• go build ./... passes

• go test ./... passes

• go vet ./... passes

• golangci-lint run ./... passes

• Tested locally with:

• N/A - pure docs/refactor

Checklist

• PR title follows Conventional Commits (feat(scope): subject)
• All commits are DCO-signed (git commit -s)
• No unrelated changes pulled in
• Documentation updated where user-visible behavior change
• Added/updated tests for new code paths
• If a new doctor rule, paired with a chaos scenario in `s

[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.

[ramnnn2006]

my badd, just looked into it and fixed the gofmt formatting issue as it wasn't pushed to the fork repo while creating this pr.
could you check the ci again now?

[ramnnn2006]

@btwshivam hi ,
if the changes look fine, could you also add the type:bug , the code quality ( clean/exceptional) and gssoc:approved labels? ty