@projectpac/transport-iroh

The iroh transport: QUIC between nodes, wherever they are.

The transport moves bytes and nothing else -- it does not read an envelope, know a session, or decide anything about a peer. Verification, routing, and retries all live above the seam in the network core plugin, which is what lets this package stay small around a native binding.

• One ALPN. The adapter's frame already says what a frame is for, so the wire needs one flow name, not one per frame kind.
• Its own key, beside the node's. The iroh endpoint wants a key for its addressing; it is a transport detail, stored by the transport, and it is not the node's identity -- an envelope proves its sender regardless of which wire carried it.
• Relays are configuration. The n0 preset reaches nodes through public relays and hole-punching; minimal stays direct, which is what the local dev environment uses so two nodes on one machine never wait on the internet.

The network seam's conformance suite runs over this transport with PAC_TEST_IROH=1 -- real QUIC, same assertions as the in-memory double, which is the seam's whole claim: nothing above it varies by transport.