log-session

# Log Session Capture the *why* and the *what-next* of a working session — the context that git history alone never records. A commit says what changed; a session log says what you were trying to do, what you decided, and where to resume. Deliberately cheap (`sonnet`/`medium`): this is structured summarization, not judgment. It must never reach for an expensive model. ## Turn contract — verify before ending the turn ``` ✓ The entry was APPENDED to docs/LOGS.md (file edited, not just drafted) with accurate git facts ✓ No past entry was edited ✓ Artifact language: explicit user instruction > the project's declared docs language > English. The CONVERSATION language never decides — a Spanish prompt still produces English PRs/issues/commits/SPECs unless one of the first two says otherwise ✓ The closing `→ Next:` block is printed as the ABSOLUTE last output ``` About to end the turn with any box unchecked? The turn is NOT done — complete the missing box first (weak models drop end-of-document duties; this list is first on purpose). ## When to use - **Before `/clear`** (or your agent's context-reset equivalent) — you're about to wipe context; capture it first. - **Before closing your agent** for the day. - **At a natural stopping point** — a feature paused mid-way, a thread you want to be able to resume cold. - **After a long session** with several decisions worth remembering. This is the *manual, rich* counterpart to the lightweight auto-logging hooks the `template/` sh...