Add token revocation semantics: revocation immediate, extension popup cache TTL 5min can look alive, session-cookie fallthrough for same-browser requests
...
Owner reported a revoked token (657738c3459fe543, Chromium PC) still working. Verified: revocation is effective (revoked_at set, last_used_at frozen, audit shows access.failed bearer:gcr_657738c3 after revocation, empirical Bearer request → 401). Apparent 'still works' = extension popup cache (TTL 5 min) and/or session-cookie fallthrough in actor_from_request for same-browser requests. Documented semantics.