[waleedlatif1]

Summary

• The usage analytics index note said every read narrowed to one workspace runs on usage_log_workspace_created_at_cost_idx; only a read over a created_at window (a range or a reporting period) is index-only there
• A Stripe-period drill-down matches the period stamps, which that index does not carry, so the note now says so, matching the scope builder, the schema and the 0446 migration

Type of Change

• Documentation

Testing

Comment-only change. usage-analytics.test.ts, bun run lint, bun run check:audits

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Oct 30, 2026 6:09pm UTC

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

[greptile-apps]

Confidence Score: 5/5

[Low impact] This comment-only change appears safe to merge.

Summary

Clarifies the workspace index note without changing executable code.

• The usage index note limits its claim to created_at windows.

_{Reviews (2) · Last reviewed commit: "docs(billing): limit the workspace index..." · Reviewed by Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}