Repository navigation

fix(#2086): gate each dev-lead retry payload on the target repo's pinned parser - #2088

Merged

don-petry merged 10 commits into

mainfrom

dev-lead/issue-2086-20261009-0347

Oct 9, 2026

Merged

fix(#2086): gate each dev-lead retry payload on the target repo's pinned parser#2088
don-petry merged 10 commits into
mainfrom
dev-lead/issue-2086-20261009-0347

Commits on Oct 9, 2026
- feat: implement issue #2086 — dev-lead-retry: resolve the dev-lead channel pin per target repo, not once for the whole sweep
  don-petry
  committed
  7d496c4
- Merge branch 'main' into dev-lead/issue-2086-20261009-0347
  don-petry
  authored
  18e7ff3
- fix(reviews): capture command-substitution status before branching in channel gate
  
  don-petry
  and
  claude
  committed
  d732c64
- Merge branch 'main' into dev-lead/issue-2086-20261009-0347
  don-petry
  authored
  9ab9b73
- Merge branch 'main' into dev-lead/issue-2086-20261009-0347
  don-petry
  authored
  77b9637
- Merge branch 'main' into dev-lead/issue-2086-20261009-0347
  don-petry
  authored
  30b530e
- Merge branch 'main' into dev-lead/issue-2086-20261009-0347
  don-petry
  authored
  c74b251
- fix(#2086): gate each retry payload on the target's pinned parser, not whole repos
  
  donpetry-bot
  and
  claude
  committed
  2021740
- fix(#2086): a contents 404 means 'no dev-lead.yml' only when the repo itself is readable
  
  donpetry-bot
  and
  claude
  committed
  136ccf1
- fix(#2086): keep the gate's cache in per-sweep files so it survives subshells
  
  donpetry-bot
  and
  claude
  committed
  47348db