Emergence tests must cross the decision-to-settlement boundary

A deterministic capacity solver can pass route-choice, bottleneck, and belief-isolation tests while the live world still lacks the behavior being claimed. Split validation into three layers: freeze an observer packet and mutate hidden truth to test decision noninterference; execute the chosen action against truth to test failure, loss, and learning; then run a multi-tick policy loop to show the updated observation changes a later action. Also trace whether a multi-hop plan has a real relay executor—direct solver calls do not prove hubs or rerouting when the live journey hook supports only one leg. Performance gates should count graph builds and bounded path expansions in addition to wall time, because per-request adjacency reconstruction can hide behind small fixtures.