@micha.bigler/ui-core-micha 3.14.3 → 4.0.0

package/work-orders/UCM-MSG-20.md

@@ -1,192 +0,0 @@
-# UCM-MSG-20 — Message composer collapses on narrow screens
-
-# A. Envelope — authored by the Expertenchat
-
-## Goal & expected outcome
-
-- Goal: on a 375 px phone a person can type and send a message in every conversation type.
-- Expected outcome:
-  - The text field keeps a usable width (at least most of the row) next to the action icons; the send
-    button is fully visible.
-  - URLs in messages are clickable links.
-  - The read marker next to the time explains itself (label or tooltip), or is not shown where it
-    carries no information.
-
-## Context — measured 2026-09-29 in jg-ferien's local browser test (ucm 3.5.0 installed there)
-
-- jg-ferien, event announcement conversation, 375 px: next to four icon buttons (attach, emoji, poll,
-  announce) the textarea is **16 px** wide (its field 44 px), "Senden" is clipped (44 px), the row
-  overflows (315 of 295 px).
-- Component: `src/messaging/Composer.jsx` (row layout incl. the four icon buttons,
-  `allowAnnouncement` prop); `src/messaging/MessageBubble.jsx` shows a bare "0/0" next to the time.
-- Long words and URLs wrap correctly inside the bubble; URLs are plain text.
-- The dcm register is canonical for `MSG-*`; this is the ucm-side row.
-
-## Scope + non-goals
-
-- In scope: composer layout at narrow widths (e.g. actions collapse into one menu, or wrap to their
-  own row), linkified URLs, an explained or hidden read marker.
-- Explicit non-goals / do-not-touch:
-  - No change to message sending, polls or announcements behaviour.
-
-## Tier · gates
-
-- **Tier 3** — shared-core component.
-- Reviewer: `reviewer` (all lenses; linkify is new logic) · `ui_reviewer` · `sec_reviewer` (linkify
-  must not create script or `javascript:` links).
-- **Done means released and jg-ferien's pin bumped.**
-
-## Risks
-
-- Linkify is an injection surface: only `http(s)` URLs, `rel="noopener noreferrer"`, no HTML from
-  message text.
-
-## Required tests to WRITE (you write them and run YOUR OWN new ones; the orchestrator's run is the gate)
-
-1. At 375 px width the textarea has at least a defined minimum width and the send button is not
-   clipped, with all four actions enabled.
-2. `https://…` in a message renders as a link; `javascript:…` does not.
-3. The read marker has an accessible label or is absent.
-
----
-
-# B. Implementation map — filled by the Orchestrator — ADDRESSED TO THE IMPLEMENTER
-
-## Context package — three independent fixes, same file family
-
-### 1. Composer overflow at narrow widths — `src/messaging/Composer.jsx`
-
-- The single overflowing row is at line 139:
-  `<Stack direction="row" spacing={1} alignItems="flex-end">` — it holds, in order: the hidden file
-  `<input>`, 4 `IconButton`s (attach `:141`, emoji `:142`, poll `:143`, announce `:144` conditional
-  on `canAnnounce`), the `TextField` (`:145`, `fullWidth multiline minRows={2}`), and the Send
-  `Button` (`:146`).
-- **Fix: split into two stacked rows, not one collapsing menu** (the WO's "or wrap to their own
-  row" option — simplest, lowest-risk, no new interaction pattern to test):
-  1. First row: a `<Stack direction="row" spacing={1}>` containing only the icon buttons (attach,
-     emoji, poll, and the conditional announce button) — 3–4 icon buttons at ~40px each comfortably
-     fit 375px on their own.
-  2. Second row: `<Stack direction="row" spacing={1} alignItems="flex-end">` containing only the
-     `TextField` and the Send `Button`.
-  3. Give the `TextField` `sx={{ flex: 1, minWidth: 120 }}` (so it never collapses to near-zero
-     width when squeezed) and the Send `Button` `sx={{ flexShrink: 0 }}` (so it is never the thing
-     that gets clipped — it should shrink last, if at all).
-  4. Everything else in the file (state, handlers, the poll/announcement dialogs, the emoji
-     popover) is unchanged — this is a pure JSX layout restructure of one `Stack`.
-- Test file: extend `tests/messagingComposer.test.jsx` (existing — read it first for the render
-  harness/mock-provider pattern already in use, follow it exactly rather than inventing a new one).
-  Add: render the `Composer`, resize the test's container is not meaningful in jsdom (no real
-  layout), so instead assert via computed style: the `TextField`'s wrapping element has
-  `minWidth: '120px'` (or your chosen value) and the Send button's element has `flexShrink: '0'` —
-  both readable via `window.getComputedStyle`, same technique as
-  `tests/StatTile.test.jsx`'s `accent` test. Also assert all four action buttons
-  (`MessagingComposer.ADD_ATTACHMENT`/`ADD_EMOJI`/`MessagingPoll.CREATE`/
-  `MessagingAnnouncement.CREATE` — pass `allowAnnouncement` + a non-`direct` `conversation` prop to
-  exercise the fourth) are present and not `disabled` (aside from the poll button's existing
-  `pollOpen || files.some(isImage)` guard, unrelated to this WO).
-
-### 2. Linkify `http(s)` URLs — new file `src/messaging/linkifyText.jsx`
-
-- No linkify library exists in this repo's dependencies today (checked — do not add one; a
-  dependency addition needs separate approval this WO does not have, and the requirement is narrow
-  enough not to need one).
-- Export a pure function `linkifyText(text)` returning an array of strings and `<a>` React elements
-  (a `key`ed fragment-safe array, the same shape `.map()` output must have). URL matching: a strict
-  **`http://` or `https://` prefix only** — e.g.
-  `/(https?:\/\/[^\s<>"']+)/g` — so a `javascript:`, `data:`, or any other scheme can never match
-  the pattern in the first place (that is the actual security property the sec_reviewer will check
-  for — not an escaping step, an inclusion-list pattern that structurally cannot match anything
-  else). Split `text` on that pattern; for each URL match render
-  `<a href={url} target="_blank" rel="noopener noreferrer">{url}</a>`; non-matching segments pass
-  through as plain strings (React renders an array of strings/elements fine as children).
-- Trim likely trailing punctuation that is prose, not part of the URL (a trailing `.`, `,`, `)`,
-  `!`, `?` immediately followed by a word boundary or end of string) so `"see https://x.com."` does
-  not link the sentence-ending period — check `tests/` for whether any existing kit code already
-  does this trimming (grep `messagingContractConformance` / `messagingApi` tests for a URL-trimming
-  precedent) before inventing your own rule; if none exists, a simple trailing-punctuation strip is
-  sufficient, name it in your `PROGRESS` narration.
-- Wire it into `src/messaging/MessageBubble.jsx:149` — the `<Typography sx={{ whiteSpace:
-  'pre-wrap', overflowWrap: 'anywhere' }}>{...}</Typography>` that renders the message body: replace
-  the raw string child with `linkifyText(<same expression>)` for the non-deleted, non-empty case
-  (deleted messages keep rendering `t('MessagingThread.DELETED')` as plain text, unlinkified).
-- Test file: new `tests/messagingLinkify.test.jsx` (or extend an existing `MessageBubble` test if
-  one already covers body rendering — check `tests/messagingChunk6.test.jsx` and
-  `tests/messagingCompactBubble.test.jsx` first).
-  1. A message body containing `https://example.com/path` renders an `<a>` with that exact `href`,
-     `target="_blank"`, and `rel="noopener noreferrer"`.
-  2. A message body containing the literal text `javascript:alert(1)` renders it as plain text —
-     assert `screen.queryByRole('link')` is `null` and the literal string is present as text.
-  3. A message body containing both a URL and surrounding prose renders the prose as plain text
-     and only the URL portion as a link (i.e. the split doesn't eat the surrounding words).
-
-### 3. Read marker explains itself — `src/messaging/ReadTicks.jsx`
-
-- Both existing branches already set `aria-label` (line 74's `<span role="img">`/`<ButtonBase>` for
-  the counted case, line 80's `<StatusIcon role="img">` for the DM case) — that covers screen
-  readers, but `aria-label` is invisible to a SIGHTED user looking at a bare "0/0", which is the
-  Envelope's actual complaint ("explains itself (**label or tooltip**)" — the current label is
-  ARIA-only, not a visible one).
-- Fix, at the `hasCounts` branch (line 56 onward): wrap the returned ratio element in MUI's
-  `Tooltip` (already imported patterns exist elsewhere in the kit, e.g. `UserListComponent.jsx`'s
-  `<Tooltip title={...}>`) using the same `label` text as the `title`, so hovering explains it
-  visually too. Import `Tooltip` from `@mui/material` at the top of the file (currently only
-  imports `List, ListItem, Popover, Typography, ButtonBase`).
-- Additionally: when `status.recipient_count === 0` (a message with literally nobody to read it —
-  "0/0" carries no information per the Envelope's alternative: "or is not shown where it carries no
-  information"), return `null` before rendering the ratio, same early-return style already used at
-  line 41 (`if (!status) return null;`) and line 50 (`if (!hasCounts && conversation?.kind !==
-  'direct') return null;`).
-- Do NOT change the DM branch (line 78–80) — it already carries a real icon-shape + colour +
-  aria-label signal (not a bare number), out of this fix's actual complaint.
-- Test file: extend `tests/messagingReadTicks*.test.*` if one exists (grep `tests/` for
-  `ReadTicks`); otherwise create `tests/messagingReadTicksTooltip.test.jsx`.
-  1. With `read_count: 2, recipient_count: 5`, assert a `title` attribute (MUI `Tooltip` renders
-     one on the wrapped element before hover, or use `@testing-library/user-event` to hover and
-     assert the tooltip text appears — follow whatever pattern this repo's other `Tooltip` tests
-     already use, grep for one) explaining the ratio is present.
-  2. With `recipient_count: 0`, assert the component renders nothing (e.g. `container.textContent`
-     is empty, or the specific test id/role used elsewhere for "renders null" assertions in this
-     test suite).
-
-## Do-not-touch / invariants
-
-- No change to message sending, polls, or announcements behaviour (Envelope non-goal) — items 1–3
-  above are the complete scope; do not touch `submit`/`submitPoll`/`submitAnnouncement`.
-- `sec_reviewer` will specifically check the linkify regex cannot match a non-`http(s)` scheme —
-  keep the pattern an explicit `https?://` prefix, never a generic "looks like a URL" heuristic.
-
-## Target repo working directory (absolute)
-
-`C:\Users\biglmi\Documents\webapps\ui-core-micha` (branch `main`)
-
-## Preamble — a REQUIRED block IN this file, not something appended at invocation
-
-> The text above is the COMPLETE spec — the committed WO file's content, not a plan to refine; there
-> is no separate plan file. Read the nearest `AGENTS.md`, the relevant `.codex/skills/<role>/SKILL.md`, and the
-> app `MEMORY.md` ONLY for conventions. Stay in scope; do not touch auth/permissions/deps/schema/CI
-> unless the spec says so; do not update `MEMORY.md`. **Do NOT edit `WORK_ORDERS.md` — the register
-> row and the review verdicts are the orchestrator's alone.** **Your tools are for editing source
-> and test files and for running the tests you wrote — nothing else.** Do NOT install dependencies,
-> touch a lockfile, run a package manager, or tidy up stray files; if something in the repo state
-> blocks you, stop and report it as `RESULT: BLOCKED <reason>` instead of fixing it. Do NOT
-> `git add`/`commit`/`push` — leave every
-> change uncommitted in the working tree for the orchestrator's independent review. WRITE the tests
-> the `Required tests` section calls for AND **RUN the tests you just wrote** to confirm they execute
-> and pass — that is the ONLY test run you do (NOT the app's affected/full suite, NOT any review).
-> The orchestrator re-runs the authoritative set + does the independent review after you finish —
-> those are the gate; your own run does not count as the gate.
->
-> Narrate continuously: a `PLAN: <step1> | <step2> | …` line up front, then a single-line
-> `PROGRESS: [<n>/<total>] <present-tense action>` before every relevant action (and `… done` on
-> completion), spaced so no gap exceeds ~2 min, stdout unbuffered, plus exactly one final
-> `RESULT: DONE|BLOCKED <reason>`.
-
----
-
-# C. Orchestrator only — NOT ADDRESSED TO THE IMPLEMENTER
-
-> **If you are the implementer reading this work order as your own specification: STOP at this line.
-> Everything below describes what the Orchestrator does AFTER you finish. You do none of it — no
-> reviewers, no verification run, no register edit, no commit.**
-
-*(to be filled by the Orchestrator: execution directive; `reviewer` (all lenses) + `ui_reviewer` + `sec_reviewer`; release; jg-ferien pin bump and 375 px check in an event conversation; register rows here, in dcm (MSG canonical) and in jg (`JG-UX-14`).)*

package/work-orders/UCM-PRIM-2.md

@@ -1,114 +0,0 @@
-# UCM-PRIM-2 — A shared empty-state primitive
-
-# A. Envelope — authored by the Expertenchat
-
-## Goal & expected outcome
-
-- Goal: every "nothing here yet" in a consuming app looks and reads the same.
-- Expected outcome: `EmptyState` in the kit — an optional icon, one line of text, an optional secondary
-  line and an optional action — built from theme tokens, accessible (text reachable by screen
-  readers, action a real button).
-
-## Context — measured 2026-09-29 in jg-ferien's local browser test (ucm 3.5.0 installed there)
-
-- jg-ferien's 15 event sections show "empty" in **seven** ways (plain text, card, blue info alert,
-  card with title, filled green card, alert inside a green card, nothing at all). No shared component
-  exists in jg or ucm; jg has only a song-search special case.
-- **Operator decision 2026-09-29: generic goes to ucm.** jg adopts it in `JG-UX-9`.
-- `PRIM-1` promoted `StatTile`/`SoftChip` along the same lines.
-
-## Scope + non-goals
-
-- In scope: the component, its export, a story or docs entry, tests.
-- Explicit non-goals / do-not-touch: no adoption in consumers here; no change to `Alert` styling.
-
-## Tier · gates
-
-- **Tier 3** — new public export in shared-core (additive).
-- Reviewer: `reviewer` (all lenses) · `ui_reviewer`.
-- **Done means released; jg adoption is `JG-UX-9`.**
-
-## Risks
-
-- A too-flexible API reintroduces the seven variants; keep the props minimal.
-
-## Required tests to WRITE (you write them and run YOUR OWN new ones; the orchestrator's run is the gate)
-
-1. Renders text only; with secondary line; with action (button with accessible name).
-2. Uses theme tokens (no literal colours; the kit's literal guard passes).
-
----
-
-# B. Implementation map — filled by the Orchestrator — ADDRESSED TO THE IMPLEMENTER
-
-## Context package
-
-- New file `src/components/EmptyState.jsx`. Model it on the existing primitives
-  `src/components/StatTile.jsx` and `src/components/SoftChip.jsx` — a small functional component,
-  default export, built from `Box`/`Typography`/`Button` (MUI), theme tokens only (no literal
-  colours — `reportOffPaletteColours` in `src/theme/themeCompleteness.js` scans every source file
-  for off-palette hex/rgb/named colours and is part of the kit's literal guard the Required Tests
-  reference).
-- Props (keep minimal per the Risk note — do not over-generalise):
-  `icon` (optional, a rendered MUI icon element, e.g. `<InboxOutlinedIcon />`), `title` (string,
-  required — the one line of text), `description` (optional secondary line), `action` (optional
-  `{ label, onClick }` — rendered as a real `<Button variant="outlined">`, not a link, so it is
-  reachable and operable like `StatTile`'s children slot), `sx` (optional passthrough, MUI
-  convention used throughout the kit, e.g. `Composer.jsx`'s `COMPOSER_EMOJI_BUTTON_SX` pattern).
-- Export it from `src/index.js` next to the other components section (`--- 5. Components ---`,
-  after `SoftChip` at line 65): `export { default as EmptyState } from './components/EmptyState';`.
-- Accessibility: `title` must be real text content (not just an `aria-label`), so a screen reader
-  reads it as part of document flow; if `icon` is passed, it must not need its own label (decorative
-  — rely on the adjacent text, matching how `StatTile` treats its icon-less design).
-- Test file: `tests/EmptyState.test.jsx`, following `tests/StatTile.test.jsx`'s pattern exactly —
-  `@vitest-environment jsdom`, wrap in `<ThemeProvider theme={createAppTheme(...)}>`, `cleanup()`
-  in `afterEach`.
-  - Render text-only, with `description`, with `action` (assert the button has an accessible name
-    matching the label and that clicking it calls the passed `onClick`).
-  - The "theme tokens only" requirement: either call `reportOffPaletteColours([{ path: 'src/components/EmptyState.jsx', source: fs.readFileSync(...) }])` (see how `themeCompleteness.js` self-tests, or grep existing callers of `reportOffPaletteColours` in `tests/` for the established pattern) and assert `findings` is empty, or (simpler, sufficient) just don't use any hex/rgb/named-colour literal in the component at all and note in a comment that the guard is structural, not a runtime assertion in this test. Prefer calling `reportOffPaletteColours` directly if an existing test already does — grep `tests/*.test.*` for `reportOffPaletteColours` to find the precedent and match its call shape exactly.
-
-## Do-not-touch / invariants
-
-- Do not add `EmptyState` to `kitSxRegistry.js` unless you export a top-level `sx` object constant
-  from the component (only needed if the root element gets kit-owned baked-in styling beyond plain
-  `sx` passthrough — for this minimal component you likely don't need one; only add a registry entry
-  if you do add such a constant).
-- No adoption anywhere in this repo's own consumers (`AccountPage`, etc.) — out of scope per the
-  Envelope's non-goals.
-- Do not touch `Alert` styling anywhere.
-
-## Target repo working directory (absolute)
-
-`C:\Users\biglmi\Documents\webapps\ui-core-micha` (branch `main`)
-
-## Preamble — a REQUIRED block IN this file, not something appended at invocation
-
-> The text above is the COMPLETE spec — the committed WO file's content, not a plan to refine; there
-> is no separate plan file. Read the nearest `AGENTS.md`, the relevant `.codex/skills/<role>/SKILL.md`, and the
-> app `MEMORY.md` ONLY for conventions. Stay in scope; do not touch auth/permissions/deps/schema/CI
-> unless the spec says so; do not update `MEMORY.md`. **Do NOT edit `WORK_ORDERS.md` — the register
-> row and the review verdicts are the orchestrator's alone.** **Your tools are for editing source
-> and test files and for running the tests you wrote — nothing else.** Do NOT install dependencies,
-> touch a lockfile, run a package manager, or tidy up stray files; if something in the repo state
-> blocks you, stop and report it as `RESULT: BLOCKED <reason>` instead of fixing it. Do NOT
-> `git add`/`commit`/`push` — leave every
-> change uncommitted in the working tree for the orchestrator's independent review. WRITE the tests
-> the `Required tests` section calls for AND **RUN the tests you just wrote** to confirm they execute
-> and pass — that is the ONLY test run you do (NOT the app's affected/full suite, NOT any review).
-> The orchestrator re-runs the authoritative set + does the independent review after you finish —
-> those are the gate; your own run does not count as the gate.
->
-> Narrate continuously: a `PLAN: <step1> | <step2> | …` line up front, then a single-line
-> `PROGRESS: [<n>/<total>] <present-tense action>` before every relevant action (and `… done` on
-> completion), spaced so no gap exceeds ~2 min, stdout unbuffered, plus exactly one final
-> `RESULT: DONE|BLOCKED <reason>`.
-
----
-
-# C. Orchestrator only — NOT ADDRESSED TO THE IMPLEMENTER
-
-> **If you are the implementer reading this work order as your own specification: STOP at this line.
-> Everything below describes what the Orchestrator does AFTER you finish. You do none of it — no
-> reviewers, no verification run, no register edit, no commit.**
-
-*(to be filled by the Orchestrator: execution directive; `reviewer` (all lenses) + `ui_reviewer`; release; register row here and cross-reference in jg (`JG-UX-9`).)*

package/work-orders/UCM-SHELL-7.md

@@ -1,134 +0,0 @@
-# UCM-SHELL-7 — User-menu avatar initials fail contrast
-
-# A. Envelope — authored by the Expertenchat
-
-## Goal & expected outcome
-
-- Goal: the initials in the header avatar are readable.
-- Expected outcome: initials reach at least 4.5:1 against the avatar background, using the consuming
-  app's theme tokens rather than MUI's default grey.
-
-## Context — measured 2026-09-29 in jg-ferien's local browser test (ucm 3.5.0 installed there)
-
-- `UserMenu` (imported in jg-ferien's `Header.jsx`) renders the MUI default avatar: white initials on
-  light grey, **1.83:1**, on every page of the app.
-
-## Scope + non-goals
-
-- In scope: avatar colours in `UserMenu` from theme tokens (e.g. primary surface with its
-  contrastText), with a fallback that passes when a consumer defines nothing.
-- Explicit non-goals / do-not-touch: no layout change of the user menu.
-
-## Tier · gates
-
-- **Tier 3** — shared-core component (small).
-- Reviewer: `ui_reviewer` (no new logic beyond the colour choice).
-- **Done means released and jg-ferien's pin bumped.**
-
-## Risks
-
-- `createAppTheme` baseline: if the chosen token is optional, `assertThemeComplete` must require it or
-  the fallback must pass on its own.
-
-## Required tests to WRITE (you write them and run YOUR OWN new ones; the orchestrator's run is the gate)
-
-1. With jg-ferien's theme values the avatar pair is at least 4.5:1.
-2. With a theme defining nothing extra the fallback pair is at least 4.5:1.
-
----
-
-# B. Implementation map — filled by the Orchestrator — ADDRESSED TO THE IMPLEMENTER
-
-## Context package
-
-- File: `src/auth/UserMenu.jsx`. The avatar is rendered at line 60:
-  `<Avatar src={avatarSrc} sx={{ width: 32, height: 32, fontSize: '0.8rem' }}>` — no `bgcolor`/`color`
-  is set today, so it falls through to MUI's default grey Avatar styling (1.83:1, the measured
-  defect). Only this one JSX element changes; nothing else in the file.
-- **Pitfall — do not just reach for `theme.palette.primary.contrastText`.** MUI's own
-  `createTheme`/`augmentColor` computes `contrastText` with `contrastThreshold: 3` (tuned for large
-  text/graphics, AA), not the 4.5:1 this WO requires for normal-size initials text. A consumer's
-  `primary.main` that legitimately passes MUI's own 3:1 threshold can still fail 4.5:1, and nothing
-  here re-validates it — so `contrastText` alone is not a fallback that "passes when a consumer
-  defines nothing", it is a fallback that USUALLY passes.
-- **Design to implement instead** (uses the kit's own exported contrast helper, satisfies both
-  required tests meaningfully since both actually depend on the consumer's `primary.main`):
-  1. Import `{ calculateContrastRatio }` from `'../theme'` (already exported from
-     `src/theme/index.js` → re-exported at `src/index.js`) and `useTheme` from
-     `'@mui/material/styles'`.
-  2. Inside `UserMenu`, read `const theme = useTheme();`.
-  3. Background: `theme.palette.primary.main` (the "primary surface" the Envelope names).
-  4. Text colour: compute
-     `calculateContrastRatio(theme.palette.background.paper, theme.palette.primary.main) >= 4.5
-        ? theme.palette.background.paper : theme.palette.ink.primary`.
-     This is not an arbitrary heuristic: for any background colour, the higher of
-     (contrast against white) and (contrast against near-black) is mathematically always ≥ √21 ≈
-     4.58 — i.e. picking whichever of the kit's own light (`background.paper`, white) or dark
-     (`ink.primary`, near-black) ink token has the higher measured contrast against
-     `primary.main` is GUARANTEED to clear 4.5:1 for every possible `primary.main`, including one
-     a consumer hasn't customised at all (the untouched baseline `primary.main` MUI ships). That is
-     what makes this "a fallback that passes when a consumer defines nothing" instead of "usually
-     passes".
-  5. Apply as `sx={{ ..., bgcolor: theme.palette.primary.main, color: <computed> }}` on the same
-     `Avatar` element — keep the existing `width`/`height`/`fontSize` untouched.
-  6. Do NOT introduce a new literal hex/rgb anywhere — `theme.palette.background.paper` and
-     `theme.palette.ink.primary` are both resolved theme values, and referencing them via
-     `theme.palette.<path>` (not writing their hex value as a string literal) keeps
-     `reportOffPaletteColours` clean, same as every other component in the kit.
-- Test file: new `tests/UserMenu.test.jsx` (none exists yet — check with `Glob` before assuming;
-  if a `UserMenu` test already exists under a different name, extend it instead of creating a
-  duplicate). Pattern after `tests/StatTile.test.jsx`: `@vitest-environment jsdom`,
-  `createAppTheme(...)`, wrap `UserMenu` in the theme provider AND `AuthContext.Provider` (it reads
-  `user`/`logout` via `useContext(AuthContext)` at line 32 — a minimal `{ user: { username: 'ab' },
-  logout: () => {} }` value is enough to render the avatar).
-  1. With a theme built from jg-ferien's actual `primary.main` — `#367964` (measured directly from
-     `jg-ferien/frontend/src/theme.js:25`, a mid-brightness teal-green), assert
-     `calculateContrastRatio(<resolved avatar text colour>, <resolved avatar bg colour>) >= 4.5`
-     by reading the rendered `Avatar`'s computed `backgroundColor`/`color` via
-     `window.getComputedStyle` (see `tests/StatTile.test.jsx`'s `accent` border test for the
-     `getComputedStyle` pattern) and feeding both into `calculateContrastRatio` directly — do not
-     hardcode an expected hex, assert the ratio.
-  2. With `createAppTheme({})` (no consumer overrides — MUI's own baseline `primary.main`), assert
-     the same ≥4.5 computed-style contrast check.
-
-## Do-not-touch / invariants
-
-- No layout change to the user menu (Envelope non-goal) — only the two `sx` colour values change.
-- Do not touch `assertThemeComplete`/`THEME_COMPLETENESS_SURFACES` — this fix reads existing
-  required surfaces (`primary.main`, `background.paper`, `ink.primary`), it does not need a new one.
-
-## Target repo working directory (absolute)
-
-`C:\Users\biglmi\Documents\webapps\ui-core-micha` (branch `main`)
-
-## Preamble — a REQUIRED block IN this file, not something appended at invocation
-
-> The text above is the COMPLETE spec — the committed WO file's content, not a plan to refine; there
-> is no separate plan file. Read the nearest `AGENTS.md`, the relevant `.codex/skills/<role>/SKILL.md`, and the
-> app `MEMORY.md` ONLY for conventions. Stay in scope; do not touch auth/permissions/deps/schema/CI
-> unless the spec says so; do not update `MEMORY.md`. **Do NOT edit `WORK_ORDERS.md` — the register
-> row and the review verdicts are the orchestrator's alone.** **Your tools are for editing source
-> and test files and for running the tests you wrote — nothing else.** Do NOT install dependencies,
-> touch a lockfile, run a package manager, or tidy up stray files; if something in the repo state
-> blocks you, stop and report it as `RESULT: BLOCKED <reason>` instead of fixing it. Do NOT
-> `git add`/`commit`/`push` — leave every
-> change uncommitted in the working tree for the orchestrator's independent review. WRITE the tests
-> the `Required tests` section calls for AND **RUN the tests you just wrote** to confirm they execute
-> and pass — that is the ONLY test run you do (NOT the app's affected/full suite, NOT any review).
-> The orchestrator re-runs the authoritative set + does the independent review after you finish —
-> those are the gate; your own run does not count as the gate.
->
-> Narrate continuously: a `PLAN: <step1> | <step2> | …` line up front, then a single-line
-> `PROGRESS: [<n>/<total>] <present-tense action>` before every relevant action (and `… done` on
-> completion), spaced so no gap exceeds ~2 min, stdout unbuffered, plus exactly one final
-> `RESULT: DONE|BLOCKED <reason>`.
-
----
-
-# C. Orchestrator only — NOT ADDRESSED TO THE IMPLEMENTER
-
-> **If you are the implementer reading this work order as your own specification: STOP at this line.
-> Everything below describes what the Orchestrator does AFTER you finish. You do none of it — no
-> reviewers, no verification run, no register edit, no commit.**
-
-*(to be filled by the Orchestrator: execution directive; `ui_reviewer`; release; jg-ferien pin bump; register rows here and in jg (`JG-DL-12`).)*

package/work-orders/UCM-SHELL-8.md

@@ -1,125 +0,0 @@
-# UCM-SHELL-8: Valid SectionNav list items
-
-# A. Envelope — operator-approved scope
-
-## Goal and expected outcome
-
-SectionNav navigation entries are genuine list items containing the existing buttons.
-The account capture in innoservice reports three serious axe list violations at 1280 px;
-these remain in ui-core-micha 3.13.0. The correction removes their structural cause.
-
-## Scope and non-goals
-
-- Correct grouped and optional overview entries in SectionNav's shared list renderer.
-- Keep selection, aria-current, labels, remembered entry, keyboard operation, callbacks,
-  controlled/uncontrolled drawer behavior and appearance unchanged.
-- Release the correction as patch 3.13.1 and update innoservice's exact package pin.
-- No navigation redesign, new text, token delta, authentication, permissions, data contract,
-  other component, CI configuration or dependency changes beyond that release/pin.
-- No new visual design or prototype: retain the existing presentation.
-
-## Tier, risk and required tests to write
-
-Tier 3: shared-core source with a rendered DOM correction used by consumers.
-Risk: wrapper defaults could alter spacing or interrupt existing button interaction.
-Write focused assertions that every grouped and overview list has li children containing
-the existing button controls, on desktop and inside the mobile drawer. Preserve existing
-selection and drawer tests; prove overview selection still passes null and closes the drawer.
-
-# B. Implementation map — ADDRESSED TO THE IMPLEMENTER
-
-## Target and ownership
-
-Target: `C:/Users/Micha Bigler/Documents/webapps/ui-core-micha`.
-Native bootstrap retains workspace-root cwd; use absolute paths and explicit workdirs.
-You are not alone in the codebase; preserve other agents' changes. Own only:
-- `src/layout/SectionNav.jsx`
-- `tests/SectionNav.test.jsx`
-
-## Context package
-
-`src/layout/SectionNav.jsx:120`, SectionNavList, is shared by the desktop nav and mobile
-drawer. The overview List currently directly contains ListItemButton; grouped Lists at
-159 map item keys to direct ListItemButton children. MUI List defaults to ul and the
-button defaults to div. Correct list containment while preserving the interactive button.
-The overview handler passes null; grouped handlers pass item.key. Selected buttons carry
-aria-current=page; remembered secondary text is shown only on its unselected entry.
-Keep exported sx constants, drawer state handlers, prop defaults and group label IDs.
-Use existing MUI primitives; prevent wrapper padding from changing the presentation.
-
-`tests/SectionNav.test.jsx` renders the real named SectionNav with ThemeProvider and a
-translation mock. Existing labels: Profile, Security, Users, Invite, Support, Notifications;
-optional Overview; trigger accessible name matches /Section Profile/i; drawer title
-Switch section. Existing tests cover selection, remembered text, controlled/uncontrolled
-drawer, theme tokens and grid. Extend this file without mocking SectionNav or changing
-existing tests to accept weaker behavior. Work from these two files, no broad exploration.
-
-## Preamble and progress contract
-
-> This committed WO is the COMPLETE spec. You are the initial implementer, not the reviewer.
-> Edit only the owned source/test paths using explicit UTF-8 I/O. Preserve other changes.
-> Do not edit dependencies, lockfiles, package/version/changelog/register/README/governance,
-> settings, environment, other repos or memory. Never read .env or dump environment/settings.
-> Your tools are for editing source/test files and running the tests you wrote, nothing else.
-> No installs, package-manager commands, containers, git operations, self-review or subagents.
-> Run your newly written SectionNav cases ONCE with the existing Node/Vitest runtime,
-> maxWorkers=2, selected by test names; no affected/full suite, build or app startup.
-> If blocked, report it rather than changing repo state. Leave all changes uncommitted.
-> The orchestrator's tests and independent reviews are the acceptance gate, not your run.
-> Start PLAN, emit PROGRESS before relevant actions with no silence over two minutes,
-> then exactly one final RESULT: DONE or RESULT: BLOCKED.
-
-# C. Orchestrator only — NOT ADDRESSED TO THE IMPLEMENTER
-
-> IMPLEMENTER STOP HERE. You ARE the initial implementation instance. No steps below belong to you.
-
-Gate #1: operator explicitly approved this exact structural correction, preserved behavior
-and appearance, tests/review, release and innoservice pin bump on 2026-10-13.
-No source approval was inferred from the earlier registration or clarification question.
-
-Dispatch: fresh native plain worker, requested codex/gpt-6-luna, full WO inline; inherited
-cwd is workspace root, target is the absolute core repo above. Record accepted identity
-and only exposed effective metadata. Assigned ownership is not technical containment.
-Parent owns repo state, package version, changelog, README/register and release/pin.
-
-Independent envelope/regression/duplication/tests lenses plus UI run concurrently on the
-same frozen diff via fresh read-only codex/gpt-6-luna processes. Security reviewer is not
-required: no auth/security behavior changes. Parent also checks exposure/permission parity.
-Parent runs SectionNav and both existing AccountPage test files, then build. Existing main
-publish workflow supplies the full shared-core regression suite and publishing evidence;
-normal reviewed main push, no manual publish dispatch. Confirm successful publication of
-3.13.1 before innoservice exact pin and lockfile update. Keep all app capture/axe checks.
-Fresh app capture at 375/1280 must verify navigation and absence of the three list violations.
-Finalize register with named reviews, deduplicated dispositions and actual test/release proof.
-
-Accepted native implementer: `/root/kit_sectionnav`, explicit requested gpt-6-luna, high
-reasoning, fresh context. Effective native provider/model metadata was not exposed and
-remains unverified. Only the two assigned files changed; no author git/review/repo-state
-operations. Author's single permitted test run failed before collection with temporary-file
-EPERM (zero tests). Parent runs the authoritative gate through the normal runtime path.
-
-Core acceptance: five fresh concurrent CLI reviews (envelope, regression, duplication,
-tests, UI), all exit 0, banners confirm codex/gpt-6-luna, provider openai, read-only.
-Deduplicated disposition: 1 raised, 0 accepted, worst accepted none. Tests lens R1 proposed
-proving the MUI implementation identity against a fabricated class-bearing stub. Rejected:
-the structural assertion fails against the actual pre-change direct div children, existing
-selection/theme/drawer tests retain their behavior checks, and the source still directly
-imports and renders the real MUI ListItemButton. No behavior or identity abstraction is added.
-Other lenses report no findings. Parent targeted pass confirms callbacks/permission filtering,
-labels and selected/remembered state unchanged; wrappers use disablePadding.
-Parent gate: 21 tests in SectionNav.test.jsx, AccountPage.test.jsx and
-AccountPage.profileStatements.test.jsx passed with maxWorkers=2; TypeScript build exit 0.
-Publish workflow's full suite is justified by shared-core consumer ripple. App pin and fresh
-consumer capture remain pending after the reviewed core source/release lands.
-
-Closing consumer proof: published3.13.1 verified by workflow38435441867,
-744tests89files plus build and npm Trusted Publishing successful. Innoservice
-exact pin3.13.1 is in sourcec527918, CI38444366349. Both source-matching account
-captures375/1280 have no axe failures, no console/network failures, and all11
-rubric items yes (22answers). Parent inspected both actual account images: same
-profile/security/admin/help navigation and consent controls, readable at both
-widths. Three previous kit list violations are gone. This completes the scoped
-consumer gate; unrelated Organisation-policy axe failures in that app candidate
-remain owned by INNO-FIX-11 and do not reopen the kit list correction.
-Review remains the named five independent readonly Luna source passes above,
-1deduplicated raised0accepted,worst accepted none; no source changes afterward.