Fix Supabase auth LockManager error in restricted browsers

[cursor]

Changes

• Configure the shared Supabase clients to disable unused Supabase Auth session behavior.
• Add a no-op Supabase Auth lock so Auth initialization does not call navigator.locks.request() in browsers where Web Locks is exposed but disallowed.
• Add a focused Jest test covering the auth-safe client options and singleton behavior.

Testing Criteria

• yarn test src/lib/supabase.test.ts --runInBand
• yarn eslint src/lib/supabase.ts src/lib/supabase.test.ts (passes with existing repository-wide warnings)
• yarn tsc --noEmit --pretty false (blocked by pre-existing SVG module declaration errors in src/icons/index.ts)

Notes

• Sentry issue: TASKS-8C / Linear: OUT-3771.
• No dependency or configuration changes required.

Impact & Surface Area of Change

• Affects the shared Supabase client setup used by realtime subscriptions and storage helpers.
• The app does not use supabase.auth; disabling Supabase Auth persistence/URL detection and replacing the lock avoids a browser-only crash while preserving realtime/storage usage with the anon key.

  

[linear-code]

OUT-3771

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	May 21, 2026 5:06pm