close-out-the-runlisted

# close-out-the-run — reconcile and leave a clean seam The run is ending. Your job is to ensure the state is accurate and the handoff is clear. ## The two triggers Close out when: 1. Clean bounded autonomous work is exhausted (everything left is gated). 2. The resource you are spending is nearly gone. ## Do not churn at the gated boundary Attempting gated work unsupervised is the single worst way to end a run. It produces low-confidence output that a human must now audit. Stopping is the correct move. State it as a result, not an apology. ## Reconcile durable records Before stopping, check every item the run touched: - Every item carries an accurate done state and a resolution title that says what actually happened. - Repositories are committed and pushed, and anything the run shipped went through the **whole** ship loop in `execute-unattended` — tagged, released where that was appropriate, and dogfooded — rather than being called done at the push. “The tests passed” is weaker than having run the new behaviour once for real, so if the run stopped early at a step, name the step. - Plans and notes agree with reality. - Nothing is left orphaned or still flagged as pending when it is finished. A historical record of a completion is worth keeping. A stale pending flag on finished work is a defect to fix. They look similar and are not the same. ## Leave a clean seam Pause any persistent goal or session-continuation mechanism. Do not leave it running against work you have