Opus finding
Override fork path skips the 4-week dedup check, allowing repeated weekly features
lowbughigh
- skills/contributor-spotlight/SKILL.md:102-108
- skills/contributor-spotlight/SKILL.md:240-244
The Constraints section states the 4-week dedup is invariant ("Even if the same fork is the top POWER candidate two weeks running, rotate"). However, the override branch in step 3 only checks bucket membership; it does not consult `contributor-spotlight-history.json`. An operator (or scheduled run with a sticky `var`) can re-feature the same fork every week, violating the documented constraint and the dedup history's purpose. This is also a maintainability/contract gap because the spec is internally inconsistent.
Recommendation
Either (a) apply the 4-week dedup to the override path as well and emit `SPOTLIGHT_BAD_OVERRIDE: recently featured` when violated, or (b) explicitly document that override bypasses dedup and add a warning in the article/notification.