Proposed work: add CI assertion that review-bounty claim scripts refuse saturated award capacity

[yanyishuai]

Related bounty or source issue

Bounty #932
Related: #797 / PR #1188 (review-bounty claim saturation checks)

Problem

Review bounties (#933/#1009) attract many /claim comments after award capacity is exhausted. Maintainers and claimants waste time on saturated rounds. PR #1188 adds saturation checks in scripts, but there is still no proposed maintainer-facing CI/docs guard that documents running the saturation check before posting additional review claims on a round.

Evidence

Live review bounties #933 and #1009 show dense claim comment streams. Open PR #1188 implements claim-saturation helpers for review bounties. A small docs/CI wiring proposal would make that check discoverable for contributors before they spam /claim.

Proposed work

Document and optionally wire a read-only CI or contributor checklist step that runs the review-bounty saturation helper against a configured bounty issue number and fails (or warns) when effective award capacity is already exhausted.

Expected value

Reduces noise on saturated review rounds and makes capacity status visible before new claim spam.

Reference tier

25-100 MRWK: small docs, typo, reproduction, triage

Acceptance or test notes

• Docs mention the saturation helper and when to run it
• Optional CI/job is opt-in or docs-only if maintainers prefer not to add CI cost
• Does not change payout execution

Duplicate search

#797/#1188 implement the helper; this proposal is specifically about discoverability/CI wiring for contributors, not re-implementing saturation logic.

Out of scope

Changing claim acceptance rules, treasury proposals, or auto-closing review bounty issues.