claude-code - 💡(How to fix) Fix [BUG] CVP repeatedly declines homelab sysadmins — no path for infrastructure owners managing personal hardware [2 pull requests]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report
• I am using the latest version of Claude Code

What's Wrong?

CVP has declined my account multiple times despite the use case being routine homelab administration on personally-owned hardware — not security research.

The CVP form assumes the applicant is a pentester, CTF player, or researcher. Homelab operators are a distinct category: infrastructure owners managing their own servers, the same as any Linux sysadmin. This use case should not require CVP eligibility at all.

Trigger examples (all on hardware I personally own)

• Editing Loki alerting rules that reference IP-rate anomalies on my own reverse proxy
• Reading an IP blocklist config on my own OpenWRT router
• VPN config files
• Prometheus/Loki monitoring rules with words like "scanner" or "block" in names
• SSH commands to my own router

What Should Happen?

Either:

• (a) Homelab/sysadmin use is explicitly carved out from CVP requirements, or
• (b) The CVP review path correctly handles "infrastructure owner" as a valid category distinct from "security researcher"

Additional context

Related runtime false-positive report: #61185 CVP submissions: declined multiple times, no human review offered.