Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

Release Timer›Inbox — on deck·1 in this wave

good-night design check parses only HSL tokens — hex-form token files resolve to zeroTo do

Wave

Inbox — on deck

Briefs Nova has teed up and are ready to run — each task's prompt is a complete, self-contained brief.

Release Timer › Inbox — on deck

0/1 done1 open

Selected taskclear

good-night design check parses only HSL tokens — hex-form token files resolve to zero

To doOwner · met_0fa8be64

Shared-runner gap found during the 2026-07-25 /good-night run. release-timer's first successful nightly produced 136 escalations, 126 of them design findings — all false positives caused by this. Not a release-timer-only bug; filed here because this is where it surfaced.

No dependencies in this wave — nothing gates it, and nothing waits on it.

Show the prompt

You are Piper, the agent for the Release Timer lane of Command.

Open the lane and work there:

```bash
cd ~/Command/release-timer && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://hub.release-timer.com) or ask. Never guess at it.

## The task

**good-night design check parses only HSL tokens — hex-form token files resolve to zero** · to do

Shared-runner gap found during the 2026-07-25 /good-night run. release-timer's first successful nightly produced 136 escalations, 126 of them design findings — all false positives caused by this. Not a release-timer-only bug; filed here because this is where it surfaced.

Where it sits: Release Timer › Inbox — on deck

## The brief on file

In ~/Command/good-night/runner/checks/design.py, `_parse_token_files` matches only `TOKEN_HSL_RE` — CSS custom properties written as `--name: H S% L%;`. Token files that declare colors in HEX form parse to zero tokens.

Consequence: `tokens_by_hex` is empty, so `_build_finding` never sets `exact_token_match`. Per design.py's own docstring, that field is what makes a finding mechanically fixable (swap literal for `hsl(var(--token))`). With it always None, every color literal in every changed file escalates instead of auto-fixing.

Concrete case: release-timer-hub/hub/src/styles.ts IS the web hub's token source — it declares `--bg:#efe7d6; --fg:#24201a; --blue:#4169E1; --sport-velo:#4169E1; --sport-general:#0F4D92;` etc. All hex. On the 2026-07-25 run this produced 126 escalated design findings across release-timer-hub/design-system.html (44), hub/src/styles.ts (31), site/public/index.html (26), hub/src/lanes-view.ts (20), hub/src/config.ts (5).

The fix is a second regex alongside TOKEN_HSL_RE for `--name:#hex;`. Two cautions:

1. Do NOT also parse rgba()-form tokens (styles.ts has `--mute:rgba(36,32,26,.62)`). Mapping them by RGB triple drops alpha, and `--fg:#24201a` already collides with `--mute`'s triple. An alpha-dropping auto-fix would be a real regression.
2. This is shared code — clearsource (apps/web/DESIGN.md) and just-electrolyte (brand/brand-guide.md) also declare token_files. Adding hex parsing may newly populate their palettes and newly enable auto-fix rewrites in those lanes. Check what those two files actually contain before shipping, or the next nightly could start rewriting literals in three lanes at once.

Separately: design.py only understands CSS custom properties, so release-timer's actual iOS non-negotiable — "never hardcode hex colors or pt values in views" (release-timer/CLAUDE.md) — is NOT machine-checked at all. The Swift files in Packages/ReleaseTimerCore/Sources/ReleaseTimerCore/Tokens/ are listed in lane.json's token_files but are inert to this check. Decide whether that gap is worth a Swift token parser.

Also worth deciding: release-timer-hub/design-system.html is the hub's design-system showcase page — color literals there are legitimate by definition. There is currently no exclude mechanism in the design check. An opt-in `exclude_globs` key in checks.design would be additive and change no other lane's behavior.

Context: the crash that hid all of this was fixed in release-timer commit 05a3b7d (lane.json token_files pointed at a directory) and Command commit 53a24b3 (crashed lanes now leave a run-log line).

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

Inbox — on deck

good-night design check parses only HSL tokens — hex-form token files resolve to zero