Sentry plugin: API requests 404 due to egress routing

[sentry-junior]

All Sentry CLI API requests from the sandbox return 404. Requests to sentry.io/api/0/... and us.sentry.io/api/0/... hit the Vercel-hosted frontend (Server: Vercel) instead of the Sentry API backend. Every CLI command fails — sentry org list, sentry issue list, sentry explore, etc.

Evidence:

• curl -D- https://sentry.io/api/0/organizations/ returns 404 with Server: Vercel, Allow: OPTIONS
• First redirect from https://sentry.io/api/0/ points to http://sentry.io:8000/api/0/ (port 8000, HTTP) — suggests DNS or proxy resolution is landing on the wrong endpoint
• The injected SENTRY_AUTH_TOKEN appears to be a placeholder (host_manag..., 23 chars) rather than a real sntrys_ token
• No SENTRY_URL or HTTPS_PROXY env vars are set; CLI defaults are all unset

Likely root cause (medium confidence): The sandbox egress path resolves sentry.io to a Vercel frontend endpoint rather than routing API traffic to the Sentry API backend. The auth token injection also appears broken, which may be a separate issue or the same misconfiguration.

Action taken on behalf of David Cramer.