switch to driver immediately if account exists; only ask name on first time

- prompts/system_new_user.md: try switch_to_driver first, only collect
name on error (no account yet)
- prompts/system_passenger.md: same fix — previously told AI to always
ask for name before switching

prompts/system_new_user.md

@@ -1,3 +1,3 @@
 Welcome new sender. Ask: travel as passenger (search/book) or work as driver (publish trips)?
 - To travel: switch_to_passenger (name optional, ask only if offered). Don't ask name before switching.
-- To drive: collect full name -> create_driver_account(name) -> switch_to_driver. Never call switch_to_driver before account exists.
+- To drive: try switch_to_driver. If no account exists (error), collect full name -> create_driver_account(name) -> switch_to_driver.

prompts/system_passenger.md

@@ -1,6 +1,6 @@
 - search_trips as soon as the user mentions a departure or destination. You do not need all details — the tool accepts partial info. Only ask a follow-up if neither departure nor destination was mentioned.
 - When search_trips finds matches, trip cards are sent to the user automatically along with a prompt to choose one. Do NOT add any text after calling search_trips — the tool will handle the response.
-- When the user replies to a trip card, immediately call create_booking_lead — trip_id is auto-detected and seats default to 1. Do not ask for seat count or other details.
-- Booking leads are pending — seats not reserved.
-- After successful create_booking_lead, tell the passenger the driver's phone number from driver_phone so they can contact the driver directly.
-- To drive: switch_to_driver. If no account: name -> create_driver_account -> switch_to_driver. Never before account exists.
+- When the user replies to a trip card, immediately call select_trip — trip_id is auto-detected and seats default to 1. Do not ask for seat count or other details.
+- Selections are not reservations — seats are not held.
+- After successful select_trip, tell the passenger the driver's phone number from driver_phone so they can contact the driver directly to arrange the booking.
+- To drive: try switch_to_driver. If no account exists (error), collect full name -> create_driver_account(name) -> switch_to_driver.

supabase/migrations/202607060001_rename_booking_to_selections.sql

@@ -0,0 +1,35 @@
+-- rename booking_leads table to trip_selections
+alter table if exists public.booking_leads
+  rename to trip_selections;
+
+-- drop old check constraint
+alter table public.trip_selections
+  drop constraint if exists booking_leads_status_check;
+
+-- migrate existing 'confirmed' rows to 'pending' (no confirmation flow anymore)
+update public.trip_selections
+  set status = 'pending'
+  where status = 'confirmed';
+
+-- add new constraint without 'confirmed'
+alter table public.trip_selections
+  add constraint trip_selections_status_check
+    check (status in ('pending', 'cancelled'));
+
+-- rename indexes
+drop index if exists public.idx_booking_leads_customer;
+create index idx_trip_selections_customer
+  on public.trip_selections(customer_id, created_at desc);
+
+drop index if exists public.idx_booking_leads_trip;
+create index idx_trip_selections_trip
+  on public.trip_selections(trip_id, created_at desc);
+
+-- rename trigger
+drop trigger if exists set_booking_leads_updated_at on public.trip_selections;
+create trigger set_trip_selections_updated_at
+  before update on public.trip_selections
+  for each row execute function public.set_updated_at();
+
+-- rename rls
+alter table public.trip_selections enable row level security;