build-merge-gate-orchestration

Build and merge gate orchestration coordinates end-to-end gate workflows for monorepos and multi-issue slices by applying parallel or sequential execution rules with Git worktree isolation to ensure ready-to-merge decisions with aligned evidence.

Git worktree isolation is a mechanism that separates runtime QA and merge readiness checks into isolated working directories, needed when coordinating gates across multiple issues to prevent branch conflicts and ensure traceable evidence collection.

To run merge readiness checks, execute Gate 5 for build handoff, Gate 5.5 for runtime QA, and Gate 6 for local merge readiness reviews in sequence to enforce standardized gating and produce traceable PR packaging.

Yes, build handoff orchestration supports parallel execution for independent slices by applying independence checks across issues and PRs, while sequential execution rules apply when dependencies exist between gates.

Merge gate orchestration applies to slice-based issues across repositories by enabling consistent gating, standardized evidence collection, and traceable PR packaging for ready-to-merge decisions across distributed codebases.

Gate orchestration limitations depend on independence checks between parallel and sequential execution rules; if slices have unresolved dependencies, automated prompts for Gate 5, 5.5, and Gate 6 cannot fully validate merge readiness without manual intervention.