feat(admin): track 12-month plan upgrade rate

[riderx]

Summary (AI generated)

• Add global_stats.upgrade_rate_12m (single new column) for the share of orgs whose last stripe_info.upgraded_at falls in the trailing 12 months
• Compute the metric daily in the logsnag_insights revenue shard
• Surface it on the admin revenue dashboard (latest card + trend chart)
• Add bun run stripe:backfill-upgrade-rate-12m to backfill historical rows

Motivation (AI generated)

Admin was missing a clear view of how many organizations upgraded their plan over the last 12 months. Daily snapshots plus a backfill script cover both forward and past data without changing other schema surfaces.

Business Impact (AI generated)

Gives Capgo clearer retention/expansion visibility: how much of the org base actively upgraded in the last year, which helps pricing and success decisions.

Test Plan (AI generated)

• Migration applied locally (upgrade_rate_12m only on global_stats)
• Local backfill ran with --apply --all and wrote non-zero rates
• Unit tests for backfill helpers (tests/backfill-upgrade-rate-12m.unit.test.ts)
• CI green
• Verify admin revenue page shows the new card/chart after deploy
• Run production backfill after merge: bun run stripe:backfill-upgrade-rate-12m --apply --all (against prod env)

Generated with AI

Made with Cursor

Summary by CodeRabbit

• New Features
  • Added a 12-month upgrade rate metric to global statistics and the admin dashboard (latest value + trend chart).
• Data & Maintenance
  • Extended stored global stats with upgrade_rate_12m (defaults to 0).
  • Added a maintenance/backfill command to recompute historical values.
• Localization / UI
  • Added localized label/description for the new metric.
  • Updated password verification hint text for clarity.
• Tests
  • Added unit tests for rate calculation, rounding, leap-year window handling, and backfill row generation.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 97d7fbba-0e65-4536-b6ec-f8ad2986abd7

📥 Commits

Reviewing files that changed from the base of the PR and between 25e3c55 and b395ec6.

📒 Files selected for processing (1)

• tests/logsnag-insights-revenue.unit.test.ts

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• Cap-go/capacitor-updater (manual)

---

📝 Walkthrough

Walkthrough

Adds a trailing 12-month upgrade-rate metric to global statistics, snapshot generation, backfill tooling, admin trend data, and the revenue dashboard. It also adds localization and tests, and renames an authentication hint translation key.

Changes

12-month upgrade rate

Layer / File(s)	Summary
Metric storage and snapshot generation supabase/migrations/..., */supabase.types.ts, supabase/functions/_backend/triggers/logsnag_insights.ts	Adds the global_stats.upgrade_rate_12m column and types, computes the rate during revenue shard processing, and persists it in snapshots.
Backfill computation and CLI scripts/backfill_upgrade_rate_12m.ts, package.json, tests/backfill-upgrade-rate-12m.unit.test.ts	Adds paginated source loading, trailing-window calculations, dry-run/apply CLI behavior, concurrent updates, and helper tests.
Trend delivery and dashboard display supabase/functions/_backend/utils/pg.ts, src/pages/admin/dashboard/revenue.vue, messages/en.json	Includes the metric in admin trend results and displays its latest value and historical percentage chart with localized text.

Authentication hint translation

Layer / File(s)	Summary
Authentication hint key update messages/en.json, src/pages/settings/account/ChangePassword.vue	Renames the password verification translation key, updates its capitalization, and changes the account page reference.

Estimated code review effort: 4 (Complex) | ~45 minutes

Suggested labels: codex

Suggested reviewers: dalanir, wcaleniewolny

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the main change: tracking the new 12-month plan upgrade rate.
Description check	✅ Passed	The description covers the required summary, test plan, and checklist, and is sufficiently detailed for review.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

_{Comment @coderabbitai help to get the list of available commands.}

[codspeed-hq]

Merging this PR will not alter performance

✅ 43 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing feat/admin-upgrade-rate-12m (b395ec6) with main (0edae7f)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_a25a7e26-0ff9-4ff7-a2bd-71dce2f3b72e)

[cursor]

Stale comment

Risk: medium. Not approving: Cursor Bugbot completed as skipped (usage limit reached), so automated review did not run. Human review is needed before merge; assigned Dalanir and WcaleNieWolny.

  

_{Sent by Cursor Approval Agent: Pull Request Approver}

[cursor]

Stale comment

Risk: medium. Cursor Bugbot did not complete (check skipped; usage limit reached), so automated review is unavailable. Human review is needed for this migration, billing metric, and admin dashboard change.

  

_{Sent by Cursor Approval Agent: Pull Request Approver External}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_0fc257d3-1200-424f-b590-d1499712b5d5)

[cursor]

Stale comment

Risk: medium. Not approving: Cursor Bugbot completed as skipped (usage limit reached), so automated review did not run. Human review is still needed; Dalanir and WcaleNieWolny are already assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Approver}

[cubic-dev-ai]

All reported issues were addressed

Confidence score: 5/5

• Safe to merge after the addressed issues were fixed.

<sub>Tip: instead of fixing issues one by one fix them all with cubic

Re-trigger cubic</sub>

[cursor]

Stale comment

Risk: medium. Cursor Bugbot did not complete (check skipped; usage limit reached), so automated review is unavailable. Human review is still needed for this migration and billing metric change; Dalanir and WcaleNieWolny are already assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Approver External}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_3086c008-2641-4fb5-99a6-91d629bcd377)

[cursor]

Stale comment

Risk: medium. Not approving: Cursor Bugbot completed as skipped (usage limit reached), so automated review did not run. Human review is still needed; Dalanir and WcaleNieWolny are already assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Approver}

[cursor]

Stale comment

Risk: medium. Not approving: Cursor Bugbot completed as skipped (usage limit reached), so automated review did not run. Human review is still needed for this migration and billing metric change; Dalanir and WcaleNieWolny are already assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Approver External}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@supabase/migrations/20260721110632_admin_upgrade_rate_12m.sql`:
- Line 5: Wrap the PostgreSQL column comment string in the migration’s IS clause
using adjacent string literals so no line exceeds SQLFluff’s length limit.
Preserve the exact stored comment text and meaning while only changing its
formatting.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 9819090d-0ae9-491d-9db1-25301b9a52b5

📥 Commits

Reviewing files that changed from the base of the PR and between 8910a3b and ce152dc.

📒 Files selected for processing (3)

• scripts/backfill_upgrade_rate_12m.ts
• supabase/functions/_backend/triggers/logsnag_insights.ts
• supabase/migrations/20260721110632_admin_upgrade_rate_12m.sql

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• Cap-go/capacitor-updater (manual)

[cubic-dev-ai]

All reported issues were addressed across 3 files (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Fix all with cubic | Re-trigger cubic</sub>

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_d41283e5-1acf-4bcb-b235-8f17f0f9d68c)

[cursor]

Stale comment

Risk: medium. Not approving: Cursor Bugbot completed as skipped (usage limit reached), so automated review did not run, and this migration plus billing metric change exceeds the low-risk approval threshold. Human review is still needed; Dalanir and WcaleNieWolny are already assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Approver External}

[cursor]

Risk: medium. Not approving: Cursor Bugbot completed as skipped (usage limit reached), so automated review did not run. Human review is still needed for this migration and billing metric change; Dalanir and WcaleNieWolny are already assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Approver}

[cubic-dev-ai]

All reported issues were addressed across 4 files (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Fix all with cubic | Re-trigger cubic</sub>

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_0f887bb4-6ebf-44d8-a8a4-89b7e88b472d)

[cursor]

Risk: medium. Not approving: Cursor Bugbot completed as skipped (usage limit reached), so automated review did not run, and this migration plus billing metric change exceeds the low-risk approval threshold. Human review is still needed; Dalanir and WcaleNieWolny are already assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Approver External}

[cursor]

Risk: medium. Not approving: Cursor Bugbot completed as skipped (usage limit reached), so automated review did not run. Human review is still needed for this migration and billing metric change; Dalanir and WcaleNieWolny are already assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Approver}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cubic-dev-ai]

2 issues found across 5 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="scripts/backfill_upgrade_rate_12m.ts">

<violation number="1" location="scripts/backfill_upgrade_rate_12m.ts:207">
P3: An interruption after scanning millions of rows still forces both source scans to restart because these cursors exist only in memory. Persisting checkpoints plus fetched/processed batches, or moving the bounded computation into the database, would make the backfill actually resumable.</violation>

<violation number="2" location="scripts/backfill_upgrade_rate_12m.ts:213">
P2: A live production scan can omit orgs inserted during pagination because random UUIDs may sort below `lastId` after that cursor has passed. A repeatable-read database snapshot would keep the org and `stripe_info` inputs internally consistent.</violation>
</file>

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: A live production scan can omit orgs inserted during pagination because random UUIDs may sort below lastId after that cursor has passed. A repeatable-read database snapshot would keep the org and stripe_info inputs internally consistent.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At scripts/backfill_upgrade_rate_12m.ts, line 213:

<comment>A live production scan can omit orgs inserted during pagination because random UUIDs may sort below `lastId` after that cursor has passed. A repeatable-read database snapshot would keep the org and `stripe_info` inputs internally consistent.</comment>

<file context>
@@ -188,17 +204,19 @@ async function fetchGlobalStatsRows(supabase: SupabaseClient, fromDateId: string
       .select('id, created_at, customer_id')
-      .order('created_at', { ascending: true })
-      .range(offset, offset + DEFAULT_PAGE_SIZE - 1)
+      .order('id', { ascending: true })
+      .limit(DEFAULT_PAGE_SIZE)
 
</file context>

[cubic-dev-ai]

P3: An interruption after scanning millions of rows still forces both source scans to restart because these cursors exist only in memory. Persisting checkpoints plus fetched/processed batches, or moving the bounded computation into the database, would make the backfill actually resumable.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At scripts/backfill_upgrade_rate_12m.ts, line 207:

<comment>An interruption after scanning millions of rows still forces both source scans to restart because these cursors exist only in memory. Persisting checkpoints plus fetched/processed batches, or moving the bounded computation into the database, would make the backfill actually resumable.</comment>

<file context>
@@ -188,17 +204,19 @@ async function fetchGlobalStatsRows(supabase: SupabaseClient, fromDateId: string
 async function fetchOrgRows(supabase: SupabaseClient, toDateId: string | null) {
   const rows: OrgRow[] = []
-  let offset = 0
+  let lastId: string | null = null
 
   while (true) {
</file context>