A sequential foreach region pinned its step count at expansion and never revisited
it, so work appended afterwards never received an instance. That is what made
named remediation unusable: `review-remediation-steps` derives fix-it steps from a
reviewer's findings and appends them to `task.steps`, and every one of them stayed
`pending` forever — the merge boundary's foreach coverage never completed and the
card terminalized with `merge-boundary-unproven`.
The region now re-reads the live step list per iteration, exactly as the existing
status probe already did, and extends its bound when the list has grown. Growth is
the ONLY relaxation: the pin still governs every step it already covers, a
shrinking list is ignored, and `pinnedStepCount + 64` stops a pathological appender
spinning the region. The worktree-isolated path keeps the strict pin, because its
instances are allocated up front.
Other workflows are unaffected by construction — with no appended steps the bound
never moves and the loop is byte-identical.
builtin:coding-ideas-v2 accordingly enables named remediation on BOTH review gates:
a rejected review now returns the card to in-progress carrying steps that name what
must be fixed, with the PROMPT.md File Scope widened to the files they touch,
instead of an unchanged checklist.
Three consecutive full runs: 122.1s, 124.5s, 122.9s of the 150s budget.
S05 and S07 stay on their original workflows: with named remediation live, S05 is
intermittent on V2 under full-lane load and S07's park oscillates instead of
settling. Both are visible, neither is shipped green.
eba8c1052d