[arshcaria]

Summary

Cursor monitoring only read the dashboard /api/usage-summary endpoint, which can describe a stale monthly period with zero usage while Cursor itself shows the current allowance from its application service (see #186 for a side-by-side comparison: summary reported 0% for October 1–November 1, GetCurrentPeriodUsage reported ~7% in an October 19–26 window).

• Prefer GetCurrentPeriodUsage (bearer + empty JSON POST), and fall back to the dashboard summary when the internal endpoint is unavailable or returns no plan usage.
• Parse the application-service response defensively (epoch-millisecond bounds as string or number, percentage fields under planUsage with snake_case aliases, flexible numeric types) and log the response keys when the expected shape is missing.
• Derive the displayed session window from the returned billingCycleStart/billingCycleEnd bounds via a new optional session_label (mirrors weekly_label), so a seven-day window reads 7d instead of the default 5h. Exposed to themes as {provider}.session.label and used in the tray summary.

Closes #186

Testing

• cargo fmt --all -- --check
• cargo test --locked — 568 passed (6 new tests, including the live response shape from Cursor shows 0% and monthly reset while GetCurrentPeriodUsage reports 7% in a weekly window #186: string epoch-millisecond bounds, planUsage percentages, seven-day label derivation, fallback triggers for disabled/empty payloads, and bearer-token extraction from the cookie forms)
• cargo build --locked --release
• Live account verification against the issue reporter's Cursor login is still needed for the undocumented application-service endpoint; the summary fallback remains in place if its shape drifts.

Checklist

• I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md.
• The change is focused and contains no credentials or sensitive data.
• I have added or updated relevant documentation and tests, where applicable.
• I have left changelog and version changes to maintainers unless requested.