Rev 10 follows Paul's ruling H25: spec 2 doesn't empty the old boxes. Each region's old box keeps its instances. The roster role `legacy`, or `platform` in IE, excludes it from every new placement and every relocation or move target. At the cut-over it swaps to a new public address of its own. The live drain is spec 4's. §22 maps round 9 and the earlier draining findings.
4
5
**Judge:**
6
1. Are round 9's findings and the draining machinery genuinely moot under H25? Is the role exclusion sound against `internal/boxchoice`, `internal/hostrelocate` and the move code? Can any path still need the old box to be empty?
7
2. **The old box's address swap at the cut-over (§9 step 3):** forced republication, cross-region forwarding to its instances, and IE's relay and MX switching with it.
8
3. **The two rollback sequences (§9).**
9
4. Anything new across the whole spec. This is a full pass: report any P1/P2/P3, not only rev 10's changes.
10
11
Give findings P1/P2/P3 with file:line and a failure scenario. End with a verdict: ready for a plan, or not.
amadan