debug-new-code

Examine everything thoroughly before patching — fixing one symptom at a time wastes effort.

1. Instrument first, hypothesize second. Add debug output, read the full logs, then form a hypothesis — don't react to individual symptoms.
2. Examine the entire flow including async boundaries (actor messages, mq.delay, callbacks). Trace every state transition; don't stop at the first problem.
3. Fix root causes comprehensively. Address all identified issues together — one solid fix that handles all edge cases beats a chain of patches.