Document Pandora production checkpoint

[besfeng23]

Summary

• Adds a production checkpoint for the Pandora retrieval/supersede/dashboard cleanup sequence.
• Records merged PRs Add retrieval evals and supersede old master packs on distill #127, Fix Pandora dashboard truth boundary #128, and Fix Pandora mobile nav label #129.
• Records read-only Supabase evidence for supersede-on-distill: two distills per namespace for the main user, older master archived, newer master active.

Validation

• Documentation only.
• No app code changed.
• No database mutation performed by this PR.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
memory	Ready	Preview, Comment	Jul 3, 2026 6:47pm

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 51 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: 0263258c-0c2c-4a88-b3e3-fa5e08f77f31

📥 Commits

Reviewing files that changed from the base of the PR and between a8a0839 and 65d621d.

📒 Files selected for processing (1)

• docs/pandora-production-checkpoint-2026-07-03.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/pandora-production-checkpoint-20260703

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 65d621d900

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Redact production user identifiers

This production checkpoint is committed documentation, but it includes the exact production auth.users.id for the main user here and another raw user ID later in the same section. When this doc is shared outside the database/operator context, those stable IDs can be correlated with memory/audit rows and defeat the repo’s redacted-proof pattern; please replace raw production user IDs with aliases or fingerprints while preserving the per-user invariant.

Useful? React with 👍 / 👎.