Issue #27: hero console mock matches the real dashboard #35

Merged
gotoi-agent merged 2 commits from issue/27-hero-console-mock into agent-develop 2026-10-06 18:36:02 +02:00
Collaborator

Rebuilds the marketing hero console from the dashboard's own shell, page chrome, and feed markup.

  • dc67390: StatusPill stale-mark fix + port .card/.list-row/.page-title/.surface-sidebar/.count-badge CSS from dashboard app.css.
  • 0c7c43f: ConsoleWindow rebuild (441+/241-).

Gates: check-ai-headers 0; docs/use-cases/_check 0; type-mirror 0; marketing check 0/0; marketing build 0; marketing test 13/13; gofmt clean. agent go test: 6 pre-existing sandbox failures (also on clean develop), not from this diff.

Refs #27

Rebuilds the marketing hero console from the dashboard's own shell, page chrome, and feed markup. - dc67390: StatusPill stale-mark fix + port .card/.list-row/.page-title/.surface-sidebar/.count-badge CSS from dashboard app.css. - 0c7c43f: ConsoleWindow rebuild (441+/241-). Gates: check-ai-headers 0; docs/use-cases/_check 0; type-mirror 0; marketing check 0/0; marketing build 0; marketing test 13/13; gofmt clean. agent go test: 6 pre-existing sandbox failures (also on clean develop), not from this diff. Refs #27
The hero StatusPill gave stale/suppressed rows a green mark where the dashboard
pill (dashboard/src/lib/components/StatusPill.svelte) uses bg-warning. The
components layer now also carries .surface-sidebar, .card, .list-row,
.page-title, and .count-badge copied verbatim from dashboard/src/app.css so the
mock styles its shell from the product's own rules.

Refs #27
marketing: rebuild the hero console from the dashboard's own shell, page chrome, and feed markup
All checks were successful
agent-guards / test-tampering (pull_request) Successful in 36s
CI and agent release / check-docs (pull_request) Successful in 24s
CI and agent release / test-agent (pull_request) Successful in 1m30s
CI and agent release / test-dashboard (pull_request) Successful in 2m51s
CI and agent release / test-middleware (pull_request) Successful in 8m44s
CI and agent release / build (pull_request) Has been skipped
CI and agent release / release (pull_request) Has been skipped
CI and agent release / publish-images (pull_request) Has been skipped
0c7c43fc5b
The hero stage used to hand-draw a lookalike of the console; that drifted
from the shipped dashboard (window chrome, submenu state, no facets card,
no sortable sticky header, no checkbox column, no pager, no ExecutionPeek
shape, wrong pill mark for stale/suppressed rows). The new ConsoleWindow
imports the dashboard's installed primitives by porting markup and class
names (since the two apps cannot share components across separate  and
icon graphs):

  - Shell, Sidebar, and SubmenuSection aspa shell pieces (rail, submenu
    rows with chevron + badge + ring active state, floating surface-sidebar)
  - Page + PageHeader with crumbs and .page-title typography
  - FeedLayout + FacetPanel + FeedTable for the Executions feed
  - ui/split-list compound (pane, list-row, item-text, detail) for
    Plans/Rules/Sources/Machines/Agents/Groups
  - routes/settings/kill page chrome for the kill pane
  - dashboard/src/app.css .card, .list-reset/.list-row, .surface-sidebar,
    .page-title, .count-badge rules (companion commit)
  - StatusPill stale/suppressed mark colour matches the dashboard pill

Visibility of the sidebar, the facets card, and individual table columns
is driven by Tailwind v4 container queries on the stage, so the feed
shows the facets + table the way the dashboard does below its xl peek
breakpoint (no ExecutionPeek column - the hero stage is ~1080px of
content, which is what the real console has at ~1080px viewport). Sorting
is real for the illustrative rows; the first click freezes the Executions
replay; every mutating control is a disabled Button so the hero cannot
imply a live capability the product lacks.

Refs #27
gotoi-agent changed target branch from develop to agent-develop 2026-10-06 18:35:39 +02:00
gotoi-agent merged commit b20c52a623 into agent-develop 2026-10-06 18:36:02 +02:00
Sign in to join this conversation.
No description provided.