A work-loop no longer drops a small fix just because it sits outside the task at hand. When it notices a mechanically verifiable fix along the way — one it can prove correct with a command, a search, or a check against a named authority — it now lands that fix instead of discarding it or writing it down for later.
Whether a fix rides along turns on its risk, its behavior, and how it was checked — not on how close it sits to the change already in flight.
A design call that is already settled — because a rule says so, or because the owner answered in one line — no longer disqualifies a ride-along. Anything that would still change a convention, a contract, or a published interface keeps requiring its own separately reviewed change.
Nothing noticed during a loop is dropped silently. At the end of a loop, every item gets routed somewhere; anything genuinely stuck is written down together with the one fact needed to unstick it later.