Root cause found and fixed: the repo secret SENTRY_ORG (last set 2026-07-22,
same day as the stale SENTRY_PRODUCT_INTELLIGENCE_TOKEN from AGE-497's root
cause #1) held a stale org slug, not 'vibetechnologies'. Every org-scoped
Sentry API call 403'd in CI while /auth/ (identity-only, not org-scoped)
kept succeeding — which is what made it look like a network/IP-level block
instead of a bad secret value. Confirmed by hardcoding org=vibetechnologies
in the probe from the same runner/IP: 200. Fixed by resetting the SENTRY_ORG
secret to vibetechnologies; the real 'Sentry noise-gate report' workflow now
succeeds (run 32222675122).
Co-Authored-By: Paperclip <noreply@paperclip.ing>
709aa97bad