Skip to content

docs: close measurement-gated catalogue payload work - #1470

Merged
BigSimmo merged 3 commits into
mainfrom
codex/merge-route-specific-catalogue-optimizations
Jul 30, 2026
Merged

docs: close measurement-gated catalogue payload work#1470
BigSimmo merged 3 commits into
mainfrom
codex/merge-route-specific-catalogue-optimizations

Conversation

@BigSimmo

Copy link
Copy Markdown
Owner

Motivation

  • Archive the [codex] Clinical KB cleanup readiness #13 route-specific catalogue / mockup payload finding under the repo's precommitted measurement rule because no Lighthouse/Web‑Vitals evidence justified speculative payload work.
  • Preserve Bump @types/react from 19.2.16 to 19.2.17 #18 (ADHD / metabolic) as open because the ADHD source is missing from the hosted corpus and metabolic structured schedule evidence is unavailable without approved ingestion and provider-backed evaluation.

Description

  • Updated docs/outstanding-issues.md to move #013 into the resolved/archive section with a measured disposition explaining why no production change is justified.
  • Did not change any production code, RAG surfaces, fixtures, ingestion, or provider-backed workflows; no Supabase/OpenAI/provider operations were run.
  • Created a local commit on branch work: 05d45b4 with the message docs: close unmeasured catalogue payload work, and prepared PR metadata titled docs: close measurement-gated catalogue payload work for handoff.

Testing

  • Ran npm run build:analyze and confirmed the production build/analyzer reports were generated successfully.
  • Ran npm run check:outstanding-issues, npm run docs:check-links, and npm run format:check which all passed.
  • Ran npm run verify:cheap which completed successfully; test summary: 436 test files passed (4,574 tests passed, 4 skipped).
  • Verified git diff --check (no whitespace errors) and committed only the intended docs change; merge to main was not performed because this checkout remained on work and no remote push/merge was issued.

Codex Task

@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

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 @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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 0f08d6f9-9d04-4478-aab4-1a7577eedd6b

📥 Commits

Reviewing files that changed from the base of the PR and between e79e499 and ef79b4c.

📒 Files selected for processing (2)
  • docs/branch-review-ledger.md
  • docs/outstanding-issues.md

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

@supabase

supabase Bot commented Jul 30, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread docs/outstanding-issues.md Outdated
@BigSimmo BigSimmo added the skip-branch-sync Opt out of hosted pr-branch-sync / update-branch on this PR label Jul 30, 2026
@BigSimmo
BigSimmo merged commit 015f2a9 into main Jul 30, 2026
32 checks passed
@BigSimmo
BigSimmo deleted the codex/merge-route-specific-catalogue-optimizations branch July 30, 2026 15:46
BigSimmo pushed a commit that referenced this pull request Jul 30, 2026
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
BigSimmo pushed a commit that referenced this pull request Jul 30, 2026
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

codex skip-branch-sync Opt out of hosted pr-branch-sync / update-branch on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant