@micha.bigler/ui-core-micha 2.36.0 → 2.37.1

package/README.md

@@ -5,3 +5,7 @@
 Run `pnpm dev` to open the local Vite harness. It mounts entries with the package's MUI theme, `react-i18next`, a memory router, and fixture-backed REST/realtime transport. Use the controls to change theme and viewport.
 
 To add an entry, create a small component in `dev/entries.jsx` and append it to `entries`. It may be a complete surface or one standalone component. Keep fixtures and transport behaviour in `dev/`, never in `src/`: the harness is not part of the published package.
+
+## Internationalization
+
+Spread `uiCoreTranslations` into the default i18n namespace as the supported aggregate; per-feature translation exports remain available to selective apps that accept responsibility for pairing every adopted feature with its bundle.

package/WORK_ORDERS.md

@@ -72,8 +72,9 @@ Two chunks. **Chunk 1** (Part 1 + Part 2 of the Envelope): extended `SPACING_SHO
 **Operator decision: fix both** (of three offered options: widen-and-fix / exempt-with-reason / narrow-the-scanner). Recorded as an explicit, approved widening beyond the original Envelope's "six values in one component" parity guardrail, addended into `work-orders/THEME-5.md` before chunk 2 ran. **Chunk 2**: (8) `SocialLoginButtons.jsx`'s Google-icon border `1px solid rgba(0,0,0,0.2)` → `divider`; (9) `exportChart.js`'s Canvas 2D `context.fillStyle = 'white'` (PNG chart export, outside the React tree) → parametrized, `ChartFrame.jsx` now passes `theme.palette.background.paper` in via `useTheme()`.
 
 **Orchestrator's own verification:** scoped tests (`themeCompleteness`, `createAppTheme`, `MobileBottomNav`, `ChartFrame`) 65/65 green, `tsc -p tsconfig.build.json --noEmit` clean. Independent `reviewer` (Sonnet) + `ui_reviewer` (Sonnet) spawned concurrently against the real, complete two-chunk diff — **this was the only independent review that actually ran; no prior pass exists despite what the uncommitted Notiz briefly claimed.** Both reviewers: **no blocking code findings.** `reviewer`: two P3 notes, not fixed — the print-document masking regex only matches the first `printWindow.document.write(...)` call in a file (currently safe, only one exists; latent fragility if a second is ever added); `exportChartPng`'s new `backgroundColour` parameter has no default (low risk, not exported from `src/index.js`, single caller always supplies it — a footgun only if the function gains a second caller or goes public). `ui_reviewer`: confirmed all nine role-based mappings resolve against real `tokens.js` values and are visually reasonable; flagged the Google-icon border change (`rgba(0,0,0,0.2)` → `divider`, roughly halving visible contrast) as the single largest visual delta of the nine and worth a live look given the operator's explicit no-rendered-gate decision for this WO — not blocking, no rendered gate was added, consistent with that decision. Version `2.34.0` → `2.35.0` (minor, new exported API). No rendered/prototype gate, per the operator's explicit decision — this note is the substitute, all nine changed values listed from-and-to above. DS-18 follow-ups. |
-| SHELL-5 | Promote the secondary-navigation shell | Promotes jg-ferien's `SectionSwitcher` (grouped sidebar + bottom drawer) into the kit as the level *below* the bottom bar, adds the trigger bar that supplies the missing affordance, and makes ucm's own `AccountPage` its first consumer by replacing its horizontal `Tabs` strip. Look and feel follow jg by operator decision. Full spec: [work-orders/SHELL-5.md](work-orders/SHELL-5.md). | 2026-08-11 | done | <pending> | DS-11. Supersedes `SHELL-2` (now `dropped`); prototype `assets/SHELL-2-account-navigation.html` kept as the composition spec. Each jg-specific concept was made optional and `AccountPage` proves it optional: no `overviewItem` (no "Übersicht" concept), no `rememberedKey`, `APP_HEADER_HEIGHT` → `headerOffset` (default `24`), `zIndex.drawer + 3` kept as default (`SHELL-3`'s bar sits at `+2`, ordering is meaningful), and the 280px two-column grid moved from the consumer into the component. The trigger bar is the one net-new piece (jg has none) — new full-width 56px bar, first thing rendered on mobile, opens a bottom drawer. `AccountPage`'s flat permission-computed `tabs` list bucketed into four fixed groups per the prototype ("Mein Konto"/"Verwaltung"/"Hilfe"/trailing "Weitere" catch-all for ungrouped `extraTabs`), new `Account.GROUP_*` i18n keys; `?tab=` contract and all permission-gating logic byte-for-byte unchanged. New component-owned chrome i18n (`src/i18n/sectionNavTranslations.ts`, all 4 locales) resolves the trap jg's `t("SectionSwitcher.TITLE")` had — no fallback, would have rendered a raw key. **Codex left the diff uncommitted and did not touch this file, as instructed** (the third consecutive WO where the explicit warning about the prior invalid-review pattern held). **Concurrent-session note:** an unrelated `I18N-1` session was uncommitted in the same working tree at the same time (`README.md`, `tests/i18nAggregate.test.js`, an aggregate-translations addition to `src/index.js`) — separated by hunk-level staging (`git add -p`) before this commit; only `SectionNav`'s two export lines in `src/index.js` are in this commit, I18N-1's own hunks were left for its own session to land. **Orchestrator's own verification:** scoped tests green (52/52 after fixes, see below), `tsc` clean. Independent `reviewer` + `ui_reviewer` (Sonnet, both mandatory — new logic and a prototype in scope) ran concurrently. **`reviewer` found two real P2s, both fixed:** the drawer's `zIndex` was set via BOTH an exported/registered `sx` object and a separate inline `style` prop on the same element — `style` always wins, so the registered `sx` value was dead code, tested but never actually reaching the DOM; removed the redundant `SECTION_NAV_DRAWER_SX` entirely (and its now-pointless `kitSxRegistry.js` entry), kept only the working `style`-based zIndex. The "optional controlled" `open`/`onClose` API (an Orchestrator design resolution for reconciling jg's controlled drawer with the new internally-triggered one) was incomplete — no `onOpen` callback existed, so a controlled consumer's trigger click was silently a no-op; added `onOpen`, fixed, added a regression test (`AccountPage` itself is unaffected, it uses uncontrolled mode). **`ui_reviewer` found one real P2, fixed:** the mobile trigger's current-section text used `fontWeight={700}`, matching neither the theme's `subtitle1` (600) nor the prototype's `.trigger-value` (16.5px/600) — an undeclared deviation that made it visually indistinguishable from the bold group headers; removed the override. One P3 left as documented, not fixed: `headerOffset` defaults to `24` vs. the prototype's `16` — a defensible generalisation (the component no longer assumes a fixed app-header height the way jg's original did; no consumer today is sensitive to the exact value). **Rendered verification:** the Browser pane could not composite frames in this session (same recurring environment limitation as `SHELL-3`/`SHELL-4`) — DOM/computed-style substitution via the test suite's own assertions (grid columns, drawer dimensions, z-index, theme-token resolution under two themes) plus static composition comparison against the prototype by both independent reviewers, one of which (`ui_reviewer`) is exactly the review type this repo relies on for design fidelity when a real render isn't obtainable. **Follow-ups named, unchanged:** jg migrates onto this and deletes its own drawer (operator requirement, separate WO); the users table is `AUTH-4`, deliberately not here. |
+| SHELL-5 | Promote the secondary-navigation shell | Promotes jg-ferien's `SectionSwitcher` (grouped sidebar + bottom drawer) into the kit as the level *below* the bottom bar, adds the trigger bar that supplies the missing affordance, and makes ucm's own `AccountPage` its first consumer by replacing its horizontal `Tabs` strip. Look and feel follow jg by operator decision. Full spec: [work-orders/SHELL-5.md](work-orders/SHELL-5.md). | 2026-08-11 | done | b283c33 | DS-11. Supersedes `SHELL-2` (now `dropped`); prototype `assets/SHELL-2-account-navigation.html` kept as the composition spec. Each jg-specific concept was made optional and `AccountPage` proves it optional: no `overviewItem` (no "Übersicht" concept), no `rememberedKey`, `APP_HEADER_HEIGHT` → `headerOffset` (default `24`), `zIndex.drawer + 3` kept as default (`SHELL-3`'s bar sits at `+2`, ordering is meaningful), and the 280px two-column grid moved from the consumer into the component. The trigger bar is the one net-new piece (jg has none) — new full-width 56px bar, first thing rendered on mobile, opens a bottom drawer. `AccountPage`'s flat permission-computed `tabs` list bucketed into four fixed groups per the prototype ("Mein Konto"/"Verwaltung"/"Hilfe"/trailing "Weitere" catch-all for ungrouped `extraTabs`), new `Account.GROUP_*` i18n keys; `?tab=` contract and all permission-gating logic byte-for-byte unchanged. New component-owned chrome i18n (`src/i18n/sectionNavTranslations.ts`, all 4 locales) resolves the trap jg's `t("SectionSwitcher.TITLE")` had — no fallback, would have rendered a raw key. **Codex left the diff uncommitted and did not touch this file, as instructed** (the third consecutive WO where the explicit warning about the prior invalid-review pattern held). **Concurrent-session note:** an unrelated `I18N-1` session was uncommitted in the same working tree at the same time (`README.md`, `tests/i18nAggregate.test.js`, an aggregate-translations addition to `src/index.js`) — separated by hunk-level staging (`git add -p`) before this commit; only `SectionNav`'s two export lines in `src/index.js` are in this commit, I18N-1's own hunks were left for its own session to land. **Orchestrator's own verification:** scoped tests green (52/52 after fixes, see below), `tsc` clean. Independent `reviewer` + `ui_reviewer` (Sonnet, both mandatory — new logic and a prototype in scope) ran concurrently. **`reviewer` found two real P2s, both fixed:** the drawer's `zIndex` was set via BOTH an exported/registered `sx` object and a separate inline `style` prop on the same element — `style` always wins, so the registered `sx` value was dead code, tested but never actually reaching the DOM; removed the redundant `SECTION_NAV_DRAWER_SX` entirely (and its now-pointless `kitSxRegistry.js` entry), kept only the working `style`-based zIndex. The "optional controlled" `open`/`onClose` API (an Orchestrator design resolution for reconciling jg's controlled drawer with the new internally-triggered one) was incomplete — no `onOpen` callback existed, so a controlled consumer's trigger click was silently a no-op; added `onOpen`, fixed, added a regression test (`AccountPage` itself is unaffected, it uses uncontrolled mode). **`ui_reviewer` found one real P2, fixed:** the mobile trigger's current-section text used `fontWeight={700}`, matching neither the theme's `subtitle1` (600) nor the prototype's `.trigger-value` (16.5px/600) — an undeclared deviation that made it visually indistinguishable from the bold group headers; removed the override. One P3 left as documented, not fixed: `headerOffset` defaults to `24` vs. the prototype's `16` — a defensible generalisation (the component no longer assumes a fixed app-header height the way jg's original did; no consumer today is sensitive to the exact value). **Rendered verification:** the Browser pane could not composite frames in this session (same recurring environment limitation as `SHELL-3`/`SHELL-4`) — DOM/computed-style substitution via the test suite's own assertions (grid columns, drawer dimensions, z-index, theme-token resolution under two themes) plus static composition comparison against the prototype by both independent reviewers, one of which (`ui_reviewer`) is exactly the review type this repo relies on for design fidelity when a real render isn't obtainable. **Follow-ups named, unchanged:** jg migrates onto this and deletes its own drawer (operator requirement, separate WO); the users table is `AUTH-4`, deliberately not here. |
 | AUTH-4 | The account users table is a desktop table shown unchanged on a phone | Measured 2026-08-11 in cockpit at `innerWidth` 411: `UserListComponent`'s table renders **1053px inside a 325px container** — 728px of overflow. The container has `overflow-x: auto` and **the document does not overflow**, so this is not a broken layout; it is six fixed-width desktop columns (Email 220, Name 180, New 90, Successful Login 163, Role 180, Actions 220) on a phone, with Role and Actions entirely outside the view. | 2026-08-11 | planned | | Split out of DS-11 by operator decision because its fix class differs from the navigation shell's. **No Envelope yet — its WHAT is undecided** and needs a design round: column priority, a card layout below `md`, or a sticky first column with horizontal scroll are three different answers with different costs. `SHELL-2` measured 1045px on 2026-08-08 and it is 1053px today (+8px), so the number is stable — cell padding is already the baseline's `10px 16px`, meaning `THEME-4`/`THEME-5` did not move the rendered density. Reached via `AccountPage` → the `users` tab, which **at least ten apps mount**, so any fix lands estate-wide. Prefix note: `AUTH-*` because the account screen's own surfaces belong to that stream, not because this is authentication. |
-| I18N-1 | One export, so a consumer cannot half-register the kit's strings | ucm exports its UI strings as **six separate bundles** that each app must spread into its own i18n resources by hand. Adopting a component without also adding its bundle renders **a raw key as visible UI text** — no type error, no runtime error. Ship a `uiCoreTranslations` aggregate so that cannot happen, and so a future ucm feature is carried automatically instead of requiring twelve apps to notice. Full order [work-orders/I18N-1.md](work-orders/I18N-1.md). | 2026-08-11 | planned | | Tier 3 (shared-core + new public export), target `2.36.0` (minor, fully additive). New `I18N-*` prefix, documented in the header above. **Two apps hit by the same mechanism, evidence not hypothesis:** (1) cockpit's `UI-3` adopted `UserMenu` without `userMenuTranslations` and shipped a header button reading the literal `UserMenu.TITLE` — **both independent static reviews were clean**, it was caught only by the rendered click-through, and only by DOM inspection at that since screenshots were unavailable; (2) **fitness-monitor is defective right now** — it imports `ChartFrame` (`BodyHistoryPage.jsx:7`, used `:295`/`:445`) but registers only `authTranslations`, so `ChartFrame.jsx:74`'s `t('ChartFrame.LOADING')` and its empty/error siblings render raw keys. It survived because those are transient edge states. **Estate survey, 2026-08-11:** twelve apps register ucm bundles — jg-ferien all six, cockpit four, hram three, **fitness-monitor one (defective)**, and eight auth-only apps that are correct solely because they have not adopted a second component yet. That is a coincidence with an expiry date, not a safety property. **The merge is safe:** 504 keys across the six bundles with **zero collisions**, verified by enumeration; every key is namespace-prefixed. **The part that makes the fix permanent is the ratchet test** — the aggregate must be asserted against the bundle list **read from `src/i18n/`**, not a hand-written list, so a future bundle that is not folded in fails. Without it the aggregate is correct today and rots exactly as the six exports did. Per-feature exports stay (removing them would break twelve apps for no gain); double-spreading during migration is harmless, which is why the zero-collision property is a test and not a comment. **Rollout is constrained by the one-repo rule** — a WO implements in one repository, so the twelve consumers cannot be migrated from here: `fitness-monitor/FM-14` is written, mandatory and blocked on this release, and **fitness-monitor renders raw keys until it lands** (the operator chose to route the fix through this rollout rather than patch it separately, so it could not be lost between two WOs; the delay is the cost and is recorded rather than left implicit). The other eleven are correct today — prevention, not repair — and ride along when each is next touched. Self-registration via `addResourceBundle` is **deliberately out of scope**: feasible (ucm components use `useTranslation()` against the consumer's own instance and ucm owns no instance), but all twelve consumers flatten into the default namespace with dotted keys, and registering at render time risks a first-paint flash of the raw key — replacing an invisible defect with a visible one. It is `I18N-2`, framed as a bundle-size optimisation rather than a correctness fix, because this WO already closes the hole. |
+| I18N-1 | One export, so a consumer cannot half-register the kit's strings | ucm exports its UI strings as **six separate bundles** that each app must spread into its own i18n resources by hand. Adopting a component without also adding its bundle renders **a raw key as visible UI text** — no type error, no runtime error. Ship a `uiCoreTranslations` aggregate so that cannot happen, and so a future ucm feature is carried automatically instead of requiring twelve apps to notice. Full order [work-orders/I18N-1.md](work-orders/I18N-1.md). | 2026-08-11 | done | a6d322d | Tier 3 (shared-core + new public export). **Shipped as `2.37.0`, not the planned `2.36.0`** — the concurrent `SHELL-5` release claimed `2.36.0` first; sequenced behind it (see below), no other change to scope. **Landed with seven bundles, not six** — `SHELL-5` (same day, same repo) added a seventh `sectionNavTranslations`, already picked up by the directory-enumerated ratchet before this WO's own commit, so the aggregate never had a six-bundle gap in practice. Codex implemented (`uiCoreTranslations` export + directory-ratcheted `tests/i18nAggregate.test.js` + README line); left the diff uncommitted as instructed. **Concurrent-session collision, real one:** `SHELL-5` was landing in the same working tree at the same time and touched `src/index.js` too; held this WO uncommitted until `SHELL-5`'s commit (`b283c33`) reached `main`, then re-diffed — clean, only this WO's seven-import/aggregate hunk remained. **Test #3 blocked Codex for a real reason, resolved by the operator, not routed around:** the required "every value keeps its `{de,fr,en,sw}` shape" test failed because `messagingTranslations`'s 116 keys have **no `sw` value at all**, a pre-existing gap, not something the merge caused — confirmed directly (`grep -c "'sw':" src/i18n/messagingTranslations.ts` → 0). Operator chose to scope the test down to `{de,fr,en}` for now with `sw` backfill tracked as a follow-up (comment in `tests/i18nAggregate.test.js` records this); key/value fidelity and the collision check are unaffected by the scope-down. **Bundle-size delta measured** (feeds `I18N-2`): +28,943 B raw / +7,327 B gzip for an auth-only app switching from `authTranslations` alone to the (then six-bundle) aggregate. **Independent `reviewer` + `ui_reviewer` (Sonnet, both mandatory, concurrent): no findings from either.** `reviewer` additionally confirmed the seven bundles are namespace-disjoint by prefix so spread order can't shadow a value, and that the ratchet's `fs.readdirSync` + `import.meta.glob` targets stay in sync (mismatch throws explicitly). Scoped tests green: 23/23 (`i18nAggregate`, `authTranslations`, `messagingExports`, `notificationsExports`). No rendered verification — the diff renders nothing. **`fitness-monitor/FM-14` is the still-open acceptance condition**, executed in another repo: fitness-monitor keeps rendering raw `ChartFrame.*` keys until it lands. **Two apps hit by the same mechanism, evidence not hypothesis:** (1) cockpit's `UI-3` adopted `UserMenu` without `userMenuTranslations` and shipped a header button reading the literal `UserMenu.TITLE` — **both independent static reviews were clean**, it was caught only by the rendered click-through, and only by DOM inspection at that since screenshots were unavailable; (2) **fitness-monitor is defective right now** — it imports `ChartFrame` (`BodyHistoryPage.jsx:7`, used `:295`/`:445`) but registers only `authTranslations`, so `ChartFrame.jsx:74`'s `t('ChartFrame.LOADING')` and its empty/error siblings render raw keys. It survived because those are transient edge states. **Estate survey, 2026-08-11:** twelve apps register ucm bundles — jg-ferien all six, cockpit four, hram three, **fitness-monitor one (defective)**, and eight auth-only apps that are correct solely because they have not adopted a second component yet. That is a coincidence with an expiry date, not a safety property. **The merge is safe:** 504 keys across the six bundles with **zero collisions**, verified by enumeration; every key is namespace-prefixed. **The part that makes the fix permanent is the ratchet test** — the aggregate must be asserted against the bundle list **read from `src/i18n/`**, not a hand-written list, so a future bundle that is not folded in fails. Without it the aggregate is correct today and rots exactly as the six exports did. Per-feature exports stay (removing them would break twelve apps for no gain); double-spreading during migration is harmless, which is why the zero-collision property is a test and not a comment. **Rollout is constrained by the one-repo rule** — a WO implements in one repository, so the twelve consumers cannot be migrated from here: `fitness-monitor/FM-14` is written, mandatory and blocked on this release, and **fitness-monitor renders raw keys until it lands** (the operator chose to route the fix through this rollout rather than patch it separately, so it could not be lost between two WOs; the delay is the cost and is recorded rather than left implicit). The other eleven are correct today — prevention, not repair — and ride along when each is next touched. Self-registration via `addResourceBundle` is **deliberately out of scope**: feasible (ucm components use `useTranslation()` against the consumer's own instance and ucm owns no instance), but all twelve consumers flatten into the default namespace with dotted keys, and registering at render time risks a first-paint flash of the raw key — replacing an invisible defect with a visible one. It is `I18N-2`, framed as a bundle-size optimisation rather than a correctness fix, because this WO already closes the hole. |
 | I18N-2 | Self-registering component strings, if the bundle cost justifies it | Have ucm components register their own strings on the consumer's i18n instance (`addResourceBundle` on the instance from `useTranslation()`) instead of relying on the consumer spreading a bundle. Would remove the last of the consumer's i18n obligations and stop auth-only apps shipping strings they never render. | 2026-08-11 | planned | | Tier 3 (shared-core, changes how every consumer resolves strings). **Deliberately NOT a correctness WO** — `I18N-1`'s aggregate closes the defect class; this is a bundle-size optimisation and is scheduled on that basis alone. **Its input is a measurement `I18N-1` must produce**: the built size delta an auth-only app takes on by switching to the aggregate. Source-side that is ~30 KB of strings (the five non-auth bundles are 188 keys against auth's 316), but a source figure is not the answer and a guess here would make this decision unfalsifiable. **Two known hazards, both to be resolved before authoring:** (1) all twelve consumers flatten everything into i18next's DEFAULT namespace with flat dotted keys, so the registration shape has to match exactly or key resolution changes under twelve apps at once; (2) registering during render risks a first-paint flash of the raw key — which would trade an invisible defect for a visible one, the opposite of the point. Feasibility is established: ucm components use `useTranslation()` against the consumer's instance and ucm owns no i18next instance of its own, so there is a real instance to register against. |
 | AUTH-4 | The account user list on a phone | Gives `UserListComponent` a card layout below `md` — one card per user, email as the title, the two boolean columns as labelled chips, role select and delete in a divided footer, plus a sort control that replaces the column headers the table loses. Above `md` the table is byte-identical. Prototype: [assets/AUTH-4-user-list-card.html](work-orders/assets/AUTH-4-user-list-card.html). Full spec: [work-orders/AUTH-4.md](work-orders/AUTH-4.md). | 2026-08-11 | planned | | Split out of DS-11 by operator decision; fix class chosen by operator (card list, over sticky-first-column and priority-hide). Envelope only (Approval Gate #1 pending). **Authored and parked by operator decision 2026-08-11 — not queued.** It is built on demand, not as SHELL-5's successor; a fresh session should not dispatch it without the operator saying so. When it does run, it runs **after** `SHELL-5` (same screen, different half). The point of this row is that the measurements above are already done, so nobody re-measures. Prototype in scope, so the two-width rendered gate applies. **Measured 2026-08-11 in cockpit** at `innerWidth` 411 (the mobile preset gives 411, not 375): table **1053px inside a 325px container**, container `overflow-x: auto` and **the document does not overflow** — so it is not a broken layout but a desktop table on a phone, with Role and Actions, the two things the screen exists for, entirely outside the view. **The cheap fix was tested and rejected:** 253px of the width is `New` (90) + `Successful Login` (163), both default-on props that `AccountPage` already forwards and cockpit simply left on — but the four remaining columns are 800px against 325px, so configuration cannot fix it. Column defaults deliberately NOT flipped: that would be a silent estate-wide change. SHELL-2's 1045px from 2026-08-08 still holds (+8px), so THEME-4/5 did not move the density. **Four prototype decisions are load-bearing:** email as title with a muted placeholder when the name is absent (verified: a 47-char address wraps to two lines in a 357px card without overflow); the icon-only flags become labelled chips **because a Tooltip is unreachable on a touch pointer**, so that data is effectively absent today; role and delete in a footer behind a divider with the full 44px target; and a **sort control**, because a card list has no column headers — without it the mobile view silently loses a desktop capability. `extraColumns` render as label/value rows with **no new required field**; `extraRowActions` beyond three must collapse into an overflow menu. Reached via `AccountPage`, which **at least ten apps mount**, and ucm has no staging net. |
+| SHELL-6 | A controlled `SectionNav` with no way to open must not render a trigger | In `mode="mobile"` the built-in trigger renders unconditionally (`SectionNav.jsx:246`), while `handleTriggerClick` calls `onOpen?.()` — so a consumer driving `open` itself without `onOpen` gets a button that is visible, focusable and does nothing. Render the trigger only when a click can open the drawer: uncontrolled, or controlled **and** `onOpen` supplied. Plus the component's **render matrix** written into its doc comment. Full spec: [work-orders/SHELL-6.md](work-orders/SHELL-6.md). | 2026-08-11 | done | <pending> | **Unblocks `jg-ferien/NAV-37`** (`blocked`, `c627d7b`), same shape as `SHELL-3`→`SHELL-4`. **Operator chose the semantics fix over a `showTrigger` prop** — a prop would leave the dead button as the default for every controlled consumer who has not heard of it, turning a defect into a configuration option; a focusable control that performs no action is wrong on its own terms. Fix: `const canOpenTrigger = !isControlled || Boolean(onOpen)`, wrapping only the `<ButtonBase>` trigger — `children` and `<Drawer>` keep rendering unconditionally in every case. Render-matrix doc comment added above the component per the WO's own framing ("not optional documentation; it is the artefact whose absence caused the defect"). `AccountPage`, the only shipped consumer, is uncontrolled and renders identically. Version `2.37.0` → `2.37.1` (patch, defect fix, no API change). **Codex left the diff uncommitted and did not touch this file, as instructed** — fourth consecutive WO where the explicit warning held. **Required test 1's non-vacuity confirmed**: Codex's own landing note states the new regression test was run against the pre-fix code and failed (dead trigger still in the DOM), then passed after the one-line fix — the Orchestrator did not re-verify this specific claim by checking out the prior commit, but both independent reviewers separately read the old-vs-new JSX and found the claim plausible/consistent. **Orchestrator's own verification:** scoped tests 47/47 green, `tsc` clean. Independent `reviewer` + `ui_reviewer` (Sonnet, both mandatory) ran concurrently — **both came back clean, no findings, no fix required.** `reviewer` confirmed the condition is keyed correctly (not on `open`'s value, avoiding the trap the WO's own test 3 exists to catch), `children`/`Drawer` stay unconditional, desktop path untouched, and the render-matrix comment matches the Envelope's table exactly. `ui_reviewer` confirmed the trigger's removal is genuine (conditional JSX unmount, not a CSS-hidden trick left in the accessibility tree/tab order) and no restyle occurred as a side effect; noted two non-blocking residual observations, not fixed: a hypothetical layout-shift if a consumer dynamically toggled `onOpen` on/off at runtime (no current or planned consumer does this), and `resolvedEyebrow`/`resolvedTitle` computed unconditionally even when unused (harmless). No rendered gate needed per the WO's own reasoning — the change is a DOM absence fact, not an appearance, and the test suite is the correct instrument. |

package/dist/index.js

@@ -1,4 +1,11 @@
 // index.js (Entry Point deiner Library)
+import { authTranslations } from './i18n/authTranslations';
+import { chartsTranslations } from './i18n/chartsTranslations';
+import { messagingTranslations } from './i18n/messagingTranslations';
+import { notificationsTranslations } from './i18n/notificationsTranslations';
+import { onboardingTranslations } from './i18n/onboardingTranslations';
+import { sectionNavTranslations } from './i18n/sectionNavTranslations';
+import { userMenuTranslations } from './i18n/userMenuTranslations';
 // --- 0. Theme ---
 export { createAppTheme, assertThemeComplete, assertKitSxDisjoint, calculateContrastRatio, KIT_COMPONENT_SX_REGISTRY, reportOffPaletteColours, reportKitSxBypasses, reportThemeAdoption, THEME_COMPLETENESS_SURFACES, } from './theme';
 // --- 1. Auth Context (Essentiell für den Wrapper) ---
@@ -81,3 +88,4 @@ export { notificationsTranslations } from './i18n/notificationsTranslations';
 export { onboardingTranslations } from './i18n/onboardingTranslations';
 export { chartsTranslations } from './i18n/chartsTranslations';
 export { messagingTranslations } from './i18n/messagingTranslations';
+export const uiCoreTranslations = Object.assign(Object.assign(Object.assign(Object.assign(Object.assign(Object.assign(Object.assign({}, authTranslations), chartsTranslations), messagingTranslations), notificationsTranslations), onboardingTranslations), sectionNavTranslations), userMenuTranslations);

package/dist/layout/SectionNav.js

@@ -90,6 +90,20 @@ function SectionNavList({ groups, activeKey, rememberedKey, overviewItem, onSele
                             }) })] }, group.key));
             })] }));
 }
+/**
+ * Render matrix:
+ *
+ * | `mode`    | `open`                 | `onOpen` | trigger | sidebar | `children`       | drawer              |
+ * |-----------|------------------------|----------|---------|---------|------------------|---------------------|
+ * | `desktop` | ignored                | ignored  | —       | yes     | yes, in the grid | —                   |
+ * | `mobile`  | absent (uncontrolled)  | ignored  | yes     | —       | yes              | yes, internal state |
+ * | `mobile`  | given                  | given    | yes     | —       | yes              | caller-driven       |
+ * | `mobile`  | given                  | absent   | no      | —       | yes              | caller-driven       |
+ *
+ * Optional parts: without `overviewItem`, no overview entry or empty Paper is rendered;
+ * without `rememberedKey`, no secondary line is rendered; without `title` or
+ * `triggerEyebrow`, `t('SectionNav.TITLE')` or `t('SectionNav.TRIGGER_EYEBROW')` is used.
+ */
 export function SectionNav({ mode, groups, activeKey = null, onSelect, open, onOpen, onClose, title, triggerEyebrow, overviewItem, rememberedKey, headerOffset = 24, 
 // SHELL-3's bottom bar uses drawer + 2, so the drawer must stay above it.
 zIndex = defaultZIndex, sidebarWidth = 280, children, }) {
@@ -100,6 +114,7 @@ zIndex = defaultZIndex, sidebarWidth = 280, children, }) {
     const [internalOpen, setInternalOpen] = useState(false);
     const isControlled = open !== undefined;
     const drawerOpen = isControlled ? open : internalOpen;
+    const canOpenTrigger = !isControlled || Boolean(onOpen);
     const resolvedTitle = title !== null && title !== void 0 ? title : t('SectionNav.TITLE');
     const resolvedEyebrow = triggerEyebrow !== null && triggerEyebrow !== void 0 ? triggerEyebrow : t('SectionNav.TRIGGER_EYEBROW');
     const rememberedLabel = t('SectionNav.LAST_OPENED');
@@ -128,7 +143,7 @@ zIndex = defaultZIndex, sidebarWidth = 280, children, }) {
     if (mode === 'desktop') {
         return (_jsxs(Box, { sx: Object.assign(Object.assign({}, SECTION_NAV_GRID_SX), { gridTemplateColumns: `${sidebarWidth}px minmax(0, 1fr)` }), "data-section-nav-mode": "desktop", children: [_jsx(Box, { component: "nav", "aria-label": resolvedTitle, sx: SECTION_NAV_SIDEBAR_SX, style: { '--SectionNav-headerOffset': resolvedHeaderOffset }, children: _jsx(SectionNavList, { groups: groups, activeKey: activeKey, rememberedKey: rememberedKey, overviewItem: overviewItem, onSelect: onSelect, rememberedLabel: rememberedLabel }) }), _jsx(Box, { sx: SECTION_NAV_CONTENT_SX, children: children })] }));
     }
-    return (_jsxs(_Fragment, { children: [_jsxs(ButtonBase, { sx: SECTION_NAV_TRIGGER_SX, onClick: handleTriggerClick, "aria-haspopup": "dialog", "aria-expanded": drawerOpen, "aria-controls": drawerId, children: [_jsxs(Box, { sx: SECTION_NAV_TRIGGER_TEXT_SX, children: [_jsx(Typography, { variant: "caption", color: "text.secondary", children: resolvedEyebrow }), _jsx(Typography, { variant: "subtitle1", sx: SECTION_NAV_TRIGGER_VALUE_SX, children: (_a = activeItem === null || activeItem === void 0 ? void 0 : activeItem.label) !== null && _a !== void 0 ? _a : resolvedTitle })] }), _jsx(KeyboardArrowDownIcon, { "aria-hidden": "true", sx: SECTION_NAV_CHEVRON_SX, style: { transform: drawerOpen ? 'rotate(180deg)' : 'rotate(0deg)' } })] }), _jsx(Box, { sx: SECTION_NAV_CONTENT_SX, children: children }), _jsxs(Drawer, { anchor: "bottom", open: drawerOpen, onClose: handleDrawerClose, style: { zIndex: resolvedZIndex }, PaperProps: {
+    return (_jsxs(_Fragment, { children: [canOpenTrigger && (_jsxs(ButtonBase, { sx: SECTION_NAV_TRIGGER_SX, onClick: handleTriggerClick, "aria-haspopup": "dialog", "aria-expanded": drawerOpen, "aria-controls": drawerId, children: [_jsxs(Box, { sx: SECTION_NAV_TRIGGER_TEXT_SX, children: [_jsx(Typography, { variant: "caption", color: "text.secondary", children: resolvedEyebrow }), _jsx(Typography, { variant: "subtitle1", sx: SECTION_NAV_TRIGGER_VALUE_SX, children: (_a = activeItem === null || activeItem === void 0 ? void 0 : activeItem.label) !== null && _a !== void 0 ? _a : resolvedTitle })] }), _jsx(KeyboardArrowDownIcon, { "aria-hidden": "true", sx: SECTION_NAV_CHEVRON_SX, style: { transform: drawerOpen ? 'rotate(180deg)' : 'rotate(0deg)' } })] })), _jsx(Box, { sx: SECTION_NAV_CONTENT_SX, children: children }), _jsxs(Drawer, { anchor: "bottom", open: drawerOpen, onClose: handleDrawerClose, style: { zIndex: resolvedZIndex }, PaperProps: {
                     id: drawerId,
                     role: 'dialog',
                     'aria-modal': true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@micha.bigler/ui-core-micha",
-  "version": "2.36.0",
+  "version": "2.37.1",
   "main": "dist/index.js",
   "module": "dist/index.js",
   "repository": {

package/src/index.js

@@ -1,5 +1,13 @@
 // index.js (Entry Point deiner Library)
 
+import { authTranslations } from './i18n/authTranslations';
+import { chartsTranslations } from './i18n/chartsTranslations';
+import { messagingTranslations } from './i18n/messagingTranslations';
+import { notificationsTranslations } from './i18n/notificationsTranslations';
+import { onboardingTranslations } from './i18n/onboardingTranslations';
+import { sectionNavTranslations } from './i18n/sectionNavTranslations';
+import { userMenuTranslations } from './i18n/userMenuTranslations';
+
 // --- 0. Theme ---
 export {
   createAppTheme,
@@ -125,3 +133,13 @@ export { notificationsTranslations } from './i18n/notificationsTranslations';
 export { onboardingTranslations } from './i18n/onboardingTranslations';
 export { chartsTranslations } from './i18n/chartsTranslations';
 export { messagingTranslations } from './i18n/messagingTranslations';
+
+export const uiCoreTranslations = {
+  ...authTranslations,
+  ...chartsTranslations,
+  ...messagingTranslations,
+  ...notificationsTranslations,
+  ...onboardingTranslations,
+  ...sectionNavTranslations,
+  ...userMenuTranslations,
+};

package/src/layout/SectionNav.jsx

@@ -164,6 +164,20 @@ function SectionNavList({
   );
 }
 
+/**
+ * Render matrix:
+ *
+ * | `mode`    | `open`                 | `onOpen` | trigger | sidebar | `children`       | drawer              |
+ * |-----------|------------------------|----------|---------|---------|------------------|---------------------|
+ * | `desktop` | ignored                | ignored  | —       | yes     | yes, in the grid | —                   |
+ * | `mobile`  | absent (uncontrolled)  | ignored  | yes     | —       | yes              | yes, internal state |
+ * | `mobile`  | given                  | given    | yes     | —       | yes              | caller-driven       |
+ * | `mobile`  | given                  | absent   | no      | —       | yes              | caller-driven       |
+ *
+ * Optional parts: without `overviewItem`, no overview entry or empty Paper is rendered;
+ * without `rememberedKey`, no secondary line is rendered; without `title` or
+ * `triggerEyebrow`, `t('SectionNav.TITLE')` or `t('SectionNav.TRIGGER_EYEBROW')` is used.
+ */
 export function SectionNav({
   mode,
   groups,
@@ -188,6 +202,7 @@ export function SectionNav({
   const [internalOpen, setInternalOpen] = useState(false);
   const isControlled = open !== undefined;
   const drawerOpen = isControlled ? open : internalOpen;
+  const canOpenTrigger = !isControlled || Boolean(onOpen);
   const resolvedTitle = title ?? t('SectionNav.TITLE');
   const resolvedEyebrow = triggerEyebrow ?? t('SectionNav.TRIGGER_EYEBROW');
   const rememberedLabel = t('SectionNav.LAST_OPENED');
@@ -243,27 +258,29 @@ export function SectionNav({
 
   return (
     <>
-      <ButtonBase
-        sx={SECTION_NAV_TRIGGER_SX}
-        onClick={handleTriggerClick}
-        aria-haspopup="dialog"
-        aria-expanded={drawerOpen}
-        aria-controls={drawerId}
-      >
-        <Box sx={SECTION_NAV_TRIGGER_TEXT_SX}>
-          <Typography variant="caption" color="text.secondary">
-            {resolvedEyebrow}
-          </Typography>
-          <Typography variant="subtitle1" sx={SECTION_NAV_TRIGGER_VALUE_SX}>
-            {activeItem?.label ?? resolvedTitle}
-          </Typography>
-        </Box>
-        <KeyboardArrowDownIcon
-          aria-hidden="true"
-          sx={SECTION_NAV_CHEVRON_SX}
-          style={{ transform: drawerOpen ? 'rotate(180deg)' : 'rotate(0deg)' }}
-        />
-      </ButtonBase>
+      {canOpenTrigger && (
+        <ButtonBase
+          sx={SECTION_NAV_TRIGGER_SX}
+          onClick={handleTriggerClick}
+          aria-haspopup="dialog"
+          aria-expanded={drawerOpen}
+          aria-controls={drawerId}
+        >
+          <Box sx={SECTION_NAV_TRIGGER_TEXT_SX}>
+            <Typography variant="caption" color="text.secondary">
+              {resolvedEyebrow}
+            </Typography>
+            <Typography variant="subtitle1" sx={SECTION_NAV_TRIGGER_VALUE_SX}>
+              {activeItem?.label ?? resolvedTitle}
+            </Typography>
+          </Box>
+          <KeyboardArrowDownIcon
+            aria-hidden="true"
+            sx={SECTION_NAV_CHEVRON_SX}
+            style={{ transform: drawerOpen ? 'rotate(180deg)' : 'rotate(0deg)' }}
+          />
+        </ButtonBase>
+      )}
 
       <Box sx={SECTION_NAV_CONTENT_SX}>{children}</Box>
 

package/tests/SectionNav.test.jsx

@@ -147,6 +147,7 @@ describe('SectionNav', () => {
     renderNav({ mode: 'mobile', onSelect });
 
     const trigger = screen.getByRole('button', { name: /Section Profile/i });
+    expect(trigger).toBeTruthy();
     expect(trigger.getAttribute('aria-expanded')).toBe('false');
     fireEvent.click(trigger);
     expect(trigger.getAttribute('aria-expanded')).toBe('true');
@@ -164,6 +165,7 @@ describe('SectionNav', () => {
     const { rerender } = renderNav({ mode: 'mobile', open: false, onOpen, onClose });
 
     const trigger = screen.getByRole('button', { name: /Section Profile/i });
+    expect(trigger).toBeTruthy();
     fireEvent.click(trigger);
 
     expect(onOpen).toHaveBeenCalledOnce();
@@ -189,6 +191,53 @@ describe('SectionNav', () => {
     expect(screen.getByRole('button', { name: 'Security' })).toBeTruthy();
   });
 
+  it('omits a dead controlled trigger while keeping children and the caller-driven drawer', () => {
+    const { rerender } = renderNav({ mode: 'mobile', open: false });
+
+    expect(screen.queryByRole('button', { name: /Section Profile/i })).toBeNull();
+    expect(screen.getByTestId('section-content')).toBeTruthy();
+    expect(screen.queryByRole('dialog', { name: 'Switch section' })).toBeNull();
+
+    rerender(
+      <ThemeProvider theme={theme}>
+        <SectionNav
+          mode="mobile"
+          groups={groups}
+          activeKey="profile"
+          onSelect={vi.fn()}
+          open
+        >
+          <div data-testid="section-content">Section content</div>
+        </SectionNav>
+      </ThemeProvider>,
+    );
+
+    expect(screen.queryByRole('button', { name: /Section Profile/i })).toBeNull();
+    expect(screen.getByTestId('section-content')).toBeTruthy();
+    expect(screen.getByRole('dialog', { name: 'Switch section' })).toBeTruthy();
+    expect(screen.getByRole('button', { name: 'Security' })).toBeTruthy();
+  });
+
+  it('keeps the desktop sidebar and children for every open/onOpen combination', () => {
+    const propCombinations = [
+      {},
+      { open: false, onOpen: vi.fn() },
+      { open: false },
+    ];
+
+    propCombinations.forEach((props) => {
+      const { container } = renderNav(props);
+
+      expect(container.querySelector('[data-section-nav-mode="desktop"]')).toBeTruthy();
+      expect(container.querySelector('nav')).toBeTruthy();
+      expect(screen.getByTestId('section-content')).toBeTruthy();
+      expect(screen.queryByRole('button', { name: /Section Profile/i })).toBeNull();
+      expect(document.querySelector('.MuiDrawer-root')).toBeNull();
+
+      cleanup();
+    });
+  });
+
   it('renders the desktop sidebar and children in a two-column grid, while mobile renders a trigger and no sidebar', () => {
     const { container } = renderNav({ sidebarWidth: 312 });
     const desktopRoot = container.querySelector('[data-section-nav-mode="desktop"]');

package/tests/i18nAggregate.test.js

@@ -0,0 +1,121 @@
+import fs from 'node:fs';
+import path from 'node:path';
+
+import { describe, expect, it, vi } from 'vitest';
+
+vi.mock('@mui/icons-material', () => ({
+  Archive: () => null,
+  Campaign: () => null,
+  Groups: () => null,
+  MoreVert: () => null,
+  NotificationsOff: () => null,
+  Person: () => null,
+}));
+
+import {
+  authTranslations as publicAuthTranslations,
+  chartsTranslations as publicChartsTranslations,
+  messagingTranslations as publicMessagingTranslations,
+  notificationsTranslations as publicNotificationsTranslations,
+  onboardingTranslations as publicOnboardingTranslations,
+  sectionNavTranslations as publicSectionNavTranslations,
+  uiCoreTranslations,
+  userMenuTranslations as publicUserMenuTranslations,
+} from '../src/index';
+
+const I18N_DIRECTORY = path.resolve('src/i18n');
+// Scoped to the three locales every bundle already carries. `messagingTranslations`'s 116 keys
+// have no `sw` value yet (pre-existing gap, out of I18N-1's scope — see the Notiz on the
+// I18N-1 register row for the tracked follow-up to backfill it and restore `sw` here).
+const REQUIRED_LOCALES = ['de', 'en', 'fr'];
+const bundleImporters = import.meta.glob('../src/i18n/*.ts');
+const PUBLIC_BUNDLES = {
+  authTranslations: publicAuthTranslations,
+  chartsTranslations: publicChartsTranslations,
+  messagingTranslations: publicMessagingTranslations,
+  notificationsTranslations: publicNotificationsTranslations,
+  onboardingTranslations: publicOnboardingTranslations,
+  sectionNavTranslations: publicSectionNavTranslations,
+  userMenuTranslations: publicUserMenuTranslations,
+};
+
+function bundleFileNames() {
+  return fs.readdirSync(I18N_DIRECTORY, { withFileTypes: true })
+    .filter((entry) => entry.isFile() && entry.name.endsWith('.ts'))
+    .map((entry) => entry.name)
+    .sort();
+}
+
+async function loadBundles() {
+  return Promise.all(bundleFileNames().map(async (fileName) => {
+    const modulePath = `../src/i18n/${fileName}`;
+    const importBundle = bundleImporters[modulePath];
+    if (!importBundle) {
+      throw new Error(`${fileName} was enumerated from src/i18n but has no module importer`);
+    }
+
+    const bundleModule = await importBundle();
+    const translationExports = Object.entries(bundleModule)
+      .filter(([exportName]) => exportName.endsWith('Translations'));
+
+    if (Object.keys(bundleModule).length !== 1 || translationExports.length !== 1) {
+      throw new Error(`${fileName} must export exactly one *Translations bundle`);
+    }
+
+    const [[exportName, translations]] = translationExports;
+    return { exportName, fileName, translations };
+  }));
+}
+
+describe('uiCoreTranslations', () => {
+  it('contains every directory-enumerated bundle key with its original value', async () => {
+    const bundles = await loadBundles();
+    const sourceKeys = [];
+
+    for (const { fileName, translations } of bundles) {
+      for (const [key, value] of Object.entries(translations)) {
+        sourceKeys.push(key);
+        expect(
+          Object.hasOwn(uiCoreTranslations, key),
+          `${key} from ${fileName} is missing from the public aggregate`,
+        ).toBe(true);
+        expect(uiCoreTranslations[key]).toEqual(value);
+      }
+    }
+
+    expect(Object.keys(uiCoreTranslations).sort()).toEqual(sourceKeys.sort());
+  });
+
+  it('does not allow duplicate keys across source bundles', async () => {
+    const owners = new Map();
+    const collisions = [];
+
+    for (const { fileName, translations } of await loadBundles()) {
+      for (const key of Object.keys(translations)) {
+        if (owners.has(key)) {
+          collisions.push(`${key}: ${owners.get(key)} and ${fileName}`);
+        } else {
+          owners.set(key, fileName);
+        }
+      }
+    }
+
+    expect(collisions, `Translation key collisions:\n${collisions.join('\n')}`).toEqual([]);
+  });
+
+  it('preserves at least the required locale shape for every aggregate value', () => {
+    for (const [key, value] of Object.entries(uiCoreTranslations)) {
+      for (const locale of REQUIRED_LOCALES) {
+        expect(typeof value[locale], `${key}.${locale} must be a string`).toBe('string');
+        expect(value[locale].trim(), `${key}.${locale} must not be empty`).not.toBe('');
+      }
+    }
+  });
+
+  it('keeps every per-feature bundle available unchanged from the package root', async () => {
+    for (const { exportName, translations } of await loadBundles()) {
+      expect(PUBLIC_BUNDLES[exportName], `${exportName} must remain a public export`)
+        .toBe(translations);
+    }
+  });
+});

package/work-orders/SHELL-6.md

@@ -0,0 +1,210 @@
+# SHELL-6 — A controlled `SectionNav` with no way to open must not render a trigger
+
+**Target repo:** `ui-core-micha` (branch `main` — this repo has no `develop`)
+**Tier:** 3 (shared core)
+**Review:** independent `reviewer` **and** `ui_reviewer` — both mandatory, concurrent
+**Version target:** the next **patch** after the published version. A defect fix, no API change, no
+consumer relying on the current behaviour. Read the published version at implementation time.
+**Unblocks:** `jg-ferien/NAV-37`, currently `blocked` (`c627d7b`)
+**Follows:** `SHELL-5` (`2.36.0`)
+
+---
+
+## A. Envelope
+
+### Goal
+
+In `mode="mobile"`, `SectionNav` renders its built-in trigger **unconditionally**
+(`src/layout/SectionNav.jsx:246`). In controlled mode `handleTriggerClick` calls `onOpen?.()`
+(`:200-206`), so a consumer that drives `open` itself and passes no `onOpen` gets a button that is
+**visible, focusable and does nothing**.
+
+Make the trigger render only when it can actually open the drawer.
+
+### This is a defect, not a missing configuration
+
+A control that receives focus and performs no action is wrong on its own terms — it is an
+accessibility defect independent of any consumer's wishes. That is why the fix is the **semantics**
+rather than a `showTrigger` prop: a prop would make the dead button the default for every controlled
+consumer who has not heard of the prop, turning a defect into a configuration option.
+
+**Nothing today relies on the current behaviour.** `AccountPage`, the only shipped consumer, is
+**uncontrolled** (it passes no `open`), so its trigger keeps rendering unchanged. `jg-ferien` is the
+consumer that hit this and is blocked on it.
+
+### How it shipped, and the rule that follows
+
+`SHELL-5`'s Envelope specified that the component *has* a trigger and never said *when it renders*.
+The implementation made it unconditional — correctly, given the spec. `NAV-37` then assumed that
+omitting `onOpen` suppresses it; that assumption appears nowhere in `SHELL-5`.
+
+**The uncovered cell and the untested cell were the same cell.** Every existing mobile test is either
+uncontrolled (`:192`, `:210`) or controlled *with* `onOpen` (`:161`) — verified. So this fix breaks no
+existing test, which is the point: the case was never specified, therefore never tested, therefore
+shipped.
+
+**Hence the second deliverable below: write the render matrix down.** A prop table plus a scope
+narrative reads complete and is not.
+
+### Scope
+
+**1. The fix.** In the mobile return path, render the `<ButtonBase>` trigger only when a click can do
+something: uncontrolled (the component owns `internalOpen`), or controlled **and** `onOpen` supplied.
+`children` and the `<Drawer>` keep rendering in every case — `jg-ferien` needs exactly that: its own
+triggers, the shared drawer, its content.
+
+**2. The render matrix, in the component's own doc comment.** This is not optional documentation; it
+is the artefact whose absence caused the defect.
+
+| `mode` | `open` | `onOpen` | trigger | sidebar | `children` | drawer |
+|---|---|---|---|---|---|---|
+| `desktop` | ignored | ignored | — | yes | yes, in the grid | — |
+| `mobile` | absent (uncontrolled) | ignored | **yes** | — | yes | yes, internal state |
+| `mobile` | given | given | **yes** | — | yes | caller-driven |
+| `mobile` | given | **absent** | **no** ← this WO | — | yes | caller-driven |
+
+Plus the optional-part cells, all already correct and worth recording so they stay that way:
+`overviewItem` absent → no overview entry and no empty `Paper`; `rememberedKey` absent → no secondary
+line; `title` absent → `t('SectionNav.TITLE')`; `triggerEyebrow` absent → `t('SectionNav.TRIGGER_EYEBROW')`.
+
+### Non-goals / do not touch
+
+- **No new prop.** Not `showTrigger`, not `hideTrigger`. The operator considered and rejected both:
+  they would leave the dead button as the default. A consumer wanting "controlled **with** `onOpen` but
+  my own trigger too" has no representation after this WO — that case has no consumer today and adding
+  a prop for it is the speculative generality the YAGNI guardrail rejects.
+- **The desktop path** — untouched, including the grid, `sidebarWidth` and `headerOffset`.
+- The drawer, its `zIndex` resolution, its safe-area padding, `SectionNavList`, and every label or
+  i18n key.
+- `AccountPage` — no change; it is uncontrolled and keeps its trigger.
+- No baseline token change, no `kitSxRegistry` change. `SECTION_NAV_TRIGGER_SX` stays registered:
+  `THEME-4`'s check is about key disjointness, not about whether an element renders.
+
+### Risks
+
+- **It is a behaviour change to a shipped component**, which is why "no consumer relies on it" is
+  stated above rather than assumed. If a consumer outside this repo passes `open` without `onOpen` and
+  wants the trigger, it breaks for them — verified as nobody today.
+- **No staging net.** A version bump on `main` publishes; the two reviews are the only gate.
+- **The condition must be `onOpen` supplied, not `open` supplied.** Keying it on the wrong prop would
+  remove the trigger from the uncontrolled case as well, which is `AccountPage`'s only affordance.
+  Test 3 exists for that.
+
+### Required tests to WRITE
+
+Extend `tests/SectionNav.test.jsx`.
+
+1. **The fix, with non-vacuity.** `mode="mobile"` + `open` + **no** `onOpen` → **no** trigger button
+   in the DOM, while `children` still render and the drawer still responds to `open`. **This test must
+   fail against the current published version** — say so in the WO's landing note, since a fix whose
+   test passes before the fix is not a fix.
+2. Controlled **with** `onOpen` → trigger renders, clicking calls `onOpen`. (The existing `:161`
+   already covers the call; assert the rendering explicitly.)
+3. **Uncontrolled** → trigger renders and clicking opens the internal drawer. This is the guard against
+   keying the condition on the wrong prop.
+4. Desktop is unchanged in all three prop combinations.
+5. `THEME-4`'s shadowing check still returns no findings.
+
+Plus `tsc -p tsconfig.build.json --noEmit` clean. **No full-suite run** — affected set is
+`tests/SectionNav.test.jsx` and the theme spec touched by test 5.
+
+### Verification
+
+The change is the **absence** of an element in one prop combination, so the rendered gate has little to
+add beyond the tests: assert the DOM, and confirm `AccountPage`'s own trigger still renders at 375 px.
+If capture is unavailable, DOM inspection is the declared substitution — and here it is not a
+fallback but the appropriate instrument, because "no button" is a DOM fact, not an appearance.
+
+### Parity guardrail
+
+`AccountPage` renders identically. The only intended change is that a controlled consumer without
+`onOpen` no longer gets a dead button.
+
+---
+
+## B. Implementation map
+
+*Filled by the Orchestrator on `git pull` — see `AGENTS.md` → "Work Order".*
+
+### Execution directive (read this first)
+
+> **If you are the implementer reading this work order as your own specification: this section is
+> NOT addressed to you.** It tells the Orchestrator how to invoke you. **You ARE that invocation —
+> do NOT shell out to `codex exec`.**
+>
+> Implement through `codex exec` in the background — invoked directly via Bash (never the
+> `debugger`/`*_coder` Agent wrappers) with BOTH flags `--skip-git-repo-check` and
+> `--dangerously-bypass-approvals-and-sandbox`. **Pass the WO via stdin, not as a positional
+> argument.** Fallback to direct Claude implementation only on Codex quota/rate-limit/non-zero exit —
+> and that flips authorship, so both reviewers stay mandatory either way.
+>
+> **Do NOT edit `WORK_ORDERS.md`**, and before your own review read `git log origin/main..HEAD` plus
+> `git status`. Check the working tree first: `NAV-37`'s rejected CSS workaround lives uncommitted in
+> `jg-ferien`, and other sessions have been active in this repo throughout this strand.
+
+### Context package
+
+**Precondition confirmed:** `SHELL-5` landed and published (`b283c33`/`ada72be`); `I18N-1` also landed
+independently in the interim (`a6d322d`). Clean starting tree, no implementer commit on top.
+
+**Current file state** (`src/layout/SectionNav.jsx`, verified — line numbers drifted a little from
+the WO's own `:246`/`:200-206` estimate since `SHELL-5`'s own review-fix pass, but the structure is
+identical):
+```js
+// :188-190
+const [internalOpen, setInternalOpen] = useState(false);
+const isControlled = open !== undefined;
+const drawerOpen = isControlled ? open : internalOpen;
+// :200-206
+const handleTriggerClick = () => {
+  if (isControlled) {
+    onOpen?.();
+  } else {
+    setInternalOpen(true);
+  }
+};
+// :244-266, the mobile return path
+return (
+  <>
+    <ButtonBase sx={SECTION_NAV_TRIGGER_SX} onClick={handleTriggerClick} ...>
+      ...
+    </ButtonBase>
+    <Box sx={SECTION_NAV_CONTENT_SX}>{children}</Box>
+    <Drawer ...>...</Drawer>
+  </>
+);
+```
+
+**The fix, precisely:** add `const canOpenTrigger = !isControlled || Boolean(onOpen);` and wrap only
+the `<ButtonBase>` block in `{canOpenTrigger && (...)}`. `children` and `<Drawer>` stay unconditional
+— do not touch their rendering. Do not key the condition on `open` (the WO's own Risks section flags
+this exact mistake as the guard test 3 exists for) — the condition is about whether a click can do
+anything, which depends on `isControlled`/`onOpen`, never on the current `open` value itself.
+
+**The render-matrix doc comment (scope item 2):** add a JSDoc-style comment directly above
+`export function SectionNav(...)` reproducing the table from the Envelope (`mode`/`open`/`onOpen` →
+trigger/sidebar/children/drawer), plus the "optional-part cells" paragraph (`overviewItem` absent →
+no overview entry; `rememberedKey` absent → no secondary line; `title`/`triggerEyebrow` absent →
+their `t()` fallbacks). This is a required deliverable per the WO's own framing ("not optional
+documentation; it is the artefact whose absence caused the defect"), not a nice-to-have.
+
+**Test file:** `tests/SectionNav.test.jsx` already has a controlled-mode test from `SHELL-5`'s own
+review-fix round (`'defers to the caller in controlled mode: the trigger calls onOpen, not internal
+state'`, roughly `:145-175` now) — that test passes `onOpen`, so it exercises the WO's "controlled
+with `onOpen`" cell, not the new "controlled without `onOpen`" cell this WO fixes. Add the four new
+tests as siblings of it, following its existing render helper (`renderNav`) and prop-passing style.
+Required test 1 (non-vacuity) needs to be run against a build BEFORE the fix lands to confirm it
+fails — since this is a live working tree with the pre-fix code already checked out, this is simply:
+write the test first, run it once to confirm it fails, then apply the one-line fix and confirm it
+passes. State this sequence happened in the register note.
+
+**Invariants:** no new prop (`showTrigger`/`hideTrigger` explicitly rejected by the WO); desktop path,
+`Drawer`, `zIndex`, safe-area padding, `SectionNavList`, all i18n keys, `AccountPage` itself, and
+`kitSxRegistry.js` all untouched. `SECTION_NAV_TRIGGER_SX` stays registered even though the element
+it styles now sometimes doesn't render — `THEME-4`'s check is about key disjointness, not element
+presence, so this is a non-issue, not a discrepancy to resolve.
+
+### Mini-handover
+
+Repo: `ui-core-micha` (`C:\Users\biglmi\Documents\webapps\ui-core-micha`), branch `main`.
+WO: `work-orders/SHELL-6.md`. Unblocks `jg-ferien/NAV-37`. Follow `orchestrate-codex`.