v0.26.3

Dely 0.26.3 makes the remediation routes performable again. Since 0.26.1 the helper releases every worker at settlement — before Control reads the verdict the batch carries — so the Remediation section's routes ("the original implementer" fixes, "the reviewer that raised the finding" re-reviews, a replacement reviewer "only when the original reviewer is unavailable or contested") could no longer be followed as written: the replacement condition held vacuously on every remediation, and the implementer had no replacement path at all.

• The original parties are defined by pin and briefing, not by session. Remediation is a fresh dispatch on the implement pin briefed with the original task prompt, the implement handoff, and the finding as the reviewer wrote it; the scoped re-review is a fresh dispatch on the review pin briefed with the original review prompt, the raised finding's handoff unedited, the fix-only diff, and the full candidate diff. Those workers are the original implementer and the reviewer that raised the finding for every rule in the skill.
• The anti-shopping guard moves to the briefing. A re-review not briefed with the raised finding's handoff is not the scoped re-review; the briefing files live in the Run's folder, so it is checkable afterwards. The vacuous "unavailable or contested" clause is deleted.
• No helper change. Release at settlement stands; this is a protocol-text release.

The delivery ran its own new route: its first review returned CHANGES_REQUESTED (the new decision record claimed a baseline measurement exact Git history contradicts), the fix was a Control amendment, and a fresh same-pin reviewer briefed as above reproduced the finding and accepted.

Decision record: docs/decisions.md, section 2026-10-12, which also closes the friction recorded inside the 2026-10-10 release-settled-workers record.