Task completion

An answer is not a substitute for an authorized action, and passing checks are not proof that every requested outcome was delivered. Track both the request and the evidence so the user does not have to discover unfinished work.

Establish the completion contract

Extract the requested outcomes, constraints, and authorization from the current conversation and applicable repository instructions. Keep a short checklist for multi-step work, using the harness's task list if available or ordinary notes if not. A one-step task does not need a ceremonial plan.

When the user has authorized persistent context, read and apply context-checkpoint using the skill loader or sibling file. Recover its scoped active plan before rebuilding it, and persist material progress and corrections with verification. A volatile task list alone does not establish that the plan will survive compaction. Report an unavailable dependency or memory store rather than claiming recovery coverage.