issues: flag #336/#222/#321 as merged-but-unresolved, #322 as in-progress

[BigSimmo]

Summary

• Queues four immutable docs/outstanding-issues-inbox/ update requests (no canonical ledger edits — reconciliation applies them later), recorded from this session's open-PR review sweep on bigsimmo/Database:
  • #336 (named responsive breakpoint tokens): PR feat(ui): standardize responsive breakpoint tokens and align header/secondary controls (#336, #222, #321) #2072 merged citing this row and the tokens now exist in src/app/globals.css, but the row's required decision — record raw-vs-named-tokens in docs/design-system/GATES.md — was never made (GATES.md untouched since PR Keep mobile sheet headers below device safe areas #1990, no mention of breakpoints). Stays open.
  • #222 (headers surface styling convergence): feat(ui): standardize responsive breakpoint tokens and align header/secondary controls (#336, #222, #321) #2072 shipped only a cosmetic font-weight tweak and an empty-state class alignment, not the PageHeader/EmptyState convergence decision the row asks for. Stays open.
  • #321 (differentials compare/filmstrip/DocumentViewer control alignment): feat(ui): standardize responsive breakpoint tokens and align header/secondary controls (#336, #222, #321) #2072's file list never touched any of these files despite citing the row. Stays open.
  • #322 (Warfarin catalogue record dedup): PR feat(medications): reconcile Warfarin records and connect catalogue drugs into interaction graph (#322, #323) #2069 is open and targets this row — it reconciles both duplicate records to the same interaction set, but its own new coverage test still fails because the two records don't cross-resolve each other by name (a content/authoring decision, not a mechanical fix). Flagged so a future session doesn't open a duplicate PR for the same dedup work.
• No product code changed. This PR only adds request files under docs/outstanding-issues-inbox/.

Verification

• npm run check:outstanding-issues — "Ledger inbox check passed: 20 pending request(s), 217 applied." / "Outstanding-issues guard passed: 348 rows (97 open, 251 archived)..."
• npm run verify:pr-local — not run: this is a docs/ledger-inbox-only change (Tier 1, static/focused per docs/process-hardening.md); check:outstanding-issues is the exact gate that covers request-file validity and write discipline for this change class.
• npm run verify:ui — not applicable, no UI/routing/styling change
• npm run verify:release — not applicable, not a release/handoff gate

Risk and rollout

• Risk: none — additive, immutable request files only; does not touch docs/outstanding-issues.md itself (canonical edits only happen via a dedicated npm run issues:reconcile branch).
• Rollback: revert this PR.
• Provider or production effects: None.

Notes

• Related work from the same session: closed PRs chore(deps): bump node from 24-bookworm-slim to 26-bookworm-slim in the docker-images group #2013, feat(design-system): adopt standard ErrorState and MissingValue components (#299, #268) #2066, feat(clinical): split ICD-11 Trance Disorder nodes and expand threshold validation (#062, #035) #2070 (with rationale comments); pushed a formatting fix + main-sync to feat(medications): reconcile Warfarin records and connect catalogue drugs into interaction graph (#322, #323) #2069; confirmed Unify the card layer behind one category-identity registry #2060's previously-flagged merge conflict was already resolved by its own author.

---

Generated by Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

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: 10 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 100 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour.

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: 3059cdef-3ecc-4b0c-a122-1ba3153c2d51

📥 Commits

Reviewing files that changed from the base of the PR and between ba4b8d1 and 21e4355.

📒 Files selected for processing (4)

• docs/outstanding-issues-inbox/1505ba13-1b2a-47c9-b6cc-03b060f7a878.json
• docs/outstanding-issues-inbox/779bc0e9-c28f-40ab-abda-cfdcf93ea752.json
• docs/outstanding-issues-inbox/8e28c783-d655-4480-852c-bafaf0b3c07b.json
• docs/outstanding-issues-inbox/a39af37c-b4dd-4e4b-84dc-395d86937615.json

---

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

[supabase]

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 ↗︎.

[Copilot]

Pull request overview

This PR updates the outstanding-issues workflow by adding four immutable inbox request JSON files under docs/outstanding-issues-inbox/ to record status updates (merged-but-unresolved for #336/#222/#321, and in-progress context for #322) without editing the canonical docs/outstanding-issues.md ledger directly.

Changes:

• Add an inbox update request for #336 noting the responsive breakpoint tokens landed but the required design-system decision record did not.
• Add inbox update requests for #222 and #321 noting PR #2072 cited them but did not implement their actual scope.
• Add an inbox update request for #322 flagging an in-progress PR and why it is not yet fully resolved.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
docs/outstanding-issues-inbox/a39af37c-b4dd-4e4b-84dc-395d86937615.json	Adds an update request capturing #336 as merged-but-unresolved (decision record still missing).
docs/outstanding-issues-inbox/1505ba13-1b2a-47c9-b6cc-03b060f7a878.json	Adds an update request capturing #222 as merged-but-unresolved (scope not actually addressed).
docs/outstanding-issues-inbox/779bc0e9-c28f-40ab-abda-cfdcf93ea752.json	Adds an update request capturing #321 as merged-but-unresolved (no relevant files changed).
docs/outstanding-issues-inbox/8e28c783-d655-4480-852c-bafaf0b3c07b.json	Adds an update request capturing #322 as in-progress to prevent duplicate parallel work.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.