Skip to content

M3 - Refined GUI complete

Open
No due date
•Last updated Nov 22, 2026

Goal (owner 2026-10-22, runs in parallel with M1 and M2): the Refined UI redesign (#18237) is fully implemented and working in both apps: tokens and themes, shell, one shared kit and one ApiClient, dashboards, and every step-5 section, with no forked components between the two GUIs. The backend behind a screen may be partial, but the screen must handle a missing backend honestly (an empty or not-available state, never a broken page). Exit: every #18237 build step is closed with code evidence; the cross-GUI duplication guard is green; i18n has no hardcoded strings on the new screens.

Phases, in order (filter issues with label phase:M3.N):

  • M3.1 (label phase:M3.1) Design docs, tokens and themes. Done when: #18238's acceptance boxes are ticked, all four themes switch in both apps from one token source, and the duplicate-token guard fails on a second base declaration (#17566 SLM tokenisation is done per screen in M3.6, owner decision 2026-10-22)
  • M3.2 (label phase:M3.2) Shell: top nav, UI mode, appearance, brand. Done when: Both apps use the new top nav, UI mode and profile appearance, and the brand mark replaces the stock logo, the social preview and the README hero
  • M3.3 (label phase:M3.3) Shared kit primitives. Done when: No component in either app re-implements a kit primitive (KIT_FORK_GRANDFATHER is empty) and the design-system registry in code names each kit owner
  • M3.4 (label phase:M3.4) One ApiClient and generated types. Done when: Each app has one HTTP client module with generated OpenAPI types, no production file calls fetch directly, and the codegen check is required
  • M3.5 (label phase:M3.5) Dashboards with movable widgets. Done when: Dashboard widgets move and resize by mouse and keyboard, each shows one header, and every figure is measured or shown as not reported
  • M3.6 (label phase:M3.6) SLM platform screens. Done when: Every server-wide screen exists only in the SLM app in the new design, a guard holds the boundary, the user app's Platform admin opens it, and screens without a backend show an honest empty state
  • M3.7 (label phase:M3.7) Company OS, Automation and BI screens. Done when: Every Company OS, Automation and BI screen uses the kit and the new design, approvals and workflow runs each have one component, approvals enforce expiry and ownership, and screens without a backend show an empty state
  • M3.8 (label phase:M3.8) Knowledge screens. Done when: Knowledge screens use one graph component and the new design, with upload and transcriber intake reachable from the UI
  • M3.9 (label phase:M3.9) Chat, Agents, Analytics and Settings screens. Done when: Chat, Agents, Analytics, Settings and Account screens use the new design, chat has a stop control and one tool-approval gate, and Usage is gated by role with an empty state
  • M3.10 (label phase:M3.10) New screens and cross-cutting close-out. Done when: Each step-6 screen ships with its backend or an honest empty state, every new-design view uses t() keys in all locales, the SFC clone pin is lowered, and every #18237 child is closed with code evidence
64% complete

Issues