Revert "Revert "feat(web): serve /usage analytics from Postgres replica""

[chrarnoldus]

Reverts #5228

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

Incremental re-review of the new commits (dedicated usage-replica pool on POSTGRES_REPLICA_EU_URL_2 plus the fixed case-insensitive is null test assertion) found no issues; the previous SUGGESTION is resolved and no memory-leak vectors were introduced (the new pool is attached via attachDatabasePool, has an error handler, and is closed in closeAllDrizzleConnections).

Files Reviewed (4 files)

• apps/web/src/lib/drizzle.ts
• apps/web/src/lib/drizzle.test.ts
• apps/web/src/routers/usage-analytics-router.ts
• apps/web/src/routers/usage-analytics-router.test.ts

Previous Review Summary (commit 8d6b79d)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 8d6b79d)

Status: 1 Issue Found | Recommendation: Address before merge

Executive Summary

Re-lands the Snowflake→Postgres replica migration for /usage analytics (unchanged from #5223); the only finding is a case-sensitive test assertion that cannot catch the regression it guards against.

Overview

Severity	Count
CRITICAL	0
WARNING	0
SUGGESTION	1

Issue Details (click to expand)

SUGGESTION

File	Line	Issue
apps/web/src/routers/usage-analytics-router.test.ts	71	not.toContain('IS NULL') is case-sensitive while drizzle emits lowercase is null, so the negative assertion always passes

Notes: scope/SQL changes were verified against packages/db schema — all joins (microdollar_usage_metadata, feature, mode) are 1:1 on primary keys, so no aggregate fan-out; all user input is parameterized (no injection paths); the organization_id IS NULL personal-scope predicate correctly replaces Snowflake's empty-string sentinel. No memory-leak vectors introduced (the AbortController/setTimeout timeout path was removed in favor of SET LOCAL statement_timeout via the pre-existing timedUsageQuery). Behavior changes (caller-supplied ISO date windows instead of day/month-aligned bounds, 500 instead of zeroed summaries when the backend is unreachable) match the intent documented in #5223.

Fix these issues in Kilo Cloud

Files Reviewed (2 files)

• apps/web/src/routers/usage-analytics-router.ts - 0 issues
• apps/web/src/routers/usage-analytics-router.test.ts - 1 issue

---

_{Reviewed by kimi-k3 · Input: 117.8K · Output: 2.8K · Cached: 135.5K}

_{Review guidance: REVIEW.md from base branch main}