context-clearinglisted

# Context clearing Session context is a running cost. Clear or hand off when the needed state has been compressed into GitHub and the next step no longer benefits from the investigation or implementation history. ## Safe order 1. Open or update the PR, issue, or parent snapshot first. 2. Verify it by direct read. 3. Resolve any genuine founder decision before handing off. 4. Run `spend` now if the completed session is worth measuring. 5. Clear, compact, end, or create a disposable successor. Do not keep both sessions working. Never clear first and hope the next session can reconstruct the work from comments or chat. ## Durable-record test A successor with zero conversation memory must be able to recover: - the intended outcome and non-goals; - controlling authority and exact repository refs; - what changed and why; - acceptance and verification evidence; - the current review stage and invocation count; - accepted and rejected findings with root-cause disposition; - unresolved blockers or founder decisions; - the next authorized action. A PR body also names the issue it closes. An audit issue names the exact merge commit and contains the complete read-only specification. A parent snapshot carries current truth rather than a transcript. ## Review-cycle boundaries The Stage 1 review request and CLEAN Stage 2 close are natural context boundaries. After requesting Stage 1, use PR event delivery where available and let a fresh session handle the response. For a Stage 2 is