Pause Checkpoint
Save the user's place so they can come straight back to it. The pause is done when the checkpoint and the execution state are both written and the user has been told how to resume.
- Run the ab-context-checkpoint skill. If the user gave a reason for pausing, use it as the checkpoint's brief description.
- Run the ab-session-continuity skill and follow its Process: Pausing Work to update
docs/context/STATE.mdwith the current execution state (wave progress, task completion, blockers).
This is documentation only: change no source code, because a pause should preserve the state, not change it, and an edit made on the way out goes unreviewed.