OPS-420: Classify connector init error as Warn

[arreyder]

Summary

• Change connector creation error log from l.Error to l.Warn
• Connector init failures are typically config/auth errors (invalid OAuth credentials, bad URL), not server errors

Test plan

• go build ./... passes

🤖 Generated with Claude Code

[linear]

OPS-420 Phase 4: Error classification sweep for containerized connector repos

[github-actions]

Claude finished @arreyder's task in 37s —— View job

---

PR Review

• Gather context and read changed files
• Review PR changes
• Post review feedback

---

Change: pkg/connector/connector.go:182 — l.Error → l.Warn

Verdict: Looks good 👍

This is a clean, well-scoped change. The rationale is sound — connector initialization failures in NewConnector are almost always caused by user-side configuration or authentication issues (invalid OAuth credentials, bad hostname, etc.), not internal server errors. Downgrading from Error to Warn is appropriate because:

1. Error is still propagated — the function still returns the error (return nil, nil, err), so callers handle it properly. The log level change only affects observability classification, not control flow.
2. Reduces noise — in containerized deployments, Error-level logs often trigger alerts. Config/auth failures are expected operational states that operators should investigate, but they aren't bugs or service failures warranting Error severity.
3. Consistent with the OPS-420 initiative — this aligns with the broader error classification sweep across connector repos.

No issues found. No suggestions.