Auth user signs

Project psgehcgzoxongohdfzen is reproducing PGRST303 — JWT issued at future. A newly created and confirmed Auth user signs in normally, but the first authenticated PostgREST/Data API read (athlete_journey_facts) fails immediately with PGRST303. We do not mint or modify JWTs and have not added client-side retries or delays. The project’s database permissions/RLS have been independently verified. This appears consistent with the currently open Supabase JWT rejection incident. Can you confirm whether this project is on an affected PostgREST deployment and whether the targeted stale-time-cache fix has reached, or can be applied to, this project?