fix(admin): fix logsnag_insights typecheck for AppBuildOnboardingMetricRow

[riderx]

Summary (AI generated)

• Add [key: string]: unknown to AppBuildOnboardingMetricRow so it satisfies Drizzle execute<T extends Record<string, unknown>>
• Fixes backend typecheck failure in Bump version / Lint and typecheck

Motivation (AI generated)

PR #2937 changed AppBuildOnboardingMetricRow from a type to an interface without an index signature. Interfaces are not assignable to Record<string, unknown>, so bun run typecheck:backend fails on drizzleClient.execute<AppBuildOnboardingMetricRow>(...).

Business Impact (AI generated)

Unblocks the bump-version / release typecheck path on main so version bumps and related CI can pass again.

Test Plan (AI generated)

• bun run typecheck:backend passes locally
• Confirm Lint and typecheck job is green on this PR

Generated with AI

  

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 5 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.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 575ccb5c-e4a8-4847-8929-6a020501f7af

📥 Commits

Reviewing files that changed from the base of the PR and between 36be1d0 and 3377348.

📒 Files selected for processing (1)

• supabase/functions/_backend/triggers/logsnag_insights.ts

---

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

[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_f0da0416-620d-42a9-b335-c3062f25da6c)

[codspeed-hq]

Merging this PR will not alter performance

✅ 43 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing cursor/fix-logsnag-typecheck-f6fd (3377348) with main (36be1d0)}

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. ↩

[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