Skip to content

Console: one plain Stop button; SkipCountdown + the override tag retired#370

Merged
ryan-johnson2 merged 1 commit into
develfrom
stop-button
Jul 4, 2026
Merged

Console: one plain Stop button; SkipCountdown + the override tag retired#370
ryan-johnson2 merged 1 commit into
develfrom
stop-button

Conversation

@ryan-johnson2

Copy link
Copy Markdown
Contributor

Per RD field feedback: Stop replaces Force end while Running (same ForceEnd command on the wire), the Armed phase shows only the off-ramps while the countdown runs itself, and the override tag/styling concept is deleted. SkipCountdown remains a valid wire command for scripts — the console just doesn't offer it.

622 rd-console tests green (transitions + screen suites updated), both svelte-checks clean, prettier clean.

🤖 Generated with Claude Code

…om the console

RD feedback from the field: the countdown is seconds long and nobody races it
with a Skip button ('I usually just hit start anyway'), and Force end read as
an alarming override when it is simply how a practice/timed heat ends early.

- Running exposes Stop (the unchanged ForceEnd wire command) + the off-ramps;
  Armed exposes only Abort/Restart while the countdown runs itself.
- The whole 'override' concept goes with it: tag, styling, isOverride() —
  actions are just actions now, styled by primary/destructive as before.
- SkipCountdown stays a valid wire command (scripts/tests); the console simply
  no longer offers it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@ryan-johnson2 ryan-johnson2 merged commit 0ba3323 into devel Jul 4, 2026
3 checks passed
@ryan-johnson2 ryan-johnson2 deleted the stop-button branch July 4, 2026 23:08
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