Skip to content

feat(dictionary): add the eight-route Dictionary reference mode - #2096

Merged
BigSimmo merged 11 commits into
mainfrom
codex/chat-dictionary-ultimate-dictionary-ultimate
Aug 18, 2026
Merged

feat(dictionary): add the eight-route Dictionary reference mode#2096
BigSimmo merged 11 commits into
mainfrom
codex/chat-dictionary-ultimate-dictionary-ultimate

Conversation

@BigSimmo

Copy link
Copy Markdown
Owner

Summary

  • Adds Dictionary as a full app mode: eight routes under src/app/(search-app)/dictionary/** — Search, Browse, Topics, Topic detail, Definition, Compare, Sources, and the shared mode home.
  • Content is a governed static catalogue of 96 entries in src/lib/dictionary-data.ts, with shared search/filter logic in src/lib/dictionary.ts. Nothing is generated: no clinical synthesis, no retrieval, no ranking, no provider call. Every definition carries its own source designation and review status, surfaced on /dictionary/sources.
  • Interaction: unified open result rows, abbreviation ambiguity handling, URL-owned filters, topic collections, responsive comparisons, phone disclosures, and the Reference Spine visual system.
  • Wired into the existing surfaces rather than bolted on: application launcher, ModeNav, universal search domains and mode context, tools catalogue, docs/site-map.md, docs/codebase-index.md, route reachability, and the design-system adoption manifests. Navigation uses <Link>/router.push and hrefs built from app-modes.ts / tools-catalog.ts; the mode uses the shared shell composer only, so the one-composer-per-page contract holds.

Verification

  • npm run verify:pr-localone stage is knowingly red; see the bundle budget note below.

Gate detail:

  • Passed: check:runtime, check:installed-lock-parity, format:changed, sitemap:check, docs:check-index, docs:check-inventory, docs:check-scripts, docs:check-links, check:branch-review-ledger, check:outstanding-issues, check:ledger-write-discipline, lint, typecheck.
  • Unit suite: Test Files 2 failed | 648 passed | 2 skipped (652) / Tests 2 failed | 6990 passed | 27 skipped (7019). Both failures were run down and neither belongs to this change:
    • tests/private-access-routes.test.ts passes in isolation on this branch: Test Files 1 passed (1) / Tests 145 passed (145). Full-suite contention.
    • tests/session-start-hook.test.ts fails identically on untouched origin/main — Windows resolves bash to WSL's C:\Windows\System32\bash.exe, which strips drive separators. Pre-existing harness issue.
  • Later stages were then run directly: next build reported Compiled successfully, check:client-bundle-secrets passed, check:rag:fixtures 36 golden cases across 25 suites, check:medication-interactions 523 rows, check:medication-lexicon-report 28 catalogue terms — all green.
  • check:bundle-budget fails on the production bucket, and the baseline was deliberately left alone:
[bundle-budget] production (what users download, 109 routes): 1516.8 KiB gzip - baseline 1372.3 KiB, +10.5% vs baseline (tolerance 10%).
[bundle-budget] FAIL - production bundle +10.5% vs baseline (tolerance 10%). This is user-facing weight; find the regression before refreshing the baseline.

Measured attribution, because the +10.5% is not all this PR:

  • main alone measures 1479.1 KiB (+7.8%) against the same baseline. That number comes from a mockup-only branch built from the same merge base, so it is main's own drift. The baseline was captured 2026-08-13 (baselineSourceca788d41) and has not been refreshed since.
  • This PR contributes 33.9 KiB gzip across 11 Dictionary-exclusive chunks, roughly +2.7 points, attributed from the per-route _client-reference-manifest.js files. The two largest are about 10 KiB each: the client-side share of the 96-entry catalogue, and the shared Dictionary UI. The catalogue reaches the client because Browse, Search, Compare and Sources filter interactively with URL-owned state.
  • The five Lighthouse route budgets and the mockups bucket are all within tolerance.

The baseline was not refreshed here: AGENTS.md is explicit that a production failure means finding the regression rather than moving the ceiling, and most of the overage predates this branch. The decision for review is whether to re-baseline production in its own change after accounting for main's 7.8% drift, or to require this PR to move the catalogue server-side and thread it into the client pages as props — about 10 KiB, enough to clear the line, but it reworks the mode's filter model.

  • After the final origin/main sync (11 further commits), npm run lint and npm run typecheck were re-run against the merged tree. The full unit suite and build were not re-run for that sync; the incoming commits touch disjoint files and were already CI-verified on main.

  • tests/ui-dictionary.spec.ts is registered in the Chromium production spec pattern and in the PR shard map, so CI runs it. It was last run green (6/6) before the merge and was not re-run locally afterwards.

  • npm run verify:ui when UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changed

UI verification not run locally after the merge: the full Chromium gate contends with the repository run coordinator on this machine. The Dictionary journey spec is registered and runs in CI.

  • npm run verify:release before release or handoff confidence claims

Verification not run: the release gate is provider-backed and was not authorized for this change.

  • npm run eval:retrieval:quality (must stay 36/36) when retrieval, ranking, selection, chunking, or scoring behavior changed

Verification not run: no retrieval, ranking, selection, chunking or scoring behaviour is touched. The Dictionary reads a static local catalogue; it does not enter src/lib/rag/**, clinical-search, retrieval-selection, ranking-config or answer-ranking, and the offline RAG fixture check still ran and passed.

  • npm run eval:rag -- --limit 15 + npm run eval:quality -- --rag-only when answer generation, the synthesis prompt, or answer post-processing changed

Verification not run: answer generation and the synthesis prompt are untouched.

  • npm run check:production-readiness when clinical workflow, privacy, environment, Supabase, source governance, or deployment behavior changed

Verification not run: no clinical workflow, privacy, environment, Supabase or source-governance behaviour changes — the Dictionary is static local content with no provider, storage or document-access path.

  • npm run check:deployment-readiness when deployment startup, hosting, or rollout behavior changed

Verification not run: deployment startup, hosting and rollout behaviour are unchanged.

Risk and rollout

  • Risk: Moderate. This adds production routes and touches shared navigation/search integration files (app-modes.ts, universal-search*.ts, search-route-ownership.ts, search-shell-props.ts, tools-catalog.ts, ClinicalDashboard.tsx, ClinicalSidebar.tsx, master-search-header.tsx). The Dictionary itself is read-only static content with no write path, no auth surface and no provider call, so the realistic failure mode is a navigation or search-integration regression rather than a clinical one. src/lib/universal-search.ts remains server-only — the two client modules that reference it use type-only imports, so the catalogue does not enter every route's bundle.
  • Rollback: Revert this PR's squash commit. The mode is additive; no existing route, mode or search domain is removed or repointed.
  • Provider or production effects: None. No Supabase, OpenAI, storage or ingestion behaviour changes.

Clinical Governance Preflight

  • Source-backed claims still require linked source verification before clinical use
  • No patient-identifiable document workflow was introduced or expanded without explicit governance approval
  • Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
  • Service-role keys and private document access remain server-only
  • Demo/synthetic content remains clearly separated from real clinical sources
  • Source metadata, review status, and outdated/unknown-source behavior remain conservative
  • Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed

Notes on the preflight: every Dictionary entry is static, source-designated content. /dictionary/sources renders the governance surface, and an entry whose source is unknown or unreviewed displays that status rather than presenting the text as verified fact. The mode introduces no patient data, no document access and no upload or download path. Supabase configuration, service-role credentials and private document access are untouched. The Dictionary defines terminology and does not recommend, diagnose or dose, so it adds no clinical decision-support behaviour and leaves the SaMD/TGA classification unchanged.

Notes

  • Opened as a draft.
  • Branch history: the work was completed on codex/chat-dictionary-ultimate-dictionary-ultimate and committed here, then origin/main was merged in (the branch was 96 commits behind, and a final sync brought it fully current). Six files conflicted; the resolutions worth reviewing are the icon ones, because main refactored icon identity while this branch was open:
    • src/lib/app-mode-icons.ts is now derived from APP_MODE_ICON in src/lib/category-identity.ts, so the Dictionary glyph moved there: bookMarked was added to CATEGORY_ICON_KEYS, resolved to Lucide BookMarked in src/lib/category-identity-icons.ts, and registered as dictionary: "bookMarked" (app mode) and "clinical-dictionary": "bookMarked" (tool).
    • "clinical-dictionary" was added to the ToolCatalogId union in src/lib/tools-catalog.ts, which main introduced to make the icon record exhaustive by type.
    • The two icon maps this branch had edited (launcherIconById in applications-launcher-page.tsx, iconByToolId in tools-search-results-page.tsx) were deleted by main in favour of that single registry; the merge takes main's side rather than reviving either copy.
    • playwright.config.ts and scripts/playwright-pr-shards.mjs keep main's patterns with dictionary re-inserted; docs/design-system/COMPONENTS.md and the design-system adoption manifests were regenerated, not hand-merged.

BigSimmoand others added 4 commits August 18, 2026 12:39
Add Dictionary as a full app mode with a governed 96-entry static catalogue,
shared search/filter logic, and eight routes under src/app/(search-app)/dictionary.
- Routes: Search, Browse, Topics, Topic detail, Definition, Compare, Sources and
the shared mode home.
- Unified open result rows, abbreviation ambiguity handling, URL-owned filters,
topic collections, responsive comparisons and source governance surfaces.
- Reference Spine visual system, simplified definition status, phone
disclosures, and shared navigation/search ownership (no second composer, no
responsive tables).
- Integrated with the application launcher, ModeNav, universal search, tools
catalogue, sitemap, codebase index, route reachability and the design-system
adoption manifests.
- Static source-governed content only: no generated clinical synthesis, no
retrieval or ranking surface touched.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…-ultimate-dictionary-ultimate
# Conflicts:
#	docs/design-system/COMPONENTS.md
#	playwright.config.ts
#	scripts/playwright-pr-shards.mjs
#	src/components/applications-launcher-page.tsx
#	src/components/tools/tools-search-results-page.tsx
#	src/lib/app-mode-icons.ts
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@supabase

supabaseBot commented Aug 18, 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 ↗︎.

@coderabbitai

coderabbitaiBot commented Aug 18, 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:55 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 101 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: ecd392e0-7a78-4bd0-a00b-03e6ece8e8a4

📥 Commits

Reviewing files that changed from the base of the PR and between 70821d6 and 15fd063.

📒 Files selected for processing (61)
  • docs/branch-review-records/958545248192195caf5c7b0a29d7daf058011f92c1b70d00c86aec57fb44822b.record.md
  • docs/codebase-index.md
  • docs/design-system/ADOPTION.md
  • docs/design-system/COMPONENTS.md
  • docs/design-system/adoption-contract.json
  • docs/design-system/adoption-manifest.json
  • docs/redesign/dictionary-reference-spine.md
  • docs/site-map.md
  • playwright.config.ts
  • scripts/generate-site-map.ts
  • scripts/playwright-pr-shards.mjs
  • src/app/(search-app)/dictionary/[slug]/page.tsx
  • src/app/(search-app)/dictionary/browse/page.tsx
  • src/app/(search-app)/dictionary/compare/page.tsx
  • src/app/(search-app)/dictionary/layout.tsx
  • src/app/(search-app)/dictionary/page.tsx
  • src/app/(search-app)/dictionary/search/page.tsx
  • src/app/(search-app)/dictionary/sources/page.tsx
  • src/app/(search-app)/dictionary/topics/[slug]/page.tsx
  • src/app/(search-app)/dictionary/topics/page.tsx
  • src/components/ClinicalDashboard.tsx
  • src/components/clinical-dashboard/ClinicalSidebar.tsx
  • src/components/clinical-dashboard/master-search-header.tsx
  • src/components/clinical-dashboard/mode-action-popup.tsx
  • src/components/clinical-dashboard/universal-search-command-surface.tsx
  • src/components/clinical-dashboard/use-sidebar-pins.ts
  • src/components/dictionary/dictionary-catalogue-pages.tsx
  • src/components/dictionary/dictionary-compare-page.tsx
  • src/components/dictionary/dictionary-home-page.tsx
  • src/components/dictionary/dictionary-result-row.tsx
  • src/components/dictionary/dictionary-sources-page.tsx
  • src/components/dictionary/dictionary-term-page.tsx
  • src/components/mode-nav/header-addon-slot.ts
  • src/components/mode-nav/registry-mode-nav.tsx
  • src/lib/app-modes.ts
  • src/lib/category-identity-icons.ts
  • src/lib/category-identity.ts
  • src/lib/dictionary-data.ts
  • src/lib/dictionary.ts
  • src/lib/information-pages.ts
  • src/lib/mode-secondary-navigation.ts
  • src/lib/search-route-ownership.ts
  • src/lib/search-shell-props.ts
  • src/lib/tools-catalog.ts
  • src/lib/ui-copy.ts
  • src/lib/universal-search-domains.ts
  • src/lib/universal-search-mode-context.ts
  • src/lib/universal-search.ts
  • tests/app-modes.test.ts
  • tests/design-system-adoption.test.ts
  • tests/dictionary-data.test.ts
  • tests/dictionary-term-page.dom.test.tsx
  • tests/information-page-shell.dom.test.tsx
  • tests/mode-nav-addon-slot.dom.test.tsx
  • tests/mode-secondary-navigation.test.ts
  • tests/search-results-band-adoption.test.ts
  • tests/shared-home-empty-state.dom.test.tsx
  • tests/ui-dictionary.spec.ts
  • tests/ui-mode-nav-density.spec.ts
  • tests/ui-tools-search-mode-mockup.spec.ts
  • tests/ui-tools.spec.ts

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

…e link proves
Three review findings on the Dictionary mode, all about a surface claiming more
than it does.
Retire the "updated" filter. Every entry shares one `REVIEW` constant, so all 96
carry `checkedOn: "2026-08-18"`, and the predicate compared that against the frozen
literal `"2025-08-18"`. "Past year" and "Past 6 months" were therefore identical to
each other and to no filter at all: picking either rendered an active, removable
filter chip and returned the whole catalogue. Remove the lens, its URL parameter,
its chip and its share of the applied-filter count rather than leave a control that
advertises narrowing it cannot do. An `updated=` parameter left in an old URL is
ignored, which `parseDictionaryFilters` already covers and the test now states.
Re-add a real cutoff when entries carry distinct review dates.
Rename the review status from `source-checked` to `source-linked`, and rewrite the
governance copy to match. Entries are generated from topic seeds: `sourceRefs`
carries the source published for the entry's collection, and the status literal is
stamped by construction. The sources page previously told a clinician that "editors
have confirmed that the link, organisation and paraphrased wording match the stated
source scope" — nothing in the pipeline establishes that. It now says attribution is
recorded at collection level, is not verified sentence by sentence, and that no
clinician has signed off an individual entry. Approval remains pending throughout.
Stop calling positional links "governed". `relatedSlugs` is the next four entries in
array order, so the term page now says "other entries from the same collection".
Also drop `DictionaryTopic.iconKey`: no Dictionary surface ever read it, and an
untyped glyph string sitting beside the typed `CategoryIconKey` registry is an
invitation to diverge from it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

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.

@github-actions

Copy link
Copy Markdown
Contributor

CI triage

CI failed on this PR. Automated classification of the 3 failed job(s):

  • Buildneeds investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
  • Advisory UIneeds investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
  • PR requiredneeds investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #11965 (cancelled).

Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger.

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Adds a static Clinical Dictionary mode with eight production routes, shared navigation/search integration, source metadata, and responsive UI.

Changes:

  • Adds a 96-entry catalogue with search, browse, topics, definitions, comparisons, and sources.
  • Integrates Dictionary into app modes, universal search, navigation, tools, and shell ownership.
  • Adds unit/UI coverage and generated documentation; the production bundle gate remains unresolved.

Reviewed changes

Copilot reviewed 60 out of 60 changed files in this pull request and generated 3 comments.

Show a summary per file
FileDescription
tests/ui-tools.spec.tsUpdates tools search expectations.
tests/ui-mode-nav-density.spec.tsCovers Dictionary navigation density.
tests/ui-dictionary.spec.tsTests all Dictionary routes and responsive behavior.
tests/shared-home-empty-state.dom.test.tsxCovers Dictionary home presentation.
tests/search-results-band-adoption.test.tsRegisters Dictionary search-band ownership.
tests/mode-secondary-navigation.test.tsTests Dictionary secondary navigation.
tests/mode-nav-addon-slot.dom.test.tsxRegisters Dictionary header owners.
tests/information-page-shell.dom.test.tsxClassifies Dictionary information routes.
tests/dictionary-term-page.dom.test.tsxTests term-page content and disclosures.
tests/dictionary-data.test.tsValidates catalogue integrity and search.
tests/design-system-adoption.test.tsUpdates route adoption totals.
tests/app-modes.test.tsCovers Dictionary search routing.
src/lib/universal-search.tsAdds the Dictionary search adapter.
src/lib/universal-search-mode-context.tsMaps Dictionary mode context.
src/lib/universal-search-domains.tsRegisters the Dictionary domain.
src/lib/ui-copy.tsAdds Dictionary home copy.
src/lib/tools-catalog.tsAdds Dictionary to the tools catalogue.
src/lib/search-shell-props.tsConfigures Dictionary shell behavior.
src/lib/search-route-ownership.tsAssigns Dictionary route ownership.
src/lib/mode-secondary-navigation.tsDefines Dictionary navigation destinations.
src/lib/information-pages.tsRecognizes Dictionary detail pages.
src/lib/dictionary.tsImplements filtering, search, and comparison helpers.
src/lib/dictionary-data.tsDefines the static governed catalogue.
src/lib/category-identity.tsRegisters Dictionary icon identities.
src/lib/category-identity-icons.tsMaps the BookMarked icon.
src/lib/app-modes.tsRegisters Dictionary as an app mode.
src/components/mode-nav/registry-mode-nav.tsxAdds Dictionary navigation icons and density.
src/components/mode-nav/header-addon-slot.tsRegisters Dictionary header slots.
src/components/dictionary/dictionary-catalogue-pages.tsxImplements search, browse, and topic pages.
src/components/dictionary/dictionary-term-page.tsxImplements definition detail pages.
src/components/dictionary/dictionary-sources-page.tsxImplements source governance UI.
src/components/dictionary/dictionary-result-row.tsxRenders mixed Dictionary results.
src/components/dictionary/dictionary-home-page.tsxImplements the mode landing page.
src/components/dictionary/dictionary-compare-page.tsxImplements term comparisons.
src/components/ClinicalDashboard.tsxUpdates shared-mode commentary.
src/components/clinical-dashboard/use-sidebar-pins.tsMakes Dictionary pinnable.
src/components/clinical-dashboard/universal-search-command-surface.tsxAdds Dictionary command results.
src/components/clinical-dashboard/mode-action-popup.tsxAdds Dictionary quick actions.
src/components/clinical-dashboard/master-search-header.tsxAdds Dictionary mode actions and routing.
src/components/clinical-dashboard/ClinicalSidebar.tsxAdds Dictionary to sidebar modes.
src/app/(search-app)/dictionary/page.tsxAdds the Dictionary home route.
src/app/(search-app)/dictionary/search/page.tsxAdds the search route.
src/app/(search-app)/dictionary/browse/page.tsxAdds the browse route.
src/app/(search-app)/dictionary/topics/page.tsxAdds the topics route.
src/app/(search-app)/dictionary/topics/[slug]/page.tsxAdds topic detail routes.
src/app/(search-app)/dictionary/[slug]/page.tsxAdds definition routes.
src/app/(search-app)/dictionary/compare/page.tsxAdds the comparison route.
src/app/(search-app)/dictionary/sources/page.tsxAdds the sources route.
src/app/(search-app)/dictionary/layout.tsxAdds the Dictionary route layout.
scripts/playwright-pr-shards.mjsRegisters Dictionary UI tests in CI.
scripts/generate-site-map.tsAdds the Dictionary mode example.
playwright.config.tsIncludes Dictionary production tests.
docs/site-map.mdDocuments Dictionary routes.
docs/redesign/dictionary-reference-spine.mdDefines Dictionary design and governance.
docs/design-system/COMPONENTS.mdUpdates generated component usage.
docs/design-system/ADOPTION.mdUpdates adoption totals.
docs/design-system/adoption-manifest.jsonRegisters Dictionary design-system roots.
docs/design-system/adoption-contract.jsonAdds Dictionary routes to the contract.
docs/codebase-index.mdDocuments Dictionary architecture.
docs/branch-review-records/958545248192195caf5c7b0a29d7daf058011f92c1b70d00c86aec57fb44822b.record.mdRecords the prior branch review.

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment threadsrc/components/dictionary/dictionary-catalogue-pages.tsx
Comment threadsrc/components/dictionary/dictionary-catalogue-pages.tsx
Comment threadsrc/components/dictionary/dictionary-compare-page.tsx Outdated
BigSimmoand others added 5 commits August 18, 2026 15:50
…es, and correct the tool tally
Addresses two Copilot review findings on #2096 and the Advisory UI failure.
- The "Source organisation" facet rendered one option per source id but labelled each
by its organisation, and five of the twelve sources are published by Healthdirect
Australia. Users saw five identical options, each filtering to a different single
document. The facet is now "Source", labelled by each source's own title, with the
organisation kept as search text and the applied chip matching.
- The compare page discarded `pair.sourceRefs`. Those references back the curated
relationship summary specifically, so MSE vs MMSE declared two comparison sources
while the footer counted one. They now count toward the covered-source total and
render as links beside the summary they support.
- `ui-tools-search-mode-mockup.spec.ts` asserted exactly 13 tool results. The mockup
renders the production `ToolsSearchResultsPage` from the shared catalogue, and the
Dictionary makes that 14.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…-ultimate-dictionary-ultimate
# Conflicts:
#	docs/design-system/adoption-manifest.json
@BigSimmo
BigSimmo enabled auto-merge (squash) August 18, 2026 08:58
@BigSimmo
BigSimmo merged commit 2f04dd9 into mainAug 18, 2026
25 of 26 checks passed
@BigSimmo
BigSimmo deleted the codex/chat-dictionary-ultimate-dictionary-ultimate branch August 18, 2026 09:03
Sign up for freeto 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.

2 participants

@BigSimmo