Cursor provider should not truncate reports at 250k bubbles

[vaibhavarora14]

Problem

When Cursor has a large local database, codeburn emits:

codeburn: Cursor database has 3,25,568 bubbles, scanning the most recent 2,50,000. Older sessions may be missing from this report.

That means lifetime or long-range reports can silently omit older Cursor sessions once the local bubble table grows past the hard scan cap.

Expected behavior

Reports should not drop older sessions just because the Cursor database has more than 250,000 bubbles. The provider should either query the relevant date/window directly, page through the rows it needs, or otherwise make the cap apply only where it cannot affect the requested report.

Actual behavior

The provider scans only the most recent 250,000 bubbles and warns that older sessions may be missing.

Notes

I checked existing issues, PRs, and discussions for the exact warning text and related phrases (Cursor database has, Older sessions may be missing, scanning the most recent, 250000, 2,50,000) and did not find this specific issue reported.

Related but not identical:

• Cursor bubbles with no createdAt are timestamped as "now", inflating today's usage #326
• Cursor provider reports $0 / "No usage data" — hardcoded 35-day lookback drops bubbles, NULL createdAt rows are filtered out #163
• Fix Cursor provider dropping data older than 35 days #169