fix(dashboard): status-text shrinks correctly when sibling text grows

[cnighswonger]

Summary

One-character CSS fix for a status-banner layout regression that surfaces when a provider has both a longer-than-usual heading AND incident detail content (currently visible on the OpenAI tile during the active "Partial System Degradation" incident).

What was broken

On a 1/3-row banner width, the OpenAI tile rendered as:

● OpenAI: Minor disruption — Partial System Degradation
fetched 32s ago
   Partial Disruption of ChatGPT Workspace Connector Write Actions [minor] (identified)

fetched 32s ago was wrapping to its own line between the heading and the incident, instead of sitting beside the heading on line 1.

Root cause

.status-banner .status-text used flex: 1 1 auto, so its initial basis was the natural content width of the heading. When that natural width met or exceeded the available banner width, the flex algorithm gave the entire row to the text and pushed .status-fetched (which has flex-shrink: 0) onto a new flex line.

This was latent for a while but became visible after the recent font-size bump on .status-fetched (0.75rem → 0.88rem) made its rendered width wider — the threshold at which the layout breaks lowered.

Fix

Change .status-text basis from auto to 0. Text starts at 0 width and grows to fill remaining space alongside other items. .status-fetched retains its natural width on the same line; .status-incident still wraps below via its own flex-basis: 100% rule.

-.status-banner .status-text { font-weight: 600; flex: 1 1 auto; min-width: 0; }
+.status-banner .status-text { font-weight: 600; flex: 1 1 0; min-width: 0; }

Why this fix vs reverting the font-size bump

The font-size bump from 0.75rem to 0.88rem was deliberate and improves readability. Reverting it would throw that away. This fix addresses the underlying layout fragility — the banner now tolerates any sibling text width without breaking, so future font-size adjustments won't regress this again.

Verification

• Tested locally against the live OpenAI "Partial System Degradation" incident text on a ~1/3 row width (3-tile dashboard layout).
• Anthropic and Gemini tiles (no incident, short heading) continue to render unchanged — text and fetched on one line, no incident below.
• Behavior matches the layout shown in the dashboard before the font-size bump regression surfaced this latent fragility.

Out of scope

• HTML structure changes (none needed).
• App.js changes (none needed).
• Other status-banner styling (untouched).

[ArkNill]

Fixed in 4d041c2. Just applied the one-char change directly — rebasing this branch against main was going to be messier than it was worth, since the v0.4.0/v0.5.0 composition work overlaps here and #16 (just merged in #17) touched the same file again.

Diagnosis was solid though, that's what made this a 5-minute job. Closing.