diff --git a/.changeset/fn-8910-premerge-remediation-hold.md b/.changeset/fn-8910-premerge-remediation-hold.md new file mode 100644 index 0000000000..03f07ff72b --- /dev/null +++ b/.changeset/fn-8910-premerge-remediation-hold.md @@ -0,0 +1,7 @@ +--- +"@runfusion/fusion": patch +--- + +summary: Review REVISE now schedules fixes for shared-branch tasks in auto-merge-off projects. +category: fix +dev: Narrows hasPreMergeRemediationAutoMergeHold; logs both executor recovery-budget refusals and guards the resume router. diff --git a/docs/workflow-steps.md b/docs/workflow-steps.md index 24192398b4..3ed4a0d613 100644 --- a/docs/workflow-steps.md +++ b/docs/workflow-steps.md @@ -757,6 +757,8 @@ Authoritative cutover now depends on existing/current parity summary evidence, n If a task is found in `in-review` with failed pre-merge workflow results and no active executor, self-healing can auto-revive it by replaying the same remediation send-back flow. Generic optional gates use the resolved workflow/project budget; built-in Plan Review and most Code Review groups are unbounded unless workflow settings or node config set a numeric cap. Compound Engineering's Code Review node supplies a two-pass cap. +Project-level `autoMerge: false` gates **merge admission**, not pre-merge remediation: Plan Review replans, Code Review/optional-gate fixes, required-artifact recovery, and failed-step revival remain available for shared-branch members and standalone tasks. Only an operator-authored task-level auto-merge Off fences those remediation seams. Every such hold or revision-budget refusal is recorded on the task; when a fire-and-forget remediation node cannot schedule after implementation is complete, the card stays visibly parked in its resolved review lane with its merge blocker rather than bouncing back to planning. +