iii-bridge The worker connects this iii engine to another iii instance over so functions on either side can call across the boundary. It opens a single outbound WebSocket to the configured , registers with the remote using , and stays open for the engine's lifetime — bridging is request/response over that long-lived connection. There are no trigger types. The worker is configuration-driven. The primary surface is two list-shaped config fields ( and ) that wire stable function ids on both sides; once configured, callers reach across the bridge by invoking those stable ids with the normal — no…