task-closeoutlisted

# Task closeout Closeout confirms that the relevant task set is actually complete, records durable evidence, and turns repeated process friction into follow-up work or skill improvements. If the remaining request is cleanup of an accepted, integrated worktree, follow the worktree cleanup lifecycle and human checkpoint in `agenticloop/AGENTIC_LOOP.md`. Cleanup does not replace closeout evidence or reopen accepted implementation. Run closeout: - for each configured group when `.agenticloop/project.md` says `group_closeout: true`, or - when a human-identified task set or work unit finishes, including in flat projects. Closeout has two ordered parts. **Closeout preparation** may begin once covered tasks are accepted; it performs only the conditional source-plan synchronization below so that any permitted plan edit can be included in the final candidate. The **final closeout gate** runs after that resulting candidate is integrated or frozen and, when enabled, certified. It is a verify-and-mark gate and does not produce a separate summary artifact. The durable record is the per-task inline summary plus the backend (task files or GitHub issues/PRs); final closeout confirms that record is complete and posts a status marker. ### Conditional source-plan progress synchronization This section is the canonical procedure for source-plan progress synchronization during closeout preparation. It is deliberately conditional: closing a task does not authorize inventing a plan status conv