learning-from-mistakes

记录调试与故障解决中的关键经验教训，避免重复成本。

把一次漫长调试或必须靠上级点拨才解决的故障教训记录下来，形成团队知识，避免以后重复踩坑。在遇到难缠 bug、长时间排查后有“aha”时立刻写入，供后人参考。重点是捕捉实战细节和关键决策，让未来能更快定位同类问题。

Capture the lesson so future-ATLAS does not pay the same debugging cost twice.

## When to write an entry

Write one — without being asked — when either is true:

- **Boss had to step in.** A bug or mistake ATLAS could not solve alone; Boss's guidance is what cracked it.
- **Aha moment after a long hunt.** A debugging session that ran long and ended in a non-obvious realization.

Skip routine fixes. The bar is *surprise*: would this genuinely save someone — likely future-ATLAS — from a hard time? If the cause was obvious in hindsight to anyone, it is not worth an entry. Apply the same high-entropy filter as `NOTES.md`: record what is surprising, not what is expected.

## Where

One file per