Skip to content

fix(agent): the working dot breathes orange to gold, never red - #685

Merged
DerekMarshall merged 1 commit into
mainfrom
fix/working-dot-less-red
Oct 15, 2026
Merged

DerekMarshall merged 1 commit into
mainfrom
fix/working-dot-less-red

Conversation

@DerekMarshall

Copy link
Copy Markdown
Member

The working activity dot breathed from pepper red (#E03222), which is redder than the blocked dot's hot red, so an agent that was only busy could look like an error.

It now breathes between the spice-heat ramp's orange (#FF9512) and spark (#FFC436), through a new BREATH_HEAT in src/app/render/chrome.rs. The visual-bell border sweep keeps the full ramp, red included, because it is an alert.

  • An intermediate version started at ember (#F46212, 21°). In testing it still read as red, so the low end moved to orange.
  • New test the_working_breath_never_turns_red holds every frame at a hue of at least 30°. With ember or pepper red restored as the low end, it fails on frame 0.
  • The smoothness, easing and 256-colour tests still pass. FEATURES.md describes the new breath.

make check-ci: === GATE: PASS ===. Tested locally on a release build based on rc.4.

Generated with Claude Code

The working dot breathed from pepper red, redder than the blocked dot's
hot red, so a busy agent could read as an error. It now breathes between
the spice-heat ramp's orange and spark (`BREATH_HEAT`). The visual-bell
border sweep keeps the full ramp: it is an alert, where red belongs.

`the_working_breath_never_turns_red` holds every frame at a hue of at
least 30°; ember (21°) still read as red in testing, and fails it.

Co-Authored-By: Claude <noreply@anthropic.com>
@DerekMarshall
DerekMarshall merged commit 576caab into main Oct 15, 2026
4 checks passed
@DerekMarshall
DerekMarshall deleted the fix/working-dot-less-red branch October 15, 2026 19:49
DerekMarshall added a commit that referenced this pull request Oct 15, 2026
Step 1 of 2 for v2.2.0 (`make release-prep VERSION=2.2.0`):

- `Cargo.toml` / `Cargo.lock`: `2.2.0-rc.4` → `2.2.0`
- `CHANGELOG.md`: the git-cliff section for v2.2.0, covering
`v2.1.1..e87d46e`. Every rc is folded into it, since rcs get no section
of their own.

After this merges: `make release-tag VERSION=2.2.0` on `main`, push the
tag, and watch `release.yml` to the end. Then a follow-up PR sets `main`
to `2.3.0-CURRENT` and archives `V2_2_PLAN.md` and the 2.2 release
notes.

No rc.5: #685 (the working dot's colours) landed after rc.4 and ships
here as is, by the owner's decision.

Generated with [Claude Code](https://claude.com/claude-code)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant