Clean stale frontend identity and CSS - #14
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Jul 21, 2026
BigSimmo added a commit
that referenced
this pull request
Jul 22, 2026
) - #8 "dead href builders" is NOT dead code: documentReaderHref / documentEvidenceHref are live via the mock wrappers (mockDocumentReaderHref / mockDocumentEvidenceHref) used by the rendered /mockups/document-search/* routes, and are covered by tests/document-flow-routes.test.ts. Removing them breaks the build. Moved to Resolved/archive as a false positive (only the production non-mock hrefs are unlinked from prod UI — a wiring gap, not dead code). - Fix#14 Source path document-viewer/signed-image.tsx -> clinical-dashboard/signed-image.tsx (the document-viewer/ path never existed; it was failing docs:check-links on main). Docs-only. No code/protected-surface edits, no provider/CI/dashboard action. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
BigSimmo pushed a commit
that referenced
this pull request
Jul 22, 2026
…ed (#14) The 44-case eval:quality report printed 'Estimated cost USD: n/a' even with the RAG_EVAL_*_USD_PER_MILLION rates set (PR #1017): every extractive or unsupported case makes no provider call, its per-case estimate was null, and the all-or-nothing total nulled on any null case. A no-usage case costs exactly $0 when rates are configured — null stays reserved for rates-unconfigured, so the total keeps meaning 'cannot estimate'. Aggregation pin added. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EXsJcLrbZUXwnBeG91cVo9
This was referenced Jul 22, 2026
BigSimmo added a commit
that referenced
this pull request
Jul 22, 2026
6 tasks
This was referenced Jul 24, 2026
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
--accentwith the existing--bordertoken.Verification
Local verification under Node 22:
npm run lintpassednpm run typecheckpassednpm run testpassed: 39 files, 240 testsnpm run buildpassednpm run test:e2e:chromiumpassed; Playwright last-run marker reports passed with no failed testsgit diff --check HEAD --passedKnown deferrals
npm run format:checkis still a known repo-wide baseline issue and will be fixed in a separate format-only branch.npm ls --depth=0reports transitive optional native/wasm packages as extraneous even afternpm ci; this is deferred to a separate npm tree-noise investigation.ClinicalDashboard.tsx,DocumentViewer.tsx,rag.ts, and oversized tests is intentionally out of scope.Risk notes