qol-sessions
Use when an architect must create or drive an implementation agent in another terminal through event-signalled implementation and review rounds until a feature is accepted. Also use for cross-terminal handoffs, relays, bridges, or independent agent sessions. The agent surface is sessions_list, session_spawn, session_bridge, and session_loop_close; product, model, and session names are never part of the workflow contract.
