Skip to content

fix(actions): quiet terminal CTA badges + dark tokens; demo single-CTA & persistence - #21

Merged
mayeedwin merged 1 commit into
mainfrom
feat/status-terminal-states-persist
Jul 28, 2026
Merged

fix(actions): quiet terminal CTA badges + dark tokens; demo single-CTA & persistence#21
mayeedwin merged 1 commit into
mainfrom
feat/status-terminal-states-persist

Conversation

@mayeedwin

@mayeedwin mayeedwin commented Jul 28, 2026

Copy link
Copy Markdown
Owner

Renderers (React + Angular parity): terminal statuses (done/failed) are no
longer actionable, so they recede into a quiet, borderless badge — colored glyph

  • label, no fill or outline — instead of a loud filled-green pill that competed
    with live CTAs. Add dark-mode overrides for --conversed-success / --conversed-critical
    (Apple's brighter dark greens/reds) under data-conversed-color-scheme="dark", so
    status colors stay legible on dark surfaces. Hover no longer highlights disabled
    (terminal/pending) buttons.

Demo: the tasks preset now uses a single CTA per row that walks its whole
lifecycle in place (Start → Complete → a quiet Completed badge) rather than
stacking Start + Complete buttons; the stage is derived from the rendered blocks
so it survives a reload. Persist the whole thread (patched blocks, not raw text)
to localStorage so reopening restores every CTA where the user left it.

Docs: document the quiet terminal treatment and the app-owned persistence pattern
in architecture.md.

…A & persistence

Renderers (React + Angular parity): terminal statuses (`done`/`failed`) are no
longer actionable, so they recede into a quiet, borderless badge — colored glyph
+ label, no fill or outline — instead of a loud filled-green pill that competed
with live CTAs. Add dark-mode overrides for --conversed-success / --conversed-critical
(Apple's brighter dark greens/reds) under data-conversed-color-scheme="dark", so
status colors stay legible on dark surfaces. Hover no longer highlights disabled
(terminal/pending) buttons.

Demo: the tasks preset now uses a single CTA per row that walks its whole
lifecycle in place (Start → Complete → a quiet Completed badge) rather than
stacking Start + Complete buttons; the stage is derived from the rendered blocks
so it survives a reload. Persist the whole thread (patched blocks, not raw text)
to localStorage so reopening restores every CTA where the user left it.

Docs: document the quiet terminal treatment and the app-owned persistence pattern
in architecture.md.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@mayeedwin mayeedwin self-assigned this Jul 28, 2026

@mayeedwin mayeedwin left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mayeedwin
mayeedwin merged commit 44ceca3 into main Jul 28, 2026
1 check passed
@mayeedwin
mayeedwin deleted the feat/status-terminal-states-persist branch July 28, 2026 12:24
mayeedwin added a commit that referenced this pull request Jul 29, 2026
Bump all packages 0.0.1-rc.11 → 0.0.1-rc.12 (root, core, react, angular) and
refresh the lockfile. rc.11 is already published to npm; this unblocks the next
publish, which includes the quiet terminal CTA badges + dark-mode status tokens
(#21) and the white terminal label in dark mode (#23).

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
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