[log] Add debug logging to rate_limit.go

[github-actions]

Adds meaningful logCircuitBreaker debug calls to the functions in internal/server/rate_limit.go that previously had no logging coverage.

Changes

• extractRateLimitErrorText: logs when the result is not a map (unexpected input), when scanning content items (with count), and when the fallback default message is used
• isRateLimitToolResult: logs the number of content items being inspected when an error result is encountered
• parseRateLimitResetFromText: logs when the "rate reset in Ns" pattern is absent from the error text

All new log calls use the existing logCircuitBreaker logger (declared in circuit_breaker.go, same package) — no new logger declaration needed.

Quality checklist

• Exactly 1 file modified
• No test files modified
• Reuses existing logCircuitBreaker logger (no duplicate declaration)
• Logger naming follows pkg:filename convention (existing: server:circuit_breaker)
• Log arguments have no side effects
• Log messages are meaningful for debugging rate-limit behaviour
• No duplicate logging with existing calls
• go build passes
• go test ./... passes
• go vet ./... passes

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• index.crates.io

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "index.crates.io"

See Network Configuration for more information.

Generated by Go Logger Enhancement · sonnet46 4.7M · ◷

[Copilot]

Pull request overview

This PR improves observability of the server-side rate limit detection flow by adding additional logCircuitBreaker debug logging in internal/server/rate_limit.go, helping diagnose unexpected tool result shapes and why reset timestamps aren’t being inferred.

Changes:

• Add debug logging when extractRateLimitErrorText receives an unexpected (non-map) result and when it falls back to the default message.
• Add debug logging showing how many content items are scanned in extractRateLimitErrorText / isRateLimitToolResult.
• Add debug logging when parseRateLimitResetFromText does not find the "rate reset in " pattern.

Show a summary per file

File	Description
internal/server/rate_limit.go	Adds debug log lines around error-text extraction, rate-limit tool-result inspection, and reset-time parsing fallback paths.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0