Skip to content

Organize dirty work: cursor/pr1196-coalesce-main-4711 - #1331

Closed
BigSimmo wants to merge 13 commits into
mainfrom
cursor/pr1196-coalesce-main-4711
Closed

Organize dirty work: cursor/pr1196-coalesce-main-4711#1331
BigSimmo wants to merge 13 commits into
mainfrom
cursor/pr1196-coalesce-main-4711

Conversation

@BigSimmo

Copy link
Copy Markdown
Owner

This PR organizes dirty work currently grouped under branch cursor/pr1196-coalesce-main-4711.

BigSimmo and others added 12 commits July 25, 2026 23:03
Delete dying search/embedding inflight map entries when the last waiter disconnects, and ceil fractional PDF render dimensions before the safe-integer pixel budget check.
Append ledger rows for the Bugbot/regression review of PR #1196 and the
main fix-forward in PR #1212.
Close without merge: tip is stale/conflicting and the remediation
family already landed on main; live coalesce/PDF fixes stay in #1212.
Append ledger row after a clean merge of origin/main into the
coalesce-poison fix branch; no product conflict resolution needed.
@coderabbitai

coderabbitai Bot commented Jul 28, 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: 25 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: 6002c4ce-b49e-4ee1-a0ef-ddbef01269d5

📥 Commits

Reviewing files that changed from the base of the PR and between 7f91d99 and a501a2c.

📒 Files selected for processing (60)
  • .cursorindexingignore
  • docs/branch-review-ledger.md
  • docs/codebase-index.md
  • docs/operator-backlog.md
  • docs/outstanding-issues.md
  • docs/search-chrome-behaviour.md
  • docs/site-map.md
  • scripts/check-design-system-contract.mjs
  • scripts/repro-coalesce-poison-race.mjs
  • src/app/(search-app)/calculators/page.tsx
  • src/app/api/search/route.ts
  • src/app/globals.css
  • src/app/mockups/calculators-bedside-sheet/page.tsx
  • src/app/mockups/calculators-clinical-console/page.tsx
  • src/app/mockups/calculators-directory-grid/page.tsx
  • src/app/mockups/calculators-guided-flow/page.tsx
  • src/app/mockups/calculators-popup-sheet/page.tsx
  • src/app/mockups/calculators-search-page/page.tsx
  • src/app/mockups/calculators-search/page.tsx
  • src/app/mockups/recent-searches-bottom/page.tsx
  • src/components/ClinicalDashboard.tsx
  • src/components/applications-launcher-page.tsx
  • src/components/calculator-mockups/bedside-sheet-mockup.tsx
  • src/components/calculator-mockups/calculator-fixtures.ts
  • src/components/calculator-mockups/calculator-pathways.ts
  • src/components/calculator-mockups/calculator-ui.tsx
  • src/components/calculator-mockups/clinical-console-mockup.tsx
  • src/components/calculator-mockups/directory-grid-mockup.tsx
  • src/components/calculator-mockups/guided-flow-mockup.tsx
  • src/components/calculator-mockups/index.ts
  • src/components/calculator-mockups/popup-sheet-mockup.tsx
  • src/components/calculator-mockups/search-detail-mockup.tsx
  • src/components/calculator-mockups/search-page-mockup.tsx
  • src/components/calculators/index.ts
  • src/components/clinical-dashboard/document-admin.tsx
  • src/components/clinical-dashboard/global-search-shell.tsx
  • src/components/clinical-dashboard/master-search-header.tsx
  • src/components/clinical-dashboard/mobile-composer-reserve.ts
  • src/components/formulation/formulation-builder-page.tsx
  • src/components/services/services-navigator-page.tsx
  • src/components/tools-page-mockups/tool-fixtures.ts
  • src/lib/extractors/pdf-extraction-budget.ts
  • src/lib/mode-home-composer.ts
  • src/lib/openai.ts
  • src/lib/search-shell-props.ts
  • src/lib/tools-catalog.ts
  • tests/header-scroll-hide-contract.test.ts
  • tests/mobile-chrome-paint-contract.test.ts
  • tests/mobile-composer-reserve.test.ts
  • tests/openai-cache.test.ts
  • tests/pdf-extraction-budget.test.ts
  • tests/private-access-routes.test.ts
  • tests/search-shell-props.test.ts
  • tests/sheet.dom.test.tsx
  • tests/tools-catalog.test.ts
  • tests/ui-chrome-scroll.spec.ts
  • tests/ui-formulation.spec.ts
  • tests/ui-phone-scroll.spec.ts
  • tests/ui-tools-task-directory.spec.ts
  • tests/ui-tools.spec.ts

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

@supabase

supabase Bot commented Jul 28, 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: a501a2c9b9

ℹ️ 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".

export { CalculatorsDirectoryGridMockup } from "./directory-grid-mockup";
export { CalculatorsGuidedFlowMockup } from "./guided-flow-mockup";
export { CalculatorsPopupSheetMockup } from "./popup-sheet-mockup";
export { CalculatorsSearchPageMockup } from "./search-page-mockup";

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Restore the production calculators route

When a user opens an existing /calculators bookmark or link, this demotion to mockup-only exports accompanies deletion of src/app/(search-app)/calculators/page.tsx and the Tools catalogue record, so the production feature now returns 404 and disappears from navigation. Keep the production route/catalogue entry or provide a compatible replacement rather than silently removing the newly shipped calculator workflow.

Useful? React with 👍 / 👎.

| 2026-07-25 | PR supersede #1186 / `cursor/pr1186-audit-remediation-c94c` | `a38e83860510a4229d5658960657cd7448aff278` | Clean main-based port of intentional #1186 audit fixes | SUPERSEDE #1186 (do not merge old PR). Ported intentional 16-file delta onto current main; dropped conflicted checkpoint tree and placeholder skills. Fixed eval single results binding; async run-heavy so lock heartbeat fires; branch:cleanup dry-run default + argv-safe deletes; skill-create interface YAML. Close #1186. | Focused Vitest tooling+lock 6/6; check:skills 33; prettier on touched files; no provider/live eval runs. |
| 2026-07-25 | PR #1200 / `cursor/typography-audit-fixes-1c1e` | pending-push | CORRECTION: remove exact-duplicate ledger row | Removed a merge-union exact duplicate of the `cursor/ledger-066-067-519b` / `f04392a40` READY row (kept the earlier copy). No product change. | `npm run check:branch-review-ledger` |
| 2026-07-25 | PR #1190 / `remediate-dark-mode-audit` | `00eca49b9b0d7e5fbfa5703a15e9e930963984a6` | Cursor review+Bugbot+prlanded+debug (fresh pass, same HEAD) | DO NOT MERGE; NOT LANDED (OPEN, mergeable=CONFLICTING/DIRTY, 468 behind / 2 ahead). Reconfirmed P0: conflict resolution deleted `trustGatedAnswerForClinicalNotes` (0 hits on head; main L584/632/659/1075) — Clinical Notes consumes ungated answer. P1: `src/app/api/answer/route.ts:6` imports nonexistent `@/lib/rag` (tsc TS2307; stream correctly uses `@/lib/rag/rag`). P1: merge-tree conflicts on answer/upload/evidence-panels + 10 paths; literal `<<<<<<<` in docs audit plan; migration timestamp collision risk vs main. Intentional dark-mode delta is only commit `363672602` (~10 files). Salvage: `cursor/pr1190-dark-mode-salvage-f453` cherry-picks that commit onto current main, restores unused-manifest-import cleanup, keeps clinical gate. Close #1190 after salvage lands. | Bugbot; `git grep` gate/import/markers; merge-tree; `tsc` TS2307 proof; gh pr view/checks (PR policy fail). Salvage: tsc clean; visual-evidence+overlay tests 13/13; eslint on changed files. No provider/UI matrix. |
| 2026-07-25 | `cursor/ledger-066-067-519b` | f04392a408eceee14215c15169cbd6b70ac2041c | Close stale ledger #066/#067 (+ drop resolved #030/#075 from queue) | READY. #066 proven on main via #1174; #067 already fixed in #1191 in-process preflight. Docs-only ledger sync; no code change. | Local proof: `git show`/`log` for #1174/#1191; preflight test already in-process on main; ledger integrity asserts. No providers. |

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Preserve append-only review history

This ledger hunk removes previously appended review and handoff records for branches such as PR #1200 and PR #1190, which erases the state used to prevent duplicate reviews and retain prior blockers. Restore the removed rows and record any correction or superseding outcome only as a new appended row, as required by the repository's append-only ledger contract.

AGENTS.md reference: AGENTS.md:L146-L146

Useful? React with 👍 / 👎.

onClick={() => move(-1)}
disabled={activeIndex === 0}
className="inline-flex min-h-tap items-center gap-2 rounded-lg border border-[color:var(--border-strong)] bg-[color:var(--surface)] px-4 text-sm font-bold text-[color:var(--text-muted)] disabled:cursor-not-allowed disabled:border-[color:var(--border)] disabled:bg-[color:var(--surface-inset)]"
className="inline-flex min-h-tap items-center gap-2 rounded-lg border border-[color:var(--border-strong)] bg-[color:var(--surface)] px-4 text-sm font-bold text-[color:var(--text-muted)] disabled:opacity-40"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep disabled formulation controls opacity-free

On WebKit, after the formulation step navigation changes from disabled to enabled, the restored disabled:opacity-40/disabled:opacity-45 utilities can leave stale reduced opacity on an enabled button, producing the low-contrast state previously fixed by b91b460 and documented by matrix run 4012. Retain the explicit disabled surface/text styling and the focused native-disabled/opacity regression coverage instead of reintroducing opacity-based state.

Useful? React with 👍 / 👎.

Comment thread src/app/globals.css
Comment on lines +1832 to +1838
background: linear-gradient(
180deg,
transparent 0%,
color-mix(in srgb, var(--background) 72%, transparent) 42%,
color-mix(in srgb, var(--background) 94%, transparent) 72%,
var(--background) 100%
);

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve the opaque phone chrome surface

On submitted phone search views, changing the edge-to-edge dock from a solid surface to this transparent gradient, while also restoring its backdrop layer and removing the phone paint tests, reintroduces multiple translucent layers over scrolling content and the compositing defect fixed immediately before this commit. Keep the single bounded phone header/footer surface and retain a narrower guard rather than deleting the existing static and Playwright coverage.

AGENTS.md reference: AGENTS.md:L221-L221

Useful? React with 👍 / 👎.

@BigSimmo

Copy link
Copy Markdown
Owner Author

Reviewed at exact head a501a2c. Superseded in part by #1362 for mockups. Production calculator/navigation removals were rejected, and the safe coalescing behavior is already on main. Source branch and worktree are preserved; this PR is closed only to remove the superseded review queue entry.

@BigSimmo BigSimmo closed this Jul 28, 2026
@BigSimmo
BigSimmo deleted the cursor/pr1196-coalesce-main-4711 branch July 30, 2026 09:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant