refactor(db): move call_logs aggregations into callLogStats module (#3500 slice 1)

[diegosouzapw]

#3500 (slice 1 of N) — Hard Rule #5: raw SQL out of route handlers → db/ module

First slice of #3500: the call_logs aggregation cluster. Extracts inline SQL from 3 route handlers into a new domain module src/lib/db/callLogStats.ts.

New db function	Replaced raw SQL in
getProviderMetrics	api/provider-metrics/route.ts
getSearchProviderStats, getRecentSearchLogs	api/search/stats/route.ts
getSearchAggregateStats, getSearchProviderCounts	api/v1/search/analytics/route.ts

Query semantics are byte-identical (pure move); the new module is re-exported from localDb.ts (it's a NEW domain module, so re-export is correct per Rule #2 — unlike the legacy internal modules in #3499).

Validation

• ✅ gate: [check-db-rules] OK — KNOWN_RAW_SQL 15 → 12 (only the 3 fixed removed)
• ✅ 3 routes: 0 raw-SQL markers remaining
• ✅ TDD test db-call-log-stats-3500.test.ts: 6/6 (seeds temp SQLite, asserts each aggregation; resetDbInstance() teardown per PII-Learnings deps: bump eslint from 9.39.2 to 10.0.0 in the development group #3)
• ✅ typecheck:core: clean; lint: 0 errors

The other 12 KNOWN_RAW_SQL offenders (excl. the 2 external-DB cursor/kiro auto-import, which are by-design) follow in subsequent slices. Part of #3500.

[gemini-code-assist]

Code Review

This pull request refactors the database access by extracting raw SQL queries from three route handlers into a new domain module src/lib/db/callLogStats.ts in compliance with Hard Rule #5. These queries are re-exported in src/lib/localDb.ts and covered by unit tests. Feedback on the changes suggests using "{}" as a fallback instead of "" when parsing request_summary in src/app/api/search/stats/route.ts to prevent throwing expensive syntax errors when the summary is null or empty.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Using row.request_summary ?? "" fallback results in JSON.parse("") when request_summary is null or empty, which throws a SyntaxError and triggers the catch block. Since throwing exceptions is computationally expensive, using "{}" as the fallback avoids throwing an error entirely and cleanly defaults to an empty object.

Suggested change

	const summary = JSON.parse(row.request_summary ?? "");
	const summary = JSON.parse(row.request_summary ?? "{}");