Appearance modes
The workspace offers Dark, Light, and High contrast from Appearance controls in both headers. Desktop shows one native radio group with a pressed active segment; compact screens keep the native select menu. Choosing a segment selects exactly one mode, and the native arrow keys move between choices. Dark is the first-visit default. The browser remembers an explicit selection under sot.appearance; unavailable or stale storage falls back to Dark. Changing appearance preserves the mounted workspace, accepted record edits, filters, selected wells, camera position, and history actions.
One theme, shared geometry
src/app/theme/palettes.ts owns typed shell, scene, table, and status roles. createTheme in theme.ts combines the selected mode with optional typed module overrides. Every mode inherits the same geometry. Extend a semantic role in its module and supply its meaning in each mode; keep scene dimensions and motion in their existing owners.
ThemeProvider sits above the mobile/desktop branch. It publishes the palette as --sot-shell-*, --sot-scene-*, --sot-table-*, and --sot-status-* variables on the document root, including portal content. theme.css maps existing utility roles to those variables. useTheme().theme supplies concrete six-digit hex colors to canvas and dynamic drawing consumers. Use withAlpha(color, opacity) for concrete colors, or CSS color-mix for variable-based tints. A CSS variable string cannot take a hexadecimal alpha suffix.
The provider accepts the same typed module overrides as the factory. The Plate domain keeps its result, storage, and query color identities in stackLens.ts; its concrete mode-aware paint derivation supplies both discs and legends, with usePlateColors sharing those hues with record companions. Dark and Light retain their established domain projection. High contrast maps the green/violet category pair to gold #ffd166 and sky blue #87c9ff, adding a center dot or short bar on otherwise unpatterned faces. A single diagonal identifies failed QC across lenses, suppressing any optional category mark on that face. Consent hold/cancellation take priority; storage textures remain visible beneath the quality mark. Both legend presentations share the same paint projection. The Plate cue research decision records the narrow scope, alternatives and community feedback questions. Existing Dark utility shades remain intact; alternate-mode utility families receive the shared semantic foreground roles. Environment accents are presentation projections of the existing environment IDs; appearance leaves identity and write policy in their established owner.
| Module | Receiving use |
|---|---|
| Shell | Workspace and record surfaces, ordinary text, controls, selected state, borders and focus |
| Scene | Corridor/Plate canvas, grid, particles, scene labels and plate body |
| Table | Specimen header, alternating records, selected rows, detail modules and dividers |
| Status | Success, warning, danger, information and violet category accents; labels and symbols retain their meaning |
Dark retains the navy scene and existing colored paper/ink art. Muted interface text uses a readable member of the same blue-gray family. Light uses pale blue surfaces and dark ink; High contrast uses near-black surfaces, bright text, and stronger dividers. Native controls follow the mode through color-scheme. Neither mode changes reference images or applies an inversion/filter to a 3D carrier. Fixed paper placards with their own dark ink remain paired art elements. The unfurled Plate result tray uses two restrained, downward shadow layers in Light mode to separate its record from the scene; Dark and High contrast retain their existing treatment. Shadows belong to the tray surface, leaving preserve-3D carriers and disc geometry unchanged.
StatusBadge.tsx owns the shared source, requirement, acceptance and release badges. Each domain value selects a typed status role, or the shell's secondary ink for a neutral label. In Light mode, record-badge.css pairs that ink with an opaque 8% tint and a 28% tinted border against the shell surface. This keeps the label readable on ordinary and selected cards without changing badge size or typography. Dark and High contrast retain their existing badge utility paints. The label, rather than its tint alone, identifies the source type, category or state; new variants enter through this shared owner.
Evidence and extension boundary
tests/theme.test.mjs checks all declared ordinary text/surface pairs at 4.5:1 or higher, complete CSS-role coverage, shared geometry, isolated overrides, and preference recovery. tests/plate-paint.test.mjs checks category/key agreement, existing semantic-pattern priority and the unchanged Dark/Light pair. Browser coverage switches actual scenes and accepted records between modes, checks retained state, and exercises the compact selector and reload. High contrast Plate inspection includes ordinary-size faces and legends under deuteranopia and achromatopsia emulation. These checks establish the named pairs and journeys; High contrast is a descriptive mode name rather than a claim of universal color-vision compatibility. Simulation invites investigation and user feedback; it does not validate every deuteranomaly severity or replace observation with people. Existing status labels, shapes, and legends remain necessary.
tests/browser/record-badges.spec.mjs measures actual rendered Light badge foregrounds and opaque backgrounds in Sources, Requirements and Artifacts at compact-desktop and wide widths, including a selected source. It requires the previously weak S3 Doc, YAML and neutral labels to be present and all observed pairs to reach 4.5:1. Focused before/after inspection at those widths preserves Dark and High contrast paints and badge geometry; independently colored scene markers remain with their domain owner.
Run typecheck, the focused theme tests, the 3D guard, and a production build before the focused browser journey. Compare Corridor, selected Sample history, an expanded Specimen record, and a compact viewport in all modes. Add a pair test when introducing a new informational foreground/background combination. Review any independent domain-art palette at its actual receiving surface.
The implementation follows React context for stable shared selection, CSS color-scheme for native controls, and the foreground/background and redundant-encoding principles in Contrast Minimum and Use of Color. The checks below establish the receiving behavior.