fix(model): redact provider error responses

[XnLemon]

Objective

Redact sensitive provider error details before they are emitted through model response error events.

Completed Changes

• Redacted ResponseError.Message in Anthropic, Bedrock, Hunyuan, and Ollama provider sendErrorResponse paths.
• Preserved existing error type, completion state, and Ollama response ID semantics.
• Added targeted regression coverage for Authorization bearer tokens, API keys, generic token/secret/password fields, and cookies.
• Fail closed with a generic message if redactor initialization is unavailable.

Validation

• go test ./model/hunyuan
• go vet ./model/hunyuan
• cd model/anthropic && go test ./... && go vet ./...
• cd model/bedrock && go test ./... && go vet ./...
• cd model/ollama && go test ./... && go vet ./...
• git diff --check
• Sub-agent open-code-review pass: 0 High / 0 Medium / 0 Low. OCR CLI config was unavailable, so the sub-agent performed read-only review following the skill flow.

Known Risks / Limitations

• Scoped to direct provider sendErrorResponse paths in Anthropic, Bedrock, Hunyuan, and Ollama.
• Windows Git reported LF-to-CRLF working-copy warnings only; git diff --check passed.

Follow-up Work

• Continue Phase2 closure by sweeping remaining provider and graph/runtime error event paths for model-visible raw error messages.

[coderabbitai]

Warning

Review limit reached

@XnLemon, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 17 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: f669f7e1-0f1d-4f3c-ac5a-43b3642b63c9

📥 Commits

Reviewing files that changed from the base of the PR and between 361e2a4 and c59379b.

📒 Files selected for processing (8)

• model/anthropic/anthropic.go
• model/anthropic/anthropic_test.go
• model/bedrock/bedrock.go
• model/bedrock/bedrock_test.go
• model/hunyuan/hunyuan.go
• model/hunyuan/hunyuan_test.go
• model/ollama/ollama.go
• model/ollama/ollama_test.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/phase2-model-provider-error-redaction

---

_{Comment @coderabbitai help to get the list of available commands.}