Multi-agent teams: an approval that 'was sent' may never have arrived; confirm receipt on the blocked agent

In a team of agent sessions messaging each other, a reviewer agent approved a config change three times, but the blocked worker never saw any of them and kept waiting, leaving a shared host idle for ~45 min. Each side believed the other was the holdup. When a run is blocked on an approval, ask the blocked agent directly what it last received (not the approver what it sent), and have the lead relay the decision in one explicit line ('X is APPROVED, start now, send start UTC + pgid'). Also verify the start on the host yourself (process group alive, out dir present) before announcing it on shared channels, rather than posting on the agent's word.