UI refresh: composer-centric controls, Hermes control center, and dialog polish

[aronprins]

Summary

This branch is a focused UI pass that reorganises the main chrome around the composer and consolidates all settings/session tools behind a single "Hermes Control Center" surface. It also replaces the scattered activity bar + native confirm/prompt calls with a consistent status+dialog system, and does a sweeping pixel/icon cleanup across the UI.

No server-side behaviour changes — everything lives in static/ plus a couple of new static-asset sanity tests.

What changed

Composer becomes the control hub (inspired by Theo / T3 Code)

• Model selector, profile chip, and workspace chip now all live in the composer footer instead of the sidebar/topbar. Each is a pill button with its own dropdown positioned relative to the footer.
• The linear context-usage pill is replaced by a compact circular context ring with a hover tooltip that breaks out % used, token counts, auto-compress threshold, and estimated cost.
• Cancel button moves next to Send in the composer-right cluster.
• Topbar model/profile/clear chips are gone; the topbar keeps only the title, meta line, and a Files toggle.

Hermes Control Center replaces the old Settings modal

• Sidebar bottom is now a single "Hermes WebUI" launch button (with the Hermes mark icon) that opens the control center.
• Control center is an 860px tabbed modal with Conversation / Preferences / System tabs, fixed-height panes (no more outer resize on tab switch), and always opens on the Conversation tab.
• Conversation tab hosts Transcript / JSON export / Import / Clear actions (previously crowded into the sidebar footer).
• System tab houses the version badge, access password, and sign-out/disable-auth buttons.
• Control center always resets to the Conversation tab when closed — covered by tests/test_sprint34.py.

Activity bar removed, status rerouted

• The standalone activity bar above the composer is gone.
• Turn-scoped status (thinking, cancelling, etc.) now renders inline in the composer footer via setComposerStatus.
• Non-chat/system messages go through toasts via setStatus.
• Live tool cards + the message timeline remain the primary progress UI.

Shared app dialogs replace confirm() / prompt()

• New showConfirmDialog / showPromptDialog helpers in ui.js, backed by #appDialogOverlay markup and a themed .app-dialog-* CSS block.
• All remaining native confirm() / prompt() callsites across panels.js, sessions.js, ui.js (delete session, delete cron, delete project, clear conversation, remove workspace, new file/folder prompts, project rename, etc.) now go through the shared dialog, with proper focus trap, Esc/Enter handling, and danger styling.
• tests/test_sprint33.py locks this in by grepping the static bundle for any remaining confirm( / prompt( calls.

Session list: hover actions → single dropdown

• Per-row pin/move/archive/duplicate/trash buttons are replaced with a single `⋯` trigger that opens a shared `.session-action-menu` dropdown (with descriptive meta text per option and a dedicated danger state for Delete).
• Session rows are now fully rounded with 2px vertical spacing; the left border indicator for active/CLI/project rows is dropped (each state already has a distinct cue — gold fill, CLI badge, project dot).
• Session search input gets a taller tap target.

Workspace panel behaviour

• New explicit `_workspacePanelMode` state ('closed' / 'browse' / 'preview') in `boot.js` with a collapse button on the panel header and a topbar "Files" toggle chip.
• Workspace switch now guards against in-flight agent runs and dirty preview edits (confirming discard via the new dialog) before calling `/api/session/update`.
• Adds a "Choose workspace path" action in the workspace dropdown that prompts for an absolute path, adds it via `/api/workspaces/add`, and switches the session to it.

Icon and emoji cleanup

• Replaces remaining emoji glyphs throughout the UI with Lucide `li()` icons for consistency (paperclip, copy, pencil, rotate-ccw, shuffle, lightbulb, check, square, loader, x, settings, clock, play, pause, trash-2, arrow-right, plus, folder).
• Adds missing Lucide paths (`paperclip`, `copy`, `rotate-ccw`, `pencil`, `save`, `chevron-right`, `arrow-right`, `pause`, `user`) to `static/icons.js`.
• `CHANGELOG.md` entries referencing emoji glyphs updated to match.

Pixel normalisation pass

• Snaps padding, gap, and border-radius values across composer chips, sidebar panels, cron list, settings, approval buttons, dropdowns, and inline message edit to the `2/4/6/8/10/12` grid — removing the assorted 5/7/9/11px drift that made sibling elements feel subtly misaligned.
• Light-theme overrides updated for the new session-action trigger and the context ring (dropping the old `.ctx-bar-wrap` rules).

Tests

• `tests/test_sprint33.py` (new, 5 tests): verifies the shared dialog markup, CSS, helpers, and the absence of native confirm/prompt.
• `tests/test_sprint34.py` (new, 2 tests): verifies the control center reset-on-close helpers exist and are the only code path for hiding the modal.
• Adjustments to `tests/test_sprint16.py`, `test_regressions.py`, `test_sprint6.py`, and `conftest.py` to account for the moved/renamed selectors.

Docs

• `ARCHITECTURE.md`, `ROADMAP.md`, `SPRINTS.md`, `TESTING.md`, and `CHANGELOG.md` touched to document the new layout and sprint scope.

Test plan

• `pytest tests/test_sprint33.py tests/test_sprint34.py` (new)
• `pytest tests/test_sprint16.py tests/test_regressions.py tests/test_sprint6.py` (adjusted)
• Full `pytest` run
• Manual: open the app, verify the composer footer shows profile / workspace / model chips with working dropdowns and that the context ring tooltip renders % + tokens + cost
• Manual: open Hermes control center, cycle through Conversation / Preferences / System tabs, close and reopen — should always land on Conversation, outer shell should not resize
• Manual: trigger each migrated dialog path (delete session, delete cron, clear conversation, new file, new folder, remove workspace, switch workspace with dirty preview, project delete/rename) and confirm the shared modal handles focus + Esc + Enter
• Manual: streaming turn — verify cancel button appears in composer footer, status text renders inline, and toasts carry non-chat status
• Manual: session list hover — `⋯` trigger opens the dropdown, danger Delete option styled correctly, pin/archive/duplicate work
• Manual: toggle workspace panel via topbar Files chip and collapse button, both desktop and <=900px viewport
• Visual sweep across dark / light / slate / solarized / monokai / nord / oled themes for the new components

[nesquena-hermes]

Thanks for this PR, @aronprins — this is a substantial UI overhaul and the description is detailed enough to review clearly.

What stands out

Composer as control hub — moving model/profile/workspace selectors into the composer footer is a coherent design choice. It reduces the number of places users need to look for controls and aligns with how other modern chat interfaces handle context. The circular context ring replacing the linear pill is a good space trade-off.

Hermes Control Center — consolidating the old settings modal into a tabbed 860px surface with fixed-height panes solves the "pane resizes on tab switch" issue that's been a friction point. Resetting to the Conversation tab on close is the right default.

Shared dialogs replacing confirm()/prompt() — this is overdue. Native browser dialogs are unstyled, non-themeable, and break the UX contract. The showConfirmDialog/showPromptDialog approach with focus trap and Esc/Enter handling is the right replacement.

Session list: ⋯ dropdown — collapsing the per-row action buttons into a single trigger is a real improvement for long session lists. The meta text per option is a good addition.

Things to verify before merging

1. Composer footer overflow — with model selector, profile chip, workspace chip, context ring, cancel button, and send button all in the footer, this may get cramped on narrower viewports (e.g., 320–480px wide). Does the footer have a defined minimum width and a graceful collapse strategy?

2. Topbar-less navigation — removing the model/profile chips from the topbar is fine on desktop, but on mobile where the composer may be offscreen during scrolling, users lose access to those controls mid-conversation. Is there a fallback for narrow viewports?

3. _workspacePanelMode state persistence — is this state persisted across page reloads, or does it always reset to 'closed'? If users typically want the panel open, resetting it on reload would be annoying.

4. Test coverage — the PR adds test_sprint33.py and test_sprint34.py and adjusts four existing test files. Given the scope of JS changes (boot.js, panels.js, sessions.js, ui.js, icons.js), are the new tests primarily checking DOM structure and the absence of native confirm()/prompt(), or do they also cover the dialog behavior and composer state transitions?

5. Theme coverage — the PR mentions a visual sweep across 7 themes. Were these manual checks, or is there automated theme validation?

---

The scope is large but the description is well-organized and the design decisions are well-reasoned. The main pre-merge question is how the composer footer degrades at narrow viewports. Everything else looks like it's been thought through.

[nesquena-hermes]

Thanks for this PR, @aronprins — we did a thorough end-to-end review of the full diff and want to share where things stand and what the path to merge looks like.

What we did

We read the entire PR, audited all JS and CSS changes, verified every onclick= handler, ran the full test suite on the branch, and ran desktop and mobile browser QA. The code quality is genuinely high — the dialog system is well-implemented with proper focus management and ARIA, the ⋯ session menu has solid click-outside/scroll/escape/resize handling, and the control center modal is clean.

Two self-contained pieces already extracted and submitted as standalone PRs

Rather than hold all of #242 on the same timeline, we extracted the two pieces that are fully self-contained and low-risk:

• PR feat: shared app dialogs replace native confirm()/prompt() (extracted from #242) #251 — feat: shared app dialogs replace native confirm()/prompt() — the showConfirmDialog/showPromptDialog system plus replacement of all 11 native browser dialog call sites. 5 new tests. Zero layout impact.
• PR feat: session ⋯ action dropdown replaces per-row buttons (extracted from #242) #252 — feat: session ⋯ action dropdown replaces per-row buttons — the single ⋯ trigger replacing the five per-row hover buttons. Clean JS state machine, proper outside-close handling. Zero layout impact beyond the session list.

Both have passed full QA (629 and 624 tests respectively, zero JS errors in browser). They're ready for review.

What remains in #242 (the larger chunk)

The rest of the PR — composer footer restructure, Hermes Control Center modal, activity bar removal, workspace panel state machine — is more involved and carries more mobile risk. Specifically:

Issues to fix before this part can merge:

1. One failing test (test_sprint16.py::test_sessions_js_active_skips_project_border) — this was already resolved in PR feat: session ⋯ action dropdown replaces per-row buttons (extracted from #242) #252, so a rebase onto master after feat: session ⋯ action dropdown replaces per-row buttons (extracted from #242) #252 merges will fix it automatically.

2. Profile dropdown max-width — .profile-dropdown in the composer footer lacks max-width: min(260px, calc(100vw - 32px)). The workspace dropdown already has this guard. Without it, the profile dropdown can clip off-screen at very narrow viewports. One CSS line to add.

3. t('create') missing from i18n.js — the prompt dialog confirm button falls back to the raw key string. Minor but should be explicit. Already included in PR feat: shared app dialogs replace native confirm()/prompt() (extracted from #242) #251.

4. Rebase onto master — the branch was cut before PRs fix: cancel button now interrupts agent and cleans up UI state #244 (cancel fix), security: redact credentials from API responses and fix credential file permissions #243 (security redaction), and [Docker] Add the ability to run with the same user id/gid as the hermes installing user #237 (Docker UID/GID) merged. After rebasing, test_cancel_interrupt.py and test_security_redaction.py will appear and the test count will align.

Mobile considerations:

The composer footer restructure moves model/profile/workspace controls out of the topbar and into the composer footer. Desktop looks great. On mobile, when users scroll a long conversation, those controls scroll out of view with the composer — which is a UX trade-off worth documenting. The @media(max-width:640px) rules you added (horizontal chip scrolling via overflow-x:auto) handle the narrow viewport adequately, but a 375px explicit test pass would be good to confirm.

We've also added PR #254 — a 14-test mobile layout regression suite that will now run on every QA pass, so future PRs (including this one) have automated coverage for mobile CSS regressions.

Suggested next steps for the larger chunk

1. Rebase onto master (picks up PRs feat: shared app dialogs replace native confirm()/prompt() (extracted from #242) #251 and feat: session ⋯ action dropdown replaces per-row buttons (extracted from #242) #252 if merged, plus the security/cancel fixes)
2. Add max-width: min(260px, calc(100vw - 32px)) to .profile-dropdown in the composer
3. Run pytest tests/ -q and confirm 0 failures
4. Do a 375px browser pass — specifically: scroll a long conversation to confirm the composer footer (and its chips) is still reachable, and that the profile/workspace dropdowns open and are fully visible at narrow widths

Once those are addressed, the remaining chunk is in good shape and we'll run the full QA gate (desktop + mobile browser sanity, full pytest, QA harness) before merge.

Thanks again for the detailed PR — this is solid work and we want to get it across the line.

[nesquena-hermes]

Hi @aronprins — big update since the last review. Here's a complete status of where things stand and exactly what your branch needs to get the remaining work merged.

---

What's already been merged (you can remove these from your branch)

Since our last comment, we extracted and merged three self-contained pieces from your PR into master. Your branch still carries all of them — rebasing will eliminate the overlap, but here's what's now in master so you can also surgically remove them if you prefer a clean rebase:

Merged in v0.47.0

Shared app dialogs (your showConfirmDialog/showPromptDialog system)
Everything from your tests/test_sprint33.py, the #appDialogOverlay HTML block, the .app-dialog-* CSS rules, and all 11 confirm()/prompt() call site replacements in panels.js, sessions.js, ui.js, workspace.js are now in master. The i18n.js keys (dialog_confirm_title, dialog_prompt_title, dialog_confirm_btn, discard, clear, create, remove, project_name_prompt) are in master for en, de, zh, and zh-Hant.

Session ⋯ action dropdown
The closeSessionActionMenu(), _openSessionActionMenu(), _positionSessionActionMenu(), _buildSessionAction() functions, the ICONS additions (pin, unpin, archive, unarchive, dup, trash, more), and the session-actions-trigger/session-action-menu CSS are all in master. test_sprint16.py was updated — the old test_sessions_js_active_skips_project_border is now test_sessions_js_uses_action_menu_not_per_row_buttons.

Mobile QA regression suite
tests/test_mobile_layout.py (14 tests) is in master.

---

The one failing test — easy fix

Your branch currently fails 1 test:

FAILED tests/test_sprint16.py::test_sessions_js_active_skips_project_border
AssertionError: borderLeftColor not found in sessions.js

This test was already updated in master as part of the session menu merge. After rebasing onto master, the test will be gone and replaced with test_sessions_js_uses_action_menu_not_per_row_buttons which passes against your sessions.js. You don't need to do anything beyond rebase.

Quick check: after rebasing, run:

python -m pytest tests/test_sprint16.py -v --tb=short

All tests in that file should pass.

---

What's left to merge — the real work

After rebasing, your PR's remaining delta is the core UI redesign. This is the piece worth focusing on. Here's exactly what it contains and what it needs:

What remains (genuine new work not in master)

1. Composer footer restructure — model selector, profile chip, workspace chip move from topbar/sidebar into the composer footer. setComposerStatus() replaces the activity bar for turn-scoped status. The circular context ring (ctx-ring) replaces the linear progress pill.

2. Hermes Control Center — the 860px tabbed modal (Conversation / Preferences / System) replacing the old gear-icon settings panel. The sidebar bottom becomes a single "Hermes WebUI" launcher button. tests/test_sprint34.py (2 tests) verifies tab reset on close.

3. Activity bar removal — the standalone activity bar above the composer is gone; status is rerouted through setComposerStatus() in the composer footer.

4. Workspace panel state machine — _workspacePanelMode ('closed' / 'browse' / 'preview') in boot.js, syncWorkspacePanelState(), _setWorkspacePanelMode(), and the workspace-switch guard (prompts for discard via the new dialog before switching).

5. Icon cleanup and icons.js additions — save, chevron-right, arrow-right, pause, paperclip, copy, rotate-ccw, user added to icons.js.

---

Step-by-step path to merge

Step 1 — Rebase onto current master

git fetch origin
git rebase origin/master

This will pick up all the merged pieces (dialogs, session menu, mobile tests, the mobile overlay fix, the profile dropdown fix). There should be zero conflicts — we verified with git merge-tree and got clean. If anything conflicts, it will be in the overlapping areas (sessions.js, ui.js, style.css) and the resolution is almost always "keep both, yours on top."

After rebasing, run:

python -m pytest tests/ -q --tb=short 2>&1 | tail -5
# Should show: 645 passed (or more with your test_sprint34.py additions)

Step 2 — Fix the three remaining issues

These were flagged in the original review comment and are still needed:

2a. Profile dropdown max-width guard
In the composer footer, .profile-dropdown (the one positioned relative to the composer, not the topbar) is missing a viewport width constraint. The workspace dropdown already has max-width: min(420px, calc(100vw - 32px)). Add the same to .profile-dropdown in your CSS:

.profile-dropdown {
    /* existing rules... */
    max-width: min(260px, calc(100vw - 32px));
}

Without this, on very narrow viewports the 260px dropdown can clip off the right edge of the screen.

2b. t('create') i18n key
This was already added to master as part of the dialog merge (it's in all 4 locales). After rebasing you'll have it automatically — just verify t('create') resolves to 'Create' in English rather than falling back to the key string.

2c. test_sprint33.py will conflict or duplicate
After rebase, tests/test_sprint33.py in your branch and master will be identical content. Git may auto-resolve this. Verify it's not duplicated. If rebase gives you a conflict there, just accept master's version — it's the same file.

Step 3 — Mobile QA pass (the most important new requirement)

We've added a mobile regression test suite (tests/test_mobile_layout.py) but there's no automated browser testing of the composer footer at mobile widths. Your PR moves the model/profile/workspace chips into the composer, which is a significant layout change. We need you to do (or document) a manual mobile QA pass specifically for:

375px viewport (iPhone SE / smallest common phone):

• Is the composer footer visible and usable? Can the user tap model/profile/workspace chips?
• Do the composer chips scroll horizontally (via overflow-x:auto) without breaking the layout?
• Does the profile dropdown open fully visible (not clipped) when tapped from inside the composer footer? (This is different from the topbar dropdown — the composer footer may have different overflow context)
• After scrolling a long conversation, can the user still reach the composer footer and its chips?

414px viewport (iPhone 12/13):

• Same as above — the wider phone is usually fine, but verify

Suggested approach: Open the browser at http://localhost:8787, use DevTools or browser responsive mode to set 375px width, test all three dropdowns (model, profile, workspace) in the composer footer.

If any of these fail, add CSS at @media(max-width:640px) to handle them. The pattern we used for the topbar profile dropdown (position:fixed; top:56px; right:8px) can be adapted for composer footer dropdowns — they'd need position:fixed; bottom:calc(70px + env(safe-area-inset-bottom)); left:8px or similar.

Step 4 — Run the full gate

# Full test suite (must be 645+ passed, 0 failed)
fuser -k 8788/tcp 2>/dev/null; sleep 1
python -m pytest tests/ -q --tb=short

# QA harness (if you have the private qa/ tests)
# If not, skip — we run this gate before merging

# Browser sanity — desktop:
# - Load app, new session, 3 messages, all sidebar panels
# - Open the Control Center (sidebar launcher button)
# - Switch tabs: Conversation / Preferences / System
# - Close and reopen — verify it resets to Conversation tab
# - Check the gear icon is gone from topbar
# - Verify model/profile/workspace chips are in composer footer
# - Click each — verify dropdowns open and work

# Zero JS console errors throughout

---

Suggested approach: merge whole vs. split

Given that the remaining work is a cohesive set of interconnected changes (you can't easily ship the Control Center without also shipping the "launcher" button that replaced the gear, and you can't remove the activity bar without setComposerStatus() being in place), we recommend merging whole once the above steps are done.

The only real complexity is the mobile composer footer QA — everything else is clean, tested, and architecturally sound based on our earlier audit.

If you'd rather split further, the cleanest seam would be:

• Chunk A (lower risk): workspace panel state machine + icons.js additions + test_sprint34.py — these don't touch the topbar or composer layout
• Chunk B (main PR): composer footer restructure + Control Center + activity bar removal

But splitting at this point would create significant merge complexity since the Control Center and composer chips share CSS tokens and the boot.js state machine. Merging whole after the mobile QA pass is cleaner.

---

Summary of what to do

1. git rebase origin/master — picks up all merged pieces, resolves the failing test
2. Fix the profile dropdown max-width guard in the composer footer CSS
3. Do a 375px mobile browser pass on the composer footer (chips, dropdowns, scroll)
4. Run python -m pytest tests/ -q — should be 645+ passed, 0 failed
5. Push and let us know — we'll run the full gate (pytest + QA harness + browser sanity) before merging

The code quality in this PR is genuinely solid. We're looking forward to getting the full Control Center experience merged.

[aronprins]

Still working on this - closed accidentally <3

[aronprins]

All reviewer feedback has been addressed. Latest push includes two additional fixes:

1. Icon-only composer chips at 768px — moved the icon-only chip breakpoint from 400px up to 768px so chips collapse earlier, preventing composer footer overflow on mid-size screens.
2. Composer-left vertical scrollbar fix — added overflow-y: hidden to .composer-left to prevent an unintended vertical scrollbar (CSS spec implicitly sets overflow-y: auto when overflow-x is non-visible).

Ready for review 🙏

[nesquena]

Full Independent Review: PR #242 — UI refresh (rebased on pr-242-review)

Complete end-to-end review: rebased onto latest master, resolved all conflicts, ran full test suite, security audit, code review.

---

Rebase Status

Successfully rebased all 23 commits onto current master (7556ea0). Resolved 4 conflicts:

1. static/workspace.js — kept master's renderFileBreadcrumb() function (added after the PR branched)
2. static/boot.js — kept both: master's breadcrumb render call + PR's workspace panel state management (closeWorkspacePanel/syncWorkspacePanelUI)
3. static/index.html — PR removes the sidebar header (replaced by control center launcher); resolved by accepting PR's intent
4. tests/test_sprint34.py — add/add conflict (master has OAuth tests, PR has control center tests). Kept both. Fixed test assertions to match actual implementation (_settingsSection not _controlSection, settings-tabs not cc-tab)

Test Results

677 passed, 0 failed, 48 skipped — clean run.

Security Audit

Clean. Reviewed all innerHTML assignments across the diff:

• static/ui.js: all user data passed through esc(). Icon calls use static li() SVG strings.
• static/panels.js: static HTML strings only, no user data in innerHTML
• static/sessions.js: user data (session.title, project.name) passed through esc()
• static/messages.js: consistent with existing patterns
• static/boot.js: no innerHTML with user data
• No new external resources (CDNs, fonts, URLs)
• No eval, exec, document.write, or shell injection patterns
• Profile dropdown has max-width: min(260px, calc(100vw - 32px)) guard — viewport overflow issue addressed

Code Review

What this PR adds (after rebase drops already-merged work):

1. Composer footer restructure — model selector, profile chip, workspace chip move from topbar into composer footer. setComposerStatus() replaces standalone activity bar. Circular context ring (ctx-ring) replaces linear progress pill. Well-implemented with overflow-x:auto on the chip container for mobile scrolling.

2. Hermes Control Center — 860px tabbed modal with Conversation / Preferences / System sections, replacing the old gear-icon settings panel. _settingsSection state machine with switchSettingsSection(). Clean tab navigation with ARIA roles. _resetSettingsPanelState() correctly resets to 'conversation' on close.

3. Workspace panel state machine — _workspacePanelMode (closed/browse/preview) in boot.js with _setWorkspacePanelMode() and syncWorkspacePanelState(). Handles the close-preview-on-navigate and discard-unsaved-on-switch flows correctly.

4. Icon additions — save, chevron-right, arrow-right, pause, paperclip, copy, rotate-ccw, user added to icons.js. Consistent with the existing li() pattern.

5. i18n additions — 6 new keys across en/de/zh/zh-Hant for control center sections.

No issues found. The code is clean, well-structured, and consistent with the codebase style.

What Needs Manual Browser Testing

The automated test suite can't verify visual layout. An agent or human should verify:

• Composer footer renders correctly at desktop width (chips inline, context ring visible)
• Composer footer at 768px (chips collapse to icon-only mode)
• Composer footer at 375px (chips scroll horizontally, no overflow)
• Control center opens/closes correctly (tabbed layout, section switching)
• Control center: Escape closes, backdrop click closes
• Workspace panel state transitions: closed → browse → preview → closed
• Profile dropdown at mobile widths (position:fixed, not clipped)
• No JS console errors during normal use

Review Branch

Branch: pr-242-review on origin

Contains all 23 original commits rebased onto latest master + 1 fix commit for test assertions. This is the branch to merge (or apply these changes back to Aaron's fork branch).

Verdict

Approved pending browser QA. The code is clean, tests pass, security is good. The main risk is layout regressions at mobile widths from the composer restructure — that needs visual verification that automated tests can't provide.

[nesquena]

Second sweep complete — pr-242-review updated

Re-rebased onto latest master (28354a9, v0.49.4), resolved 3 new conflicts from recent merges, re-ran full test suite.

Rebase conflicts resolved (this pass)

1. boot.js cancel function (commit 4/24) — master added guaranteed-cleanup pattern; PR uses setComposerStatus. Merged: kept master's guaranteed cleanup with setComposerStatus fallback.
2. index.html sidebar header (commit 8/24) — same as before, PR removes header for control center launcher.
3. boot.js mobile responsiveness (commit 16/24) — another cancel-function conflict from master's latest cancel cleanup merge. Same resolution: guaranteed cleanup + setComposerStatus.

Test Results

686 passed, 0 failed, 48 skipped. +2 from last sweep (new tests merged to master).

Second-pass verification

• All critical functions verified present: toggleSettings, renderMessages, send, loadSession, renderSessionList, loadDir, populateModelDropdown, showApprovalCard, hideApprovalCard, showToast, setStatus, setBusy, syncTopbar, toggleMobileSidebar, closeMobileSidebar, toggleMobileFiles
• CSS brace balance: 774/774 (perfect)
• No leftover conflict markers in any file
• All PR features confirmed present: composer footer (5 CSS rules), setComposerStatus (2 refs), workspace state machine (10 refs), context ring (10 CSS rules), control center tabs (3 refs)
• i18n keys all resolve correctly
• Key test files all pass: test_sprint34 (21 pass), test_regressions, test_sprint16, test_mobile_layout

Branch

pr-242-review on origin — 24 commits ahead of master, force-pushed with latest rebase. Ready for browser QA and merge.

[nesquena-hermes]

Merge ready — pr-242-review branch

Full end-to-end review complete. Merging via pr-242-review (26 commits, rebased onto current master v0.49.4).

Review summary:

• Code review: clean — all innerHTML uses esc(), setComposerStatus uses textContent, no XSS vectors, CSS balanced 774/774
• Security: no new eval/document.write, no CDN additions, no shell injection patterns
• Tests: 742/742 pass (all passing, zero flaky)
• Theme sweep: all 7 themes (Dark/Light/Slate/Solarized/Monokai/Nord/OLED) render correctly
• Browser QA: 16 checks — all pass, zero JS errors throughout
  • Desktop layout, composer chips with labels, icon-only at ≤640px
  • Control Center: open/tabs/ESC/backdrop-close/reset
  • Workspace panel state machine: closed→browse→preview→closed with breadcrumb
  • Profile dropdown viewport guard confirmed
  • Session ⋯ dropdown: all options, ESC+click-outside close
  • All sidebar panels, settings save, concurrent chat, CSP inline handlers

One fix pushed to branch: version badge in System tab v0.45.1 → v0.50.0.

README and CHANGELOG updated for v0.50.0. Ready to merge.

[nesquena-hermes]

🎉 Merged — thank you, @aronprins!

v0.50.0 is live. Your UI overhaul is the biggest single contribution to the project and it shows — the composer footer layout, the Control Center, the context ring, the ⋯ session menu, the workspace state machine. It's genuinely a better product because of this work.

We've added a Contributors section to the README that calls out your contribution specifically. We'd love to see more PRs from you.