Each mover gets a validate step on the seat mesh-wants before its composition, its status from
the policy; one ask per pipeline that every mover's validate step reads (a mover placed later
reads it, its result too). A mover's composition waits until validate ends: asked once it
passed, ended not asked when it did not, so a manifest the validator refuses is never composed.
The step runs name the runner's seat as their asker. Unit tests 81 to 82.
Builds: design 47 H §745 (the runner's order); lead answers H-A-51, H-A-88
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy