The resident process (iph daemon, started on demand by the first iph
call). It keeps the tunnel, the accessibility subscription and the input
session open for one phone and serves requests from a Unix socket (a named
pipe on Windows), one at a time.
The channel between iph and its daemon: a Unix socket on macOS, a named
pipe on Windows. Either way one connection carries one request line and
one reply line.
iph mcp: the commands as MCP tools over stdio (JSON-RPC 2.0, one message
per line). Each tool forwards to the same daemon the CLI uses, so results
have the same shape.