* fix(runtime): let connections own host status recovery
Verify runtime status after authenticated connection recovery and publish
ordered snapshots to desktop and browser viewers. Consolidate failed-status
retries in the connection owner and remove renderer retry/diagnostics merging.
Adapt sidebar host-state derivation and regression coverage from Omar
Shahine's original fix in https://github.com/stablyai/orca/pull/19163.
Co-authored-by: Omar Shahine <10343873+omarshahine@users.noreply.github.com>
* fix(runtime): show blocked hosts honestly and remove obsolete status options
* fix(runtime): preserve timeout guidance and update IPC test fixtures
* fix(runtime): preserve status evidence and address review gaps
* test(sidebar): assert workspace host icons dimming and recovery tooltips
* fix(palette): require available hosts before adding implicit badges
* fix: retain disconnected host snapshots for new renderers
---------
Co-authored-by: Omar Shahine <10343873+omarshahine@users.noreply.github.com>
A control-handshake test that expects a timeout was instead getting
'Unexpected server response: 401' about once in fourteen runs. A slow machine
cannot turn a timeout into a 401 -- that needs a real HTTP response, so the
connection was reaching a different server.
new WebSocketServer({ port: 0 }) binds the wildcard address while the client
dials 127.0.0.1. On macOS those differ, and with SO_REUSEADDR a foreign process
can hold the more specific 127.0.0.1:P and win the connection. Caught live: a
wildcard bind took port 52584, which a running Orca app already held on
loopback, and Orca answered the probe. A listener that checks a token answers
401.
Ten constructions across seven files now pass host: '127.0.0.1', so the
reservation covers the address the client dials and a duplicate bind is refused.
Adds a ratchet, because this is not authors forgetting a convention: all 30+
.listen(0, ...) sites already pass '127.0.0.1', while 7 of 7 ws constructions
did not. ws accepts { port } alone and binds the wildcard silently, so nothing
told them. The guard pins the wildcard count, and pins separately at zero the
option shapes it cannot read -- spreads and variable option objects fail rather
than being exempted, and a recognized-construction floor catches the matcher
going blind, which otherwise reads exactly like a clean tree.
mobile/scripts/mock-server.ts stays on the wildcard deliberately: a phone
reaches it over the LAN.
Jinwoo HongandOmar Shahine
Neil
Brennan BensonandMerge Sim