feat: persist AI conversation state in DB and fix LangGraph flow bugs

- Replace in-memory Maps in aiHandoffStore with DB-backed async functions
  using new patient_conversation table (stage + aiHandoff per patient)
- Add afterHoursEnabled to ai_settings table (persists across restarts)
- Fix runtime crash in reschedule-graph: mon/tue/wed variables were out
  of scope in the next-week fallback branch (ReferenceError)
- Wire rescheduleGreeting and generalFallback chat templates through to
  LangGraph nodes so user-configured messages take effect
- Add otherNode to reminder-graph to handle unclassified patient replies
  (e.g. "I want another appointment") and route to booking flow
- Fetch chatTemplates once per webhook request instead of per stage

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

packages/db/shared/schemas/findFirstOrThrowAiSettings.schema.ts

@@ -13,6 +13,7 @@ export const AiSettingsFindFirstOrThrowSelectSchema: z.ZodType<Prisma.AiSettings
     id: z.boolean().optional(),
     userId: z.boolean().optional(),
     apiKey: z.boolean().optional(),
+    afterHoursEnabled: z.boolean().optional(),
     user: z.boolean().optional()
   }).strict() as unknown as z.ZodType<Prisma.AiSettingsSelect>;
 
@@ -20,6 +21,7 @@ export const AiSettingsFindFirstOrThrowSelectZodSchema = z.object({
     id: z.boolean().optional(),
     userId: z.boolean().optional(),
     apiKey: z.boolean().optional(),
+    afterHoursEnabled: z.boolean().optional(),
     user: z.boolean().optional()
   }).strict();