Access path status
The action starts GitHub provider initiation through Supabase only after browser-safe public config is supplied outside committed source.
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.
The action starts GitHub provider initiation through Supabase only after browser-safe public config is supplied outside committed source.
Returning from the provider can be classified by the callback/session precondition, but guarded entry depends on recognized Supabase session state.
This path does not create a production workspace, operational release system, live model-execution claim, or customer deployment claim.
Return to Workspace Preview