Development record

The --route prediction parity test (internal/core/implement/loop/route_parity_test.go) checks predictHand against fake stage bodies, not the real validateStage and implementStage. If validateStage's hand-out order changed (openRound's roles reordered, or a Stay or Goto returned before its Await), a --route for a reviewer role would be accepted and then silently not used: no refusal, and no route_unused entry, since nothing is unsure without a landing ahead. The real bodies agree with the prediction today; the gap is that no test would notice them drifting apart.