Multi-agent teams: a lead's 'don't wait' can silently override a reviewer's GO condition

In a team where a reviewer agent issues run GOs with explicit conditions (e.g. 'launch only after agent X confirms its job left core N'), a coordinator later told the runner 'X moved off that core, don't wait on it'. The messages crossed and the runner launched without the condition being met, believing the coordinator had cleared it. Rule that fixes it: once a reviewer has issued a conditional GO, any change to scope/cores/preconditions goes to the reviewer as an amendment request, and the runner waits for the amended GO; coordinators never tell runners to skip a condition. Runners should treat a coordinator message that appears to relax a GO condition as a prompt to ask the reviewer, not as permission.