fix(ui): five regressions the sidebar restyle and the token re-tier introduced #118
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lz/agent-nexus!118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/sidebar-regressions"
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?
An adversarial pass over the whole merged body of work (#112–#117) found six regressions. Five are fixed here; the sixth is a knowing trade, explained at the bottom. Each was verified by reading the code, and the high one by driving the UI.
1 — HIGH: "New session…" was dead everywhere, and lied about why
focusNewSession(MainSplit.svelte) looks the workspace up by[data-worker-id]— an attribute the restyle deleted along with the.sessions-mountwrapper that carried it. Nothing in the app emitted it any more.So the query returned
null, the scroll and focus were no-ops, and control always fell through totoast('Sessions appear once the workspace has finished starting')— on healthy running workspaces, with the add-session form visible right there. The one branch written to catch a genuine failure had become the only branch that ever ran.It is the first item of the workspace menu, reachable from the sidebar ⋯, the rail ⋯, and a workspace dock tab's context menu.
Verified live: picking "New session…" now focuses the
feature-nameinput and shows no toast.2 — MEDIUM: the rail's hover card lost its capability chips for good
Workers.sveltestopped callingworkerImages.load()when it stopped rendering capability chips, butRailHoverCardstill readscapabilitiesFor()and never loaded anything itself. The two remaining loaders only fire when a Settings panel or the New-workspace modal opens.Worse: the hover card renders only in rail mode, where
<Workers>is unmounted — so nothing could have loaded it there even before. Moved the load toMainSplit, which is mounted in both branches.3 — MEDIUM:
.ws.dormantundid the WCAG work it shipped besideAt
opacity: 0.45a stopped workspace's name composited to ~3.9:1 on--bg, and its repo line to ~2.03:1 — the exact value #113 had just been written to eliminate.0.6keeps the name near 6:1 and still reads clearly as recessed.4 — LOW-MEDIUM: the empty states became full-bleed dashed boxes
.emptydraws a dashed box; giving it horizontal padding insets its text and leaves the border flush against both pane edges, now that.lp-bodyhas none of its own. Margin, not padding. Affects the load-error, no-provider and no-workspaces states — two of which are the first thing a fresh operator sees.5 — LOW:
<b>emphasis silently became a no-op.foot band.hint bwere--mutedagainst a--muted-2line. After the re-tier both sides are--muted, so the palette's ↑↓ / ↵ / Tab / Esc keys and the hover card's "terminal" render identically to their labels. Raised to--text.Deliberately not fixed
dockview no longer distinguishes the focused group from an unfocused one — the four tab-background vars were its only signal, and #112 set them all transparent. That trade was made knowingly and is called out in #112; it needs a replacement signal rather than reverting the fill, so it stays a known limitation rather than a silent one.
Gates: typecheck 4898 files / 0 errors, lint clean, 121 files / 1202 tests.