Files
pipelines/docs/notes/federated-chat-browser-acceptance.md
T

2.1 KiB

Multi-machine browser acceptance

The manager ran the production Flutter entry point with two isolated HTTP/WS backend fixtures, each behind the real authenticated web proxy. Both backends intentionally returned the same native chat ID. Browser cookies and remote registration used the actual peer relay API; no operator chats or passwords were changed and no model inference ran.

Verified in real headless Chrome:

  • Both machine-labelled chats and both connected statuses appear together.
  • Opening Linux reads its transcript; sending reaches Linux only, with the original native ID rather than the UI's composite identity.
  • The password helper changes a scratch proxy password immediately: old login fails, new login succeeds, and the existing Linux chat still accepts a prompt.
  • Two-machine creation shows the picker; choosing Linux loads its harness and directory choices without switching the primary page.
  • Removing Linux leaves the Mac list available; one-machine creation opens the Mac dialog directly. No browser console exceptions were recorded.

Inspected screenshots: /tmp/review/federated-chat-live-browser/01-both-machines.png through 06-single-server-skips-picker.png. The first harness run needed its selector corrected for the accessible row's harness-name prefix; no application change was needed. Final script: /tmp/pipelines-federation-browser-e2e.mjs, log: /tmp/pipelines-federation-browser-e2e.log. All scratch services/browser processes were awaited and removed by the harness.

A separate real mDNS query on the Mac found both operator servers, tank and Alans-MacBook-Pro; /tmp/pipelines-live-lan-discovery.json records the response. Discovery/edit-name UI also has inspected Material/Cupertino fixture captures.

Checks: 1140 chat/core/application integration tests passed; after native thumbnail integration, 133 relevant combined tests passed (out.lVi8MA), analyzer clean (YXAEGK). Go build/vet/full tests passed; all 14 web proxy tests passed, including remote credentials, alias revocation and generated-content sandboxing. The password helper has 11 passing tests. No physical device test ran.