Skip to content

style(rail): at-rest chevron on the pending-but-clickable pulse chip - #94

Merged
kateebonner merged 2 commits into
local/amicodefrom
kate/rail-pulse-chip-affordance
Jul 28, 2026
Merged

style(rail): at-rest chevron on the pending-but-clickable pulse chip#94
kateebonner merged 2 commits into
local/amicodefrom
kate/rail-pulse-chip-affordance

Conversation

@kateebonner

Copy link
Copy Markdown
Contributor

What

The pending pulse chip (clickable since 766e201 — it opens the Run Inspector before a pulse is banked) now carries an always-visible trailing chevron so it reads clickable at rest, not just on hover.

Why

The dotted border is the rail's grammar for "inert placeholder" — every other pending chip really is dead. The pulse chip broke that grammar semantically (live button) without breaking it visually: its only at-rest distinction was ink strength (f9d20e7), and cursor/hover feedback only reveals once you're already on it. Kate hit exactly this today: "doesn't appear clickable when it is in fact clickable."

How

  • entity-rail.tsx: trailing (aria-hidden; the button keeps its existing aria-label/tooltip) rendered only on the pending-but-clickable chip — recorded chips keep their solid-pill affordance unchanged.
  • amicode.css: chevron in neutral muted ink (--v2-text-text-muted), bumping to base on hover and focus-visible; --font-size-md, 0.16s ease — same glyph family as the receipt card's chevron but never hover-gated here. No yellow (no accent-foreground-on-light), tokens only, both themes covered by the v2 ink tokens. Dotted border still carries the not-yet-banked state.
  • Retired the stale comment claiming recorded chips carry a soft-yellow fill (removed 2026-07-24 in 8aa3d74).

Verification

  • npm run lint: 0 errors
  • tsgo -b in packages/app: clean
  • No unit/e2e tests reference the rail chip markup; data-slot hooks unchanged

@Rchari1 — this rides on top of your two pulse-chip commits from today rather than reverting them; the inspector handoff behavior is untouched.

🤖 Generated with Claude Code

@kateebonner
kateebonner requested a review from Rchari1 July 28, 2026 22:26
The pulse chip opens the Run Inspector while still un-banked (766e201),
but it kept the dotted border — the exact grammar every OTHER pending chip
uses to mean inert — so its clickability was only discoverable on hover.
Add an always-visible trailing chevron (neutral muted ink, bumps to base on
hover/focus) so the shape signals the action at rest; the dotted border
still tells the truth about not-yet-banked state. Also retire the stale
comment claiming the recorded chips' soft-yellow fill (removed 2026-07-24).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@jack-champagne
jack-champagne force-pushed the kate/rail-pulse-chip-affordance branch from f6cd52c to 59321d1 Compare July 28, 2026 22:52
…ne inspector entry

The chip and the button opened the same panel from the same row; with the
chip now carrying an at-rest affordance, the button was redundant chrome
(Kate 2026-07-28). Comments referencing the button updated to name the
pulse chip as the rail's inspector entry.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@kateebonner

Copy link
Copy Markdown
Contributor Author

Scope addition per Kate's review in the live loop: the rail's standalone Inspect Run button is removed (2f7c9e1) — with the pulse chip carrying an at-rest affordance it was redundant chrome opening the same panel from the same row. The pulse chip is now the rail's single inspector entry; stale comments referencing the button updated. Note the branch was rebased onto the refreshed local/amicode base (the force-update earlier today), so the PR is two commits: chevron + button removal.

@kateebonner
kateebonner merged commit 54accef into local/amicode Jul 28, 2026
1 of 4 checks passed
@kateebonner
kateebonner deleted the kate/rail-pulse-chip-affordance branch July 28, 2026 23:58
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