Expose per-model rate limits (e.g. Sonnet) in statusline rate_limits field

Feature Request

The rate_limits field in the statusline input JSON currently only exposes two windows:

{
  "five_hour": { "used_percentage": 2, "resets_at": 1774137600 },
  "seven_day": { "used_percentage": 1, "resets_at": 1774213200 }
}

On Claude Max subscriptions, there is a separate Sonnet usage limit that is visible in /usage but not exposed in the statusline rate_limits field.

Request

Please add per-model rate limits to the rate_limits statusline data, e.g.:

{
  "five_hour": { "used_percentage": 2, "resets_at": 1774137600 },
  "seven_day": { "used_percentage": 1, "resets_at": 1774213200 },
  "sonnet": { "used_percentage": 15, "resets_at": 1774213200 }
}

This would allow statusline scripts to display Sonnet usage alongside the existing Opus limits, which is useful for Max subscribers who want to monitor both limits without running /usage.

Context

• Added in v2.1.80: rate_limits field for statusline scripts
• The Sonnet limit is already tracked server-side and shown in /usage
• It's just not passed through to the statusline JSON input