c-12-closeout

To require approval before committing code and memory changes in a git worktree, enforce an explicit approval gate during closeout. You preview proposed commits and require developer approval before applying any finalization.

Memory-ledger synchronization for code commits is the process of aligning external memory state with code changes during finalization. It ensures worktree-backed edits are verifiable and prevents state drift across code and memory contexts.

Yes, you need external-memory mode and a code-memory shared worktree to enforce commit approval gates. This closeout process operates on the worktree manager workflow and requires explicit preview and apply steps.

To prevent state drift when finalizing worktree-backed tasks, coordinate with the worktree manager to synchronize code and memory state. This ensures gate-controlled closeout aligns all contexts before finalizing the commit.

You should use an approval gate for code-memory closeout in multi-user environments when external memory governance and traceability are required. It provides auditable, explicit commit approvals to finalize worktree-backed tasks safely.