Fast mode status bar indicator should reflect actual state, not just setting

Problem

When fast mode is toggled on but hits its rate limit, the status bar still shows the ↯ fast mode indicator as active. Meanwhile, a separate notification appears saying fast mode isn't enabled. This creates a confusing discrepancy — the status bar says it's on, but it's not actually being used.

Expected Behavior

The ↯ indicator in the status bar should reflect the effective state of fast mode, not just whether the setting is toggled on. When fast mode falls back to standard speed due to rate limiting, the indicator should either:

• Be hidden/removed until fast mode is actually active again
• Be visually distinguished (e.g., grayed out) to indicate cooldown
• Include a brief label like ↯ (cooldown) to communicate the state

Current Behavior

• Status bar shows ↯ as long as the fast mode setting is on, regardless of whether responses are actually using fast mode
• A separate notification informs the user that fast mode is not enabled
• These two signals contradict each other

Why It Matters

Users rely on the status bar as a quick glance indicator. If it shows fast mode as active when it's actually rate-limited, users may not realize they're getting standard-speed responses and may not understand why performance changed.