pause-and-resume

# Pause and Resume Keep this workflow in the current session. Store its state in the pause response; do not create files, commits, or new tasks solely to checkpoint it. ## Pause 1. Stop expanding the task. Do not begin another subtask, retry, or optional check. 2. Let an already-started atomic action finish only when interruption would leave inconsistent state. Otherwise stop at the nearest safe boundary. Use only the smallest necessary read-only check or already-authorized cleanup to record an accurate, safe state. 3. Preserve facts, not guesses. Distinguish completed, in progress, blocked, and unknown work. Record exact non-sensitive paths, parameters, job IDs, and receipts when they are needed to continue. Never expose secrets. 4. If work continues independently, record its handle, observed status, and how to reconcile it. Do not cancel, restart, or dispatch it again merely to pause. 5. End the turn with the compact checkpoint below, in the user's language. Keep the marker exact, omit irrelevant detail, and state explicitly when there is no known non-repeatable effect. ```text PAUSE_CHECKPOINT: ACTIVE - Goal and done condition: - Completed: - Current stopping point: - Remaining work: - First action on resume: - Do not repeat: - Constraints and settled decisions: - Live state, running work, and facts to recheck: ``` Finish with the equivalent of: `Paused. When you return, say "continue".` Then stop. Do not perform the first resume action i...