Nightly bump sweep starves entries in the tail of marketplace.json (max-bumps cap exhausted before reaching them) — forgeproof stale since 07-07

The forgeproof entry is pinned at d71376c while upstream HEAD has been c204ea9 since 2026-07-07 (validate-clean — claude plugin validate .claude-plugin/plugin.json passes at HEAD). No bump(forgeproof) PR or branch was ever created, it's not in freeze-shas.txt, and the entry shape is standard.

Root cause appears to be starvation: bump.sh iterates entries in file order and stops at max-bumps (default 30). All 89 bumps merged 07-09→07-12 fall in the 42crunch→design-is-code-plugin range; daily churn among early entries exhausts the cap before discovery reaches later ones (forgeproof is at index 836 of 2248). This affects every entry in the latter part of the file, not just ours.

Immediate ask: a targeted dispatch (gh workflow run bump-plugin-shas.yml -f plugin=forgeproof). Longer-term: consider stalest-first ordering, a rotating start offset, or a raised cap so the tail can't starve indefinitely.

Read bump.sh and the bump-plugin-shas.yml workflow, then inspect forgeproof in marketplace.json and its position relative to the max-bumps limit; check freeze-shas.txt as described. Reproduce the file-order starvation and compare the proposed dispatch or scheduling approaches. Done means forgeproof is updated and later marketplace entries can be reached without indefinite starvation.

Escrito por el modelo de indexación a partir del texto del issue.