parallel-dispatch-merge

Git worktrees keep parallel feature branches isolated in separate directories, but merging them sequentially requires DAG-derived dependency ordering and per-branch quality gates to prevent integration conflicts and broken builds in main.

Sequential feature branch integration requires classifying conflicts into textual, semantic, structural, and integration categories to apply targeted resolution strategies, ensuring downstream branches merge cleanly against the updated main branch.

Enforce an explicit quality gate after each sequential merge to stop the CI workflow early when a parallel branch fails validation, attributing the failure to the correct scope and preventing downstream broken merges.

Use a scope-qualified naming convention like .wt/<agent>-<scope> to keep parallel agent worktree instances unambiguous, ensuring clear ownership and reliable cleanup after sequential merges complete.

DAG ordering matters because it ensures dependency-required branches merge first, preserving downstream correctness and preventing semantic or structural conflicts when multiple integration branches are combined into main.

Read-only nodes pass findings forward to dependent branches without requiring a merge step, allowing them to contribute analysis results to the pipeline while excluding them from the sequential squash-merge workflow.