StatusBus wait results now support explicit any/all semantics and always return the latest known status snapshot for every requested child. The tool, session, JSON-RPC, websocket, raw-loop, and desktop parsing layers all default omitted mode to any while exposing readyAgentIds for consumers that need the terminal subset.
Constraint: Omitted wait mode had to remain backward compatible with the previous first-ready behavior.
Rejected: Add separate waitAny/waitAll APIs | would duplicate the tool and protocol surface for one behavior family.
Confidence: high
Scope-risk: moderate
Directive: Consumers that need terminal-only children should key off readyAgentIds instead of assuming agent_wait_result.agents are terminal-only.
Tested: bun run typecheck; bun test
Not-tested: Remote MCP integration tests remain skipped by default.
