[codex] sync applied adaptive log RLS migration version

[besfeng23]

Summary

Supabase MCP applied the adaptive log RLS migration as 20260704114354_adaptive_log_rls_policies. This PR keeps the repository migration filename in sync with the migration history now recorded on the Memory Supabase project.

Changes:

• Rename 20260704103859_adaptive_log_rls_policies.sql to 20260704114354_adaptive_log_rls_policies.sql.
• Update the RLS regression test to read the synced filename.

Validation

• vitest@2.1.9 run tests/unit/rls-policies.test.ts passed: 4 tests.
• Supabase migration history for project Memory includes 20260704114354 / adaptive_log_rls_policies.
• Post-apply database verification showed force RLS enabled on memory_retrieval_logs and memory_model_call_logs, plus select/insert owner policies for both tables.

Rollout Notes

• No production jobs were run.
• No dryRun:false execution was run.
• No secret files were read.
• This PR is metadata/history alignment only; it does not introduce a new schema operation beyond the already-applied migration.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 53 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: 6623db63-3aec-4065-b22b-35c3a647b288

📥 Commits

Reviewing files that changed from the base of the PR and between e90f3ed and c86e734.

📒 Files selected for processing (2)

• supabase/migrations/20260704114354_adaptive_log_rls_policies.sql
• tests/unit/rls-policies.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/sync-applied-migration-version

---

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

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
memory	Ready	Preview, Comment	Jul 4, 2026 11:47am