Add safe core repositories

[besfeng23]

Summary

• Adds concrete server-side repositories for selected safe core tables.
• Repositories enforce owner and namespace filters for reads/lists and owner-bound create preparation.
• Adds injectable query client support for unit tests.
• Excludes memory patch repository behavior until validation and append-only patch services exist.
• Adds core repository documentation, tests, and status/health metadata updates.

Scope control

This PR does not add public memory APIs, memory ingest behavior, memory extraction, memory validation, patch behavior, pgvector, OpenAI calls, GPT Actions, MCP, seed data, or fake operational rows.

Expected checks

• npm run typecheck
• npm run lint
• npm run test
• npm run build
• npm run ci

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
memory	Ready	Preview, Comment	Jun 19, 2026 6:52pm

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

@besfeng23, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 53 minutes and 48 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e8c609c4-81e5-4168-86e3-4b569d443531

📥 Commits

Reviewing files that changed from the base of the PR and between a47426a and 96fc651.

📒 Files selected for processing (6)

• app/api/health/route.ts
• docs/core-repositories.md
• lib/app/status.ts
• lib/db/core-repositories.ts
• tests/unit/app-status.test.ts
• tests/unit/core-repositories.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch assistant/repos

---

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 and usage tips.}