chore(deps): bump @next/env from 16.2.9 to 16.2.10 - #309
Merged
Conversation
Bumps [@next/env](https://github.com/vercel/next.js/tree/HEAD/packages/next-env) from 16.2.9 to 16.2.10. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](https://github.com/vercel/next.js/commits/v16.2.10/packages/next-env) --- updated-dependencies: - dependency-name: "@next/env" dependency-version: 16.2.10 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
# Conflicts: # package-lock.json
BigSimmo
enabled auto-merge
July 6, 2026 16:10
BigSimmo
pushed a commit
that referenced
this pull request
Aug 12, 2026
The Codex P2 on PR #1858 is correct — nine derived domains should be in the 6-20 dense-list band, and ResultFilterFacetChips has only a chip layout. Making the shared renderer density-aware is a design decision affecting every facet consumer and overlaps the tier PR F ports up from documents, so it is captured rather than folded into a mode adoption. Services hits the same rule via the >3-groups branch, so it should be settled before or with PR C. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011btGFwWKYFWDs5McQkqz9J
BigSimmo
added a commit
that referenced
this pull request
Aug 13, 2026
) * feat(services): adopt the filter contract with real facets (PR C) Services gains its first real filtering: five typed dimensions (catchments, age_groups, setting_flags, acuity_flags, housing_flags) become facets with union counts, substance_flags ships as a lens (an exact partition — every service carries exactly one of general/aod), and a scope segment escapes a filtered-to-zero state without discarding the query. The six query-replacing "quick filters" are evicted from the filter sheet to AnswerSuggestionChips, closing the navigate-kind defect docs/filter-contract.md exists to remove. The shared filter renderer (ResultFilterSheet/ResultFilterFacetChips) grows a dense tier — find-a-filter plus collapse-by-default — for services' 5 groups / 24 options, resolving the open density decision tracked as /issues #309. The OR-within-group/AND-across-group selection algorithm is extracted from document-tags.ts into facet-selection.ts so services and documents share one counting rule rather than each inventing their own. Live-registry verification that catalog_payload.tags is fully populated on the production Supabase project is still outstanding — rowToServiceRecord degrades conservatively to empty facets if it isn't, and this is called out explicitly for review. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K1kfPCeWWSrbprFz56UeDD * docs(ledger): record PR #1882 review row (services filter contract) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K1kfPCeWWSrbprFz56UeDD * fix(services): preserve query and lens-scope facet counts * test(services): verify scope widening preserves query * chore: retain current Run PR workflow and shared ledger * fix: use lens-scoped services for care type counts * style: format services filter journey assertions * style(services): format navigator page * style(services): format tools UI coverage --------- Co-authored-by: Claude <noreply@anthropic.com>
BigSimmo
pushed a commit
that referenced
this pull request
Aug 13, 2026
Services gains its first real filtering: five typed dimensions (catchments, age_groups, setting_flags, acuity_flags, housing_flags) become facets with union counts, substance_flags ships as a lens (an exact partition — every service carries exactly one of general/aod), and a scope segment escapes a filtered-to-zero state without discarding the query. The six query-replacing "quick filters" are evicted from the filter sheet to AnswerSuggestionChips, closing the navigate-kind defect docs/filter-contract.md exists to remove. The shared filter renderer (ResultFilterSheet/ResultFilterFacetChips) grows a dense tier — find-a-filter plus collapse-by-default — for services' 5 groups / 24 options, resolving the open density decision tracked as /issues #309. The OR-within-group/AND-across-group selection algorithm is extracted from document-tags.ts into facet-selection.ts so services and documents share one counting rule rather than each inventing their own. Live-registry verification that catalog_payload.tags is fully populated on the production Supabase project is still outstanding — rowToServiceRecord degrades conservatively to empty facets if it isn't, and this is called out explicitly for review. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K1kfPCeWWSrbprFz56UeDD
BigSimmo
pushed a commit
that referenced
this pull request
Aug 13, 2026
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011btGFwWKYFWDs5McQkqz9J
4 tasks
BigSimmo
pushed a commit
that referenced
this pull request
Aug 13, 2026
… band The Codex reviewer on PR #1925 is right and my closure was wrong. Verified on main 2d27039: result-filter-control.tsx computes const dense = facetGroups.length > 3 || totalFacetOptions > 20 so formulation — one facet group of nine derived domains, the exact case that opened #309 — evaluates dense=false and still renders a wrapping chip row. The 6-20 full-width tier with its right-aligned count column does not exist, and neither does the nine-option DOM assertion the row asked for. What PR F (#1910) delivered is the upper tier: find-a-filter and collapse for >3 groups or >20 options, which is what documents needed. Section 5 has two thresholds; I conflated them and would have archived the row whose specific band is unbuilt. Replaces the done request with an update recording the partial delivery, what remains, and an explicit stop rule against closing on the strength of the upper tier. #170 is unaffected — mode adoption did complete. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011btGFwWKYFWDs5McQkqz9J
BigSimmo
added a commit
that referenced
this pull request
Aug 13, 2026
BigSimmo
added a commit
that referenced
this pull request
Aug 18, 2026
… favourites timestamps, and answer notice (#309, #281, #339, #165) (#2074) * feat(ui): implement filter density tiers, mobile route deduplication, favourites timestamps, and answer notice (#309, #281, #339, #165) * fix(ui): repair CI blockers on filter density tiers (PR #2074) * fix(ui): keep document-viewer retry panel ids unique under density tiers (PR #2074) * fix(favourites): fix O(N²) storage callbacks and hydration mismatch in useSyncExternalStore Co-authored-by: BigSimmo <87357024+BigSimmo@users.noreply.github.com> * style: fix prettier formatting in favourites command library page CI's format:changed check was failing on this file's useSyncExternalStore formatting. * fix(ui): keep document rail high-yield summary visible when printing `max-sm:hidden` (added to dedupe the summary panel on phone viewports) also suppressed it during print emulation at narrow viewport widths, since the print stylesheet only restores overflow/box-shadow and never overrides display:none. Add `print:block`, the pattern already used elsewhere in this codebase (verification-notice.tsx, medication-considerations.tsx) to keep a responsively-hidden element printable. Fixes the "document viewer content disclosures are naturally closed and mutually exclusive by default" Production UI failure, which set a 390px viewport and asserted the high-yield-summary content becomes visible under print media. * fix(test): update high-yield summary nav assertion for mobile dedup The exclusive-accordion assertions after clicking the "High-yield summary" section-nav row assumed the rail's <details id="source-summary"> still opens on a 390px viewport. Since the mobile route-dedup change hides that rail copy (max-sm:hidden) in favour of the always-visible in-flow DocumentClinicalSummary card, jumpToDocumentSection's existing "displayed copy" resolution (use-section-spy.ts's source-summary -> source-summary-card alias) now scrolls to the card instead of toggling the hidden accordion — so `summary.open` never becomes true at this viewport. Assert the visible copy scrolls into view instead, matching the pattern already used for the "Indexed source text" row above it. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com>
7 tasks
BigSimmo
pushed a commit
that referenced
this pull request
Aug 18, 2026
…favourites/filter-contract scope Resolves 10 real merge conflicts and removes content that should never have shipped on this branch: - Reverts the fabricated "Clinical Lead APPROVED" sign-off in docs/medication-interaction-lexicon-review.md back to the true unreviewed placeholder. Line 3 of the same file still says "Status: UNREVIEWED" - the sign-off table contradicted its own document and named no real reviewer. - Reverts the Warfarin record merge (warfarin-vka / warfarin-anticoagulant) in data/medications-snapshot.json. A prior explicit decision on this exact question (ledger #322) chose "leave it, flag for clinical review" over merging, because the row says merging is not an agent's call. - Reverts all edits to src/lib/medication-interaction-lexicon.ts. Beyond the two changes disclosed in the PR body (loperamide exclusion, NSAID narrowing), the branch silently deleted 18 lexicon terms covering antibiotics, penicillins, cephalosporins, oral contraceptives, sulfonylureas, calcium channel blockers, and methotrexate (immunosuppressants), among others - undisclosed in the PR body and covered by a code comment describing an unrelated "z-drugs" removal that does not correspond to anything actually deleted here. - Restores src/app/api/images/signed-urls/route.ts, which the branch deleted as "dead uncalled" code. It is not dead: main now calls it from src/lib/batch-signed-urls.ts via useBatchSignedImageUrls, used by document-search-results.tsx and source-panels.tsx, plus a route alias at /api/documents/signed-urls that re-exports from this exact file. Restores its tests in tests/private-access-routes.test.ts and its docs/site-map.md entry accordingly. - Reverts docs/filter-contract.md and src/components/clinical-dashboard/ result-filter-control.tsx to main's content: the branch was reverting the already-landed three-tier filter density fix (ledger #309, main commit 0b5b92c) back to two-tier behavior. - Reverts src/components/favourites/favourites-storage.ts (add/add conflict - the branch independently reinvented a file that already exists on main, dropping main's shared-module-level storage listener fix that avoids O(N^2) callback fan-out) and favourites-command-library-page.tsx (main's useSyncExternalStore calls use a stable empty-literal server snapshot; the branch's version called the client storage-reading function as the SSR snapshot too). - Resolves the DocumentViewer.tsx id conflict in favour of main's "source-summary-card", which use-section-spy.ts's section map and tests/ui-smoke.spec.ts both depend on; the branch's plain "source-summary" would collide with the nav rail's own id of the same name. - Resolves the document-rail-panels.tsx className conflict in favour of main's print:block utility. Kept: the Crop-to-Page Bounding Box Overlay feature (#320) in full (bbox-overlay.ts, PdfCanvasViewer/PdfPageSlot wiring, DocumentViewer.tsx highlightedBbox wiring, document-detail-contract.ts and document-detail.ts bbox typing/normalization, tests/bbox-overlay.test.ts), the disclosed and verified-safe therapies.ts/therapy-ranking.ts modality field removal, and the outstanding-issues-inbox request files.
BigSimmo
pushed a commit
that referenced
this pull request
Aug 18, 2026
Cancels four pending requests found while diagnosing the docs:check-links CI failure — two were duplicates of already-applied requests (#222, #336, each already closed by a different, more accurate applied request), and two asserted "done" outcomes for work this branch's final state does not actually contain after the fabricated-content revert (#318: lexicon sign-off and loperamide exclusion; #309: filter-density fix). All four are cancelled via immutable cancel requests rather than deleted, per ledger-write discipline.
BigSimmo
pushed a commit
that referenced
this pull request
Aug 18, 2026
Cancels 88868df4-c310-4ac2-9e83-cd3ad7702a1d, another false "done" claim from this branch's original batch (same pattern as #222/#318/#309/#336): #183 asks for a live Sentry production metric alert, blocked on missing credentials and unreachable via a code diff. This branch's actual final diff contains no Sentry or alerting changes. Also resolves a collision with a separate, legitimate concurrent update request on the same row from an unrelated branch.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps @next/env from 16.2.9 to 16.2.10.
Release notes
Sourced from @next/env's releases.
Commits
9dadfd6v16.2.10534d9c1[16.2.x] Release pipeline updates (#95160)6e1a94d[16.2.x][ci]: fix release script to not strip newlines (#94640)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)