@gemboss/ui 0.21.0 → 0.30.2

package/CHANGELOG.md

@@ -2,6 +2,329 @@
 
 Versions up to 0.9.0 are described in the README, each in the section that introduced it.
 
+## 0.30.2 (09/10/2026)
+
+The admin's chat moves onto the package's composer and engine picker (gemboss admin, assistant sync).
+
+- `ChatComposer` `canSend`: overrides the empty-box rule for the action. The admin sends a reference picture with no words,
+  and holds send while an upload runs, without disabling the text box. React only: `chat-plain.js` sits at its weight
+  ceiling (8698 B gzip) and no plain-HTML surface needs it yet.
+- `ChatComposer` `stopDisabled`: Stop stays in the slot, disabled, while a stop is on its way (the admin's turn can take
+  seconds to abort; a second press was a silent no-op).
+- chat-composer.css / chat.css: the admin's own engine chip rules are deleted (`.gemboss-ec-enginepick`, `-enginepick-btn`,
+  `-chiplabel`, `-chipsub`, `-chipmark` and their density and 44px-target rules). The admin now draws `EnginePicker` like
+  every surface (`gb-engine-*`, assistant-engine.css); nothing in the fleet wears those classes any more.
+
+## 0.30.1 (09/10/2026)
+
+- `LayerList` / `SortableLayerList` under a finger (`pointer: coarse`): the row's action buttons are 44x44 (were 26x26,
+  the mouse size) and the row's pick button is at least 44px tall. Where the name and the buttons do not fit side by side
+  (the 300px Layers drawer), the row wraps and the buttons take a line of their own, so a name is never drawn under them.
+  Measured on the funnel canvas's section list at 768 with touch. Mouse sizes are unchanged.
+
+## 0.30.0 (09/10/2026)
+
+**What gemform had and the package did not** (Chris 08/10/2026: "cái page login của gemform cái background bên dưới logo
+cũng đẹp… trong gemform có cái gì mà gemboss ui không có thì chuẩn hoá đăng ký vào gemboss ui"). gemform
+(gemlabs `toolkits/gemform`) was inventoried screen by screen; three things in it were shared patterns the package lacked.
+Everything else it draws (shell, KPIs, cards, tables with bulk actions, filters, pager, switches, banners, key-value
+lists, skeletons) the package already has, and gemform moves onto those. README "The sign-in screen", "Mini charts",
+"Setup guide".
+
+Added
+- `AuthLayout backdrop`: `"facet"` (default, the markup and pixels of 0.29.2), `"grid"` (gemform's ground: a 34px iris
+  grid fading out from the panel's top-left corner, on an ink gradient), `"none"`. Tokens `--gb-panel-grid-bg`,
+  `--gb-panel-grid-line`, `--gb-panel-grid-size`, `--gb-panel-grid-fade` on `.gb-auth`; classes `gb-auth-panel--grid` /
+  `--none` for a page that writes the markup. Drawn only where the panel is (900 wide AND 520 tall).
+- `Sparkline` + `sparklinePaths` and `ShareBar`, a new entry `minichart.css` (0.5 KB gzip). Six hand-drawn sparklines in
+  the fleet (admin x3, talent-radar, search-radar, gemwatcher, gemform); the baseline is 0 for counts unless fixed.
+- `SetupGuide`, a new entry `setup-guide.css` (0.9 KB gzip): the admin's Setup guide (StoreChecklistCard,
+  `gemboss-setup-*`) with the kit's tokens, all native `<details>` (no script for plain HTML). The admin keeps its own
+  until it moves onto this one in a PR of its own.
+- The catalog draws the sign-in screens at 1280 (at the catalog's column width the panel never showed), the grid beside
+  the facet, the mini charts in "Báo cáo", and a "Hướng dẫn thiết lập" section.
+
+Neither new entry is in `gemboss-ui.css` or the core (parts gate); the admin imports none of them. The grid's rules are
+in auth.css (+0.2 KB gzip there and in the bundle). `apps/admin/scripts/check-token-fallbacks-agree.mjs` now reads
+minichart.css and setup-guide.css too.
+
+Review #3925 (in this version): class names are written out (no `ui-sharebar__seg--${tone}` stem: the admin's orphan-rule
+gate went red on it); ShareBar grows by share, so fractions fill the track; a sparse array's holes are gaps; SetupGuide
+decides the open step once, draws a step without a body as a plain row, fills a `<progress>` instead of a styled width,
+renders nothing for no steps, remembers a fold (`rememberKey`), takes a `group` name; the reduced-motion block names the
+head's chevron with its own selector (`setup-guide-browser.test.tsx` reads the computed transition, with the weak
+selector as negative control); the specificity test computes specificity instead of matching strings.
+
+## 0.29.2 (08/10/2026)
+
+Fixes the rollout to search-radar (gemlabs #943) and content-radar (#944) found in the chat body. `chat-plain.js` does the
+same as the components, held to them by chat-plain.test.ts.
+
+- `ChatMarkdown` / `parseInline`: a bare `https://…` (and `<https://…>`) is a link again, as the surfaces' own renderers
+  drew it. GitHub's reading of where it ends: trailing `. , : ; ! ? _ ~ ' "` and a `)` or `]` with no partner inside the
+  URL go back to the sentence (linear time: a URL followed by 50 000 `)` parses in milliseconds). It also ends at `*`,
+  CJK text and full-width / typographic punctuation, and one glued to a word (`foohttps://…`) is not a link. Same
+  allowlist as a written link (`linkTarget`, then `new URL`: http(s) with a host), so `https://.`, `ftp:`, `javascript:`
+  stay text. New export `bareUrl`.
+- `ChatMarkdown` / `parseBlocks`: `####` to `######` are headings at the bubble's lowest step (`level: 3`, an `h5` with
+  `gemboss-md-h3`) instead of four hashes in front of a sentence. `#######` and `#tag` stay text; a heading line with no
+  words (`#### `) is dropped instead of drawing an empty heading.
+- `ImageHost.host` is optional: an entry with no host is the page's OWN origin (`imageHosts={[{ path: "/api/img/" }]}`),
+  for a root-relative picture (content-radar's `/api/img/…`). Checked after the browser's normalisation: the resolved
+  path must start with `path`; `../`, `%2e%2e`, `\`, an encoded slash or backslash, a double encoding (`%25`), a `;` path
+  parameter (`..;/`), `//host` and `/\host` are refused, and the src drawn is the resolved path. `path` must be a
+  directory below the root (`/x/`; `/` and `/x` are ignored). An entry WITH a host never opens relative paths.
+- chat.css: the send circle is `.gemboss-ec-toolbar > button[type="submit"]` (the toolbar's own child, same specificity).
+  `.gemboss-ec-input button[type="submit"]` also reached the engine popup, a DOM descendant of the composer even in the
+  top layer, and drew a surface's Pair button there as the 44px filled circle (five surfaces wrote `type="button"` to
+  dodge it). Test of the forbidden combination in chat.test.tsx, and the popup measured in Chromium against the same
+  button outside the composer (chat-browser.test.tsx, chat-plain.test.ts), each with the old selector as its negative.
+
+## 0.29.1 (08/10/2026)
+
+- `ChatThread` and plain `chat.thread`: keep following when a native scroll event from their own write-to-end arrives
+  after new content. The increased content gap no longer masquerades as the reader scrolling up. Wheel, key, touch and
+  direct programmatic moves up still unpin the thread.
+
+## 0.29.0 (08/10/2026)
+
+**The assistant's chat body as components** (Chris 08/10/2026: "đồng bộ hết giao diện của AI assistant… mọi service có
+panel này đồng bộ style + code dùng gemboss ui"). Until now the package drew the frame, the conversation list and the
+engine picker; every surface wrote the bubbles, steps, starters and composer by hand on chat.css's classes, with its own
+markdown renderer (five of them). The surface now hands in data and actions. README "The chat body".
+
+Added
+- `@gemboss/ui/assistant`: `AssistantChat` (thread + empty state + composer, from `messages`), and its pieces
+  `ChatThread` (role=log, follows the end only while the reader is there, aria-busy), `ChatMessage`, `ChatBubble`,
+  `ChatMarkdown` (the admin's parser and renderer: tables, headings demoted, fenced code that folds, safe links, pictures
+  only from fleet hosts, no raw HTML; `ownLink` / `renderLink` for a surface's own scheme), `ChatSteps` (rows print and
+  stop; kinds step / thinking / trace / steer), `ChatPending` (the one heartbeat; says its label once to a screen
+  reader), `ChatStarters` (they wrap), `ChatMeta` (Copy · engine · seconds · cost), `ChatError` (a fix: sentence,
+  command, Copy, the original folded), `ChatNote`, `ChatComposer` (a DIV, not a form; Enter sends, Shift+Enter and an IME's
+  Enter do not; one 44px slot that is send or stop; grows to 84px; `data-density` full → compact → icon → tight, measured),
+  `ChatAttach`, `PaperclipIcon`, `useComposerDensity`, `ChatLabelsProvider`, `CHAT_EN`.
+- `useChatTurns()`: the conversation's state with an id per message; a turn is written BY ITS ID (`start`, `write`,
+  `step`, `finish`, `fail`, `note`), so a note landing mid-turn or the next turn opening cannot take its text (the
+  "patch the last element" bug of partner-radar #929 / content-radar #937). `bridgeTurnError(e)` + `atBridge(e, status)`:
+  only a failure AT the bridge (its call threw, or it answered 401: pairing code rejected) is the bridge's; its 400 / 503
+  and failures on the way to the server are the turn's.
+- `parseBlocks`, `parseInline`, `linkTarget`, `imageSource`, `FLEET_IMAGE_HOSTS`: the markdown, testable without React.
+- `EngineMark`, `ENGINE_MARK_ART`, `isEngineMarkId`: each engine's mark (from the admin).
+- `EnginePicker`: `EngineChoice.mark` (the chip shows the engine's mark instead of its name when the composer is too
+  narrow), `EngineChoice.models` + `onPick(engine, model)` (every engine with its own models, one click picks both: the
+  admin's popup), `problem` (a red line on the Engine tab), `disabled` (the chip itself, while a switch is in flight).
+- `assistant-chat.css`, a new entry (0.9 KB gzip), imported by the chat components; not in `gemboss-ui.css`.
+  chat.tsx imports chat.css and chat-composer.css too (they were "the surface links it").
+- `chat-plain.js` (after `kit-plain.js`, and `engine-plain.js` when the page has the picker): `gembossUI.chat` with
+  `markdown`, `message`, `render`, `thread`, `steps`, `pending`, `starters`, `meta`, `error`, `note`, `composer`, `attach`,
+  `turnError`, `atBridge`, and `gembossUI.engineMark`. Same markup as the components, element by element (chat-plain.test.ts).
+- `AssistantChat` `title` / `subtitle`: the chat's own heading where the frame has no title bar (full screen).
+- `useFullChromeRoom(ref)`: how far full screen's floated buttons reach into an element (`--gb-chat-chrome-w` / `-h`,
+  `data-chrome`), for a surface arranging the pieces itself; `AssistantChat` uses it.
+- Exports `./assistant/markdown` (the parser) and `./assistant/engine-mark-art` (the artwork): no JSX, no CSS, so a node
+  test or a server module imports them. The admin's `components/chat/markdown-blocks.ts` and `lib/engine-mark-art.ts`
+  now re-export these (one owner; the admin's tests read the package's code). A fence with a tag like `c#`, `c++`,
+  `objective-c` is a fence (it opened nothing, and its closing fence swallowed the rest of the answer as code).
+
+Fixed
+- Full screen: the frame's floated buttons (Back to the popup and a surface's `fullActions`) covered the first message of
+  a chat with no heading (content-radar /v2/assistant at 1280). `AssistantChat` measures how far they reach into it and
+  makes room (`data-gb-dock-chrome` on the host's button row is what it measures).
+- On a phone, a `fullActions` button with no icon lost its words and showed an empty circle (assistant-chat.css).
+- `BridgeNotice`'s "Open setup" was a 16px box with a 24px overlay, which a measuring tool reads as 16: its own box is now
+  24px with a mouse and 44px under touch / at phone width (negative margins keep the line 16px). A long sentence no longer
+  wraps away from its dot (dot | sentence, the action under the sentence).
+- `engine-plain.js`: the chip carries the engine's mark (`mark`) when chat-plain.js is on the page.
+
+Review #3910 (all in this version): the log unpins at the reader's first move up (wheel, finger, keys), not 24px later, and
+goes back to the end on a send or another conversation (`ChatThread pinKey`; plain: `log.toEnd()` / composer `thread`);
+`turns.step` keeps a field an update leaves out; a bridge `TimeoutError` is the bridge's; clicking the pick already in
+force changes nothing; a step for an engine with no mark keeps its ✓ / ✕; message keys never mix ids and positions;
+plain `render()` keeps a message's element when its look did not change, the heartbeat's clock, and the folds the reader
+opened; the full-screen room is measured again when the buttons themselves change size.
+
+## 0.28.0 (08/10/2026)
+
+**Action card: an assistant proposes, a person applies.** The look of GemFeedback's merge and board-action cards (Chris
+08/10/2026, "follow theo gemboss ui"), so every assistant in the fleet asks before a change the same way. README "Action card".
+
+Added
+- `ActionCard`, `ActionCardSection`, `ActionCardItem`, `ActionChange` (React), `action-card.css` (its own entry
+  `./action-card.css`, loaded by the component; `gemboss-ui.css` unchanged).
+- Catalog section "Thẻ hành động".
+- `packages/ui/weight-budget.json`: a ceiling for `packages/ui/src/action-card.css`.
+## 0.27.0 (08/10/2026)
+
+**The engine picker for plain HTML**, for gemcare's two assistants (inbox, Reports), which have no React.
+
+Added
+- `engine-plain.js` (new entry, after `kit-plain.js`): `gembossUI.enginePicker(host, options)` → `{ update, openTab, open,
+  close, isOpen, destroy, element, panel }` and `gembossUI.bridgeNotice(options)`. Same markup as `EnginePicker` (one
+  stylesheet, `assistant-engine.css`), same behaviour; a redraw patches in place. README "Plain HTML:
+  `gembossUI.enginePicker()`". 5.3 KB gzip minified, its own ceiling.
+- `gembossUI.placeFloating(layer, anchor, end)` in kit-plain.js: the menus' placement, one plain copy (floatMenu and
+  engine-plain.js use it).
+
+Changed
+- `EnginePicker`: an Escape that closes the panel is marked handled (`preventDefault`) also when focus is outside the
+  panel. A surface whose Escape hides the assistant and checks `defaultPrevented` waits for the next one; the
+  window-capture markers the surfaces added (gemlabs #922, gemfeedback #66) are no longer needed. Not an Escape it does
+  not own: an IME composition (keyCode 229), or one in a modal opened from the panel; and focus entering such a modal
+  closes the panel, which would otherwise sit above it in the top layer.
+
+## 0.26.0 (08/10/2026)
+
+**A tablet glyph to draw with** (the funnel canvas's "All sizes": each page at desktop, tablet and phone widths).
+
+Added
+- `TabletGlyph` in `@gemboss/ui/editor`, beside `MonitorGlyph` and `PhoneGlyph`. `DeviceToggle` draws it for its Tablet
+  button (it carried the same SVG inline), so there is one tablet.
+
+## 0.25.0 (07/10/2026)
+
+**The assistant's engine picker** (Chris 07/10/2026): a chip in the composer row, as in the admin, that opens a popup
+with Engine · Setup · Status tabs. Engine, model, effort, the bridge's status and its install command leave the chat.
+
+Added
+- `EnginePicker`, `EnginePanel`, `BridgeNotice`, `useEnginePicker` (+ types `EngineChoice`, `Choice`, `BridgeStatus`,
+  `BridgeSetup`, `BridgeState`, `EnginePickerTab`) in `@gemboss/ui/assistant`. README "The engine picker".
+- `assistant-engine.css`, a new entry (1.9 KB gzip), imported by the component; not in `gemboss-ui.css`.
+- `placeFloating(layer, anchor, end)` in `menu-layer.ts`: the menus' placement, now shared with the picker's panel
+  (`floatMenu` calls it; same geometry).
+
+## 0.24.0 (07/10/2026)
+
+**The Studio canvas in the editors' frame** (gemboss #3856): the pieces the admin's Studio needed from the editor kit.
+
+Added
+- `EditorChatToggle` takes a `name` ("Hide <name>"; default "chat panel"): a column that is not a chat says so.
+
+Changed
+- A folded editor column (`.is-chat-collapsed`) is `visibility: hidden`: at width 0 its fields stayed in the Tab order.
+
+Removed
+- `.gemboss-pageedit-status` and `.gemboss-pageedit-kind` looks: the page editor draws Polaris' Badge, as the funnel beside it does
+  (`.gemboss-pageedit-status` stays on a wrapper as a hook, `data-status`, with no look).
+
+## 0.23.0 (07/10/2026)
+
+**The CSS comes in parts: a core every surface loads, and entries that come with the components that draw them.**
+README "Load only what you use" has the table and the imports for Next and for plain HTML.
+
+Added
+- `@gemboss/ui/core.css` (reset + tokens, 1.0 KB gzip), `@gemboss/ui/components.css` (the kit, the field look,
+  kit-plain.css; 8.2 KB), `@gemboss/ui/shell.css` (the shell + app-shell.css; 5.5 KB): built into `parts/` from the
+  same sections as `gemboss-ui.css`, each opening with a header that names the gemboss commit (kept through minify).
+  The core is 14.7 KB against 21.7 for the bundle. Like `gemboss-ui.css`, the parts exist after `build-css.mjs` (the
+  tarball has them; in this repo, build first).
+- Components import their own entry: `AuthLayout` & co. → `auth.css`; `AssistantHost`, the launcher → `assistant.css`;
+  `TopbarNav`, `SearchDialog`, `Avatar`, `Leaderboard`, `Podium`, `ThemeToggle` → `portal.css`; `ThemeToggle` /
+  `themeScript` (now in `theme-script.ts`, so a root layout with only the script does not take portal.css) → `theme-dark.css`; the collections components → `collections.css`; the editor components → `editor.css`.
+  A component a surface never imports takes its CSS out of the build with it (`sideEffects`).
+- The editor kit's step 4 (#3850: `LayerList`, `SortableLayerList`, `LayerTree` in `layers.tsx`, `sortable.tsx`, `tree.tsx`)
+  imports `editor.css` like the rest of the editor; `editor-layers-plain.js` is minified and weighed like the other plain
+  scripts (1.8 KB gzip).
+- `Reactions` (#3861, born an entry) imports `reactions.css` itself too; the parts gate found it unclassified on the
+  rebase, which is the gate doing its job.
+
+Changed
+- `@gemboss/ui/shell.css` is the built shell PART (was `packages/ui/src/shell.css`, which only the admin imported). The source is
+  `@gemboss/ui/shell-source.css`; the admin's `gemboss-shell.css` imports that, same file as before.
+- `SearchDialog` moved to its own module (`search-dialog.tsx`, same export from `@gemboss/ui`), so a surface that only
+  opens a `Dialog` does not get `portal.css`.
+- kit-plain.css → app-shell.css: `.ui-menu__item { display: flex … }` and the thread rail's 44px buttons at phone width
+  (`.gemboss-assistant-collapse`, `-newchat`). Both override a shell.css rule by coming after it; kit-plain.css sat
+  after shell.css in `gemboss-ui.css` but is in `components.css` now, which loads before it. Same rules, same weight.
+- `gemboss-ui.css` holds the same parts as 0.19.0, in the parts' order (kit-plain.css now sits before the shell).
+  Computed style of every element of both catalogs at 1280 and 390, 0.19.0 bundle vs 0.23.0 bundle: 0 differences.
+
+Measured on surfaces (tarball installed locally, nothing committed there), gzip of the package's CSS a page loads:
+- content-radar (Next 16): `/v2` 38.5 KB on 0.19.0 → 32.3 with the core; `/login` 31.2 → 25.4; `/v2/accounts` 43.1 →
+  36.9. Keeping `gemboss-ui.css` on 0.23.0 instead costs +1.9 KB (`/v2` 40.4): the launcher brings assistant.css twice.
+- taskdesk (plain HTML): 22.2 KB (the minified bundle) → 15.0 with the core; every element's computed style the same and
+  screenshots byte-identical at 1280 and 390.
+- GemFactory sign-in (plain HTML): 22.2 KB → 17.7 with the core + auth.css; screenshots byte-identical at 1280 and 390.
+
+Upgrading
+- A surface that bundles the package with esbuild needs a CSS loader (`loader: { ".css": "empty" }` if it links the CSS
+  itself): esbuild stops at a component's own `import "./auth.css"` without one. GemFactory's gbui.mjs has it already.
+
+The compatibility bundle, and the road out
+- `gemboss-ui.css` stays, minified, FROZEN at the 0.19.0 set: a surface that links it does not break, and a new
+  component never goes into it (`parts-gate.mjs`, CI).
+- 1. Now: every surface moves to the core + entries on its next bump (Next and Vite: three imports in the root layout and
+  drop `gemboss-ui.css` in the same bump; plain HTML: link the core and the entries each page draws).
+  2. A search across the fleet's repos for `gemboss-ui.css` shows who still loads it (06/10/2026: content-radar,
+  partner-radar, search-radar, talent-radar, GemCommunity admin, GemFeedback, gemwatcher, GemFactory, taskdesk).
+  3. When nobody does, it is removed in its own release, with this note pointing at it. Not before.
+
+Checks
+- `packages/ui/scripts/parts-gate.mjs` (CI, with `--selftest`): the core and the bundle frozen; every stylesheet in `src/`
+  classified; every entry exported; a component that draws an entry's class imports it; the built bundle holds exactly
+  the frozen sections.
+- `parts-cascade.test.ts` (`test:ui-browser`): the catalog with the parts (the core first, then the entries in order and
+  reversed, collections.css and editor.css included) paints what the bundle paints, element for element, at 1280 and
+  390; two planted entries that only agree by order turn it red. The core loads first by contract (README "Order"):
+  an entry before it loses its modifiers (`.ui-empty--no-match`), measured.
+- Ceilings for the three parts in `weight-budget.json`.
+
+## 0.22.0 (07/10/2026)
+
+**The layers, the element outline and the drawer as components (editor kit, step 4 of 5).** Nothing changes on screen
+or in behaviour in the admin: its page editor's Layers, Page settings and Edit content drawers and its element
+inspector's Elements outline now render these, measured equal on a production build (below). README "Layers and
+drawer".
+
+Added
+- `@gemboss/ui/editor`, three more modules behind the entry: `layers` (`LayerList`, `EditorDrawer`), `sortable`
+  ("use client": `SortableLayerList`) and `tree` (`LayerTree`).
+  - `LayerList`: the page's sections as rows (34px, 50 with a subtitle); select (`aria-current`), the caller's actions,
+    an empty line; off until asked: an eye to hide / show (`onToggleHidden`, `aria-pressed`), indent per `depth`.
+  - `SortableLayerList`: the same rows, reordered by drag (a grip, the dragged row faded, a drop line) and Alt+↑ / Alt+↓
+    (the focus kept on the moved row, also when `onMove` answers after a server write); the drag is kept by id. Its own
+    module, so the admin's Layers (no reordering) do not carry it. For GemFactory's Builder (step 5).
+  - `LayerTree`: an indented outline, `role="tree"` of `treeitem`s with level, position and selection.
+  - `EditorDrawer`: backdrop + a side panel (`right`: `.gemboss-settings`, `left`: `.gemboss-layers`), head with ✕,
+    `before`, body, `footer`.
+- `editor-layers-plain.js` (its own file and its own weight ceiling, 2,315 B gzip; editor-plain.js is unchanged):
+  `gembossUI.initEditorLayers()`: select, hide, drag and Alt+↑/↓ (the row moves in the document),
+  outline select / clear, drawers opened by `data-gb-drawer` and closed by ✕ and the backdrop; an event for each.
+- editor.css: the optional pieces (`.gemboss-layer-grip`, `.is-dragging`, `[data-drop]`, `.is-hidden`,
+  `.gemboss-layer-eye`) and `[hidden]` for a drawer a plain page keeps in the document.
+- `catalog/editor.html`: Layers (drag, hide, select, indent), Page settings and the outline, running, at 1280 and 390.
+
+Measured in the admin (two production builds, before = main f23a60729 with the #3848 fixes (0.20.1) and after, pinned SENTRY_RELEASE /
+GIT_COMMIT_SHA / GEMBOSS_BUILD_STAMP, served by `next start` on the same local data; every write the harness could cause
+was held)
+- DOM and computed style (+ ::before / ::after, box, control values) of every element, and :hover / :focus-visible /
+  :active forced on every control of the editor's columns and drawers, for 13 states (page editor: Layers open, a layer
+  selected, focus on a row's actions, closed with ✕, closed from the backdrop, ↓ pressed with the write held; Edit
+  content drawer; Page settings drawer, typing in it; theme editor inspector, Elements: the outline, a node picked, "Add
+  inside" open, a node picked and cleared) at 320, 390, 768 (touch), 1280, 1366, 1920: 78 captures, 22,888 element
+  renders, 10,620 forced-state checks. 0 differences in computed style or box. In markup, the intended ones only (720):
+  `data-id` on each layer row and outline node, `type="button"` on the buttons the components draw (no form around
+  them), `aria-current="true"` on the selected layer's button. Not the change: inline styles serialised by the server or
+  by the client (computed equal), the logo's per-port URL, the canvas's loading spinner (four states re-captured with
+  the canvas settled: equal), and the forced states of the chat column's work-mode select, which differ between two
+  captures of the SAME base build too. Negative controls (one declaration laid over the after build: the layer button's
+  padding, the outline name's, the drawer head's) are reported in 3 of 3 states.
+- Re-checked after rebasing onto main with 0.20.0 (#3846) and 0.20.1 (#3848): the 13 states at 1280 and 390, 26 captures,
+  7,612 element renders, 3,540 forced-state checks: again 0 differences in computed style or box, markup as above.
+- First load (brotli), against main with 0.20.1: the shell 239,674 → 239,655 B (−19); page editor +693 (LayerList and
+  EditorDrawer; SortableLayerList is not in it), campaign editor +327, theme editor +314, product studio +198, section
+  editor +125, plugin editor −12. Package weight gate: editor.css 8.1 / 8.4 KB gzip, editor-plain.js unchanged,
+  editor-layers-plain.js 1.8 / 2.3 KB.
+- Behaviour the admin does not use (drag, Alt+↑/↓, the eye, indent) and the plain-HTML side are asserted in Chromium:
+  editor-layers-browser.test.tsx (React and `initEditorLayers()`, with negative controls).
+
+Known, kept as it was (this step moves markup, not behaviour)
+- The admin's Layers do not drag and have no eye: they move with ↑ / ↓ buttons, which also work on touch (HTML drag and
+  drop does not start from a touch). Using `onMove` there is a change of its own.
+- The drawers have no Escape, and do not move the focus into themselves or back to their opener.
+- `DesignControls` (the inspector's Design tab body) is not moved: moving it changes how it looks.
+- The theme editor's "Sections on this page" list (ThemeSectionList) keeps its own bordered rows (inline styles); drawn
+  as a LayerList it would look different.
+
 ## 0.21.0 (07/10/2026)
 
 **Reactions: one emoji set and one chip for the fleet.** GemCare's team chat reactions, moved into the kit so GemFeedback
@@ -68,8 +391,13 @@ Fixed
 - `.ui-seg svg` filled a stroke icon solid (`fill: currentColor` over `fill="none"`): the monitor and phone glyphs drew
   as blocks. A `fill="none"` svg keeps its outline.
 
+- A folded editor column (`.is-chat-collapsed`) is `visibility: hidden`: at width 0 its fields stayed in the Tab order.
+- `EditorChatToggle` takes a `name` ("Hide <name>"; default "chat panel"): a column that is not a chat says so.
+
 Removed
 - The `.gemboss-ei-seg` look from `editor.css`.
+- `.gemboss-pageedit-status` and `.gemboss-pageedit-kind` (the page editor draws Polaris' Badge, as the funnel beside it does).
+
 ## 0.19.0 (06/10/2026)
 
 **The published CSS and plain scripts are minified, and each file has a wire-weight ceiling.** README "Minified on