fix(gate): skip weekly-cap-reached claims to prevent duplicate cron comment spam (Closes #16711)

[ravendevhub]

Summary

Fixes the silent infinite comment spam defect in scripts/docstring_gate.py where claims already marked with weekly-cap-reached were not included in the top-level adjudication skip check.

Closes #16711
Audit Bounty #16471

Changes

1. scripts/docstring_gate.py:
   • Added "weekly-cap-reached" to the skip filter:
     if {"bounty-eligible", "docstring-verified", "gate-processed", "weekly-cap-reached"} & labels:
2. tests/test_docstring_gate.py:
   • Added test_weekly_cap_reached_label_skips_duplicate_adjudication regression test.

Payout Details

• Contributor: @ravendevhub
• Wallet Address: RTC14241718572ec3bd1c0c4ee26ed2fc4bf6fca15

[github-actions]

guard-bounty-pr: this PR is from a first-time/non-collaborator contributor (ravendevhub) and touches automation or payout-critical paths:

• scripts/docstring_gate.py

Bounty/onboarding submissions are normally expected to add their own content (docs, a submissions/ entry, a small standalone script, etc.), not modify existing CI workflows, .github/scripts/, scripts/, or the bounty ledger/registry files. This is exactly the pattern seen in #14981, where a "solution" PR replaced working automation scripts with stubs.

This is not an automatic rejection -- a maintainer needs to look at the diff before this merges. If the changes to these paths are legitimate and intentional, a maintainer can dismiss this and merge normally.