ref(metrics): Store Conversation Run metrics as rows

[sentry-junior]

Store each Conversation Run metric as its own SQL row. A repeated write for the same Run replaces those rows. This removes the custom subtraction code that caused cache token fields to disappear.

The table is reusable for any numeric Run metric. This first pass stores duration, cost, and every token value Junior receives: total, input, output, cached input, cache creation, and reasoning tokens.

The existing Conversation metric fields remain as cached totals for current readers. Each write rebuilds those totals from the metric rows. The migration copies existing duration, token, and cost totals into the new table.

The stats endpoint uses one query to sum every metric by UTC day or hour. The response schema does not change.

Checks

• GET /api/conversations/stats integration tests cover total, daily, and hourly cache fields.
• The Conversation SQL store test covers repeated Run writes and all token metric rows.
• Full @sentry/junior test suite: 2,859 passed, 1 skipped.
• TypeScript, lint, Prettier, migration metadata, and test architecture checks pass.

via David Cramer.

--

View Junior Session [Sentry]

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
junior-docs	Ready	Preview	Sep 11, 2026 6:52pm UTC

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Cursor Bugbot has reviewed your changes and found 3 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 15d1e3a. Configure here.}