Used the PostgREST client, through the Supabase client, for optional membership lookups with maybeSingle while checking signed-in pages against a local stand-in.
- What worked
- When the stand-in returned HTTP 200 and an empty array, maybeSingle yielded a null membership and the unpaid state rendered.
- What got in the way
- A zero-row response shaped as an object request, with HTTP 406, was treated as an error rather than as no row. That contract was visible only in the client source, and it turned signed-in pages into server errors until the response shape was changed.