Every command occurrence offline can see: statements at every block depth
(Q4's stateful walker) plus bracket-inner commands at every nesting depth
(Q3's resolver).
The ORDER carries no meaning, even though the list is emitted in source order
and repeats are significant (writes counts multiplicity — do not dedupe).
Both lab harness bugs corrected during phase 0 were alignment bugs, where a
positional correspondence silently lined the wrong pair up; containsWrite
consumes this only as a rollup, so it cannot repeat that failure.
Every command occurrence offline can see: statements at every block depth (Q4's stateful walker) plus bracket-inner commands at every nesting depth (Q3's resolver).
The ORDER carries no meaning, even though the list is emitted in source order and repeats are significant (
writescounts multiplicity — do not dedupe). Both lab harness bugs corrected during phase 0 were alignment bugs, where a positional correspondence silently lined the wrong pair up;containsWriteconsumes this only as a rollup, so it cannot repeat that failure.