docs: close measurement-gated catalogue payload work - #1470
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 36 minutes Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Comment |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 266144e1cb
ℹ️ 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".
Fourth genuine conflict on docs/outstanding-issues.md, confirmed with git merge-tree before acting. Main's #1470 rewrote #13 as measurement-gated while this branch changed #17, #105 and added #147. Verified by hash that main touched neither #17 nor #105 — both are byte-identical at the merge base and at origin/main — so those rows take this branch's version and #13 takes main's, rather than either side winning wholesale. Also de-duplicated against main's new #118, which already owns adopting the Lighthouse baseline and flipping enforce. #147's gate paragraph now cross-references it instead of restating it, and contributes the constraint #118 was missing: pinning a baseline today would bake CLS 0.363 on /dsm in as the accepted value, so the CLS fixes must land first or the gate ratifies the breach. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01361jh3eYVjJCzXWjAhdZiF
Resolves the docs/outstanding-issues.md conflict against #1441 and #1470. That file deliberately carries no merge driver (#133), so overlapping edits conflict loudly rather than being silently concatenated. Resolved by the prescribed recipe: rebuilt the file from origin/main and re-applied only this branch's own change (the #86 row's "Hydration SHIPPED (#101)" edit). Verified the result has an identical row count and an identical id set to origin/main, so #1470's closures were preserved and nothing was dropped; the only content delta against main is that one row. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GGEBHp4Seoh1jK1vGTNtYS
Motivation
Description
docs/outstanding-issues.mdto move#013into the resolved/archive section with a measured disposition explaining why no production change is justified.work:05d45b4with the messagedocs: close unmeasured catalogue payload work, and prepared PR metadata titleddocs: close measurement-gated catalogue payload workfor handoff.Testing
npm run build:analyzeand confirmed the production build/analyzer reports were generated successfully.npm run check:outstanding-issues,npm run docs:check-links, andnpm run format:checkwhich all passed.npm run verify:cheapwhich completed successfully; test summary: 436 test files passed (4,574 tests passed, 4 skipped).git diff --check(no whitespace errors) and committed only the intended docs change; merge tomainwas not performed because this checkout remained onworkand no remote push/merge was issued.Codex Task