Wire clinical calculators into Tools catalogue#1227
Conversation
Promote the calculators search-page mockup to a production route under the shared search shell, add a Tools catalogue entry linking to /calculators, and teach the shell that calculators owns its composer. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
|
Warning Review limit reached
Next review available in: 13 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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 Plus Run ID: 📒 Files selected for processing (34)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Drop the Mockup alias and point the mockup route at the production export. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Production calculators must use size-tap tokens for the design-system contract. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
CI triageCI failed on this PR. Automated classification of the 3 failed job(s):
Compared with main CI run #5784 (success). Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger. |
…rs-tools-2bcb Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Clear the dock focus latch when opening a calculator
On a phone, focus the bottom input, narrow the query to one result, and press Enter: submitSearch sets openId, so activeCalc immediately unmounts this focused dock without firing its blur handler and dockFocused remains true. After closing the sheet, dockHidden = footerHidden && !dockFocused keeps the footer forced visible until another explicit focus/blur cycle, while the shell header can still hide; reset the latch when opening/unmounting and cover the submit-close-scroll sequence.
AGENTS.md reference: AGENTS.md:L219-L219
ℹ️ 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".
|
@codex resolve actionable Codex review findings for this pull request and current head using the repository instructions. This is the pull request's single automatic repair pass: do not perform a fresh review, create new standalone findings, or request another review. Work only the existing unresolved Codex threads on the current head. Always fix P0 and P1 findings. For P2 and lower findings, fix only clear, scoped, low-risk issues; otherwise disposition them with a concise reason. After fixing or dispositioning a thread, reply in that thread with as the first line, followed by a concise summary; that marker authorizes the workflow to close that exact thread. If human input or new authorization is required, do not use the marker and leave the thread open with the blocker. Finish only after every actionable thread is fixed or dispositioned and closed, or explicitly left open for a human decision. Do not update the branch from main, address unrelated reviews, broaden scope, or create more than one scoped fix commit. Do not use external APIs, paid services, credentials, dependency changes, or broad refactors unless explicitly authorized. Add targeted tests where behavior changes and run the narrowest relevant validation. |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
Prettier was failing on the calculators page and codebase index. Advisory UI expected 8 tools; Calculators brings the mockup catalog to 9. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
…om/BigSimmo/Database into cursor/wire-calculators-tools-2bcb Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Git merge-tree was clean (staleness). Accepts main #1227 calculator package relocation; calculator-mockups prune from this branch is superseded by that move and needs a separate re-port decision. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
GitHub CONFLICTING was staleness; merge-tree clean. Calculator rename from #1227 carried the IMP-04 prune onto src/components/calculators/. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
2 participants
Summary
Promotes the best calculators design (
calculators-search-page) to a production/calculatorsroute and adds it to the Tools catalogue so clinicians can open bedside rating-scale calculators from/tools.Changes
/calculators(src/app/(search-app)/calculators/page.tsx) using the search-results + popup scoring UI.src/components/calculator-mockups/→src/components/calculators/(production-safe imports; mockup routes kept as thin wrappers)./calculators./calculators(page-owned desktop top + phone dock); zero shell reserve with page pad.docs/site-map.md,docs/codebase-index.md,docs/search-chrome-behaviour.md.Proof
Tools page showing Calculators tile
Calculators page
RAG impact: no retrieval behaviour change — Tools navigation and a client-side calculator UI only.
Verification
npm run verify:cheap(3424 passed)npm run format:check/ Prettier on changed filesnpm run ensure(Tools → Calculators); Advisory/Production UI CI covers Playwrightnpm run verify:pr-localfull gate deferred to CI after the Prettier/count fix pushRisk and rollout
/calculatorsroute.Clinical Governance Preflight
Clinical KB Database(sjrfecxgysukkwxsowpy)Notes
To show artifacts inline, enable in settings.