Is there an existing issue for this?

• I have searched the existing issues

What happened?

Issue Overview
The function fails because environment variables (VEXA_API_KEY, SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY) return undefined when Deno is not run with the --allow-env permission flag. This causes immediate failure in environment checks and Supabase client initialisation, making the entire bot startup process non-functional.

Steps to Reproduce
-Deploy the function without --allow-env permission
-Call the start-bot endpoint with a valid meeting URL and ID
-Check the response - returns 500 error
-Observe logs showing "VEXA_API_KEY is not set" even when variables are configured

Expected Behavior
-Function should properly access environment variables when configured
-Clear error message if permissions are missing
-Graceful degradation with helpful resolution guidance

Actual Behaviour
Function fails immediately with "VEXA_API_KEY is not set" error
All environment variables return undefined
No distinction between missing variables vs missing permissions
Complete service outage until permissions are fixed

Record

• I agree to follow this project's Code of Conduct
• I want to work on this issue