From b3040ac0383bc887e75751a6e892ed2b21d8680b Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 2 Nov 2026 18:23:24 +0000 Subject: [PATCH] docs(glitch-invaders): say how to make the Sentry token The token needs read scopes an organization token can't carry, so the README now names an internal integration in the game's own org. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01ViFVZZzWH6bDpJkxdRGgty --- challenges/glitch-invaders/README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/challenges/glitch-invaders/README.md b/challenges/glitch-invaders/README.md index 0928aa2..771d120 100644 --- a/challenges/glitch-invaders/README.md +++ b/challenges/glitch-invaders/README.md @@ -112,7 +112,11 @@ version: | Auth | `bearer`, token `SENTRY_AUTH_TOKEN` | | Host | `sentry.io` | -The token needs the `event:read`, `project:read`, and `org:read` scopes. The +The token needs the `event:read`, `project:read`, and `org:read` scopes, in +the org the game reports to. Make it with an internal integration under +**Settings > Custom Integrations** in that org, with Project, Issue & Event, +and Organization set to Read. An organization token won't do: its scopes are +fixed for CI and lack these. A token from another org gets `403`. The station also needs a boothstrap that sets each `vault_services` credential in the challenge's hooks. Release `0.1.0` predates that, so on it the challenge gets no token and runs in demo mode.