Best possible solution:

Land this UI direction after assignee or UX maintainer acceptance and green exact-head CI; if the direction is contested, split the accepted sidebar polish from the disputed topbar/navigation changes.

Do we have a high-confidence way to reproduce the issue?

Not applicable; this is a user-visible Control UI layout improvement, and the relevant evidence is the after-state screenshots plus source inspection rather than a bug reproduction.

Is this the best way to solve the issue?

Yes, conditionally; moving navigation controls into the existing sidebar and workspace rail is a coherent implementation shape, but final acceptance depends on maintainer UX direction.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 64015e71dd5a.

Label changes:

• add proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes mobile and desktop screenshots that were inspected and directly show the changed UI after the fix.
• add proof: 📸 screenshot: Contributor real behavior proof includes screenshot evidence. The PR body includes mobile and desktop screenshots that were inspected and directly show the changed UI after the fix.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🦞 diamond lobster and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (screenshot): The PR body includes mobile and desktop screenshots that were inspected and directly show the changed UI after the fix.

Label justifications:

• P3: This is low-risk Control UI navigation polish with screenshots and focused E2E coverage, not a crash, data-loss, security, or broken-channel workflow report.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🦞 diamond lobster and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (screenshot): The PR body includes mobile and desktop screenshots that were inspected and directly show the changed UI after the fix.
• proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes mobile and desktop screenshots that were inspected and directly show the changed UI after the fix.
• proof: 📸 screenshot: Contributor real behavior proof includes screenshot evidence. The PR body includes mobile and desktop screenshots that were inspected and directly show the changed UI after the fix.

PR surface:

Source +308, Tests +21. Total +329 across 54 files.

What I checked:

• Repository policy read: Root AGENTS.md and ui/AGENTS.md were read fully; the UI guide treats locale bundles as generated output and the root policy requires deep PR review plus protected maintainer handling. (AGENTS.md:1, 64015e71dd5a)
• PR state: Live PR view shows head b0495ee, author association MEMBER, label maintainer, assignee shakkernerd, and mergeable but blocked status. (b0495eee0477)
• Shell wiring: The shell passes command palette, drawer/collapse, route, sidebar, and terminal panel state through the existing Control UI shell boundary without adding config or protocol surface. (ui/src/app/app-host.ts:774, b0495eee0477)
• Sidebar behavior: The sidebar now renders the brand row, search action, collapse action, scoped recent-session visual state, and compact docs tooltip in the owner component. (ui/src/components/app-sidebar.ts:290, b0495eee0477)
• Terminal availability: The current head computes terminal availability with config, connection, admin access, and an advertised terminal.open method check before exposing the workspace-rail terminal action. (ui/src/pages/chat/chat-pane.ts:573, b0495eee0477)
• Theme follow-up: The latest head preserves single-button theme cycling through system, light, and dark, addressing the prior theme-mode review path. (ui/src/components/theme-mode-toggle.ts:25, b0495eee0477)

Likely related people:

• shakkernerd: Assigned on the live PR and authored the latest branch fixes for topbar/breadcrumb restoration, sidebar alignment, terminal availability, and theme cycling. (role: recent follow-up owner; confidence: high; commits: 090c974da538, e68fc28a56d1, a2e8822dd2a7; files: ui/src/components/app-topbar.ts, ui/src/components/app-sidebar.ts, ui/src/pages/chat/chat-pane.ts)
• vyctorbrzezowski: Authored the initial branch commit and the closed related sidebar polish PRs that this PR says it folds in. (role: original proposer and related UI polish author; confidence: medium; commits: 2817aa80b161, 4187fe4e2ba0, 26ac7310197f; files: ui/src/components/app-sidebar.ts, ui/src/components/app-topbar.ts, ui/src/styles/layout.css)
• vincentkoc: The available current-main blame/log history for the touched Control UI shell files points to commit c96c60d; deeper attribution is limited by the shallow checkout. (role: current-main area contributor in shallow history; confidence: low; commits: c96c60d22d01; files: ui/src/components/app-topbar.ts, ui/src/styles/layout.css, ui/src/components/app-sidebar.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

• reviewed 2026-07-06T17:47:17.951Z sha 772dfa7 :: found issues before merge. :: [P2] Remove boolean literal comparisons
• reviewed 2026-07-07T08:48:59.231Z sha 772dfa7 :: found issues before merge. :: [P2] Remove boolean literal comparisons
• reviewed 2026-07-07T09:30:09.112Z sha 772dfa7 :: found issues before merge. :: [P2] Remove boolean literal comparisons
• reviewed 2026-07-08T06:35:05.972Z sha 3461f7d :: found issues before merge. :: [P2] Coerce advertised terminal support to boolean | [P2] Return a fallback theme mode | [P3] Remove the stale AgentsListResult import
• reviewed 2026-07-08T06:43:57.493Z sha 3461f7d :: found issues before merge. :: [P2] Coerce terminal availability to boolean | [P2] Return a fallback theme mode | [P3] Remove the stale AgentsListResult import