# Round 0 issues ## Historical record Recorded names, source locations and external scratch evidence describe the review's original tree, not current runtime APIs. From two independent judges (opus, gpt) against NL-SPEC-VQXGUHYK; duplicates between judges are listed once per judge on purpose. Excluded by house precedence or scope: - bar p7: usage-ordered chips are house precedence - bar p1: keep-awake strong emphasis is house precedence - shared p3: aurora backdrop is wallpaper, house precedence - notifications p8: toast time-left drain is a progress indicator, allowed by rule 8 - bar p6: popups open by niri keybinds the shell does not own; no bar focus mode in this round - osd p5: unsupported events rendering as errors is specified and tested behaviour ## bar - [p1 major opus] The bar never says 'something needs me' for system incidents, low battery or lost network, so 13 identical text chips answer nothing at a glance. Fix: Bind barActive/barStrong (warning role) on system to open incidents, on power to low battery and on connectivity to offline, and keep every other chip quiet. Evidence: Registry.qml:282-341 (system, power, connectivity entries have no barActive/barStrong); shell-system.png shows 'high load' incident while 'system' chip is plain - [p4 blocker opus] The vertical bar replaces words with cryptic consonant abbreviations, which are exactly the acronyms the rule forbids where plain words exist. Fix: Use an icon per chip on the vertical bar (icon-led house style) with the full lowercase word as tooltip and accessible name instead of abbreviations. Evidence: idle-awake-vertical.png, tasks-power-vertical.png: 'lnc', 'nok', 'clp', 'vlt', 'brg', 'ntw', 'ntf', 'try', 'idl' (Bar.qml:430 Format.abbreviate) - [p12 major opus] Chips are text pills with no icon, tooltip or explicit accessible name, which goes against the compact icon-led house style and leaves vertical abbreviations unexplained. Fix: Give each FeatureEntry a bar icon, render chips icon-first and attach PopupToolTip plus Accessible.name with the full lowercase feature name. Evidence: shell-loaded.png (text-only chips); Bar.qml:577-689 BarChip has no tooltip or Accessible.name - [p4 major gpt] Vertical chips expose cryptic abbreviations such as ntw and vlt without full-name tooltips. Fix: Use verified compact role icons with lowercase full-name tooltips and accessible names. Evidence: bar/idle-awake-vertical.png; Bar.qml:374–380 - [p8 minor gpt] The busy indicator uses 520 ms animation legs, exceeding the 250 ms limit. Fix: Shorten each busy-state animation leg to at most 250 ms. Evidence: Bar.qml:660–672 ## clock - [p4 blocker opus] The clock mixes capitalised English dates, German weekday initials and German labels in an otherwise lowercase English shell, and shows the jargon 'caldav'. Fix: Use one language in lowercase throughout ('sat 14 nov', 'm t w t f s s', 'connect calendar', 'username', 'save', 'no events today'). Evidence: clock-agenda.png 'Sat 14 Nov', weekday header 'M D M D F S S'; clock-setup.png 'caldav einrichten', 'benutzername', 'speichern'; clock-agenda-empty.png 'keine termine' - [p5 major opus] Offline or stale calendar data is marked only by a trailing dot, so old events look current. Fix: When status is offline or stale, show a meta line 'calendar offline · showing last sync' with a retry action. Evidence: ClockPanel.qml:107 stale shown as appended ' ·'; CalDav.qml:101,157 status 'offline' - [p15 minor opus] A one-second timer runs for the whole session although the bar shows only minutes and the seconds display is visible only while the panel is open. Fix: Tick on minute boundaries while the panel is closed and switch to 1 s only while the clock popup is open. Evidence: Time.qml:216-221 Timer 1000 ms always running - [p4 minor gpt] The calendar mixes German controls, English capitalized date abbreviations, and unexplained caldav terminology. Fix: Use consistent lowercase localization and a plain calendar-setup label. Evidence: clock/clock-setup.png; clock/clock-agenda.png; features/clock/ClockPanel.qml:109–121,319 - [p5 major gpt] Stale calendar data is indicated only by an unexplained dot beside the date. Fix: Display an explicit stale or offline label with the last successful refresh context. Evidence: features/clock/ClockPanel.qml:84–88 - [p11 major gpt] Loading and offline states can render the same no-appointments message as a genuinely empty agenda. Fix: Render distinct loading and unavailable agenda states with a retry action. Evidence: features/clock/ClockPanel.qml:16,275–282; features/clock/CalDav.qml:99–110,115–137 - [p13 major gpt] Agenda summary text has no width constraint or wrapping inside the clipped agenda viewport. Fix: Constrain each summary to the remaining row width and wrap long event names. Evidence: features/clock/ClockPanel.qml:251–273 - [p14 major gpt] Dimmed weekday headers and neighbouring-month dates fall below the required text contrast. Fix: Use contrast-checked text colours and distinguish neighbouring dates without extreme opacity reduction. Evidence: clock/clock-agenda.png; features/clock/ClockPanel.qml:121,169 - [p15 blocker gpt] Calendar refresh runs every fifteen minutes while closed although the bar control displays only local time. Fix: Refresh on opening and gate periodic calendar fetching on visible agenda use. Evidence: features/clock/CalDav.qml:273–278; Registry.qml:119–138 ## launcher - [p11 blocker opus] The no-match state leaves the list blank and fills the detail pane with a fake app header, a dead button and an empty card. Fix: Replace both panes with one sentence 'no apps match "terminalx"' plus a clear-search action, and hide the actions and desktop-entry sections. Evidence: launcher-no-matches.png: empty left list, detail pane 'no apps / app', disabled 'open', blank 'desktop entry' card - [p2 minor opus] Desktop-entry metadata is always visible beside the launch task, although it is secondary detail. Fix: Collapse the desktop-entry section behind a disclosure and keep only name, icon and actions visible. Evidence: shell-launcher.png 'desktop entry' card with 'keywords —', 'terminal no' - [p2 minor gpt] Desktop-entry metadata remains permanently exposed beside the launch task. Fix: Place technical metadata behind a details disclosure while retaining launch actions. Evidence: launcher/launcher-apps.png; launcher/shell-launcher.png - [p11 major gpt] No results leave an empty desktop-entry card and disabled launch controls instead of a coherent search-empty state. Fix: Replace the detail column with no matching apps and a clear-search action. Evidence: launcher/launcher-no-matches.png; features/launcher/LauncherPanel.qml:437–522 ## media - [p10 minor opus] Every transport click, seek and player switch made inside the open media popup also raises a 'Media' OSD with raw text such as 'seek 72', echoing what is already on screen. Fix: Trigger the media OSD only for hardware or shortcut media keys, never for actions taken in the media panel. Evidence: Media.qml:285,300,310 osd(name) / osd(`seek ${position}`) / osd(`select ${id}`) ## noko - [p2 major opus] The primary task, capture, sits below a diagnostics block that only matters when something is missing, and its button looks like plain text. Fix: Lead with a primary 'start capture' button and collapse the setup checks behind a disclosure that opens automatically only when an asset is missing. Evidence: noko-open.png: setup block with five '· ok' pills and 'up to date' badge precedes capture; 'start capture' is a ghost button - [p3 minor opus] Accent colour and badges are spent on routine all-ok status. Fix: Render healthy checks as neutral text, or hide them, and keep tint for missing or outdated items only. Evidence: noko-open.png accent-tinted '✓ voice detector · ok' pills and '● up to date' badge - [p4 minor opus] The subtitle repeats the title's state, and labels such as 'local runtime · ok' are jargon. Fix: Drop the subtitle when ready and use plain words such as 'speech model', 'microphone', 'typing into apps'. Evidence: noko-open.png title 'noko ready' with subtitle 'local speech ready' - [p15 major opus] Two node processes are spawned every minute for the whole session, even while the popup is closed and nothing has changed. Fix: Run the doctor at startup, on popup open and after install/update, and stop the always-on 60 s poll. Evidence: Noko.qml:305-310 Timer 60000 running: true → refresh() spawns 'node noko.mjs assets-json' and 'node noko.mjs doctor' - [p2 major gpt] Ready-state setup diagnostics dominate the surface before its primary recording action. Fix: Lead with capture and collapse healthy setup details behind disclosure. Evidence: noko/noko-open.png - [p8 blocker gpt] Waveform timers keep changing geometry in low-power mode because only interpolation duration is disabled. Fix: Stop waveform ticks in low-power mode and render a static capture or transcription indicator. Evidence: features/noko/NokoFocusOverlay.qml:18–22,63–76; features/noko/NokoPanel.qml:66–70 ## system - [p4 blocker opus] The agent action is labelled with joke text. Fix: Label it with a verb such as 'diagnose' and keep the robot icon plus the existing tooltip. Evidence: system-populated.png, system-incidents.png button 'arrrgh' (SystemIssueRow.qml:105) - [p1 major opus] Failed services and other incidents are discovered only after the user opens the popup, so the bar can never flag them. Fix: Run a cheap failed-unit check on a slow cadence and drive a warning dot on the system chip from its result. Evidence: Resources.qml:250-256,878 issue detection (systemctl --failed etc.) runs only while popoutOpen; Registry.qml system entry has no barActive - [p2 major opus] Static identity facts lead the popup, while the actionable problems are pushed down and partly scrolled away. Fix: Put 'needs attention' first and move machine identity behind a disclosure below the live meters. Evidence: system-populated.png: 'machine' identity card (hostname, kernel, packages) and 'live' meters lead; 'needs attention' sits below the fold in system-incidents.png - [p3 minor opus] Meter colours are decorative per metric, and red marks a normal temperature as if it were an error. Fix: Use one neutral or accent fill for all meters and switch to warning or error colour only past a threshold. Evidence: system-populated.png temp meter red at 52°C; cpu, net and disk meters each in a different accent - [p5 minor opus] A count of zero is shown next to a sentence saying the history is unavailable, which contradicts it. Fix: Hide the count when history is unavailable and say why, e.g. 'crash log unreadable · needs journal access'. Evidence: system-all-clear.png 'incident history · 0 recorded' above 'incident history unavailable or incomplete' - [p13 major opus] The live card layout truncates values and crushes the sparklines, although free space is available. Fix: Lay out each metric row as label, value, meter and sparkline with the value column sized to content and the sparkline filling the remaining width. Evidence: system-populated.png: sparkline column squeezed against the card's right edge at x≈985; net '↑ 512 ...' and disk 'W 1.0 Ki...' elided while a ~170 px gap stays empty - [p15 minor opus] /proc and /sys are sampled every 2 s for the whole session although nothing visible uses most of the data while the popup is closed. Fix: Keep the always-on loop limited to what the bar or backdrop actually shows and sample the rest only while the popup is open. Evidence: Resources.qml:863-870 fastTimer 2000 ms running: true - [p1 blocker gpt] The system chip remains neutral while the panel reports a current failed service. Fix: Bind chip attention to existing current-problem severity, excluding historical incidents. Evidence: system/system-populated.png; Registry.qml:209–226 - [p2 major gpt] Machine identity and live metrics precede current problems and push recovery actions down the surface. Fix: Lead with current problems and disclose identity and detailed metrics beneath them. Evidence: system/system-populated.png; system/system-incidents.png - [p4 major gpt] The recovery action is labelled arrrgh, obscuring its purpose with a joke. Fix: Rename the action diagnose with a tooltip explaining its agent handoff. Evidence: system/system-agent-unavailable.png - [p15 major gpt] Detailed metric sampling and history-ring updates continue every two seconds while the popup is closed, beyond the neutral chip's needs. Fix: Separate genuinely visible-consumer sampling from panel-only metrics and suspend unused history work. Evidence: features/system/Resources.qml:172–247,863–870; Registry.qml:209–226 ## clipboard - [p5 major opus] A pending paste shows no wording or scope, so it looks like a disabled control rather than work in progress. Fix: While pending, change the button label to 'pasting…' and show the target app in a meta line, and reset it when the paste finishes or fails. Evidence: clipboard-paste-pending.png: only a dimmed 'paste' button - [p1 minor opus] Paused clipboard capture is invisible from the bar, so the user can forget that history is not being recorded. Fix: Set barActive on the clip chip while private mode is on and add a meta line 'capture paused' under the search field. Evidence: clipboard-private.png: private mode shown only by an eye-slash icon inside the popup; 'clip' chip unchanged ## vault - [p5 minor opus] The list misstates the next step when the vault is not configured yet. Fix: In needs-setup state, make the list read 'set up the vault to search'. Evidence: shell-vault.png: list says 'unlock to search vault' while the detail pane shows 'configure vault' and status says 'needs setup' - [p12 minor opus] The favourite icon reads as a broken or partial glyph and does not match its neighbours. Fix: Use the same Nerd Font star outline/filled pair as the list's favourite mark, at the shared icon-button size. Evidence: vault-unlocked.png first detail action renders as a half-star glyph next to the sync and lock icons - [p11 minor gpt] Zero search results leave the detail pane instructing the user to select an item that does not exist. Fix: Replace the detail pane with a no-results explanation and clear-search action. Evidence: vault/vault-empty.png ## audio - [p11 minor opus] The no-device state gives no cause or next step and leaves most of the popup blank. Fix: When both lists are empty, show one sentence such as 'audio service not running' or 'no devices found' with a retry action, and let the popup shrink to fit. Evidence: shell-audio.png: 'no output devices' and 'no input devices' in a 520 px tall empty panel ## brightness - [p15 blocker opus] A sensor presence probe process is spawned every 5 s for the whole session, even with the popup closed and adaptive mode off. Fix: Detect the sensor through a udev/hotplug watch or probe only on popup open and while adaptive mode is enabled. Evidence: Registry.qml:83 AmbientLight monitoring: true; AmbientLight.qml:169-174 Timer 5000 ms → presenceProbe process - [p4 major opus] Acronyms and raw sensor units ('ddc', 'counts') stand where plain words exist. Fix: Say 'monitor control', 'set up monitor control', 'not controllable' and show light level as 'dim' without raw counts. Evidence: brightness-docked.png 'ddc?', 'setup ddc'; brightness-setup-needed.png 'ddc unavaila…'; brightness-adaptive-ready.png 'dim · 50 counts' - [p2 minor opus] Completed setup steps and a duplicate slider crowd the brightness task. Fix: Collapse finished setup steps into one 'monitor control ready' line and hide the global slider when only one display exists. Evidence: brightness-ready-expanded.png seven 'preflight: done … ready: done' lines; brightness-live.png global slider plus an identical per-display slider - [p3 minor opus] A status is painted as the primary action, so the strongest accent goes to something that needs no action. Fix: Render ready status as neutral meta text and reserve the primary button for 'set up monitor control' when setup is actually needed. Evidence: brightness-adaptive-ready.png 'ddc ready' rendered as a filled primary accent button - [p11 minor opus] The unavailable state gives neither a reason nor a next step. Fix: Add a sentence such as 'this display does not accept brightness changes' and hide the disabled setup button. Evidence: brightness-unavailable.png disabled 'setup ddc' and yellow 'unavailable' - [p12 minor opus] The same preset controls look different depending on mode, and unlabeled they cannot be told apart. Fix: Always show the preset labels under the icons. Evidence: brightness-live.png four icon-only preset buttons with near-identical sun glyphs; brightness-adaptive-ready.png the same buttons with labels 'dark/dim/bright/sunlight' - [p13 major opus] Display names and the status word are both truncated while the row's slider area sits empty. Fix: When a display has no slider, give the name and status the full row width and wrap the status onto a second meta line if needed. Evidence: brightness-setup-needed.png 'working monit…' and 'ddc unavaila…'; brightness-docked.png 'hdmi-a-1 · ext…' - [p2 major gpt] An already-complete setup remains the primary coloured action above brightness adjustment. Fix: Make completed setup a neutral secondary disclosure below the adjustment controls. Evidence: brightness/brightness-adaptive-ready.png; features/brightness/BrightnessPanel.qml:153–165 - [p4 minor gpt] Setup and unavailable states rely on ddc terminology and the ambiguous label ddc?. Fix: Use monitor setup and a specific setup-needed explanation, keeping protocol details secondary. Evidence: brightness/brightness-docked.png; brightness/shell-brightness.png - [p9 major gpt] Threshold drafts and editor expansion live only in the disposable panel and have no retained state. Fix: Retain threshold drafts and expanded bucket across popup dismissal and switching. Evidence: features/brightness/BrightnessPanel.qml:25–28,43–51; Registry.qml:286–302 - [p11 major gpt] Unavailable displays have only a status word and a disabled setup button, with no explanation or recovery guidance. Fix: Show why control is unavailable and the applicable reconnect, setup, or retry step. Evidence: brightness/brightness-unavailable.png - [p15 blocker gpt] Sensor discovery launches a helper every five seconds regardless of popup visibility or adaptive-mode use, although the brightness chip shows none of that state. Fix: Gate discovery on visible brightness UI or an enabled adaptive session. Evidence: Registry.qml:81–84; features/brightness/AmbientLight.qml:169–181 ## connectivity - [p11 blocker opus] An empty table header is shown with no sentence when there are no Bluetooth devices or the adapter is off. Fix: Hide the headers when there are no rows and show 'bluetooth off · turn on to find devices' or 'no devices · scan' instead. Evidence: connectivity-open.png, shell-connectivity.png bluetooth 'device trust state battery actions' headers with no rows - [p5 major opus] The panel says the hardware is missing while the controls claim it is on and scannable, and the connected network is not marked. Fix: Disable the wireless toggle and scan when no device exists, and mark the connected network with a 'connected' label. Evidence: shell-connectivity.png red 'no wireless device' above a wireless toggle showing 'on' and an enabled 'scan' - [p4 minor opus] Raw security and signal jargon is shown, and 'on'/'off' toggles are ambiguous between state and action. Fix: Show 'secured · strong signal' and label the toggles with the noun plus a checked state (e.g. 'wi-fi', 'bluetooth'). Evidence: connectivity-masked-update.png 'wpa · -48 dBm'; toggles labelled 'on'/'off' - [p4 minor gpt] Connection details expose wpa and dBm without a plain-language interpretation. Fix: Lead with secured and a human signal-strength label, retaining technical values behind disclosure. Evidence: connectivity/connectivity-masked-update.png - [p5 major gpt] Several failures collapse to network action failed or bluetooth action failed without a specific problem or next step. Fix: Map failure states to safe, specific explanations with the applicable retry or setup action. Evidence: features/connectivity/ConnectivityPanel.qml:107–129 - [p11 blocker gpt] The empty Bluetooth region displays table headers over a blank area, including while Bluetooth is off. Fix: Hide empty headers and show an off, unavailable, or no-devices state with the appropriate enable or scan action. Evidence: connectivity/connectivity-open.png; connectivity/shell-connectivity.png ## notifications - [p7 blocker opus] Dismissing a single notification is possible only after hovering, which the rule explicitly forbids. Fix: Keep the close button visible at reduced emphasis (ghost, minor colour) and only raise its contrast on hover or focus. Evidence: NotificationCard.qml:232 close button opacity: cardHover.hovered || activeFocus ? 1 : 0; notifications-history.png shows no close control - [p4 major opus] An acronym labels the do-not-disturb toggle. Fix: Label the toggle 'quiet' or 'do not disturb' as a checked noun toggle. Evidence: notifications-history.png, notifications-empty.png button 'dnd' - [p3 minor opus] Every normal notification gets the accent tint, so accent no longer means anything special. Fix: Render normal cards neutral and reserve tint for critical (error) and unread emphasis. Evidence: NotificationCard.qml:56 active: urgency === 'normal'; notifications-history.png accent-tinted card - [p4 minor gpt] The interruption toggle exposes the unexplained acronym dnd. Fix: Label the toggle quiet mode with a concise explanatory tooltip. Evidence: notifications/notifications-empty.png; features/notifications/NotificationGroup.qml:60 - [p7 blocker gpt] The individual dismissal action is invisible until hover or keyboard focus. Fix: Keep its close control visible at rest. Evidence: notifications/notifications-history.png; features/notifications/NotificationCard.qml:221–233 ## tray - [p11 minor opus] An item without an icon leaves an empty hole instead of a designed fallback. Fix: Show a generic app glyph whenever the tray icon cannot be resolved. Evidence: tray-populated.png blank space left of 'fixture tray' where the item icon belongs - [p12 minor opus] The same attention state is accent-coloured in the bar and warning-coloured in the panel. Fix: Set the tray entry's barRole to 'warning' while attentionCount > 0 so the chip matches the panel. Evidence: tray-populated.png accent dot on 'tray 1' chip vs warning-tinted 'needs attention' card ## osd - [p4 blocker opus] OSD labels are capitalised, which breaks the house lowercase law. Fix: Lowercase every displayLabel ('volume', 'microphone', 'brightness', 'media', 'screenshot', 'color', 'error') and the 'OSD' fallback. Evidence: osd-volume-meter.png 'Volume', osd-microphone-muted.png 'Microphone', osd-long-message.png 'Error' (osd.js:66-75) - [p12 major opus] When the system icon theme lacks a name, the OSD shows an empty square where its icon should be. Fix: Fall back to a Nerd Font glyph per event when iconPath returns empty, as the rest of the shell does. Evidence: osd-volume-meter.png, osd-brightness-retrigger.png, osd-microphone-muted.png empty tinted icon tiles (OsdPanel.qml:62-77 Quickshell.iconPath with no fallback) - [p13 major opus] The error body is cut at two lines, so the cause is lost. Fix: Let the error body wrap to its full length within the card (or shorten the message at its source) instead of eliding. Evidence: osd-long-message.png 'screenshot failed: the output disappeared while the capture wa…' - [p4 minor gpt] Owned OSD labels use capitals despite the lowercase house rule. Fix: Lowercase the display-label strings. Evidence: osd/osd-volume-meter.png; features/osd/osd.js:65–74 - [p12 major gpt] Several OSDs render an empty icon tile when theme-icon resolution fails. Fix: Provide a verified local glyph fallback for every supported event. Evidence: osd/osd-volume-meter.png; osd/osd-microphone-muted.png; features/osd/OsdPanel.qml:27,65–73 - [p13 major gpt] The error explanation elides before its cause can be read. Fix: Preserve the complete explanation in persistent notification history while keeping the OSD summary compact. Evidence: osd/osd-long-message.png; features/osd/OsdPanel.qml:135–144 ## privilege - [p5 major opus] After submitting, the field empties and nothing says the password is being checked, so slow PAM failures look like nothing happened. Fix: While the request is in flight, disable the field and show 'checking…' on the authorize button. Evidence: PrivilegeSurface.qml:276-289,365-368 submitSecret then text = '' with no pending label; no 'checking' state in any screenshot - [p5 major gpt] Submitting sets awaitingCompletion, but the prompt shows neither pending feedback nor a disabled authorization action. Fix: Show an authorizing state and disable repeated submission until the response arrives. Evidence: Privilege.qml:85–102; PrivilegeSurface.qml:341–378 - [p14 minor gpt] The focused password placeholder fades to 42% opacity against the input background, reducing text contrast below 4.5:1. Fix: Use an opaque placeholder colour meeting 4.5:1 against the input background. Evidence: privilege/privilege-initial.png; PrivilegeSurface.qml:248–256 ## screenshots - [p5 minor opus] Captures that niri never confirmed as saved are tracked internally but never shown to the user. Fix: After a short timeout, surface an unconfirmed capture as a single error OSD or toast saying the screenshot may not have been saved. Evidence: Screenshots.qml:73-75 'Pending means unconfirmed'; niri-unconfirmed-history.png shows 'unconfirmed: 3' only in the test fixture ## shared - [p12 major opus] There is no spacing or radius scale in the theme, so each control hardcodes its own values and surfaces at the same level drift apart. Fix: Add spacing and radius tokens (e.g. radius.control/card/surface, spacing 4/8/12/16) to Theme.qml and route shared Popup*.qml controls through them first. Evidence: Theme.qml (colours only); radii 8 PopupButton, 9 BarChip, 10/12 NotificationCard, 11 workspace tray, 14 OSD, 16 privilege field - [p7 major opus] Shared slider and small icon buttons fall below the 24×24 px target minimum. Fix: Raise PopupSlider's implicitHeight to 24 and enforce a 24 px minimum on PopupButton. Evidence: PopupSlider.qml:46 implicitHeight 20; NotificationCard.qml copy button 26×22 - [p7 minor opus] Text buttons repeat their own label as a tooltip, and hover plus focus tooltips stack over neighbouring controls. Fix: Default tooltip to empty when showText is true and the label is visible, and show at most one tooltip at a time. Evidence: noko-history.png two tooltips at once ('start capture', 'copy'); audio-keyboard-scroll.png tooltip covering the next row's slider; PopupButton.qml:10 tooltip defaults to the visible label - [p6 major gpt] The shared bar StateLayer accepts keyboard focus but renders no focus-specific indication. Fix: Add a visible contrast-checked focus ring to the shared StateLayer. Evidence: Bar.qml:405–505 - [p7 blocker gpt] Shared sliders have a 20 px-high hit area, below the required 24 px minimum. Fix: Increase the slider input frame to at least 24 px without changing its visual track or value mapping. Evidence: PopupSlider.qml:58–59; features/audio/AudioPanel.qml:157–169 - [p12 major gpt] Icon-only shared buttons inherit 14 px icons instead of the specified 20–24 px role size. Fix: Default icon-only buttons to 20 px and inline icons to 16 px. Evidence: PopupButton.qml:17,135–154; tray/tray-populated.png; vault/vault-unlocked.png ## power - [p6 major gpt] The three-column action grid supports Tab activation but implements no directional navigation. Fix: Add row-aware arrow navigation without activating or arming actions on movement. Evidence: features/power/PowerPanel.qml:265–325; PopupButton.qml:76–117