This is a comment left during a code review.
Path: apps/backend/src/lib/ai/tools/sql-query.ts
Line: 40-45

Comment:
**`MAX_ROWS_FOR_AI` truncates after loading all rows into memory**

The comment describes this as a "backstop if LIMIT is missing," but `resultSet.json()` eagerly loads every row returned by ClickHouse into the Node.js heap before the slice. A query missing a LIMIT clause (e.g. `SELECT * FROM events`) would still materialise the full result set in memory before being truncated to 50 rows, defeating the backstop for large datasets.

Enforce the cap at the database level instead:

```typescript
const safeQuery = `SELECT * FROM (${query}) LIMIT ${MAX_ROWS_FOR_AI + 1}`;
```

Then remove the `rows.slice(0, MAX_ROWS_FOR_AI)` post-processing, or keep it as a secondary safety net.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: apps/backend/src/app/api/latest/internal/metrics/route.tsx
Line: 397-405

Comment:
**Duplicate all-time revenue aggregation between `loadSessionReplayAggregates` and `loadPaymentsOverview`**

Both functions independently compute the all-time paid `SubscriptionInvoice` sum with identical SQL, resulting in two separate database round-trips that always return the same value. The result is exposed as both `analytics_overview.total_revenue_cents` and `payments_overview.revenue_cents`. If either query's filter diverges in the future, the two fields will silently disagree.

Consider computing this once in `loadPaymentsOverview` and passing the value through to `loadSessionReplayAggregates`.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: apps/backend/src/app/api/latest/internal/metrics/route.tsx
Line: 355-370

Comment:
**`refund_cents` is always hardcoded to `0`**

`loadDailyRevenue` pushes `refund_cents: 0` for every day; no refund query exists. `MetricsDailyRevenuePointSchema` exposes this field, so any dashboard widget reading it will perpetually display $0 in refunds. At minimum a comment should note this is a placeholder, or the field should be omitted from the schema until refund data is actually tracked.

How can I resolve this? If you propose a fix, please make it concise.