Files
pipelines/app/notes/machine-provenance-and-chat-creation.md
T

43 lines
2.5 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Machine identity and new chats
Pipeline/run/chat rows and their detail subtitles show the owning saved machine's
name. A rename updates mounted labels without changing gateway identity, stored
workspace, credentials or native IDs. Compact chat lists show the machine name
under Expand and include it in each chat's tooltip/accessibility description.
Profiles and address aliases remain editable in Settings → Servers.
New chat first presents a native machine picker, then uses that machine's own
`chat_backends` and directory catalogue. A cross-machine selection retains a
one-shot creation intent outside the disposable app. Root replaces the old
socket and credentials normally, routes the new app to Chats and waits for its
connection before mounting the create dialog. Sign-in/onboarding can complete
first; an offline target stays at its connection gate. Failed profile saves or
selection clear the create intent, and ordinary server switching abandons it.
A browser navigation carries only `newChat=1` to the target origin, where the
normal route canonicalization consumes the query. No credentials cross origins.
No chat is created until the final explicit New chat confirmation.
Lists remain scoped to the selected machine. This change does not aggregate
rows or combine native IDs across machines.
## Validation
- 51 selected Flutter tests passed, including real Root app/socket replacement,
target-only catalogue discovery, exactly-once intent consumption, failed
persistence and live alias rename; memory-watchdog peak 1715 MB, 8s.
`/tmp/memwatch/out.Q5UKgn`.
- `tool/analyze.sh`: clean, 6s.
- Fixture web release build passed on Flutter 3.44.6, 26.2s.
- Browser Material dark 1280×1000 captures: pipeline list, run list/detail,
chat list/detail, machine picker, then the actual harness dialog. Cupertino
light 560×1000 captures: chat list, native machine action sheet and harness
dialog. Every PNG inspected; no overflow or missing alias observed.
`/tmp/review/machine-provenance-material/`,
`/tmp/review/machine-provenance-cupertino/`. Compact list dragging was also
captured and inspected at `/tmp/review/machine-provenance-compact/`; the
machine label remains readable at the 72px compact width.
- Native device and second physical server were not used. Tests use owned
fixture gateways; real operator chats, server processes and devices untouched.
- Source checks precede manager landing/deployment; this note does not claim
published artifacts or installation on the Linux machine/phone.