Vouch request (follow-up to #4292): 5 compatibility scrapers ready to extend the matrix

[zhangb06]

Hi — following up on #4292 (closed not_planned).

I'm a vetted contributor: my two compatibility scrapers completed a full review round with @michaeljguarino before the vouch gate went live (closed in the 2026-09-09 queue cleanup, all feedback addressed):

• Add ClickHouse Operator compatibility scraper #4240 — ClickHouse Operator: product-org icon, 3-minor kube window, fail-closed floor guard, 15 unit tests
• feat: add OpenSearch compatibility scraper and matrix #4254 — OpenSearch: chart-driven, floors pinned to immutable release tags, 248-line test suite

Since that request I've scoped 3 more ready-to-build scrapers from the open matrix bounties:

• Clusternet Hub compatibility scraper: documented coverage and contributor reward #4266 — Clusternet Hub
• Piraeus Operator compatibility scraper: source and bounty eligibility #4241 — Piraeus Operator
• Contributor program: VolSync chart compatibility scraper scope #4216 — VolSync

Each is a self-contained, review-ready PR (scraper + static/compatibilities/<app>.yaml + manifest line + unit tests) matching the already-merged conventions (product-org avatar icon, 3 latest minor kube versions, release-tag driven, fail-closed when floor > latest). I can deliver one per calendar month per the award rule, starting with whichever app is most valuable to the matrix.

Could a maintainer with write access comment !vouch @zhangb06 so I can resubmit from the existing branches? Both code branches are complete and conflict-free. Thanks for considering.