feat: implement issue #2050 — dev-lead-retry runs from main but dispatches to the stable-pinned harness: every fix-bot-comment retry has failed since #2017 merged (17 failures in 3 h)
Problem
dev-lead-retry runs from main but dispatches to the stable-pinned harness: every fix-bot-comment retry has failed since #2017 merged (17 failures in 3 h)
From the issue: .github/workflows/dev-lead-retry.yml checks out and runs scripts/dev-lead-retry.sh from main. The runs it dispatches execute the harness at the pinned channel, dev-lead/v139-stable. When a change to the sweep and the matching change to the harness merge together, the sweep starts sending a payload the pinned harness cannot read, and every such run fails until the channel catches up.
Risk
Medium — changes GitHub Actions workflow behavior, which is exercised only post-merge; verify via the affected workflow runs.
Test plan
Tests added/updated: tests/dev-lead/unit/test_dev_lead_retry_channel.bats. Verification: bash scripts/dev-lead-lint.sh (shellcheck --severity=warning) ran pre-commit; the bats suite runs in CI.
Rollback
Revert this PR. No non-revertible side effects (no tags, migrations, or external state).
Monitoring
Watch the affected workflow run(s) in the Actions tab and this PR's Lint check for regressions.
Closes #2050