3 commits

Author	SHA1	Message	Date
Daniel	9df2230479	refactor: rebuild the admin settings page around what each card does ... The page had grown by accretion: model discovery scattered across five cards with a search box each, one Save writing eight keys from the bottom of a card that also held a second Save for something else, and a banner apologising that a button "applies only the settings above it". Now it reads in groups — Accounts, Models, Assistant & prompts, Site — and every card is a <details> that folds, so Save & Close means something. The rule is that each card saves exactly what it shows, which is what removed the need for the banner. Models is one workflow in three steps. Discover & test has a single search box and a kind switch (chat / image / speech / transcription / embedding); the five discovery calls are unchanged, the switch only decides which one answers. Roster is what has been added, including the image roster, which had no visible list before. Availability is the chat model, the two allowed lists, the per-workflow image settings and the slide reviewer, under one Save. Splitting the eight-key save follows from that rule: Save & Close writes the five retrieval and citation keys; Save availability writes the chat model, both allowed lists, the reviewer and the three image-settings PUTs. No route, request shape or setting key changed. Switching kind clears the results first — a row button would otherwise add an image model to the chat roster. The kind switch dispatches its event through document.defaultView's CustomEvent. jsdom refuses one built from another realm, and the existing announceModelsChanged() has exactly that bug: its event is built from the Node global, dispatchEvent refuses it, and a try/catch swallows the error — so models-changed propagation has only ever been source-grepped, never actually tested. Left alone here to keep this change to one subject. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dv6sqaY6Vq3ChZHMem3cnU	2026-09-12 21:42:27 +02:00
Daniel	1f06a19007	feat: a text-only model can ask a model that can see; and the image regex is gone ... **The regex is gone.** The route ran a pattern over the user's message and enqueued an image from the answer text when the model had not called the tool. It was a compatibility path for models without tool calling and it did more harm than good: it decided in English only, it could not see the conversation, and "image summary" fell through it while reading as an obvious image request to the model itself — which was measured, not assumed. A second and worse decision-maker sitting behind the first. Whether a message deserves a picture is now the model's call, made from the tool description, which is the only place it ever belonged. **Lending eyes.** The same shape, for a different capability. When someone attaches a photograph and the chat model cannot accept image input, the attachment was either refused by the provider or silently dropped — an answer about a picture nobody had looked at, which is worse than a refusal. The chat model is now offered look_at_image beside the image tool and decides when to use it. The attachment goes to clinical_assistant.vision_model, whose description comes back as a tool result, and the chat model answers in its own voice with its own sources. Only the seeing is delegated; the clinical reasoning stays with the model an administrator chose. The seeing model is told to report and not to diagnose, because it has a picture and no context and an opinion from it would carry weight it has not earned. Delegation triggers only on an explicit supports_vision: false from the gateway. An unknown is left alone — most of a roster reports nothing, and treating silence as blindness would route good models through a detour. The capability lookup moved to its own module, is cached for five minutes because it runs on exactly the requests that are already slowest, and is never inferred from the model id. liteLLMBaseUrl moved from the admin route to litellm.js, where the other gateway helpers live. The new setting is guarded like the slide reviewer: a model the gateway calls text-only cannot be saved as the one that looks at images. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dv6sqaY6Vq3ChZHMem3cnU	2026-09-12 15:43:36 +02:00
Daniel	67e416c6d9	docs: merge the duplicate pairs and correct them against the running app ... Three pairs of docs described the same thing twice, and the copies had drifted apart. Merged each into one file, keeping the unique content from both: - ARCHITECTURE.md -> architecture.md (its operational map: ownership, request flow, runtime boundaries, source of truth, deployment shape) - DEVELOPMENT.md -> developer-guide.md (change workflow, Clinical Assistant high-risk areas, frontend rendering rules, deployment checks) - transcription-options.md -> speech.md (the clinic setup table, and the list of browser-Whisper paths that must stay removed) Then audited what remained against the code and the live database rather than against the previous docs. Corrected: - Google Vertex was still documented as a provider across nine files. The SDK is gone; AI_PROVIDER=vertex now logs an advisory and falls back to OpenRouter, and Gemini is reached through LiteLLM. Fixed the provider selection order to match src/utils/ai.js, which starts from LITELLM_API_BASE. - promptSafe was documented on 8 routes; it is on 13. - Node 20 -> 24, "24 vanilla JS modules" -> no fixed count, and transcribe.js/tts.js -> sttProvider.js/ttsProvider.js, which is what exists. - STT/TTS are LiteLLM-only; README listed direct Google, AWS Transcribe and ElevenLabs paths that are not in the runtime. - Learning Hub PPTX export was documented as pptxgenjs, which is not a dependency. It is pandoc against a reference deck. - POST /api/admin/milestones/seed does not exist; it is /bulk-import. - NEXTCLOUD_URL and NTFY_TOPIC are not read anywhere. Nextcloud is per-user in the users table, and the ntfy topic is derived as pedscribe-{userId}. - A prose paragraph sat inside the Clinical Assistant settings table, so half the rows rendered as text. Filled the gaps the audit exposed: - database.md was missing 12 of 29 tables, including user_resources, personal_notes, login_codes, registration_invites and generated_image_jobs. - developer-guide.md was missing 11 routers and 10 frontend modules. - api-reference.md detailed 121 of 244 endpoints and said so, but whole features were absent. Added an endpoint index covering Clinical Assistant, My Resources, Notes, Diagrams, ED Encounters, invites and sign-in codes. - configuration.md was missing METRICS_TOKEN, REDIS_URL, API_RATE_LIMIT_MAX, the LITELLM_* model variables, the DB_* ones maintenance.js reads, and the per-purpose S3 resolution scheme. - clinical-assistant.md documented 2 of its 17 environment variables. - features-explained.md had no entry for My Resources or Clinical Assistant. Renamed the three remaining SHOUTING filenames to kebab-case, which is what the docs viewer's prettyName() was working around, and rewrote README's index, which listed architecture.md twice and omitted nine files. Noted but not changed: the Turnstile site key is hardcoded in index.html rather than read from TURNSTILE_SITE_KEY, and /api/health/detailed can report tts: 'elevenlabs' though no ElevenLabs path exists. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dv6sqaY6Vq3ChZHMem3cnU	2026-09-12 04:57:35 +02:00

Renamed from docs/CLINICAL_ASSISTANT.md (Browse further)