Every 401/403 was answered by signing in again on the spot. For a login that
works but may not list the account's venues (media@waters.church at North
Attleboro got 403 on /venues), that was a successful sign-in on every 1s poll
-- the pattern that had just got another Resi account locked.
- A refusal straight after signing in is a permission, not an expired
session: it is held off like a failed login, with the message "This Resi
login isn't allowed to see its venues (403) — ask a Resi admin for access".
Only a session over a minute old is renewed.
- 429 on any request holds off too, not only on the login.
- The players cache-bust fallback no longer drops the parameter for good on a
401/403/429, which are about the login rather than the parameter.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
christianandClaude Opus 5.5
79d3237328