Windows

Command palette — ⌘K

Top-anchored launcher. A search Input header, a scrollable MenuItem list with the first row pre-highlighted, and a monospace hint footer. The fastest path to any command — every action should be reachable here.

Search field ground — normal · focused (2026-10-27)

The palette shell is --tasty-surface-raised, so its search field is an Input ground="raised" (the 10-14 rule, no exception). The box steps down to bg-panel with a border-strong edge, so it reads against the shell before it takes focus. The field opens focused (autoFocus); normal is the box after focus moves away. Width, icon, placeholder, list and footer are unchanged; no copy changes.

Listening ports — the Table popup

Tools › Listening ports. A 660×520 modal built directly on the Table component — the canonical example of a data-table surface. Header carries a live filter + refresh; a Show all checkbox toggles between Tasty-owned and system-wide ports; the scan state shows a Spinner. Rows are sortable; the State column renders a StatusDot.

Favorites — star toggle, pinned section, NONE badge

Port favorites are keyed by (addr, port) — never the PID, which changes on every restart. A tight 28px leading column in the table carries the star (outline = unregistered, gold starFill = registered, same pair the Explorer sidebar uses); clicking it registers or unregisters immediately, with no confirm step. This is the only writing control in an otherwise read-only popup. A Favorites section sits between the filter row and the table and lists every favorite regardless of the search box, the scope checkbox and the sort — and it always judges LISTEN/NONE against the full system scan, so a favorite that Tasty doesn't own still reads LISTEN. A favorite whose port is not in the scan gets the NONE badge: StatusDot idle, muted, no pulse — apart from LISTEN (green + pulse) and other states (yellow). Stars can be toggled from either region.

Process column — a minimum, not a fixed width (on Table, 2026-10-08)

Drawn on the shared Table with the popup's own columns (star · Port · Proto · Address · Process · Workspace · State), so header, row height, fonts and padding are the popup's. The Process column has a floor, --tasty-port-process-col-min-width (200), passed as the Table column's minWidth: it takes spare width and never shrinks below the floor. A column's width is also its floor, so the fixed columns never shrink. Address is fixed at its floor --tasty-port-addr-col-min-width (140, fits 255.255.255.255 and :: forms; IPv6 ellipsises). Process takes all the spare width; Address never grows (2026-10-08). The sum is the popup's column budget. At the popup's own 660 the budget is a little wider, so the table body scrolls horizontally, the existing scroll policy of the popup. No column shrinks away or hides. Process text ellipsises inside its cell; the PID Tag stays visible.

Remote connections — profiles + passkeys

Tools › Remote connections. A 520×460 modal with three top tabs: a type-agnostic remote-profile store (ssh / smb / http / anything), an Attach store (tasty-attach targets), and a separate Passkey credential store. Each tab routes list → form → confirm-delete off a shared header. SSH profiles get a dedicated form; everything else uses a generic key-value editor. The Profiles add-bar carries a protocol filter (right) — a dropdown of the protocols present, checkbox-toggled with Select all / Deselect all / Reset, committed on Apply. Secrets live only in passkeys, referenced by name.

Passkeys tab — rows, reveal, unknown kind (2026-10-06)

The third tab, same 520-wide frame. Each row: name (600) + kind Tag — or the warning badge when the stored kind is unknown — then a mono line kind · value, masked until revealed. Actions on the right: reveal, edit, delete (trash, as on the other two tabs), IconButton sm. Revealed = IconButton active and the glyph swaps eye → eyeOff. The value line ellipsizes, revealed or not; the action cluster is flex: none and is never pushed out of the row.

Attach tab — tasty-attach targets

The middle tab. An Attach holds everything needed to attach to a remote tasty instance — it either references an ssh profile (→ prod-web) or carries inline ssh info, plus a remote tasty executable path and a port discovery mode. Splitting this off the ssh profile keeps ssh profiles pure connection info. Rows show name + (label), the reference/host summary, remote-tasty + port-mode captions, and an inactive badge when the referenced profile or inline shell isn't reachable.

Attach form — reference vs. inline

The add/edit route on the Attach tab, on the shared [--tasty-remote-label-col · 1fr] grid. A Connection segmented toggle switches between SSH profile (an ssh_ref dropdown of existing ssh profiles) and Direct (inline) (the ssh profile fieldset — host / user / port / shell / passkey). Both share a Remote tasty group: Executable (default tasty), Port mode (auto / subcommand / file-unix / file-windows), and an optional Port file that overrides the mode.

Profile form — SSH (the [112px · 1fr] row grid)

The add/edit route inside the popup. Every row is the same grid: a fixed 112px right-aligned label + a 1fr control (columnGap 12, rowGap 8) so labels never collapse/truncate and all controls share one left edge. SSH gets the dedicated fields (Type · Name · Host · User · Port · Label · Shell + hint · Passkey) — remote_tasty moved to the Attach tab. Body scrolls; the footer is pinned with a full-width separator and right-aligned Cancel (ghost) / Save (primary). Right: the same form with a validation error.

Generic & Passkey forms · badges

A non-ssh Type swaps the SSH grid for a generic key-value editor (Type · Name · FIELDS rows `[112 · 1fr · 28]` + Add field · Passkey), with a peach Unknown type badge when the type isn't registered (still saves). The Passkey tab's form has Name · Kind (path / inline segmented) · Value — singleline path vs. 3-row multiline secret — plus the local-only note.

Segmented active is an accent fill — tab strips keep the underline

Two components were drifting into one another. A tab strip (the window's Profiles / Attach / Passkeys bar) marks the current tab with a 2px accent underline and a weight change, no fill. A segmented control (the attach form's profile / inline switch, the clipboard type segment, the apply-preset scope) marks the active segment with an accent-primary fill and --tasty-text-on-accent ink. --tasty-surface-active is the row-selection fill and is not used by either — that was the gallery's bug, now fixed.

From ssh config — a second, subordinate list

Hosts parsed out of ~/.ssh/config sit below the profiles, in the same scroll — it is the same question (“which machine?”), and a separate tab would hide the answer. Everything about the section says one tier down: a section header instead of a card, the source path in mono so the origin is unambiguous, two lines per row instead of the profile row's three, secondary ink on the alias, and no per-row icon buttons — one ghost Add profile, which is the import action that already exists. An already-imported host shows a muted in profiles Tag and no action, so importing twice is not offered.

Two-pane remote-workspace picker — 4 states

Sidebar workspaces-header / new-workspace(+) right click → Add remote workspace. A 680×460 modal in the remote_tool language (Scrim · content-drawn header · --tasty-bg-panel frame). It consumes the tasty-attach profiles registered on remote_tool's Attach tab — it never edits them. Left (240px): the attach-profile list, single select, with an inactive badge on profiles whose last detection failed. Right: the selected profile's remote workspaces. Footer: Connect (primary, enabled only when a selectable remote workspace is chosen) · Cancel (ghost, always enabled — closes, aborting any in-flight connect).

Right-pane states — initial · connecting · error · empty

The three non-list states, plus the empty remote (plan B: the list path with the pre-selected “+ New workspace” row), driven by the left selection. Each is a centered column (glyph → title → one muted line), so the pane never looks broken while a connect is pending or failed.

“+ New workspace” row — the escape from a dead-end remote

The first row of the loaded list opens the other path: instead of mirroring a workspace the remote already has, create one there and mirror that. It is deliberately a row in the list, not a button or a second tab — so it inherits the list's select-then-confirm contract: clicking selects, the footer confirms (§6-5). No name or cwd is ever asked for; the remote's defaults are used, which the row's tooltip states outright.

New-workspace row — rest · hover · selected · creating · failed

All five row states at pane width (440px), each with the first real ws row beneath so the shared alignment line is visible. Creating swaps the glyph for a 14px Spinner and the label for “Creating workspace…” (§6-3: inline, not a full-pane takeover — the user keeps the list they were reading, and the roundtrip is seconds, not minutes). Failed keeps the row and hangs the remote's own message under it with a Try again button (§6-4), clamped to 3 lines with the full text in title.

Empty remote — plan A (center-state + CTA) vs plan B (list path)

§6-1, the decision that sets the implementation's render branch. Before this change a reachable-but-empty remote ended at a center-state with nothing but Cancel. Plan A keeps that center-state and adds a CTA button. Plan B takes the list path even when empty: caps header + the one “+ New workspace” row, with a muted line explaining why nothing follows it.

Decisions — the eight open questions, resolved

What was chosen and why. This is the implementation spec.

Native file picker — local & remote, one component

Tasty's own Open file dialog, replacing the OS-native picker so it can browse a remote attach host over the same SSH mechanism as attach — the OS picker only ever sees the local disk. It's a select-and-confirm dialog (pick a path, hand it back, close), not the Explorer surface (that's a free-roam tab). A 640×480 modal in the remote_tool popup language: Scrim · content-drawn header · --tasty-bg-panel frame. Local and remote are the same component — they differ only in the header host indicator and the breadcrumb root. Rows reuse the folder/file list language; folder double-click descends, file click fills the name field, file double-click = Open.

Remote indicator — three candidates

§6.1 open decision: how to signal "this dialog is looking at a remote host, not your local disk," clearly but not loudly. Three candidates on the same --tasty-accent-info axis. Badge (recommended): a mono user@host chip beside the title — explicit about which host, reuses the attach/remote visual language. Glyph + host: swap the header icon to remote and print the host inline — lighter, no chip. Border: tint the whole frame edge + a 2px top strip — unmissable but the heaviest; use only if remote/local confusion is a real hazard.

States — loading · empty · permission · connection lost · multi-select

The body region swaps between list and status states without changing the frame. Loading: Spinner while the directory reads (remote adds "over SSH"). Empty: muted folderOpen + "This folder is empty." Permission denied (local) and Remote connection lost share the layout — danger glyph · title · one reason line · action — but differ in copy and action (Retry vs. Reconnect, which resumes from the last folder). Multi-select (§6.2): a checkbox column, a comma-joined name field, and an N selected count — spec'd for the future, single-select is the default.

Save mode — one confirm, in the footer

The same picker, asked to produce a path instead of read one (Settings → Export, and every future save target — rfd blocks the calling thread, so no OS dialog). There is exactly one confirm control, and it is the footer's primary button — the File name row the picker already owns becomes editable and the button reads Save. No second row is appended below the view, because a second button would point at a second target and the screen could hold two answers at once.

One target. Selecting a list row does not confirm anything — it writes that row's name into the input, and the input is the only thing the button reads. Typing after a pick keeps the row selected only while the name still matches; edit a character and the selection clears. So "the picked file" and "the typed name" are never two different paths.

Overwrite is inline, not a second dialog. When the typed name already exists in this folder, a warning line appears above the buttons and the primary relabels to Overwrite — the decision stays on the button the user is already reaching for. A modal confirm on top of a modal picker would be a second scrim for a reversible write.

Gestures & folder targets — the six open branches

The save-mode decision left six branches undecided, and because save and open are the same view, each answer had to hold in both modes. One gesture table now covers them: single click selects, double click descends — in both modes, for both kinds. A folder is never a save target: the footer button still reads the input only, so a selected folder can't change what gets written; a muted line says so where the reading happens. In save mode a file's double-click stops at select — it writes the name, which is the overwrite state, and the warning line has to be readable before the write. Only open mode confirms on a file's double-click.

Path bar — what gives way when the folded path still doesn't fit

Folding the middle (root › … › parent › current) is not always enough: at 400px with 53-character folder names the current folder used to be clipped without an ellipsis. The bar now allocates the width it actually has — the path bar minus the Up and Refresh buttons and their gaps, never the popup width — in a fixed priority order: current folder → parent → root → the … menu. Five steps, each taken only when the one before it has hit its floor.

File-type filter chip — a read-only readout (2026-10-06)

The chip shows the filter the caller passed and nothing else: there is no menu and no way to change it, so it is drawn as a readout, not a control — no chevron, no fill, no hover, not focusable. Text is the extension list in mono (*.toml, *.json), lowercase, in the caller's order. No filter → no chip; the name field takes the width. Width is the content, capped at --tasty-fp-filter-max-width; past that the list ends in an ellipsis and the tooltip ("Showing …") carries all of it. Both consumers (Tools menu picker, the picker inside Settings) and both modes show the same chip. In save mode the filter does not touch the name field — no extension is appended.

Folder mode — mode="folder" returns a folder (2026-10-21)

The third mode of the same frame, for the three callers that used the OS folder dialog (Settings › Remote transfer › Save folder, Plugins › Add › Find folder…, Preset editor dir). Local only. The target is the selected folder row, or the current folder when nothing is selected, so Select folder is enabled whenever the folder reads (also when it is empty) and disabled while loading or on an error. The footer swaps the File name input for a read-only Folder readout of the full target path (front ellipsis, tooltip = full path) and one muted hint line. Files stay listed so the folder is recognisable, but they are inert: disabled ink, no hover, skipped by ↑↓, tooltip "Only folders can be selected." The filter chip is hidden: filters don't apply to folders. Not the same thing as folderSel above, which is a folder row in open / save mode.

PresetView — list → toolbar + live preview

The modeless window behind Tools › Presets. L1 tabs pick the scope (Workspace / Tab / Pane); a left list of saved presets for that scope feeds a right detail = a toolbar (rename · duplicate · delete · Edit) over a live demo-layout preview. The selected row uses the surface-fill + 2px accent left-bar (the file-handler / sidebar idiom). Click a preset, switch its mini tabs, then hit Edit — structure edits happen on the preview, a leaf's gear opens its settings screen in this same column.

Demo-layout preview — the new component

An interactive miniature of a preset's tree — not a screenshot. It draws the three structural levels with distinct visual weights: pane split (upper layout) as separate bordered cards with a wide app-bg gap; tab strip as a mini 20px row whose active tab carries the accent bar; surface split (lower layout) as a thin hairline; and each surface leaf as its kind plus a summary of its configured fields (cwd / startup / file / url) so same-kind leaves are told apart. Mini tabs are live — click one to swap that pane's surface layout.

WYSIWYG edit mode — direct manipulation of STRUCTURE

The Edit button turns the same preview editable in place with the manipulation grammar of a real tasty pane — for structure. Split by edge: hover a surface's ~30% edge band (left / right / top / bottom) to preview a split there, then click to add a new surface on that side. Click the center of a surface to select it — a 2px accent outline plus two handles: settings (gear) and remove. The gear, or a double-click, opens the surface settings screen (next spec) for that leaf's parameters; the selection stays the target of the structure shortcuts, which is why a single click never leaves the preview (decision A1). Tabs: the mini strip gets a trailing + add-tab and a hover/active close × per tab (hidden on the last remaining tab). Structure changes save automatically. Try it below — edge-split, tab add/close, delete, and the gear all work.

Surface settings screen — parameters as a draft

Editing a leaf's parameters (kind · cwd · startup · whatever the kind declares) used to open a form inside the leaf cell, which clipped in the six-surface workspace (the input and startup command fell outside the box). Now the settings screen takes over the whole detail column — toolbar and preview — as three stacked boxes: a header (kind icon in its accent + kind name · mono breadcrumb preset › pane N › tab › surface k · an unsaved dot once the draft differs), a scrolling body (one-column form, label over full-width input, capped at 460px; Kind first, then the kind's fields — changing Kind swaps the fields in place, keeping keys both kinds share), and a fixed footer (1px rule, right-aligned Cancel ghost · OK primary — the Settings-window footer grammar; product labels 취소 / 확인 via button.cancel / button.ok). The screen is a draft: OK applies the whole surface at once and auto-saves, Cancel discards. OK is disabled until something changed (decision E). While it is open the left list and L1 scope tabs dim and ignore input (decision C) — leaving would silently drop the draft; an outside selection change (context-menu “save as preset”, window close) drops it like Cancel, without a prompt. Save failure: the screen and draft stay put, the error goes to a toast. Try a frame: change Kind, hit Esc / Enter.

Settings — two-tier navigation

The largest dialog. L1 = a small, fixed set of top tabs (General / Appearance / Keybindings / Plugins). L2 = a growable, filterable left sidebar of sections (plugins contribute here). This split keeps top-level navigation stable while the content tree scales. Reuse it for any settings-like surface.

General › General — row grid, row captions, webhook row (2026-10-07 · grid 2026-10-08)

Every settings subtab uses one label column · control grid. Label column = the subtab's longest label, clamped to --tasty-settings-label-width (150) … --tasty-settings-label-max-width (240); a label longer than 240 wraps. Gap 16 (--tasty-settings-label-gap). The app's own fit-to-longest measure is canonical with this clamp; the old 12 gap moves to 16. A description that belongs to one row sits directly under that row (--tasty-settings-row-caption-gap 4), at the row's left edge, measure-md: that is where the wheel-scroll and language-restart lines go. The webhook row keeps its always-shown warning callout the same way. Terminal › TUI's OSC 52 row follows the same rule (on the grid, callout measure-md).

Keybindings › Plugins — plugin picker + per-command mode (2026-10-08)interactive

Pick a plugin, then edit each of its commands on one control line: mode Select (Inherit / Custom / None) · slot (inherit-source Select, key Input, or “(Unassigned)”) · Reset. Rides the settings Row grid (title column 150 + gap 16, so the picker and every mode Select start at the same x), not the 288 Import/Export column: 288 + the line overflows the 620 cap. Every control on a line is 28 (md) — Select, Input and the ghost Reset alike. Titles wrap inside the column, never ellipsise. Inherit adds a caption under the line with the resolved key; a Custom value that fails to parse turns the Input invalid and adds an error caption. An unsaved change shows a 6px accent dot after the title. Reset is disabled when there is no override. Save / Cancel stay in the window footer.

Keybindings › Plugins — Custom = record slots (2026-10-10 b12)

Custom now records, using the same record slot as the other subtabs (one slot per key, then +, or a None slot), with two local changes so the line keeps one control height: slots here are --tasty-kb-plugin-record-height 28, like the mode Select and Reset. Slots are one group (space-xs 4 between them); the group's ends keep the line's 8. The slot column is no longer a fixed 200 box: one key is 140 + 4 + 32 = 176, more keys push Reset right. When the line runs out of width it wraps as one flow: the next line starts at the mode Select x (the same control x where other subtabs wrap), and Reset stays the last item. Every key is shown; the single-button sample is retired. The Esc hint sits under the subtab as on the other subtabs.

General › Overlay — toast duration

The General L1 tab gains a fourth L2 section, Overlay (after General / Notifications / Accessibility) — the umbrella term for Toast / Banner / Modifier-hint / Marker overlays. It ships with one row: Toast duration, a mono number field (the Numbers in settings shape — DragValue retired 2026-10-07) that controls how long a toast stays before auto-dismissing (today hardcoded at 2000ms). Exposed in seconds (matches the user's mental model), stored as ms. Same Grid (label + control) and hint-text pattern as the other General sections — no new interaction invented.

Settings · General › Remote transfer — 5th L2 subtab

The General L1 tab gains a fifth L2 section, Remote transfer (after Overlay) — the umbrella for the remote (mirror) file-transfer channel, following the Overlay-subtab precedent: a topical L2 with room to grow rather than rows crammed into General. Two rows edit RemoteTransferSettings: Save folder — a mono path Input + a Browse… secondary button (opens the native folder picker, same pairing as the Scripts file row) — and Maximum size — a numeric Input with a mono MiB unit suffix. Each row keeps the settings-row grid (150px label · control), a muted description line beneath, and a separator between rows.

Settings · Misc › Task pipeline — Report limits (2026-10-09)

A new Misc L2 subtab Task pipeline (after Scripts, before Tastyrc on Windows). The content column is one mono micro uppercase heading, REPORT LIMITS, then two settings rows in the row grid (label column = longest label clamped 150 … 240, gap 16), each a mono numeric Input (90) with the static unit B, its description caption directly under it (gap 4, measure-md), and a 1px separator between the rows. The two values are tied (note limit < attempt limit): each field's range narrows to the other's current value, so a crossed pair can't be committed. The relation stays in the description copy; the range line appears only when a value is out of range, like every numeric field. Values are raw bytes with no grouping (they are typed, and match the config file); the unit stays B.

Numbers in settings — one shape: mono Input + a static suffix

Three different numeric controls had appeared: a mono text Input with a static unit (remote transfer Maximum size · MiB), a drag number (plugin Default zoom · %), and a proposed stepper. The settled shape is the first, everywhere: a mono text Input, keyboard entry only, a static muted suffix outside the field, and clamp on commit (blur / ↵) — not while typing, so you can type 150 in a 25–200 field without the second keystroke fighting you. Out of range shows the danger border + one inline line naming the range. A drag surface inside a scrolling settings pane steals the scroll and hides its own range; a stepper needs two more hit targets for a field people set once.

Settings · control metrics — shortcut rows · drag flip modifier · font combo · open Select (2026-10-09 b10 · b11)

Values that were literals in the app become tokens. Shortcut rows (Keybindings General … Scripts): the record button is the Import / Export slot size — --tasty-kb-record-width 140 × --tasty-kb-record-height 24, mono, surface-raised — and the add button is --tasty-kb-record-add-width 32 × 24; buttons in a row sit 4 apart; rows sit --tasty-kb-row-gap 8 apart with no divider (a long, scanned list — denser than the 12 of settings rows). The Explorer drag flip modifier is the last row of Keybindings › General, alone after the shortcut rows behind space-sm · separator · space-xs (b11 — the app's placement; the category switch modifier stays in Workspace and carries no caption, nor do Tab / Workspace switch modifiers). Shape: label + modifier Select (field-width-md) + caption. A combination from config.toml that is not in the list is appended at the end of the list as written. Record button, add and None slot share --tasty-kb-record-border → --tasty-kb-record-border-hover on hover (fill unchanged; Mocha “Ctrl+W” shows hover). A row with no binding shows one None slot (record width, border only, muted) that starts recording on click — no + beside it. The font search combo is the shared SearchableSelect (2026-10-19 — Components › Form controls #searchable-select); the Tab / Workspace / Category switch modifier combos are a plain Select. The font search combo list caps at --tasty-font-combo-list-max-height 300 and its search field is the list width minus --tasty-font-combo-search-inset on each side. An open Select trigger takes the existing --tasty-select-border-focus (→ border-focus), as in the components “no value” panel. Appearance › General keeps the app's order: font rows, the preview right after them (space-lg before, caption heading “Preview”), then a separator and Ligatures / Opacity.

Hook Handlers — origin decides whether a row can be removed

The registry re-seeds host and plugin defaults on every start, so a remove button on those rows promises something the system undoes. Rows now carry their origin as a Tag — host / you / the plugin in mauve — and only user rows get the trash affordance. Host and plugin rows show a lock glyph in the same slot (not a disabled button: nothing is pending) with the tooltip “Provided by host — can't be removed”. IpcSequence stays a one-line mono summary with an Edit button that opens the sequence editor; editing a multi-step sequence inline inside a settings row has nowhere to put the steps.

Hook Handlers — IpcSequence text editor (2026-10-06)

Edit expands the row inline: the one-line summary is replaced by a CodeArea (mono, line-number gutter) holding the sequence as text, one IPC call per line — method, a space, then optional one-line JSON params. A help line under the field states the format. The text is parsed on every change; the first error shows on its own line under the field (glyph + translated sentence with line / column, then the untranslated parser reason in mono muted), the line is marked in the gutter, and Apply is disabled while an error stands. Apply writes the tab draft; Settings Save commits it, Cancel in the footer reverts it, like every other row. An empty sequence is allowed with a muted note. Mod+Enter = Apply, Esc = Cancel; Enter is a newline. Adding a new IpcSequence handler from the Add card is out of scope this round.

Hook Handlers — edited default: mark + Revert (2026-10-07)

Editing (or switching off) a handler that host or a plugin registered saves a user patch under the same id; the row keeps its origin Tag and padlock. The row now says so: an edited Tag right after the origin Tag, and a Revert ghost button on the action line beside Edit. Revert follows the extension-mapping pending pattern: the summary goes back to the default, the button becomes Undo in the same slot, and the Tag reads reverts on save. Settings Save drops the patch (same effect as tasty hook-handler remove --id); Cancel restores it. Any patch counts — a changed sequence, a Switch turned off, or both — and one Revert clears all of it.

Appearance › colour rows — the Default hex is read-only, not disabled (2026-09-29)

With Default checked, a colour row has no override and its hex field cannot be edited. The field still carries the base value in use, the only text value on the row, so it is read-only, not disabled: the same neutral box as a disabled Input, with the value in --tasty-input-readonly-fg (text-secondary) instead of the disabled ink. The value can be selected and copied; the field takes focus (1px focus edge, no ring). Unchecking Default starts the override and the field becomes a normal Input. Applies to the Tasty colour rows, the terminal surface background row and the Colors group.

Appearance › Colors › Terminal-specific — 5 rows, active match ink after its fill (2026-10-12)

The theme key search_match_active_fg gets a row like every other palette field, so it can be changed without editing TOML. It goes right after search_match_active_bg: the ink sits on that fill, and reading the pair together is how a user judges it. The swatch stays the same plain swatch as every row. A text-on-fill sample would be the only row of its kind and would need the other row's value to draw; the live terminal is the real preview. Reset all clears it like any other override. The list is now 6 groups / 47 rows; Terminal-specific has 5.

Appearance › Font override — rows + preview below (2026-10-06)

The override grid uses the colour-override idiom already in Settings: label in --tasty-settings-label-width (150), the control at its own field width, then a trailing Checkbox "Use default" with its label always shown. Trailing means a long ko / ja label grows into free space instead of pushing the control. The Preview leaves the side column and sits below the grid at every window width, Focused and Unfocused side by side (they wrap under each other when narrow), then the one-line font summary. Nothing overlaps at 1100 or at the minimum width; the two-column egui split goes. A defaulted row keeps its control visible at the shared disabled look, filled with the default.

FileHandler › File Extension Mapping — order + Add (2026-09-29)

The product's structure is the design (it replaces the earlier per-extension Select). An extension Input + Add (Button secondary sm, the same pair as the capture blacklist), then per extension an ordered detector list — first match wins. Reorder with IconButton sm chevronUp / chevronDown (the ▲ ▼ text glyphs go). Arrows are disabled, not hidden: ▲ on the top row, ▼ on the last candidate, both on a row whose detector is off (muted name + disabled Tag), so rows keep one slot layout. Add is disabled while the input is empty or no detector is installed.

Row — side by side · stacked when the control doesn't fit

Below the supported minimum (a tiling WM ignoring 1100 × 700) a one-piece control can be wider than what is left beside the label. Each Row decides on its own: when its control's natural width does not fit in content − label column − gap, the label takes the full row width and the control moves under it at the row start x (not the control column), --tasty-settings-row-stack-gap 4 below. Rows whose control fits stay side by side, so a subtab can mix both. To stop flicker while resizing, a stacked row goes back only when the control fits with --tasty-settings-row-stack-hysteresis 16 to spare. Inside a stacked control the existing wraps still apply (second shortcut buttons wrap from the control x, units drop under the field). Dashed outlines are the label / control boxes.

Registered rows — two lines, no table

Both subtabs list every registered entry as a two-line row (the Hook Handlers row). Line 1 carries identity and state: id, origin Tag, prio (handlers), Switch and the trailing slot. Line 2 is one mono summary: the detector's rules, or the handler's detector → action. Seven columns do not fit the settings content width, and a table would truncate every column; two lines truncate only the id and the summary, both with the full value in a tooltip. Only user rows have Remove; host and plugin rows show the padlock.

Add card — open, empty

“Add detector” / “Add handler” (secondary sm, plus glyph, right of the intro) opens the card between the intro and the list, and is disabled while it is open. Add stays disabled until the required fields have a value (Hook Handlers rule): detector = Id; handler = Short name + Detector + the action's required field. The Saved as user/… caption shows the stored id as you type.

Add card — typing, validation errors

Format errors are checked when Add is pressed (Add was enabled: the required fields are filled). The error replaces the field's caption and stays until the field is valid again; Add stays clickable. Detector: id characters (lowercase, digits, -, ≤ 64) and the cross-field no extension and no glob line above the buttons. Handler: short name characters (≤ 32), priority not a whole number, IPC method not dotted. There is no duplicate error any more: an existing id is a patch (below). The detector Id caption is the character rule; the stored id equals the input, so there is no “Saved as” line. Handlers keep “Saved as user/<short>”.

Handler add card — action kinds

The Action Select swaps the rows below it. Open surface: Surface kind (required) + Param key (empty = file). IPC: Method (required). System: no rows; the Action caption says what it does.

Several sources on one detector (2026-10-21)

A detector id merges contributions Host → Plugin → User. Line 1 shows one origin Tag per source in that order; line 2 lists every source's rules in the same order. A user patch with no rules (e.g. the user only switched a plugin detector off) adds a user override Tag. Any user contribution puts Remove in the trailing slot even when other sources exist; rows with no user contribution keep the padlock. When the Tags would push the id into an ellipsis (narrow column, long German strings) they collapse into one N sources Tag whose tooltip lists them; the id keeps its room.

Remove a user contribution — the row stays (2026-10-21)

On a row with other sources, Remove takes out only the user part. The row is not struck: only the user Tag is struck (Tag disabled), the user rule pieces in line 2 are struck in summary-removed-fg, and the pending Tag says what goes: your rules removed on save, or your override removed on save for a rule-less patch. The Switch is disabled and shows the state the row will have after Save (the plugin default for notebook). Undo restores the row. A row with only a user contribution keeps the old idiom: whole id struck, removed on save.

Add with an existing id — patch, not an error (2026-10-21)

Typing an id that is already registered shows an info line under the field at once (before Add), and the primary button reads Update detector. No rule changes for Add being enabled. With no user contribution yet: “{id} already exists. Your rules and settings are added to it on save.” With an earlier user contribution: “You already changed {id}. This replaces your earlier rules and settings on save.” A registered reserved id ($directory) is patched the same way. A new reserved id ($foo) passes the character check but fails with the reserved error on Add. After Update the card closes and the existing row gets a user Tag and your rules added on save / your rules replaced on save; no new row appears. Undo restores the previous contribution.

Handler — same short name replaces (2026-10-21)

A short name whose user/<short> already exists shows the info line “user/{short} already exists. This replaces it on save.” in place of the Saved as caption, and the button reads Update handler. After Update the row shows the new values with replaced on save + Undo (back to the old values). Host / plugin handlers never collide: their ids have no user/ prefix.

Handler run order — the list is the order handlers run (2026-10-21)

A detector with several handlers runs the first one by priority ↑, then owner user > plugin > host, then id. That contract is fixed; the list now sorts by it, so reading a detector's rows top to bottom is reading the run order. Sorting by id alone put plugin ids (com.…/) before host/ before user/ at a tie, the reverse of what runs. The intro says the rule and that the list follows it. Pending rows (added · replaced · removed) take the same slot rule.

Add card on a raised ground — error ink · Cancel · field edges (2026-10-21)

The add card is surface-raised. Three things on it fell under 4.5:1 or vanished in Latte: the error lines (accent-danger 3.52:1), the Cancel ghost label (text-secondary 4.05:1) and the normal box of Input and Select (border-default equals surface-raised in both themes). The card ground stays; the parts on it switch to their raised roles: a new semantic accent-danger-raised for error ink, Button ground="raised" for ghost, and ground="raised" on every Input and Select (Select gains the same variant Input has had since 2026-10-14).

Narrow column · long labels — pending rows keep the id (2026-10-21)

At size-360 in German, “N Quellen” plus a long pending Tag used to squeeze the id to one ellipsis character and push Switch / Undo off the row. Line 1 now gives room up in a fixed order: the origin Tags collapse first; if the id would still ellipsize, the pending Tag moves to its own line under line 1 (ellipsis + tooltip if even that line is short); only then does the id ellipsize, and never below 96 px (or its full width if shorter). Switch and the trailing slot never shrink. Wide columns keep the one-line layout.

Pending — added on save · removed on save

Nothing is written until the Settings Save; Cancel drops it. Add closes the card and puts the entry in the list at its sort position with a disabled Tag added on save; Undo (same slot as Remove) takes it out. Remove keeps the row, strikes the id, shows removed on save, disables its Switch and turns Remove into Undo. Same pair as File Extension Mapping and Hook Handlers.

Empty list

One row-height line in caption text-muted where the rows would be, with the same bottom separator. The header count reads (0); the Add button is unchanged.

Long labels · narrow column

Labels wrap inside the 150 column (German). When the card is narrower than label + gap + field-width-lg the control drops under its label. Long ids and summaries ellipsize on one line.

Apply note + the three rows

The old top line said every change needs a restart, in small accent-warning text. Saved values actually reach the terminals opened afterward; terminals already open do not switch over at save time. That is a fact about timing, not a warning, so the line becomes a neutral note: info glyph + text-secondary caption, at the top of the page above the rows, one sentence pair for all three rows. It does not promise that open terminals never change (a terminal that later reconnects may pick the new polling value), and it names no internal mechanism. The rows keep their order, controls, defaults and the existing HelpHint pattern; their descriptions say what the setting does and do not repeat the timing. Disk scrollback lines keeps default 10000, -1 = no limit, stays separate from Scrollback lines (Terminal › General), and is disabled while disk swap is off. A larger valid value from the config file is shown as is and is only written back when the user commits an edit.

Disk scrollback lines — the field fits its value, unit after the field (2026-10-22)

At 110 with the unit inside, 9 digits (100000000) lose their last digit and read ten times smaller; neither front- nor end-anchored clipping is safe for a number. So a number is never clipped: the unit word moves after the field (the pattern the remote-transfer and pipeline number fields already use), and the field fits its value — floor number-field-min-width (90, room for 9 digits + caret), growing by one character per digit while the user types and for any value read from the config file. Width is counted in ch of the field's own mono font, so a user-chosen font fits as well. Rest, hover, focus, blur and disabled draw the whole value; editing never scrolls inside the field, so Home / End / arrows only move the caret and Ctrl+A selects all. No ellipsis, no tooltip, no new string. -1 shows “no limit” in place of the unit (“-1 lines” is not a count). A value outside -1 … 100000000 is drawn as typed with the field's invalid edge and the range line under it until commit clamps it; a large config value is drawn verbatim and not clamped on read, as before. When the page is narrow the row wraps under its label and the field keeps the same width.

Default — nine values, notifications on / off / on

A new Misc L2 subtab Anomaly detection, after Task pipeline and before Tastyrc (Windows). The page opens with one info notice (the Performance apply-note recipe): these are heuristic signals that normal work can trigger, turning notifications off hides them only, and saved values apply from the next check. Then three sections in fixed order — Memory growth · Repeated calls · Call bursts. Each is a mono micro heading, the Show notifications Switch row, then the two number rows in backend order, with a 1px separator between rows. The switch row's caption says what the detector flags in plain words and ends with its internal name in mono (Detector: slow_loop.). Each number row has its own caption ending in its default. By default only Repeated calls is off. The first two frames are live: type, then Enter or click away.

All on · notifications off while editing a number

Turning Show notifications off changes the Switch only. The two number rows keep their normal ink and box, stay focusable and editable, and keep applying: the detector still runs and records, it just doesn't notify. That rule is stated once, in the page notice; the rows are not dimmed or disabled, so they don't read as switched off.

Out of range · after commit · bounds

Typing never corrects the value. While the typed number is outside the range the field gets the invalid edge and one line under it names the range and the value it will commit as. Enter or leaving the field commits: the value is clamped and the line goes away. A non-number reverts to the last committed value; there is no error popup. Values at either bound (including Minimum RSS 0) are valid and show no line.

Narrow · ko / ja

The page reuses settings_stack_row as is. Each row decides on its own: when its control does not fit beside the label column it stacks (label on its own line, control under it at the row start, gap 4) and returns side by side only with 16 px to spare. Headings, captions and the range line always wrap and are never cut; the field and its unit stay on one line. ko / ja keep the internal names untranslated.

Status table, one action per row, one request button

macOS builds only, the last L2 under General. A three-column table: permission · status · row action. The four states are told apart by glyph + word, with colour as a third channel: Granted check / success, Not granted alertCircle / warning, Unknown helpCircle / muted, Cannot check automatically eyeOff / muted. Unknown (inference failed) and Cannot check (deliberately not looked at) share the muted ink but never the glyph, and neither can be misread as granted. The Full Disk Access shortcut moves into its own row as Secondary / Sm [Open System Settings]. What needs explaining per row now lives in HelpHints, so the two notes under the table are short. [Request all permissions] stays Primary / Md under the table. While requesting it is disabled and the line below becomes a spinner + requesting copy; the button carries no spinner. The debug-only Accessibility row carries a debug Tag.

Plugin identity mark — one component, two sizes

A plugin manifest carries no image, so its identity in the Plugins window is a square initial mark: the first letter of the plugin name, mono, bold, in a tinted square at --tasty-radius. There are exactly two sizes — sm (32) on Installed / Attention list rows and lg (46) on a detail identity block and the Add plugin manifest preview (the old one-off 42px preview copy is gone; it was the same thing at different numbers). The tint is mixed into --tasty-surface-raised, a fixed bed — not the row background — so the mark is pixel-identical on a rest, hover and selected row. The initial's size is a token per size, not a ratio of the box: 13 at sm, 14 at lg — inside the 14px UI cap, with no exception (2026-10-07; the earlier 16 is withdrawn). The two sizes differ by the box (32 / 46) and one type step. Weight is regular: no bold mono face ships, so colour and size carry the mark.

Copy fingerprint · Add plugin that can't be added (2026-09-29)

Copy fingerprint moves out of the action bar: an IconButton sm copy right after the mono fingerprint, in Attention and in the Add plugin manifest card alike. No fingerprint → no line and no button (nothing to copy, so no disabled state). Attention's action bar has no Details for signature reasons (2026-10-06): the reason panel already shows the blurb and the fingerprint. Add plugin on a verified manifest that can't be added (already installed · signed but the public key file is missing · signature error) stays in its slot disabled — the variant it would have had, drawn with the shared disabled ink — and the reason replaces "Grants N permissions" on the left of the bar.

Add plugin — trust judgment, six kinds (2026-10-06 · re-cut 2026-10-19: unverified = danger + Add anyway, see next spec)

One box under the manifest card, toned by what Add will do: success — adds as is; warning — adds, and adding trusts the key (unknown key) or the new permission set (permissions changed); danger — unverified (2026-10-19: no longer blocked; explicit Add anyway, see the next spec). The fingerprint line follows the body whenever a fingerprint exists (signature errors have none). Untrusted-but-addable uses Trust & add in Primary: the agent variant is reserved for AI-agent surfaces.

Unverified plugin — warning + explicit Add anyway (2026-10-19)

Four signature states are now addable by an explicit choice: unknown key, public key file missing, unsigned, signature error. They share one danger trust box: the same title “Unverified plugin”, a cause line that names the actual state, and the same risk paragraph (a plugin is a program with the user's access; the permission list limits only what it can ask Tasty to do). A fingerprint line follows only when a fingerprint exists. The action bar keeps its order; the primary becomes Add anyway (danger fill) — Trust key & add anyway for an unknown key, because adding still trusts that key. Trusted and its flow are unchanged.

Trusted verdict — contrast on both grounds (2026-10-27)

After Verify on a folder signed by a trusted key, the box keeps its one line, shield, copy, padding, success tint fill and border. Only the two inks move to a new success ink role: the body to --tasty-plugin-trust-body-trusted-fg, the shield to --tasty-plugin-trust-glyph-success, both → --tasty-accent-success-ink. In Mocha that role is accent-success, so Mocha is pixel-identical; Latte remaps it to green 60% toward black. Each theme is shown on mantle (the host Add tab, panel_fill) and on base (this board's AddPanel). The shield is a hover-only display element; pointing at it adds no tint. Permissions changed and unverified stay as they were (reference rows).

Adding · failure · narrow window · ko / ja · Needs attention › Register anyway (2026-10-19)

While adding, both buttons are disabled and the primary shows a 14 Spinner + “Adding…” — a second click or Enter cannot start a second install. A failure uses the existing result path (toast, buttons back to rest). In a narrow window the bar wraps: reason on its own line, buttons right-aligned under it; long names and paths wrap anywhere. A plugin found in the plugins folder sits in Needs attention with the same box (no fingerprint in the box; the Signature section below keeps it) and a Register anyway danger button. Not clicking it = it stays unregistered; selecting the row never focuses the button.

Add plugin — dashed empty hint · manifest read error (2026-10-07)

Before Verify the slot under the path field holds the empty hint: a dashed 1px border-default box. Renderers without CSS dashes draw it with --tasty-border-dash / --tasty-border-dash-gap (4 / 4) on the straight edges, centred so each edge starts and ends on a dash; the corners stay solid arcs. When Verify cannot read tasty-plugin.toml (missing, parse error) the same box takes the slot with a solid accent-danger edge: alertTriangle + “Can't read tasty-plugin.toml”, then the reader's reason as one mono caption line (untranslated). No fill, no action — the path field above is how to fix it.

Installed detail — install path · log path · Open folder (2026-10-07)

Last section of the installed detail, after Command (identity · description · error · Permissions · Command · Install path). Open folder moves to the caption row, right-aligned, so the path never competes with it for width: at the 720 minimum and the 880 default the button is always whole. The install path and the log path are mono caption muted, wrap at any character and stay selectable, so nothing is cut and no tooltip is needed.

Installed detail — command keycaps per platform (2026-10-10 b11)

A command keycap is the manifest chord split on “+”. On Windows / Linux each part is a word keycap. On macOS the chord first goes through the keybinding mapping (alt → Command, option → Option, ctrl → Control), the modifiers sort in Apple order Ctrl · Option · Shift · Command (⌃ ⌥ ⇧ ⌘), and each one follows the user's modifier display style from Settings › General — the same as the Settings keybinding rows and the modifier hint on that machine. Ctrl stays the word “Ctrl”: it has no display style and no glyph, so no Control icon is added. Manifest ctrl + shift + h and alt + k shown below.

L2 placement & entry screen

A single L2 section named Import / Export, pinned last under Keybindings (after Plugins). It moves a configuration rather than editing bindings, so it gets a separator above it — a NEW axis on the settings L2 row model (today a row carries only a label + is_plugin); the separator is suppressed while the sidebar filter is active, since filtering breaks the adjacency it describes. The section's list position is not a list: two action rows, each with a one-line description and its own trailing button. Import is primary, Export secondary — import is the path with consequences and the one people come here for; export is a single fire-and-forget write.

While we were here we also corrected the Keybindings L2 roster to the eleven real sections (General · Workspace · Pane · Tab · Surface · Clipboard · Zoom · Explorer · Scripts · Preset · Plugins) plus the new twelfth: the design carried a phantom Image section and was missing Explorer and Scripts.

Import preview — group headers, select column, long-table handling

The detail view keeps the Preset skeleton (back bar with Apply in the right slot, over the diff grid) and grows two axes. Group headers (NEW on this table): one row spanning all columns, carrying a select-all box, the group name in mono micro caps, a changed / total count and a collapse chevron — it does not repeat Action / Current / Imported. Four groups: general combos, quick switch, script bindings, plugin overrides. A select column (32px, leading) makes apply per row; the group box is the group's select-all. The third column header is the fixed word Imported — the file name lives in the intro line, where it can be long without breaking the grid.

Length is handled by both levers: the table opens changed-only (a Show all 73 toggle in the back bar) and every group collapses. At minimum 73 rows — 100+ once slots are expanded — neither alone is enough. Quick switch is summarised one row per axis, not per slot: slots store raw keys and the combo is composed for display, so the axis row's value is the composed range (Ctrl+1…0) with the slot count as a sub-line. That keeps 29 slot rows out of the table and matches where the edit actually happens.

The six open values — failure, notices, conflicts, placeholder, tokens (4 · 5 belong to the removed option migration — retired 2026-10-10)

Six things the first pass left blank. The rule behind all of them: a result with nothing to do is a toast; a result with something to do is inline, where the thing to do lives.

1 · Export failure — success stays a toast carrying the resolved path. Failure is an inline danger block inside the Export row (the row that started it), with Try again and Choose another location…; the row's button goes disabled while the block is up, so there is one live retry, not two.

2 · Other bundle warnings — the dropped-override info line stays exactly as it is (muted, no tone, no glyph weight): nothing is wrong and there is nothing to do. Everything that is a warning — newer schema tag, unknown actions, empty groups — collects in one warning block, one line per notice, count in the header, in that fixed order. Three lines show; the rest fold behind Show {n} more. Never a block per notice.

3 · Parsing failure with no line number — the line clause is replaced, not dropped: the middle sentence always says why the file failed. With a position: “parsing stopped at line 1.” Without: “the file isn't TOML.” The first and last sentences never change, so the two read as one message.

4 · Several conflicts — count first, in the card intro: “3 conflicts — those shortcuts are already bound.” The per-row inline reason stays on every row (it names which binding), so the summary never repeats the list and nothing needs collapsing. The summary line appears from 2 up; at 1 the row line alone carries it.

5 · Modifier Select placeholder — Select a modifier, sentence case, UI font (not mono — it is not a key), --tasty-text-placeholder. It is a sentinel first option that leaves the list once a real combo is chosen, and the row keeps its warning-toned Not set trailer. Not an em-dashed pseudo-value like “— pick a modifier —”, which reads as a choice.

6 · Tokens — opened. The raw --tasty-size-* reads in the spec jsx were a tier violation, so they now have names (below). The off-grid 14px card inset was a slip: it snaps to --tasty-space-md (12). Drop the quoted constants and the raw-dimension ratchet and read the tokens.

Open values — unknown failure reason, counts of one, and the 620 cap

Three blanks left by the first round. An export failure with no known cause keeps the block exactly as decided — only the middle clause changes, from a fixed set (read-only · permission · disk full · catch-all the write didn't finish.), and the OS string is never spliced into the sentence: it gets its own muted mono line below, one line, ellipsised, full text in title. Counts of one get singular forms (1 notice, 1 unknown action was skipped) — English only; ko/ja don't inflect.

Key names · OS-reserved caption · text-entry hint

The option token now also means Win on Windows and Super on Linux. They are shown as words, like Ctrl and Alt — no logo glyph (the Windows logo is a trademark and Linux keyboards print different marks). Linux uses Super on every desktop, KDE included, so one config reads the same everywhere. The display-style dropdown stays macOS-only (there is nothing to choose between on the other two). A shortcut typed as text (config file, bundle import, plugin shortcut field) that matches a short known list of OS-owned combos gets a warning caption — the list is a hint, not a guarantee, and the copy says “may”. A text field that receives an OS key name (cmd+k, super+k, win+k, meta+k) gets a dedicated caption saying how to write it.

Scripts subsection — list, states & empty

Settings › Misc › Scripts. A subsection (not a separate popup) that manages user Lua scripts run by a shortcut. Each ScriptRow: the display name, the absolute path (middle-elided — dir tail truncates, filename always shown), a bound-shortcut Kbd badge (or italic Unbound), a peach changed badge + help line when the file's SHA no longer matches the one recorded at registration (TOFU re-confirm on next run), and an Auto-run row: mono trigger chips for the host-lifecycle events the script fires on (click a chip to remove it) plus a dashed Add trigger… control offering the remaining events. Row actions: bind shortcut (→ Keybindings), rename (inline), remove (inline confirm).

Git worktree viewer — read-only popup

Tools → Git. A 960×640 read-only popup that surveys every worktree. A header (Git + Refresh) sits over a context strip (current worktree · branch · HEAD oid · repo path). A left worktree rail (fixed 232px) lists main + linked worktrees as two-line rows — name + type badge, then oid + state badge — so nothing overflows the rail; the right column splits 50/50 into Changes (status) over Commits (log). Every badge is a token-tinted pill (the Tag visual), not colored text. No writes — only Refresh, selecting a worktree (re-binds the panes), selecting a changed file, and the diff Back button.

Diff variant — file row → unified diff

Clicking a file in Changes swaps the bottom pane (log → diff): a Back toolbar + file path, then unified hunks with an old/new line-number gutter. Hunk header in --tasty-accent-info, + in success, - in danger, context primary. Back returns to the log.

Diff toolbar — a container height, not a button height

The diff toolbar is 32px tall and holds 28px controls with 2px of air above and below. It now has its own name — --tasty-git-toolbar-height — rather than borrowing --tasty-control-height: the two are different roles and, as it happens, different numbers (32 vs 28), so aliasing them would have been wrong in value as well as in meaning. The value does not change.

Clipboard viewer — read-only snapshot popup

Tools → Clipboard Viewer (or a toggle shortcut). A 480×360 screen-centered popup that shows what's on the system clipboard right now — a one-time snapshot, not history. Single column: a header (clipboard icon + snapshot tag), a type bar, then a recessed mono code well. The type bar treats a single type as first-class — just a Text badge + live metadata (284 chars · 6 lines · UTF-8); two-plus types expand it into a segmented switch (Text / Image / Files / HTML / Other). No rail. At 5 segments the switch compacts to icon-only (the active segment keeps its label; tooltips carry the names) so it survives 20–40% longer translations inside 480px. HTML is shown as source text only — never rendered; a Pretty print checkbox takes over the type bar's meta slot (metadata moves beside the mime in the footer) and re-indents the same source instantly (0ms). Other buckets every format that isn't text/image/files/html — one row per format: mono name + size, then its textualized content, separated by 1px rules, all of it scrolling in the same well (long content clamps with a muted +N more lines). Read-only — no copy/paste/edit/delete.

Notifications popup — 352 × 400 (2026-10-17)

The existing popup, extended. Shared title bar (centred title, fullscreen fit + close). A 28 toolbar shows the same unread level pills as the LNB and Mark all read. The list is newest first. Each item: level glyph · title · elapsed time · unread dot / body (2 lines) / source · ✓ mark read · Jump. Unread = semibold title + blue dot; read = regular title, muted body. A source that has closed keeps its record, gets a · closed tag and a disabled Jump ("Source closed"). The first frame is live: click a row, ✓ or Mark all read.

Fullscreen stage — same list, wide

The fit button moves the same list onto the fullscreen stage. Content, order, actions and read rules are identical; only the body clamp grows to 3 lines and titles get the width.

Warning level glyph — Latte contrast, rest and hover (2026-10-27)

The warning glyph is the only thing in a row that says “warning” (no level word in title, body or meta), so it must clear the 3:1 non-text floor on both the resting row (bg-panel) and the hover bed (bg-panel + overlay-hover). --tasty-notification-item-warning-glyph now points at the existing --tasty-accent-warning-glyph instead of notify-warning. Mocha resolves to the same yellow as before; Latte gets the darker warning-glyph ink. Read and unread use the same colour (level is identity, not state). Error and info glyphs, the count badge and accent-warning are unchanged. Popup and fullscreen render the same NotificationItem, so both lists follow.

Read rules and arrival

Drag handles — TitleBar · Region · None

How a popup moves. A titlebar popup drags from the whole bar (the close button is excluded). A headless popup can declare a Region handle — a header band (currently the left half: icon + title) — while the header's own widgets (search, close) keep priority. None means the popup can't be moved. Affordance is the cursor only (grab → grabbing); no painted grip. Hover the bars below to feel the cursors.

8-direction resize — handle map & cursors

Opt-in (resizable popups — today: Listening ports & Remote connections). A band just inside the border holds 8 hit zones: 4 edges + 4 corners (corners take priority). There's no visual grip — the cursor is the only affordance. Dragging an edge moves only that edge (the opposite side stays fixed); a corner moves two. Hover the outlined zones to see each cursor.

Constraints & z-order — quiet limits, top-most wins

Limits are enforced silently. A popup can't shrink past its min size (or its default size if none is set), and no part may leave the scope rect (Window / Workspace / Pane / Tab / Surface) — drag or resize just stops at the boundary, and a shrinking scope auto-repositions the popup back inside. The scope edge is the effective max (there's no separate max size). When popups overlap, only the top-most one's handles/cursor respond; pressing a popup brings it to front.