integrate

To verify cross-task integration, you merge parallel worktree branches into a feature branch using a parallelization branch map, which stops on any merge conflicts. The process then runs integration and security reviewers to produce file:line findings before pushing to CI.

The best way to gate CI is to require explicit user approval after integration and security reviewers finish producing file:line findings. Only after you approve the integration review can the combined branch optionally push to CI and present any failures for generating fix tasks.

Yes, merging parallel worktree branches requires approved design, structure, and parallelization branch map artifacts. These documents ensure multiple task implementations merge cleanly and cooperate correctly across interfaces before meeting integration standards.

Interface mismatches found during cross-task integration review are converged into fix tasks routed back through the pipeline. The integration and security-integration reviewers produce actionable file:line findings to guide these required fixes.

CI failures are presented directly after the push and generate CI-specific fix tasks that must pass before acceptance. This ensures the combined worktree branches meet all integration and security standards before any production change.

You should avoid automated worktree merge if you lack approved design, structure, and parallelization branch map artifacts, or if your feature does not require combining multiple parallel task branches validated by integration and security reviewers.