feat(client): unify Host settings and device-local appearance

.agents/skills/verify-deepseekbot/features/README.md

@@ -4,7 +4,7 @@
 | --- | --- | --- | --- |
 | Bot Marketplace cards, filters, remembered sorting and upload/import | no | `verify-app` Bot mode path | [marketplace.md](marketplace.md) |
 | Connect encrypted pairing, resources and native private input | yes for DM/tool/private request | `verify-app` isolated Host and shared native QA | [connect-channel.md](connect-channel.md) |
-| Browser Remote Host pairing, icon strip, Host Feed and Host-level settings | only for a reply | `verify-app` two-Host path | [remote-hosts.md](remote-hosts.md) |
+| Browser Remote Host pairing, icon strip, local appearance/notifications and Host-level settings | only for a reply | `verify-app` two-Host path | [remote-hosts.md](remote-hosts.md) |
 
 | VRM companion Panel | yes for speaking | `scripts/e2e-vrm-companion.mjs` | [vrm-companion.md](vrm-companion.md) |
 | Desktop whole-window zoom (controlled S1 / Windows candidate) | no | `scripts/e2e-desktop-zoom-launch.mjs`, `scripts/e2e-desktop-zoom-windows.mjs`, `scripts/e2e-dock-zoom.mjs`, `scripts/e2e-workspace-chrome.mjs` | [desktop-window-zoom.md](desktop-window-zoom.md) |
@@ -100,4 +100,3 @@ Historical failures from 2026-10-14 (not requalified by this audit):
 
 | Three-action tool approval and coherent Full Access | yes | `scripts/e2e-tool-approval-simple.mjs` | [tool-approval-simple.md](tool-approval-simple.md) |
 | Workspace request read/write approval and original-task continuation | yes | `scripts/e2e-workspace-request-write.mjs`, `scripts/e2e-mobile-folder-browse-web.mjs` | [workspace-request-write.md](workspace-request-write.md) |
-

.agents/skills/verify-deepseekbot/features/remote-hosts.md

@@ -16,8 +16,9 @@ The browser pairs a Remote Host as a Paired Device and reads its Host Feed throu
 - `secret-route`: pinned Connect pairings carry private input, resources and logical streams through Noise; legacy pairings fail closed. The browser must be served by its own trusted Host. Loopback/Tailscale retain their contract.
 - `viewers`: a remote Bot DM opens Browser or Computer when that Bot has access. The shared Host viewer modules read frames and send input to that Host only; closing, switching source or losing the connection tears down the viewer and releases requested control.
 - `viewer-control`: queued input belongs to one takeover. Resume or frame loss invalidates it; frame recovery remains read-only even when the Host Feed never disconnected. Remove closes viewers and waits up to five seconds for takeover/release cleanup before revoking the pairing.
-- `settings`: right-click a Remote Host icon → Remote settings opens that Host's models, usage and storage. Default model and preset changes use its shared Host client. Usage includes Memory activity, without a link to a This Host Bot page. Storage retains preview, acknowledgement and destructive confirmation.
-- `notifications`: right-click a Remote Host icon and choose Remote notifications; enable browser permission explicitly and choose Tool approvals, Questions, Private input requests, Mentions & replies. Choices survive reload in this browser only. Verify the initial Inbox and reconnect backlog are silent, a new permitted Host attention item alerts once, disabled kinds stay silent and removing the Host closes its alerts. Private input text is never shown. Capture the new entry and dialog in light/dark; page-open API evidence does not qualify closed-page push or Desktop.
+- `host-appearance`: Host settings → Appearance edits the device-local name, symbol/emoji and icon colour through the shared HostLooks owner. Enter or blur saves the name; choices apply immediately. Tabs, conversation/Activity headings and new notification titles use the saved display name. Empty name restores the original.
+- `settings`: right-click a Remote Host icon → Host settings opens Appearance, Notifications, Models, Usage and Storage with the Host icon and display name. Default model and preset changes use its shared Host client. Usage includes Memory activity, without a link to a This Host Bot page. Storage retains preview, acknowledgement and destructive confirmation.
+- `notifications`: open Host settings → Notifications; enable browser permission explicitly and choose Tool approvals, Questions, Private input requests, Mentions & replies. Choices survive reload in this browser only. Verify the initial Inbox and reconnect backlog are silent, a new permitted Host attention item alerts once, disabled kinds stay silent and removing the Host closes its alerts. Private input text is never shown. Capture the new entry and dialog in light/dark; page-open API evidence does not qualify closed-page push or Desktop.
 
   Discovery uses the Host's notification query, not the Activity display window. Keep more than 30 old mentions and produce a new ordinary DM reply and a non-mention group reply; both must alert once when enabled. Traverse `deepseekbot inbox --notifications` cursors and compare the Host-decided items. Verify stable same-timestamp pagination, a live invalidation during paging, a partial-page failure followed by recovery, and no historical replay. A refused Notification constructor records a bounded redacted `remote-notification-show-*` diagnostic through the existing Client diagnostics surface. Settings apply immediately and close through the normal close control.
 
@@ -41,7 +42,7 @@ For control races, delay an input response, queue text, Resume, then take contro
 
 Keep the remote screen stationary during frame recovery. The Host must keep its sequence unchanged and answer matching `after` polls with 204 after ten seconds; the viewer recovers by fetching the current frame without that stale cursor, not by requiring a screen change. In both UI languages, inject a frame/input failure: the Web panel must show localized recovery guidance and a reconnect action, while the viewer snapshot retains the original diagnostic notice rather than rendering it as product copy.
 
-For Remote settings, use two disposable Hosts with different home basenames and distinguishable model presets and chat data. Open Host B's icon menu in Host A's browser. Capture the menu and all three settings sections in light and dark. Change B's default model or a preset, then read both Hosts with `model-catalog` and `model-presets`; A must be unchanged. Compare Usage and Memory with B's `overview-usage` and `overview-memory`. In Storage, select a disposable chat, preview media or whole messages, verify Clear/Delete is disabled before acknowledgement, then confirm. Read B's storage and timeline and verify A's data is unchanged. Exercise both cleanup targets; use their matching CLI preview/confirm commands against B as well. Disconnect B and revoke its browser pairing in separate runs: settings must show an unavailable state or refusal, with no local data fallback or replayed write. Never clean up real conversations for this journey.
+For Remote settings, use two disposable Hosts with different home basenames and distinguishable model presets and chat data. Open Host B's icon menu in Host A's browser. Capture the menu and all five settings sections in light and dark. Change B's default model or a preset, then read both Hosts with `model-catalog` and `model-presets`; A must be unchanged. Compare Usage and Memory with B's `overview-usage` and `overview-memory`. In Storage, select a disposable chat, preview media or whole messages, verify Clear/Delete is disabled before acknowledgement, then confirm. Read B's storage and timeline and verify A's data is unchanged. Exercise both cleanup targets; use their matching CLI preview/confirm commands against B as well. Disconnect B and revoke its browser pairing in separate runs: settings must show an unavailable state or refusal, with no local data fallback or replayed write. Never clean up real conversations for this journey.
 
 The default-model proof must change the model value on a Profile whose native settings owner can save it; a same-value no-op is insufficient. Keep a page's observed revision, change the default from another client, and verify the old page refuses without overwriting it. Explicit refresh must permit a subsequent save. Omit the catalog revision at the test transport boundary to verify the shared client refuses before any write; label that case as fault injection. For existing presets, verify Enter plus blur increments the revision once, a later blur saves independently, composition Enter does not submit, and a delayed write remains on its original Host/preset after closing and switching Hosts. Preserve the draft/error on a rejected save. New presets retain an explicit create action. Reject a remote storage preview token on the other Host, and verify neither cleanup command proceeds without its confirmation flag.
 
@@ -72,3 +73,12 @@ Read-failure recovery: keep the same Host connected with the same credential aft
 Permanent Remove regression (F01): enable a Remote Host and change its notification kinds, then remove it through the icon context menu. Verify the Host revokes this browser, the local pairing disappears, open notification handles close and `botharness.remoteNotifications.v1` no longer contains that Host. Reload and pair the same Host again: notifications start off with default kinds. Repeat while activation is waiting; a late permission or notification-page response cannot restore the forgotten choice. Other Hosts retain their choices; temporary disconnection, reconnect and page disposal retain the existing choice. The phone-global preference is outside this browser operation. The historical T4 driver assertion `persistedChoiceUnchanged` was incorrect for permanent Remove; retain that historical artifact but do not count it as F01 proof.
 
 Storage-refusal regression: selectively reject deletion of the notification key (removeItem for the last choice, setItem when another choice remains), while pairing storage stays writable. Permanent Remove must still stop the connection/feed, close handles, cancel late activation and revoke the pairing. The existing Client diagnostic stream records only the fixed remote-notification-forget-persistence-failed code. In-memory removal is complete but persisted removal is not; do not promise reload/re-pair will forget a choice the browser refused to delete. Pairing-storage failures are outside this regression.
+
+
+Unified Host settings regression: use two isolated Hosts with distinct home basenames. In both themes and locales, capture the old separate notification/icon/settings entry points as Before and the unified dialog as After, including a narrow viewport. Verify all five sections, Host identity in the sidebar, and notification help only inside the notification content. Rename, choose a symbol/emoji and colour, close and reload; compare the visible Host labels with `botharness.hostLooks.v1` and `host-look` from the explicitly selected `appearance-clients` target. Confirm pairing metadata and both operating-system hostnames are unchanged. Interleave a UI edit with a stale CLI revision and verify refusal. Inject browser storage refusal and verify a visible save error plus `host-look-storage-failed`, with no unsaved in-memory value. Delay Client delivery beyond the relay deadline, dispose the Client and remove the source: no late look write or acknowledgement may occur.
+
+Stop only Host B: Appearance and notification-kind choices remain usable, while Models/Usage/Storage show the source unavailable. Enabling notifications still requires the existing complete source baseline and may refuse offline. While activation waits, leave Notifications for Appearance and separately close the dialog; late results must not enable notifications. Repeat F01 Remove/re-pair and T7 viewer release regression as prerequisites allow. Existing T8 model revision, usage and destructive storage confirmations remain intact; no model request is needed for this settings UI journey. Record missing Docker/native/tailnet prerequisites explicitly.
+
+Host look concurrency and recovery: open two actual same-origin tabs, select each appearance Client ID explicitly, and use the same paired Hosts. Read B's revision, save a name from A, then submit B's old revision and require `host-look-revision-stale`. Concurrent edits of different fields and different Hosts must preserve both; record actual Web Lock names and storage values. A mocked lock manager or one-instance Promise queue is not cross-tab runtime evidence. Deny reads after a known look is loaded and on initial hydration: CLI reads/writes must return `host-look-storage-read-failed`, preserve known state and leave storage untouched. Restore access, explicitly refresh in UI/CLI, then save successfully. Missing Web Locks must return `host-look-lock-unavailable` without fallback. Keep native synchronous owner/migration regressions in the focused test set.
+
+Host look expiry: cover a CLI timeout shorter than eight seconds, delayed hydration, waiting for another tab's lock, late command delivery, and wall time past the deadline while timeout callbacks have not run. Observe storage before and after release; overdue writes must not begin. Also prove a write inside the deadline succeeds. Early CLI kill or HTTP disconnect before expiry is **unknown outcome**, not a cancellation pass: read back the same Client/Host. Do not extend this Host-look deadline contract to the unchanged notification relay.