session-continuitylisted

# Session Continuity ## What this is Seam bugs are coherence failures between parts written at different times. AI assisted development manufactures exactly that condition: many short sessions, each fast, each locally correct, none holding the whole. The code accumulates; the understanding resets every session. This protocol is the small ritual that carries understanding across the gap. ## Trigger - Session start in a scaffolded repo, before the first change - Session end, or any point where the work stops and context will be lost - Resuming a task another session began ## Required behavior **On start, orient before acting:** **1. Read the seam map** (`.seamstress/seam-map.md`). Know where the dangerous ground is before walking on it. **2. Read the continuity note** (`.seamstress/session-notes.md`) if it exists: what the last session changed near seams, what was left open, what was overridden and why. **3. Verify the ground, do not assume it.** `git log --oneline` since the note was written; `git status` for uncommitted work. The note is a hypothesis about the repo; the repo is the fact. If they disagree, say so before doing anything. **On end, leave the note you would want to find:** **4. Write the continuity note:** which seam files changed and why, in one line each; what is verified green versus expected but unverified (the labels from the [verification protocol](../verification-discipline/SKILL.md) carry over); anything left half done, named honestly as half do