Files
orca/tests/e2e/cross-version-wire
Brennan Benson 7208be6902 test(native-chat): cover paired runtime launch compatibility (#25072)
* test(native-chat): cover paired runtime launch compatibility

* test(native-chat): use production prompt response fingerprints

* test(native-chat): pass journal items to the paired-runtime outbox hook

Main made journalItems a required outbox input; mirror production by
passing the read state's items.

* test(native-chat): pin paired-runtime routing and capability questions

- Move the paired-runtime chat test into its own file and render the real
  session hook against a paired server that advertises today's capabilities
  while this machine advertises none, so Stop, prompt cancel, repeated Stop
  and question answers fail if their capability question goes to the wrong
  runtime. Add a local and a paired session sharing one id.
- Cross-version: state that the file pins the capability strings a
  v1.4.219 server really advertises, use the desktop's real handshake list,
  and keep the current server only as the control for the refusal.
- agent-launch-routing: give the released-server case a capable client so
  it is refused by the server gate, not the client one.

* test(native-chat): route the paired launch suite and cover the outline read

- Start the cross-version job when the launch route or the client list the
  desktop sends a paired host changes, since the paired launch suite runs
  them.
- Check the rail's conversation outline is read from the paired server, and
  narrow the hook test's header to what it covers.
2026-10-05 14:48:52 -07:00
..