You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your recent review volume is higher than typical usage, so adaptive limits are currently applied.
Next review available in:28 minutes
Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).
How can I continue?
After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.
To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.
How do review limits work?
CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.
For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.
Adds daily registration-source analytics to the admin onboarding response and users dashboard. The change classifies accounts into three sources, zero-fills dates, adds a reusable stacked-bar chart, translations, integration fixtures, and frontend/backend tests.
The onboarding response now includes daily normal, invite, and profile-less registration counts. Queries classify auth.users records and apply date boundaries. Tests cover classification, date grouping, exclusive end dates, and cleanup.
Reusable helpers and a Vue component build themed stacked bar charts with localized dates, counts, percentages, loading states, and empty-series handling.
The dashboard maps the three trend categories into chart series and renders a translated chart card. Source wiring and English labels have unit coverage.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk: medium. Left a non-blocking comment rather than approving: Cursor Bugbot was not present, and this admin registration-source trend (auth.users SQL + dashboard UI) is above the low-risk auto-approve threshold. Assigned a reviewer for human review.
Sent by Cursor Approval Agent: Pull Request Approver External
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 5
🤖 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 `@docs/superpowers/plans/2026-08-09-admin-registration-source-trend.md`:
- Line 13: Update the task headings in the document from level-three headings
(`###`) to level-two headings (`##`), including the headings at all referenced
locations, so they follow the level-one title without skipping a hierarchy
level.
- Around line 168-173: Update the commit steps for backend and frontend changes
to run the required lint command immediately before each commit: use bun
lint:backend for the backend commit and bun lint:fix for each frontend commit.
Apply this to the referenced steps as well, without relying on the later
validation step.
In `@src/components/admin/AdminStackedBarChart.vue`:
- Around line 2-16: Update the local imports in the AdminStackedBarChart
component to use the frontend ~ alias, replacing both relative references to
adminStackedBarChart with ~/components/admin/adminStackedBarChart while
preserving the imported symbols.
In `@supabase/functions/_backend/utils/pg.ts`:
- Around line 3444-3450: Update the registration bucket filters in the query
around normal_registrations and invite_registrations so profiles with a null
created_via_invite value are counted as non-invite profiles. Use
u.created_via_invite IS DISTINCT FROM TRUE for normal_registrations while
keeping invite_registrations limited to TRUE, ensuring every matching profile is
included in a bucket.
In `@tests/admin-stats.test.ts`:
- Around line 1203-1228: Extend the test around getOnboardingFunnelDirect to
issue a request ending at 2026-02-02T00:00:00.000Z, then assert the user created
exactly at that timestamp is absent from the returned registration_source_trend.
Preserve the existing full-range assertions while explicitly verifying the end
boundary is exclusive.
🪄 Autofix
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: 8a1450af-ea6a-4444-bf5c-82be8ab02774
📥 Commits
Reviewing files that changed from the base of the PR and between ecfb160 and 0722917.
The reason will be displayed to describe this comment to others. Learn more.
Risk: medium. Left a non-blocking comment rather than approving: Cursor Bugbot was not present after the first poll, and this admin registration-source trend (auth.users SQL + dashboard UI) is above the low-risk auto-approve threshold. Human review is needed; a reviewer is already assigned.
Sent by Cursor Approval Agent: Pull Request Approver External
95-103: 🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Reset the database before the integration test commands.
These commands run tests/admin-stats.test.ts, which inserts rows into auth.users and public.users. Without a reset, stale rows from an earlier run can change the expected daily counts and make the regression test order-dependent. Add bun run supabase:db:reset immediately before each database-backed test run, or make the test command perform that reset.
As per coding guidelines, database-backed test runs must reset the database before execution.
Proposed command change
- bunx vitest run tests/admin-stats.test.ts -t "returns subscribed as the last onboarding funnel step without exceeding the bundle cohort|returns every auth registration in exactly one daily profile bucket"+ bun run supabase:db:reset+ bunx vitest run tests/admin-stats.test.ts -t "returns subscribed as the last onboarding funnel step without exceeding the bundle cohort|returns every auth registration in exactly one daily profile bucket"
Also applies to: 450-458
🤖 Prompt for 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.
In `@docs/superpowers/plans/2026-08-09-admin-registration-source-trend.md` around
lines 95 - 103, Update each documented database-backed test command in this plan
to run bun run supabase:db:reset immediately beforehand, including the focused
integration test command in Step 2 and the corresponding command at the other
referenced section. Preserve the existing Vitest arguments and expected results.
Source: Coding guidelines
🤖 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.
Outside diff comments:
In `@docs/superpowers/plans/2026-08-09-admin-registration-source-trend.md`:
- Around line 95-103: Update each documented database-backed test command in
this plan to run bun run supabase:db:reset immediately beforehand, including the
focused integration test command in Step 2 and the corresponding command at the
other referenced section. Preserve the existing Vitest arguments and expected
results.
ℹ️ Review info⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 9eeebb08-50aa-4f3d-82f2-388dddec8bf2
📥 Commits
Reviewing files that changed from the base of the PR and between 0722917 and 18ec354.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitHub Actions
Inactive
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Summary
Test plan
Summary by CodeRabbit
New Features
Tests