saridsa2 a576552f8a feat: pre-fetched caller context replaces tool-based patient lookups ...

- CallerContextService: fetches lead profile, appointments, call history,
  activities in parallel. Caches in Redis (5 min TTL). Renders as
  human-readable KB section — no UUIDs exposed to the LLM.
- Caller resolution controller: prewarms context cache on resolve
  (fire-and-forget) so the AI stream has a cache hit.
- AI chat stream: injects caller context into system prompt KB instead
  of raw Lead ID. LLM answers patient questions from context, no tool
  calls needed for current caller data.
- Eliminates UUID hallucination: LLM never sees leadId or patientId,
  can't pass wrong ID to wrong tool parameter.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-17 09:56:18 +05:30

..

caller-context.service.ts

feat: pre-fetched caller context replaces tool-based patient lookups

2026-04-17 09:56:18 +05:30

caller-resolution.controller.ts

feat: pre-fetched caller context replaces tool-based patient lookups

2026-04-17 09:56:18 +05:30

caller-resolution.module.ts

feat: pre-fetched caller context replaces tool-based patient lookups

2026-04-17 09:56:18 +05:30

caller-resolution.service.ts

fix: set platform name on every entity create — patients/appts/calls/etc no longer "Untitled"

2026-04-15 09:32:28 +05:30

caller-resolution.spec.ts

test: unit tests for Ozonetel integration, caller resolution, team, missed calls

2026-04-10 09:32:40 +05:30