Cursor/cloud agent 1787842840327 vmus2 - #2441
Conversation
Remaining Lucide size={15} and 1px shadow spreads were blocking the
token contract. Map those to named tokens, drop unused v2 line-height
companions, and record leftover Hazard 2/3 items in FIX-GUIDE.
Co-authored-by: Cursor <cursoragent@cursor.com>Co-authored-by: Cursor <cursoragent@cursor.com> # Conflicts: # src/components/therapy-compass/therapy-card.tsx
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Keep quoted contract numbers in lockstep with the baseline JSON, and replace nested brief-duration ternaries plus leftover Lucide size={16} on screens this sweep already touched.
Co-authored-by: Cursor <cursoragent@cursor.com>Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Warning Review limit reachedNext included review available in 33 minutes. View limit detailsLimit details: You’ve used the included review currently available. Your 103 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (15)
📒 Files selected for processing (16)
Comment |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_39bfc42d-2e76-4c27-be1e-50495561c0dd) |
BigSimmo
commented
Aug 27, 2026
Closing as superseded/stale. This branch forked from Evidence:
There's no net-new content here worth salvaging — everything genuine in this diff already landed through a cleaner lineage. Recommend closing rather than rebasing; a rebase would mean discarding nearly the whole diff in favor of what Generated by Claude Code |
Summary
Verification
npm run verify:pr-localDuring development, use
npm run verify:cheapas the faster iteration gate before the final PR-local preflight.npm run verify:uiwhen UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changednpm run verify:releasebefore release or handoff confidence claimsFor retrieval, ranking, selection, chunking, source/citation rendering, or answer-contract changes,
verify:pr-localrunseval:rag:offlineautomatically. Run the offline command directly during iteration before spending a live eval.npm run eval:retrieval:quality(must stay 36/36) when retrieval, ranking, selection, chunking, or scoring behavior changed — CI cannot run it (needs live keys), so run it locally and paste the summary. A metadata/governance-weighting change once buried correct docs (recall 1.0→0.76) and only this eval caught it.npm run eval:rag -- --limit 15+npm run eval:quality -- --rag-onlywhen answer generation, the synthesis prompt, or answer post-processing changed (grounded-supported must not drop; citation-failure 0)npm run check:production-readinesswhen clinical workflow, privacy, environment, Supabase, source governance, or deployment behavior changednpm run check:deployment-readinesswhen deployment startup, hosting, or rollout behavior changedRisk and rollout
Complete this section for clinical, data, API, auth/privacy, workflow, dependency, build, or deployment changes.
src/lib/rag/, retrieval RPCs, golden fixtures, ranking tests; seedocs/rag-behaviour/safeguards.md). Must use one of:RAG impact: no retrieval behaviour change — <reason>RAG impact: behaviour change — canary pair <baseline run> -> <post run>RAG impact: noneor omit for non-RAG PRs)Clinical Governance Preflight
Complete this section when the change touches ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical output.
Clinical KB Database(sjrfecxgysukkwxsowpy)Notes
Note
Low Risk
Changes are documentation, indexes, and a repo snapshot; no application or gate script changes appear in this diff.
Overview
Closes the Hazard 1–2 design-system sweep in documentation: adds
docs/design-system/FIX-GUIDE.mdas the disposition ledger (Fixed / Documented / Deferred / Out-of-scope) and wires it into the design-system README and top-level docs index.Doc set is brought in line with sweep outcomes without re-stating rules in the fix guide: registry counts 55 visual exports;
ErrorStateis recorded as built/registered;--text-placeholderis live; type-scale contract text drops per-step-lh/-trorphans in favor of--leading-proseand hero companions; medication#0f766edefaults are documented as scopedRAW_COLOR_EXEMPTIONS(data, not--clinical-accent);GATES.mdanddesign-system-contract.mdreflect updated ratchet numbers (e.g. raw colours 0, edge/spread/tap debt counts).Navigation hygiene: UI work is pointed at
docs/design-system/README.mdas the front door (withdesign-system.mdas live-layer transition notes) across codebase index, testing, and process-hardening;repo-awareness-snapshot.jsonis refreshed (new SHA, FIX-GUIDE catalogued, doc counts). A branch review record notes verification gaps on the sweep branch (focused tests / contract checks not run).Reviewed by Cursor Bugbot for commit 5e3eaae. Configure here.