feat(voice): per-restaurant voice_agent_name

[ByteStreams-AI]

Summary

• Adds nullable voice_agent_name column on restaurants (migration 0014). When set, the prompt instructs the LLM to introduce itself by this name verbatim if asked; null falls through to whatever the model invents (currently "Ruth" on Sui's calls).
• Threads through RestaurantLookup → buildPromptContext → PromptContext → PROMPT_TEMPLATE (one new conditional line at the top of the persona section).
• Pronunciation is handled by storing what should be spoken — operators spell phonetically ("My-tay" instead of "Maite") or embed inline SSML phoneme tags for exact IPA. Both work in ElevenLabs.
• Seeds Sui's Sushi with "Maya" so local + cloud test calls answer with a stable name.
• Backfills the canonical schema doc with voice_id (was added in 0013 but never reflected) so the doc stays the source of truth it claims to be.

Test plan

• pnpm ci:fast — 280/280 (one new prompt-template test covering set / phonetic-respelling / whitespace-only-treated-as-null)
• Migration applied locally; types regenerated
• After deploy + cloud db push: update restaurants set voice_agent_name = 'Maya' where slug = 'suis-sushi', place call, ask "what's your name?", confirm "Maya"
• Set voice_agent_name = 'My-tay' on a test restaurant, confirm ElevenLabs pronounces it that way

Operational note

The cloud deploy workflow does NOT push migrations (known gap, tracked in PR #16). After this merges, run pnpm supabase db push --linked against the cloud project before relying on the new column — select voice_agent_name from restaurants limit 1 to verify.

🤖 Generated with Claude Code

Greptile Summary

Adds a nullable voice_agent_name column on restaurants and threads it end-to-end — migration → DB types → RestaurantLookup → buildPromptContext → PromptContext → PROMPT_TEMPLATE — so operators can give the voice agent a stable, pronounceable name. The custom Mustache renderer's existing isTruthy guard correctly treats null and whitespace-only values as falsy, preventing the Identity section from rendering when no name is configured.

Confidence Score: 5/5

Clean, well-scoped feature addition — safe to merge after the manual cloud migration step noted in the PR.

No P0 or P1 findings. The rendering logic is correct (non-greedy section regex + interpolate pass handles two {{#agent_name}} sections cleanly), the migration is idempotent, types are in sync, and all branching paths are covered by tests.

No files require special attention.

Important Files Changed

Filename	Overview
packages/shared/src/voice/prompt.ts	Adds {{#agent_name}} Identity section and threads the name into the "are you a real person?" disclosure; rendering logic is correct given renderSections non-greedy regex and subsequent interpolate pass.
supabase/functions/_shared/context.ts	Selects voice_agent_name from DB, threads it through RestaurantLookup into PromptContext; straightforward plumbing with no logic issues.
supabase/migrations/0014_voice_agent_name.sql	Adds nullable voice_agent_name column with add column if not exists guard; clean and idempotent.
packages/shared/test/voice/prompt.test.ts	New tests cover named/unnamed/phonetic/whitespace-only cases and the "are you a real person?" disclosure variant; good coverage of the feature's branching logic.
packages/shared/src/voice/types.ts	Adds `agent_name: string
packages/shared/src/supabase/types.ts	Adds `voice_agent_name: string
supabase/seed.sql	Seeds Sui's Sushi with voice_agent_name = 'MeSee'; code and tests are internally consistent.
developer/dialtone-schema.sql	Backfills voice_id (added in 0013 but missed here) and adds voice_agent_name; keeps the canonical schema doc in sync.

_{Reviews (3): Last reviewed commit: "feat(voice): swap seed to MeSee + streng..." | Re-trigger Greptile}