/done

/done is a separate, explicitly invoked completion workflow. Standalone entry resolves the item and request; caller entry reuses their exact context. Available item labels and status data are carried forward, while a minimal caller packet is completed with one item read. The shared completion branch then verifies the inspection and merge requirements and asks once before changing anything.

How /done completes delivery

01 · PreflightVerify completionRequire agent-inspected, an unchanged request, mergeability, and squash support.

↓

HumanConfirm completionApprove the exact remaining request and item mutations, or stop without changes.

↓

02 · After confirmationSquash mergeRecheck the same request and merge it when it is still open.

↓

OutcomeComplete itemMove the official item to its resolved done state only after observing the merge.

/done stops on a changed or blocked request. It never modifies the delivered work, deploys, releases, retries, or invokes another workflow.

What /done does

1	Preflight	Reuse or complete the current item context, require agent-inspected, and verify the remaining completion operations for the exact request.
2	Confirm	Present the exact identities, states, merge method, and remaining mutations for one human decision.
3	Merge	Recheck the unchanged request and squash-merge it when it is still open and mergeable.
4	Finish	After observing the merged request, move the official item to done and report both results.