chore: improve OSS contributor experience

[deepu0]

User description

Summary

Makes it easier for contributors to run and contribute to the project.

Changes

• README.md — added Database Setup section pointing to scripts/setup.sql
• .env.example — merged all env vars (Supabase, Gemini, Cron, Capture, Turnstile, LogoDev, Notification)
• .github/workflows/pr-checks.yml — audit with --omit=dev so dev-only vulns don't block PRs
• .gitignore — added stray files
• docs/auth-standardization-spec.md — spec document for auth refactor

Notes

npm audit fix reduced 31 vulnerabilities (1 critical, 10 high) to 12 (all in @lhci/cli devDependency only). Production deps are clean at audit-level=high.

---

CodeAnt-AI Description

Improve contributor setup and tighten auth checks

What Changed

• Added setup instructions for creating the required database tables and marking your account as an admin
• Expanded the example environment file with the missing capture, notification, and admin guidance settings
• Updated the PR security audit to ignore dev-only issues so contributor checks are less likely to fail on non-production vulnerabilities
• Added a spec describing the planned auth rules and cleanup work for consistency across the app

Impact

✅ Easier local setup
✅ Fewer blocked PR checks
✅ Clearer admin setup

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
frontend-junction	Ready	Preview, Comment	Jun 29, 2026 7:34am

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[coderabbitai]

Warning

Review limit reached

@deepu0, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 921807b7-c506-4945-bf4d-de5eb18e1a22

📥 Commits

Reviewing files that changed from the base of the PR and between 3b401cf and 89e522b.

📒 Files selected for processing (5)

• .env.example
• .github/workflows/pr-checks.yml
• .gitignore
• README.md
• docs/auth-standardization-spec.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/oss-readiness

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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