fix(claude): keep hot status line readings on a dark pill - #25
Merged
Merged
Conversation
Once context or a rate limit crossed 80 or 90 percent, the status line painted that reading on a solid warning yellow or danger red box inside the ramp's brightest segment. With the five-hour and seven-day limits both running hot the right third of the line turned yellow and salmon, which is the opposite of the palette's mood. Hot readings now sit on a dark pill: the alert hue blended a quarter of the way into the page background, with the alert colour itself as text. The prompt ramp exposes warning_surface, danger_surface, warning_text and danger_text for every variant. The text is lifted toward the ramp's brightest foreground only as far as WCAG AA needs, since the reds do not clear 4.5:1 on their own dark surface unaided. The starship keys warning, danger and foreground_warning are untouched. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RpxCFKCCDdhy1DQLdBjGQv
β¦iant The pill text is lifted toward the ramp's brightest foreground only as far as it needs, and nothing stopped a future palette change from landing a pill under 4.5:1 or on the bright side of the page. The spec now checks both for the warning and danger pills of all five variants. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RpxCFKCCDdhy1DQLdBjGQv
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
π What broke
Once the context reading or a rate limit crossed 80 or 90 percent, the Claude Code status line painted that reading on a solid warning yellow or danger red box, sitting inside the ramp's brightest pink segment. With the five-hour and seven-day limits both running hot, the right third of the line turned yellow and salmon. A dark neon theme has no business going peach.
π Why
pill()in the generated script used the ramp'swarninganddangercolours directly as backgrounds, with the page background as text. Those two colours are the palette's alert accents, tuned to read as text or thin markers on a dark page, not to fill a run of cells. Three of them side by side on hot pink swamped the whole segment.π οΈ The fix
Hot readings now sit on a dark pill. The prompt ramp gains four keys per variant:
warning_surfaceanddanger_surface: the alert hue blended a quarter of the way into the page background, so the pill reads as a tinted dark hole rather than a bright block.warning_textanddanger_text: the alert colour itself, lifted toward the ramp's brightest foreground only as far as WCAG AA needs. The yellows already clear 4.5:1 on their surface, but the reds land near 4:1 unlit, soreadable()binary-searches the smallest lift that gets them over the line.The template swaps its three alert variables for these four, and the five scripts under
extras/claude/are rebuilt. The Starship generator still readswarning,dangerandforeground_warning, which are unchanged, and its TOML output is byte-identical.β Verification
make checkgreen: 106 tests, lint and format clean.π€ Generated with Claude Code
https://claude.ai/code/session_01RpxCFKCCDdhy1DQLdBjGQv