session-handofflisted

<!-- Format adapted from MoAI-ADK session-handoff §Diet Constraints (6-block form reduced: localization tables, mode-seeding, and CLI save integration all dropped). Rationalization table entries come verbatim from the 2026-07-13 RED baseline run. --> # Session Handoff — Minimum Executable Resume A handoff block is the **next session's minimum executable context**. It is not an audit record, not a diary, and not storage. Everything durable already has a home: code and diffs live in git, verdicts and steps live in the run ledger (`.specify/specter-run.jsonl`), review findings live in `docs/review/`, lessons and decisions live in memory files. The block only carries what none of those can: which entry point to take, how to verify the ground is still solid, and the one action that resumes the work. ## When to fire (any of) 1. Context threshold approaching (harness compaction warnings, or the conversation has been summarized repeatedly). 2. `/ms.specter` finished a Feature and the Feature Map has remaining Features. 3. The user declares the session over ("세션 종료", "내일 이어서", "오늘은 여기까지"). 4. `/ms.fin` created a PR and unfinished Features remain. ## The block (the only durable output of a handoff) ```text ✂──── 여기부터 복사 ────✂ <Feature/작업> <단계> 재개. 적용 교훈: <메모리/원장 참조, 최대 4줄> 전제 검증: 1) <검증 가능한 명령> → <기대 결과> (최대 4개, 각 200자 이내) 실행: <단일 명령 또는 액션 1개> 후속: <머지 후/다음 Feature, 최대 2줄> ✂──── 여기까지 복사 ────✂ ``` Output order: the fenced block → (only if you saved overflow) the