Batch: agent work from agent-develop #32
Loading…
Reference in a new issue
No description provided.
Delete branch "agent-develop"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
One batch of agent work, integrated on
agent-developand conflict-free againstdevelop.Commits:
Merged issue PRs:
Merge pull request 'Issue #26: docs: gotoi is not self-hostable — remove every claim that it is' (#31) from issue/26-docs-unsell-selfhost into agent-develop
CI runs on this PR: the five required contexts on
developmust be green before it is merged.Every contained PR was already green on its own branch.
Refs (#26 etc. - no closing keywords).
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