`agentLinkTerminalColumns` was uncovered on the #3115 map. The existing
case uses `todo` and `in-progress`, so the terminal skip is never the
deciding branch.
## The corrected fixture is the lesson
An earlier attempt of mine put the card in a renamed **wip** lane and
stayed green when blinded — **correctly**. Such a card is caught by the
wip∪review set first, so the terminal resolver never decides anything.
The card has to rest in a renamed **complete** lane for this guard to be
the one that matters.
That is the same class as my two discards on the branch-conflict sweeps:
**the fixture has to reach the branch the resolver gates.** A test can
exercise the sweep, pass, and still never touch the line under test.
## What the literal costs
A finished task's agent is not skipped, so the sweep **unlinks an agent
from a task that completed normally** — churn on a row that needed no
repair, and a lost link if that agent was about to be reused.
## Observable
Asserts `syncExecutionTaskLink` — the action the guard prevents — rather
than a return value, per the rule from #3202.
## Measured
421 pass; blinding `agentLinkTerminalColumns` fails exactly this case.
**21 of 26 pinned** across 20 merged PRs.
## Still open, with the obstacle recorded
`reclaimHoldColumns` / `reclaimReviewColumns` resist: both audit paths
in that sweep emit the same `branch:auto-reclaim` type, differing only
by a `trigger` string the branch-level scan also produces, so no
observable I found isolates the bucket resolvers from the branch scan.
`agentParkedColumns` needs a fixture where parked-ness changes the
outcome — mine forced the proof true via a fresh run.
## Verification
`self-healing.test.ts` **421 passed** · `pnpm test:gate` full pass ·
lint — green.
23403e1426