Access path boundary
The action starts GitHub provider initiation through Supabase only after browser-safe public config is supplied outside committed source.
Section 1.2 Provider Login Initiation
Provider authentication initiation
This authenticated-surface entry can start the verified Supabase/GitHub provider-backed access path when external public runtime config is present. Callback/session recognition and guard admission happen only after the provider return. It does not create an authenticated workspace, and no production workspace is active here.
Provider-backed access path
Supabase/GitHub initiation
No repository credential fields
No signup surface
No production workspace
No application-data persistence
No public NEXUS runtime
Session recognition required
Returning from the provider can be classified by the callback/session precondition, but guarded entry depends on recognized Supabase session state.
No product maturity claim
No backend, database, RLS, tenant isolation, billing, monitoring, model API execution, or production SaaS claim is created by this path.
Return to Preview Workspace