Record multi-chat workspace acceptance and release checks

This commit is contained in:
2026-11-06 18:41:44 +00:00
parent b34c3fa875
commit a223089c08
+8
View File
@@ -16,3 +16,11 @@ Narrow windows show only the active pane, with an **Open chats** picker retainin
Implementation is app-only; no new backend, pipeline definition or TUI changes. The existing WebSocket multiplexes session streams. A new generic capture key mapping supports physical Slash/left/right key codes for browser acceptance.
Background `/new` completions update their retained pane without navigating away from Search or another destination. Returning to Chat publishes the current active session route. Narrow-window Back returns to the list without issuing a server chat-close or interrupt request.
## Verification
Combined source `b34c3fa875e09c9883e37dce3d17ce8829a8e7cd` passed full app analysis and 1,059 chat/shell/Search/shared-input tests through the watchdog (peak 1820 MB, 116s). Production web and Android builds passed. Earlier focused checks additionally covered menu capabilities, both divider drags/clamps, state identity/draft preservation, native single-pane text selection, close/collapse, isolated streams, reconnection, async `/new`, and no hidden-destination navigation.
Fresh full-app Chrome captures with the final source passed at 1800x1100 Material light and Cupertino dark, with a 560x1000 fallback/restoration interaction. All 11 final PNGs were inspected. Reports: `/private/tmp/chat-splits-release-material/report.json`, `/private/tmp/chat-splits-release-mac/report.json`. The Material run checks both physical drag axes, Ctrl+Shift pane focus, Ctrl+/ Search/query retention, narrow picker/drafts and widening restoration. The macOS run uses raw physical keys to prove Command+Shift pane focus, local pane closure, Command+/ continuous typing, Clear/retype, and Search revisit with retained query. Capture tools exited normally; only scratch fixtures were used. No physical-device or Safari acceptance was performed.
The browser checks exposed and fixed a Cupertino web search input defect: the native nested clear control changed editable semantics into a disabled browser input on first text. A web-only native clear sibling keeps the field enabled and stable; explicit user Clear/shortcut actions hand focus back after layout. Ordinary query updates never refocus. Native non-web fields are unchanged. The source and regression evidence are also recorded in `chat-search-keyboard-shortcuts.md`.