pocket-closing
Pocket Closing
The closing stage of the Pocket pipeline. Use it when the user asks to close a reviewed phase or plan; an explicit end-to-end request that includes closeout also authorizes this stage. Reconcile verdicts against the execution log, advance only a passing phase, and append a readable record of that phase. A passing verdict alone is not authorization to close.
Core principle: Current verdicts decide. pocket-closing never re-reviews or overrides them; it reconciles the task verdict artifacts with log.json, advances only a passing phase, and records what the sources support. No current clean verdict, no phase advance.
Core v4 lifecycle boundary
pocket-closing is a Core workflow. Core keeps plan closure local-first: log update and log close commit lifecycle state and neutral events with CLI CONTRACT=3 and lifecycle schema 1 for unpatched documents or 2 for stacked plans. Core does not call gh, does not merge pull requests, and does not close issues. An optional, compatible Enterprise adapter may later reconcile the plan-closed event. Closing locally succeeds without Enterprise, and pending events remain available for replay.
If a projection write needs recovery, run pocketto-pi lifecycle repair <spec_dir> --json --contract 3 before pocketto-pi lifecycle drain <spec_dir> --json --contract 3. Repair preserves task progress and fails closed when task state is unrecoverable; drain replays pending events in order without creating events. Active v3 plans with progress stay on v3 and are never silently converted.