consensus-loop:merge

To squash-merge a git worktree, the workflow validates the worktree context, enforces pre-merge checks, and generates a standardized, structured commit message to finalize work as a clean, single-commit history.

The best way to finalize a git branch after audit consensus is to apply a squash-merge that completes the retrospective phase and consolidates all worktree commits into one structured commit for full auditability.

You should use a squash-merge for git worktree integration when you need to finalize work after an audit consensus and retrospective completion, ensuring a clean history with a standardized commit message for traceability.

Yes, this squash-merge workflow is phase-aware and requires retrospective completion and audit consensus before merging the worktree, ensuring that pre-merge validation gates are successfully passed.

During a worktree squash-merge, the workflow enforces pre-merge checks by validating the worktree context and verifying phase-aware execution aligned with retrospective gates and consensus status before creating the structured commit.

To generate a standardized commit message for a squash merge, the workflow automatically creates a structured commit during the worktree integration, ensuring end-to-end auditability and a clean single-commit history.