cc-watch retry recovery — gaps carry-forward

2.1.152's triage hit a 401 (expired token) → its gap entry was marked parse_failed. Then the next cron tick wiped it, so cc-triage --retry-failed found an empty file and could never recover. Toggle the behavior and step the cron to see why — and what the fix changes.

shared/cc-adoption-gaps.json (start of tick)

after cc-release-watch + cc-triage --retry-failed