Statusline Simulation — All Scenarios

1. Extra Usage Active (5h=102%, 7d=87%)

launcher-v2 Opus ■■ 85% $3.87
⎇ feature/extra-usage ~ 100 4:30pm ▰▰▰▰87% Thu 9:15am ⚡ $12.47/$50
5h over limit → amber spend/limit shown. 7d shows reset day+time.

2. Approaching Limit, Extra Enabled (5h=97%, 7d=91%)

launcher-v2 Opus ■■ 85% $3.87
⎇ feature/extra-usage ~ 97% 5:15pm 91% Thu 9:15am ⚡ Extra
Both bars show %. Dim "Extra" = enabled but not yet consuming.

3. Approaching Limit, No Extra (5h=98%, 7d=72%)

launcher-v2 Opus ■■ 85% $3.87
⎇ feature/extra-usage ~ 98% 5:15pm ▰▰▰ ⚡ No extra
5h at 98% with %. 7d at 72% (no %). Dimmer "No extra" warning.

4. Normal Usage (5h=35%, 7d=52%)

launcher-v2 Opus ■■ 85% $3.87
⎇ feature/extra-usage ~ ▱▱▱ ▰▰▱▱
Both bars under 80% — no %, no reset times, no extra usage indicator.

5. First Render of New Session (5h=45%, 7d=60%)

launcher-v2 Opus □□□ 0%
⎇ master ▰▰45%▱▱ ▰▰▰60%
First render shows % overlay on both bars regardless of threshold.

6. Nested Git — CWD Has Repo, Project Root Doesn't (5h=35%, 7d=52%)

CodeMaestro:code-maestro-ue Opus 4.6 ■■ 82%
⎇ main ~ ▱▱▱ ▰▰▱▱
Project root has no git, but CWD (code-maestro-ue) has its own repo. Dim "↳" prefix signals nested/child repo.

7. With Update Available (per-session cached)

launcher-v2 Opus 35% $0.52 ↑ 2.1.39 → 2.2.0
⎇ master ▱▱▱ ▰▰▱▱
Amber update arrow on line 1 when npm has newer version. Cache is per-session (keyed by session_id) and refreshed hourly — parallel sessions on different CLI versions each see their own correct state.