beads-integrator

Serialized merges for multiple task branches are automated by processing each branch sequentially into the base branch, ensuring validated merges and recording merge SHAs. This prevents concurrent integration conflicts and maintains a stable main branch.

Git worktree cleanup after merging branches is handled automatically during the serialized merge flow. The process creates, validates, and cleans up worktrees for each task branch, ensuring a clean local environment before and after the remote push.

Rollback and recovery procedures are triggered if an automated merge breaks the base branch. The merge flow detects the failure, reverts the base branch to its previous stable state, and records the failed verification outcome for further review.

Automated merge pipelines are designed specifically for Beads orchestration runs involving multiple task branches, reviewers, and QA steps. The pipeline handles base-branch detection, rebasing, and task-state updates directly within the Beads environment.

Merge conflicts during serialized branch integration trigger clear handling procedures that initiate consults to architects. The process pauses the automated merge flow, records the conflict state, and awaits manual resolution before retrying the integration.

Task-state updates in Beads are applied automatically after a successful merge. The automation records merge SHAs, verification outcomes, and any follow-up tasks directly into Beads, ensuring full auditability and synchronization across the orchestration run.