log-lesson

A lesson changes future behavior. Record it while the particulars are still available.
Before writing any project record, confirm you are still in the registered project
checked at session start: this folder's docs/STATUS.md Project root names this folder
(or reads any clone of this repository). If not, write nothing yet; follow the Builder
protocol's location check and write gate, naming the project and this folder.

1. Search docs/LESSONS.md for related lessons first. Merge duplicates and archive
   superseded entries without losing their history.
2. Record context, what failed, what worked, a specific action to prevent a repeat
   (the Mitigation field), date and useful tags. Add an entry at the top using the file's
   format and verify the saved text. If the write fails, say it was not saved and provide
   the intended entry in the response.
3. Name when to act and what to do. "Be more careful" is not a useful action. Keep it scoped to
   the actual evidence; a one-off preference does not become a universal prohibition.
4. Promote recurring, broadly applicable lessons to concise standing rules in the
   shared project instruction file (AGENTS.md in the kit's project template). Keep the
   current lesson record focused.
5. Briefly report what to do next time and whether the lesson was saved, then continue.