Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" is a real answer.
1GitHub App propflow-agent-smith cannot read Actions variables (HTTP 403 on actions/variables/CI_RUNS_ON, verified live 2026-10-06). Add 'Variables: read' to the App, or keep the hourly fallback to the shared gera-propflow account?
In plain terms. Smith's new GitHub identity is not allowed to read one setting, so once an hour it borrows the shared account again — should Gera give it that one permission?
Why, and what was tried
The session raising this recommends: Give the App permission to read Actions variables The App exists so Smith's reads stop spending the shared account; a permanent hourly fallback is a hole in that, and today's 07:00Z canary page was this exact 403 Tried first, unsuccessfully: Verified the App token reads commits/release fine but gets HTTP 403 on the Actions variable (both read live 13:0xZ); the per-call fallback from #822 fires hourly (5 worker-log receipts 09:00–13:00Z). Only the App owner can change its permissions, so no Smith code change closes it.