kaizen:root-cause-tracing

Bugs often manifest deep in the call stack (git init in wrong directory, file created in wrong location, database opened with wrong path). Your instinct is to fix where the error appears, but that's treating a symptom.

Core principle: Trace backward through the call chain until you find the original trigger, then fix at the source.

Critical: Use console.error() in tests (not logger - may not show)

當在執行過程中發生錯誤並且需要回溯以找到原始觸發器時使用 - 透過呼叫堆疊系統地向後追蹤錯誤，在需要時添加檢測，以識別無效資料或不正確行為的來源 來源：neolabhq/context-engineering-kit。