build1 publisher
One 403 among five fetches lets a nightly prune delete a repo that still exists
A refresh job builds its keep list from successful GitHub responses, so a throttled request looks exactly like a repo that was curated out of the seed. The published fix is a per-slug failure counter that suppresses the prune.
Publishers:dev.to
Reality
- Evidence58
- Adoption14
- Hype gap+10
- Incentives35
- Confidence62