merge-queue

Automating approved feature merges involves organizing them into per-base-branch FIFO queues and landing them in isolated merge worktrees. This ensures safe, auditable landings by processing merges sequentially and validating conflicts before finalizing.

Handling merge conflicts during automated landings requires truthful conflict reporting within isolated worktrees. The system identifies blockers during the merge process and provides recovery mechanisms to resume blocked merges after validation.

Yes, a governed feature runtime is required as a dependency. It provides the necessary environment for executing automated merge pipelines, ensuring that feature state synchronization and handoff to implement-plan state are managed durably.

Yes, blocked merge requests can be resumed. The queue processing logic includes blocker-aware recovery, allowing you to process the next merge or retry a previously blocked one after performing validation and resolving the reported conflicts.

Isolated merge worktrees improve branch management by creating dedicated environments for each merge operation. This prevents concurrent merge operations from interfering with each other, ensuring safe landings and accurate conflict detection.

State synchronization after landing an approved commit provides end-to-end traceability. It updates the implement-plan state to reflect the current merge status, ensuring the feature pipeline has a durable handoff and accurate closeout readiness checks.