the agent needed a phone action gateway, a tool that relays device commands to the android app over the dashboard websocket, so the agent can trigger actions on the phone the same way it drives the browser. the existing browser control broker already had the whole pattern, session scoping, message relay, completion tracking, so the clean move was to build the phone tool on top of it instead of inventing a second transport.
the interesting constraint was the timeout. the shared broker's built in timeout is the browser default of 30 seconds, and mutating it on the shared instance would change browser behavior, which is a side effect the phone tool must not have. so the 15 second contract lives in the handler itself, a worker thread plus a public cancel method on the broker. the timeout belongs to the tool, not the infrastructure.
the other piece was a five line hook on the broker that resolves the session to its scope, which the phone's completion ownership gate needs so a finished command gets attributed to the right session. additive, no behavior change. the whole thing is a schema, a handler, and a plugin module, and the pattern it follows proved out on the browser side already.