41 lines
2.2 KiB
Markdown
41 lines
2.2 KiB
Markdown
# Chats tab retap
|
|
|
|
The selected Chats destination distinguishes its list from an open chat. After
|
|
Back, switching tabs, and returning to the Chats list, a second tap on the
|
|
already-selected Chats tab restores the retained workspace route. The mounted
|
|
`ChatScreen` workspace supplies existing panes, active pane, drafts/scroll
|
|
state, quick-switch ordering, and divider sizes. Tapping Chats while a chat is
|
|
already open is non-destructive, and closing the last pane clears retention.
|
|
|
|
Retap validation is tied to the loaded chat-session controller. Retained IDs
|
|
that are no longer present or are closed remain on the list rather than being
|
|
resurrected; validity is unknown until the list has loaded, so an initial list
|
|
transition does not discard a valid retained workspace prematurely.
|
|
|
|
Focused checks passed:
|
|
- `test/application/app_route_test.dart`
|
|
- `test/application/chat_registration_test.dart` (full PipelinesApp mobile tab-retap flow)
|
|
- `test/features/chat/chat_workspace_restore_test.dart`
|
|
- `test/features/chat/chat_list_detail_test.dart`
|
|
- `tool/analyze.sh`
|
|
- `flutter build web`
|
|
|
|
Full-app fixture evidence at mobile width is in the shared artifact
|
|
`chat-retap-capture-v2/`: it captures opening a fixture chat from the list,
|
|
Back, Pipelines, Chats, then Chats again, with the restored conversation shown
|
|
at 560x1000.
|
|
|
|
Manager follow-up adds real shell regressions for a resized mobile peek,
|
|
quickswitch pane ordering, a deliberately scrolled transcript, restored active
|
|
pane and both drafts, no-history retap, single-pane restore, and a session removed
|
|
from the loaded list. The restored UI reuses the existing workspace controller.
|
|
The session-list refresh test answers the cached thread's outstanding network
|
|
reads before refreshing, matching the client's serialized request protocol.
|
|
Focused follow-up: 18 tests passed (`/tmp/memwatch/out.0cayzm`); no new product
|
|
implementation changes were needed for these acceptance cases.
|
|
|
|
Boot deep links now seed the same retained route as later selections. A full-app
|
|
regression opens `/chat/a` directly, folds from wide to phone, goes Back and
|
|
retaps Chats; the conversation and original draft return. Six application
|
|
chat-registration tests pass (`/tmp/memwatch/out.hPT6re`).
|