@gemboss/ui 0.48.0 → 0.51.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (84) hide show
  1. package/CHANGELOG.md +457 -0
  2. package/README.md +280 -12
  3. package/catalog/editor.html +25 -12
  4. package/catalog/index.html +641 -99
  5. package/gemboss-ui.css +3 -3
  6. package/package.json +29 -2
  7. package/parts/components.css +3 -3
  8. package/parts/core.css +1 -1
  9. package/parts/shell.css +2 -2
  10. package/src/app-shell.css +1 -1
  11. package/src/assistant/chat.tsx +50 -6
  12. package/src/assistant/host.tsx +19 -7
  13. package/src/assistant/index.ts +1 -1
  14. package/src/assistant/sessions.tsx +2 -1
  15. package/src/assistant-chat.css +1 -1
  16. package/src/assistant.css +1 -1
  17. package/src/auth-extras.css +1 -0
  18. package/src/auth-footer.css +1 -0
  19. package/src/auth-footer.tsx +71 -0
  20. package/src/auth-signin-plain.js +1 -0
  21. package/src/auth-sso-plain.js +1 -1
  22. package/src/auth-steps.css +1 -0
  23. package/src/auth-steps.tsx +179 -0
  24. package/src/auth.css +1 -1
  25. package/src/auth.tsx +239 -14
  26. package/src/briefing-card.css +1 -1
  27. package/src/collections.css +1 -1
  28. package/src/create-shell.css +1 -0
  29. package/src/create-shell.tsx +221 -0
  30. package/src/dialog.tsx +3 -0
  31. package/src/editor/color-picker.tsx +183 -0
  32. package/src/editor/controls.tsx +49 -33
  33. package/src/editor/index.ts +8 -0
  34. package/src/editor/picker-grid.tsx +186 -0
  35. package/src/editor/picker.tsx +275 -0
  36. package/src/editor/popover.tsx +160 -0
  37. package/src/editor/swatch.ts +2 -1
  38. package/src/editor-color.css +1 -0
  39. package/src/editor-insert.css +1 -0
  40. package/src/editor-picker-grid.css +1 -0
  41. package/src/editor-picker.css +1 -0
  42. package/src/editor-plain.js +1 -1
  43. package/src/editor-popover.css +1 -0
  44. package/src/editor.css +1 -1
  45. package/src/empty-stage.css +1 -0
  46. package/src/empty-stage.tsx +31 -0
  47. package/src/icons.tsx +6 -0
  48. package/src/index-table.tsx +7 -4
  49. package/src/index.ts +19 -2
  50. package/src/kit-plain.css +1 -1
  51. package/src/kit-plain.js +1 -1
  52. package/src/language-switcher.tsx +10 -41
  53. package/src/list-page.css +1 -0
  54. package/src/list-page.tsx +239 -0
  55. package/src/menu-extras.css +1 -0
  56. package/src/menu-keys.ts +199 -0
  57. package/src/menu-layer.ts +2 -1
  58. package/src/menu-plain.js +1 -0
  59. package/src/menu.css +1 -0
  60. package/src/menu.tsx +83 -35
  61. package/src/pager-extras.css +1 -0
  62. package/src/pager.css +1 -0
  63. package/src/pager.tsx +88 -0
  64. package/src/portal.css +1 -1
  65. package/src/segmented.tsx +12 -2
  66. package/src/selection.tsx +3 -1
  67. package/src/session-rail-plain.js +1 -1
  68. package/src/settings-dialog.tsx +29 -2
  69. package/src/shell.css +1 -1
  70. package/src/stage-path.css +1 -0
  71. package/src/stage-path.tsx +89 -0
  72. package/src/stage.css +1 -0
  73. package/src/stage.tsx +52 -0
  74. package/src/starting-point.css +1 -0
  75. package/src/starting-point.tsx +93 -0
  76. package/src/status-list.css +1 -0
  77. package/src/status-list.tsx +65 -0
  78. package/src/status-matrix.css +1 -0
  79. package/src/status-matrix.tsx +131 -0
  80. package/src/team-chat.css +1 -1
  81. package/src/theme.tsx +13 -3
  82. package/src/translation-row.css +1 -0
  83. package/src/translation-row.tsx +113 -0
  84. package/src/ui.css +1 -1
package/CHANGELOG.md CHANGED
@@ -4,6 +4,463 @@ Versions up to 0.9.0 are described in the README, each in the section that intro
4
4
 
5
5
  ## Unreleased
6
6
 
7
+ ## 0.51.0 (24/10/2026)
8
+
9
+ **AuthSignIn: the server's sentence, a notice, the cursor, and a sentence that blames no field** (24/10/2026). Moving the
10
+ fleet's 20 sign-in pages onto `AuthSignIn` 0.50.0 found four things the hand-built forms did and the component could not:
11
+
12
+ Added
13
+ - `error` (+ `errorFields`): the sentence the server answered a plain form post with (a press before React loaded; the page
14
+ reads it from `?error=`), shown as if `onSignIn` had said it. Without it, that press came back to a silent form (8 gemlabs
15
+ toolkits). `errorFields={false}` for a lock or a closed door.
16
+ - `onSignIn` may answer `{ message, fields: false }`: a 429 lock or a 503 closed door no longer marks Email and Password
17
+ `aria-invalid` (a screen reader heard "invalid" over correct input). Only what was typed is blamed.
18
+ - `notice`: one line above the form until the first press ("Your session expired. Sign in again."): `.gb-auth-notice` in
19
+ auth.css. The admins had each drawn their own above the GemBoss button.
20
+ - `autoFocus`: the cursor in Email (three radars had it by hand).
21
+ - `signInRefusal(res)`: a sign-in route's refusal read the way the plain form reads it (the body's `error`, `detail` or
22
+ `message`; the fields marked for 400, 401 and 422 only). `if (!res.ok) return signInRefusal(res);` in an `onSignIn`, so no
23
+ toolkit writes that mapping itself.
24
+ - auth-signin-plain.js: the same as `data-error-fields="false"`, `data-notice`, `data-autofocus`; in `data-submit="json"` only
25
+ 400, 401 and 422 mark the fields (it marked every answer under 500, a lock included).
26
+ - auth-signin-browser.test.ts: both forms compared in the refused-with-notice and the locked states; the notice goes on the
27
+ first press on both sides; `signInRefusal` and the plain json form give the same sentence and marks for 400, 401, 429,
28
+ 503, an empty 500 and a dropped network. Negative control: the plain form ignoring `data-error-fields` is red.
29
+
30
+ Fixed (review of this change)
31
+ - An `onSignIn` answer whose `message` is empty no longer leaves the button on "Signing in…": it says "Couldn't sign in. Try
32
+ again."
33
+ - `error` changing after the form is on the page (a client navigation to another `?error=`) is shown; it was read only once.
34
+ - The notice is in the page when it is read, so its live region never spoke: Email's `aria-describedby` now names it too.
35
+ - `data-autofocus` on a second plain form no longer takes the cursor from the first, nor from a field someone is in.
36
+
37
+ Fixed (review of the five product pages moving onto it: gemfactory, gemform, gemcapture, gemcare, gempress)
38
+ - `AuthSignIn`'s fields are no longer controlled: submit reads the form. A password manager that filled them before React
39
+ loaded fires no change event, so the press sent an empty email and password, and the door counted a wrong try.
40
+ - `next` is posted with the form (a hidden field, both twins; the plain one from `data-next`), so a press made before React or
41
+ the script took over still lands there. Left out, no field: the server keeps its own default.
42
+ - `autoFocus` / `data-autofocus` put the cursor in Email only when nobody is in a field yet (a click into Password while the page
43
+ loaded kept it there before; React's own autofocus did not ask) and never while the page goes on to GemBoss by itself (a
44
+ phone's keyboard opened over the redirect). `autoFocus` no longer writes the HTML attribute.
45
+ - auth-sso-plain.js: `gembossUI.continuesByItself()`, the rule its door already used, for initSignIn and for a page that draws
46
+ its own form.
47
+ - `initSignIn({ onSignIn })` for a one-page app that checks the two values itself (GemCapture's console, GemCare's inbox):
48
+ `onSignIn({ email, password }, form)` answers as AuthSignIn's does, and the plain form keeps the button, the sentence and the
49
+ marks. Both apps had copied the package's error writer and busy state, and found the error region by guessing its id.
50
+ `gembossUI.resetSignIn(form?)` puts a form back as it first came when the app shows it again after sign-out (no sentence, no
51
+ password, the eye shut, Sign in pressable, no `?sso=` reason the address no longer carries).
52
+ - Back from GemBoss into a page the browser kept in memory, the door no longer still reads "Continuing with GemBoss…" (both
53
+ twins; auth-sso-plain.js `resetContinueWithGemBoss`).
54
+ - `data-submit="json"` goes to `data-next` only when it is a path on this site: `//host` or `/\host` lands on `/` (GemPress's
55
+ page check let `/.//evil.com` through as `//evil.com`).
56
+ - auth-signin-plain.js's ceiling 2096 → 2730 B gzip (measured 2218 + the 512 slack), with Chris's OK 24/10/2026: the plain twin
57
+ now holds what each one-page app had copied, and the fixes above.
58
+
59
+ **One sign-in and sign-up for GemBoss, GemCommunity and GemBoss Affiliates** (24/10/2026, Chris's design canvas). The
60
+ screen gains a real screenshot of the product on the panel, "Forgot password?" on the Password row, a row under the card
61
+ (theme, language, Help · Terms · Privacy), and the pieces of a sign-up asked one question a step. Nothing changes for a
62
+ caller that passes none of the new props: the same markup, and auth.css gains no rule (only notes).
63
+
64
+ Added
65
+ - `AuthLayout` `panel.shot` (`AuthShot`: `src`, `alt`, `caption?`, `width?`, `height?`): the screenshot in a white window
66
+ (12px corners, a 28px bar with three grey dots) under the panel's words. Lazy (a phone never downloads it), cropped
67
+ before the panel would cut it (swept 900 to 1920 wide, 600 to 1080 tall), gone under 600px of height.
68
+ - `AuthLayout` `footer`: a row at the bottom of the form's column, outside the card (`gb-auth-stage--foot`,
69
+ `gb-auth-bottom`); gone with the keyboard up, under 400px of height.
70
+ - `PasswordField` `forgot` (`{ href, label?, onClick? }`) and `AuthSignIn` `forgot`: the link on the label's row, at its
71
+ right end, after the field in the tab order, adding no height. Plain twin: `data-forgot` / `data-forgot-label` on
72
+ `initSignIn()`'s form.
73
+ - `AuthFooter` (auth-footer.tsx): the kit's `ThemeToggle` and `LanguageSwitcher` (ghost variant) and the Help, Terms and
74
+ Privacy links, each 44 x 44; the two kit controls take the screen's `--gb-*` colours, so on a dark OS with no theme
75
+ chosen they are dark with the screen. `AUTH_FOOTER_LABELS` for its words.
76
+ - `AuthSteps`, `AuthStepActions`, `AuthChoices`, `AuthChips` (auth-steps.tsx): the step header ("Step 1 of 3", the step's
77
+ name, iris segments, `aria-current="step"`), Back + Continue, radio cards (title, line, iris note; chosen = 2px ink edge
78
+ on a light surface) and checkbox pills (44px), drawn from auth.css's tokens so they follow the screen's dark mode and
79
+ need no core.
80
+ - `ThemeToggle` `followsSystem`: with no `data-theme` set yet, it reads the OS (the sign-in screen does). Off by default.
81
+ - Three entries, each with its ceiling: `auth-extras.css` (0.7 KB gzip, imported by auth.tsx beside auth.css),
82
+ `auth-footer.css` (0.5 KB), `auth-steps.css` (1.0 KB). Not in auth.css: it rides in the frozen gemboss-ui.css, which was
83
+ 21 bytes under its ceiling.
84
+ - `auth-standard-browser.test.ts` in Chromium (1280 x 800 and 390 x 844, light and dark), each layout claim beside a
85
+ negative control; the catalog's "Đăng nhập" section draws the standard sign-in (light and dark) and two sign-up steps.
86
+
87
+ **The public site layer is deprecated** (24/10/2026). Public websites use `@gemboss/website-ui` (gemboss-www
88
+ [packages/website-ui](https://github.com/chriskoh26/gemboss-www/tree/main/packages/website-ui), on npm), the full site kit with its rules and CLI; Chris chose one kit for every GemCommerce
89
+ website. `SiteHeader`, `SiteBrand` and `site.css` stay, unchanged, until news.gemboss.ai and the community home move;
90
+ no new page should adopt them. README "The public site layer" says so.
91
+
92
+ **One way to open a picker: the focus, Escape and back** (24/10/2026, picker standard). Five editor pickers opened in `Dialog`
93
+ with the focus on its ✕, the sixth (the page picker) in a popover of its own with its own focus code, back row and copy of the
94
+ Escape rule. Now every picker opens in a kit container with the focus in its search box, and Escape and ← Back are the kit's.
95
+
96
+ Added
97
+ - `Dialog`: a `[data-autofocus]` inside it gets the focus as it opens, as in `Popover` (without one, the browser's first control).
98
+ - PickerList / PickerGrid: with `search.autoFocus` the box carries `[data-autofocus]`, under a mouse only (under a finger a
99
+ focused box raises the on-screen keyboard over the list).
100
+ - `Popover` `placement="below"`: under the anchor, from its left edge (a menu from a top bar).
101
+
102
+ Changed
103
+ - `Popover`: Escape in a nested panel (`onBack`) steps back, as ← Back, and the focus stays in it; at the top it closes as before.
104
+ - `Popover`'s rounding is the shared `gemboss-popover-surface`'s (it declared the same 12px itself); its phone sheet only squares
105
+ the bottom corners.
106
+ - The editor's page picker is a `Popover` (`.gemboss-pagepicker-menu`, `-back` and their animation removed from editor.css).
107
+
108
+ **PickerItem `picture` and `drill`: the editor's page picker on PickerList** (24/10/2026, picker standard, the last picker that drew
109
+ its own list). The top bar's page picker (home, products, collections, cart, the store's pages, then a product, a collection or a
110
+ page) drew its own buttons, search box, thumbs and empty lines (`.gemboss-pagepicker-item`, `-search`, `-list`, `-thumb`, `-empty`,
111
+ `-drill`, `-check`), now removed from editor.css; the trigger, the menu surface, the back row and the sample note stay.
112
+
113
+ Added
114
+ - `PickerItem.picture`: a drawn picture of the caller's (an SVG the kit has no icon for) in the same 40px tile.
115
+ - `PickerItem.drill`: a row that opens a list of its own ends with a chevron instead of the check; picking it is the caller's
116
+ step into that list. Current, it is marked by the chosen row's tint and `aria-selected`, as every current row.
117
+ - `search.autoFocus` (PickerList and PickerGrid): the box takes the focus as the list appears, so a popover that opens on a
118
+ picker does not reach into the kit's markup for its input.
119
+ - Icon `chevronRight`, the stroked chevron the drill row ends with (it drew a filled one of its own).
120
+
121
+ **PickerGrid: PickerList's search and states for things chosen by their picture** (24/10/2026, picker standard slice 3). The
122
+ image picker drew its own grid, search box and loading / empty lines in the admin's CSS, the icon library the editor's ChoiceTiles
123
+ with a search of its own.
124
+
125
+ Added
126
+ - `PickerGrid` (`@gemboss/ui/editor`, editor/picker-grid.tsx): tiles as many to a row as fit (`photo`: square pictures at 120px+,
127
+ the name and a line; `icon`: a 26px drawing over its name on up to two lines at 88px+, 56px+ tall), the chosen tile with the accent edge and a check.
128
+ ↓ ↑ move the highlight by a row (the columns read from the layout), to the tile nearest the column in the next row holding a
129
+ choice (a short last row, a row of uploads); ← → Home End along it, in the search box once ↓ or ↑ has stepped into the grid
130
+ (the WAI-ARIA grid combobox: before that, and after the next keystroke typed, they move the caret); a click or Space selects,
131
+ a double click or Enter uses at once where the caller has `onActivate` (the image picker's Use image). A tile being uploaded
132
+ (`status.busy`, a spinner) or that failed (`status.error`, said in red) shows, cannot be chosen, and is announced from live
133
+ regions outside the grid. The search box, the highlight and the states (loading skeletons, the danger notice with Try again,
134
+ no match with Clear search, empty, reloading, Show more) are PickerList's, shared from picker.tsx (`PickSearch`,
135
+ `usePickHighlight`, `PickNothing`). `PickerTile.tooltip` (the title when left out): the image picker's file address.
136
+ - `editor-picker-grid.css` (`@gemboss/ui/editor-picker-grid.css`), its own entry, 1.1 KB gzip (its ceiling in weight-budget.json
137
+ is that plus 512 B, as every entry's).
138
+ - `PickerItem.titleStyle`: a title drawn as what it names (a font's name in its own face).
139
+ - `editor-picker-grid-browser.test.tsx` in Chromium, each case beside the one the old code failed.
140
+
141
+ Fixed
142
+ - PickerList (and PickerGrid): the highlight is scrolled into view when the keys move it, not when the pointer does (a pointer
143
+ resting on a half-shown row scrolled the list under itself).
144
+ - PickerList and PickerGrid: `more` shows after "no results" and an empty list too (the next page may hold it), and "no
145
+ results" offers the empty state's action (a library with nothing in it, searched, hid Upload).
146
+
147
+ **ColorControl `onDraft`; Popover beside the card that holds the column** (24/10/2026, gemboss #5323, the page editor's section
148
+ Background color on the kit's control).
149
+
150
+ Added
151
+ - `ColorControl.onDraft(text)`: the text box as it is typed, each key, before the commit (blur / Enter). A host that keeps unsaved
152
+ edits (a claims queue, a flush when its panel switches) holds the typing with it; kept only in the control, a value landing from
153
+ elsewhere replaced the half-typed one unseen.
154
+
155
+ Fixed
156
+ - Popover: placed beside the card AROUND the settings column (each edge within 24px of the column's), not the column itself (it
157
+ overlapped the page editor's card edge, 372 vs 389); a box that does not hold the column (`display: contents`, a narrower
158
+ wrapper) is passed over instead of taken as the card.
159
+
160
+ **PickerList: the body of every "choose one" popup in the editors** (24/10/2026). Chris, on the admin's link picker: the
161
+ pickers look bare and should follow the kit. Each of them drew its own list in the admin's CSS: the link and video pickers one
162
+ way, media, fonts, pages and the catalog four others (survey of 24/10/2026), with their own search box, rows, empty and loading
163
+ lines.
164
+
165
+ Added
166
+ - `PickerList` (`@gemboss/ui/editor`, editor/picker.tsx), Polaris' Combobox over a Listbox at the kit's numbers. The search box
167
+ keeps the focus while ↑ ↓ move the highlighted row and Enter picks it (Escape clears the box first, then is the popup's); with
168
+ no box the list takes the keys. A row is a 40px picture (a photo, or an icon for a page or a section), the title on a 20px
169
+ line at 650 with a `ui-tag` pill, and a second line whose NOTE comes first in a box the ellipsis never reaches (gemboss #5283:
170
+ "Opens the popup" was cut off at the end of a long line). The chosen row has a check and `aria-selected`; a row that cannot be
171
+ picked shows and says why (`disabledReason`). Loading keeps the rows' place with skeletons; `reloading` keeps the last answer's
172
+ rows dimmed and `aria-busy` and picks nothing from them (an Enter typed before a search's answer wrote the previous search's
173
+ row); an error is the kit's danger notice with Try again; a search that finds nothing offers Clear search; an empty list says
174
+ the caller's words; `more` adds Show more. The highlight is kept by row, moves with the pointer, and an Enter or Escape that
175
+ ends an IME composition is the typing's.
176
+ - `editor-picker.css` (`@gemboss/ui/editor-picker.css`), its own entry, 1.0 KB gzip: only a surface that draws a picker loads it.
177
+ - `editor-picker-browser.test.tsx`: the rows' numbers, the keys, a click, a locked row, the states and the 44px clear button
178
+ under a finger, in Chromium; a negative control where a note that may shrink is cut by the same line.
179
+
180
+ **Popover and the colour picker: a setting's panel beside the column; ColorControl's swatch opens the kit's picker** (24/10/2026).
181
+ Chris: the editor lacks the small panels GemPages opens from a setting, and the colour picker should be standard and easy to use
182
+ ("tham khảo cái gì hợp lý… ưu tiên ui ux dễ dùng"). ColorControl's swatch was `<input type="color">`: the operating system's
183
+ picker, a different window on every machine, with no opacity and none of the theme's colours.
184
+
185
+ Added
186
+ - `Popover` (`@gemboss/ui/editor`, editor/popover.tsx): in the top layer, BESIDE the settings column the anchor scrolls in, on the
187
+ side with room, its top at the anchor's row; under the anchor when neither side has room; a sheet along the bottom at phone width.
188
+ A head with its title, ← Back for a nested panel and ✕; Escape (only it) or a press outside closes it; the focus goes in, and
189
+ back to `returnTo` on Escape or ✕. `editor-popover.css`, 0.6 KB gzip.
190
+ - `ColorPicker` (editor/color-picker.tsx): a saturation × brightness square that works with the pointer and the keys (← → ↑ ↓,
191
+ Shift for 10), hue and opacity as native ranges (the opacity over a checkerboard), a hex box, an eyedropper where the browser has
192
+ `EyeDropper`, the theme's colours under "Theme", the recent ones under "Recent" (`ColorChoice.group`), and None. A pick keeps the
193
+ value's transparency and way of writing (`pickSwatch`); a drag writes at most every 80 ms and once at its end, a key at once.
194
+ `editor-color.css`, 1.2 KB gzip. Not copied from GemPages: its square hides on desktop until a second click and is mouse-only,
195
+ and it offers no theme colours.
196
+ - `eyedropper` in the icon set.
197
+
198
+ Changed
199
+ - ColorControl's swatch is a `button.gemboss-ei-swatch` (`aria-haspopup="dialog"`, `aria-expanded`) that opens the picker in a
200
+ Popover; it paints the colour with its opacity over a checkerboard (`--sw` on `.gemboss-ei-swatch-fill`), and nothing for a value
201
+ it cannot show (the native swatch painted those black, a colour nobody chose); disabled with its reason as before. The text box,
202
+ the opacity box and the chips while the field is in use are unchanged. editor-plain.js (pages without React) keeps the native one.
203
+
204
+ ## 0.50.0 (24/10/2026)
205
+
206
+ **Continue with GemBoss says which name the page is on** (24/10/2026). Every internal tool answers to a flat name and an .ops
207
+ name; GemBoss sent the token to the one registered URL, so a person on the other name signed in there and the name they used
208
+ kept asking (review of gemlabs #1163).
209
+
210
+ Changed
211
+ - `gemBossSignInUrl(service, next, issuer, host?)` adds `&host=`; `AuthContinueWithGemBoss` passes the browser's
212
+ `location.host` once mounted (the server-rendered first paint links without it), and auth-sso-plain.js always does.
213
+ GemBoss only CHOOSES among the tool's registered URLs with it (`FLEET_SSO_SERVICES[...].alias`, apps/admin).
214
+ - `AuthSignIn` renders `method="post"` always and takes `action`: on a server-rendered page a press before React loaded was a
215
+ native GET, with the password in the URL, history and server logs (measured 24/10/2026: 8 Next sign-in pages in gemlabs).
216
+ - `?sso=not_member` now reads "Your GemBoss account is not a member here. Ask an admin to add your email." It said "Use the
217
+ password", but since 23/10/2026 both doors check the same member list, so the password door refuses that person too.
218
+
219
+ **StartingPoint: a chat door where the person asks** (24/10/2026). The chat door's picture always drew Gem asking, the person
220
+ answering and a "Drafting" tile, so a door that asks Gem a question (the empty Funnels page's "Which funnel should I build?")
221
+ read as Gem drafting pages. `chat.from: "me"` puts the person's question first and Gem's answer under it; `chat.step` names the
222
+ tile. Both optional: a door that passes neither draws as before.
223
+
224
+ **AuthSignIn: the whole sign-in form of a fleet tool** (23/10/2026). Every tool wrote its own form around the kit's pieces, and
225
+ the words drifted: "Your lark email", "Team password", "Access password", placeholders of dots, buttons saying `Enter →`, `Vào`,
226
+ `Continue`, `Log in` (measured on the live sign-in pages of 60 services, 23/10/2026: one of them, GemPress's, had the whole
227
+ standard). Chris: "cái này chắc phải đưa vào gemboss ui".
228
+
229
+ Added
230
+ - `AuthSignIn` (auth.tsx): Continue with GemBoss (with `service`), then Email, Password with its eye, the error and Sign in, in
231
+ the kit's words and with no placeholder. The tool passes `service`, `next`, `onSignIn({ email, password })` (returns the
232
+ server's sentence on a refusal, nothing once it has moved the browser on; a throw reads as the network) and an optional `foot`.
233
+ `SIGN_IN_OFFLINE` is that network sentence.
234
+ - `auth-signin-plain.js` (`@gemboss/ui/auth-signin-plain.js`), its own weight entry: `gembossUI.initSignIn()` fills an empty
235
+ `<form data-gb-signin>` with the same markup, for a page with no React. Loaded after auth-sso-plain.js. `data-submit="json"`
236
+ posts `{email, password}` and follows `data-next`; otherwise the browser posts the form and the server's sentence comes back
237
+ in `data-error`. A form written without `method` is posted (a GET would put the password in the URL). A redirect the server
238
+ answers with is followed as a page, never read as success. With `data-sso` but no auth-sso-plain.js it draws no button and
239
+ says so in the console. Its eye stops its click at the button, so kit-plain.js's delegated `initPasswordFields()` does not flip
240
+ it a second time.
241
+ - `initContinueWithGemBoss()` (auth-sso-plain.js) can be called again: a link it already set up gets no second click handler.
242
+ - `auth-signin-browser.test.ts`: the React and the plain form compared element by element in Chromium (a word changed on one
243
+ side is red), what each does on submit, the eye with kit-plain.js on the page; two negative controls.
244
+
245
+ **ListPage: the frame of a list page** (23/10/2026, step 3 of the list standard, Gems/CLAUDE.md §13). Every admin list page
246
+ drew its own frame on Polaris `Page`, and its states its own way: five kinds of empty state, four labels on a retry, a skeleton
247
+ of 3 or 4 lines or a spinner or nothing (survey of 14 pages, 23/10/2026).
248
+
249
+ Added
250
+ - `ListPage` (+ `ListPageAction`, `ListPageState`): the header (a way back, the title and its badge, one line under it, the page's
251
+ primary button, secondary actions), notices, a toolbar, and ONE card holding the list or the state it is in (`state`:
252
+ `loading` placeholder rows, `empty` the page's own empty state, `no-match` with Clear filters, `error` with Try again).
253
+ Polaris Page's numbers as the admin draws it, measured at the six widths. From a page column of 560px two secondary actions
254
+ are buttons and the rest are behind ⋯; under it, and below 768px, all of them. Below 768 the header is two rows and its
255
+ controls 44px. Its CSS is an entry, `list-page.css` (`@gemboss/ui/list-page.css`, imported by list-page.tsx).
256
+ `list-page-browser.test.ts`, four cases with negative controls.
257
+ - `Icon` `arrowLeft` (ListPage's way back, the arrow Polaris' Page draws there).
258
+ - ListPage, steps 3c and 3d (Pages, Themes, Plugins, Media, Offers, Funnels): `card={false}` for a list that draws its own cards
259
+ (its own empty stands on the page; loading, no match and error are still boxed), `cardProps` (stay on the card in every
260
+ state: a drop zone), `cardMeta` (beside the card's heading), and `cardLead`: rows at the top of the card in every state, the
261
+ state's body after them (Funnels' Website row, which does not wait for the list's read); a page with a lead always has its
262
+ card, so the lead stays the same element. Notices or a toolbar that draw nothing take no gap. The page's status region
263
+ ("Loading…") is one element in every state and only its words change (one added with its words in it is often not read out).
264
+ `list-page-browser.test.ts` cases 6–8, with negative controls.
265
+ - ListPage, step 3e (Tests): an `external` action (a new tab, a download) is a plain link, as a button and as a ⋯ row, not the
266
+ app's `linkAs`: Next prefetches its Link, so the Tests page's Export CSV built its file on every visit. Case 5.
267
+ - ListPage, step 3f (Products): `actionGroups` (Polaris Page's name), choices of one kind always behind ⋯ at every width, a
268
+ title and the one that is on marked `active` (Products' Auto-refresh: Every day, Off). Case 9, with a negative control.
269
+ - `MenuItem` `checked`: a choice (`menuitemradio`, `aria-checked`) with a check before the one that is on and the same space
270
+ before the others; `MenuGroup`: a titled `role="group"` of such rows. Their CSS is in the `menu-extras.css` entry (the core
271
+ is frozen). list-page-browser.test.ts now loads menu-extras.css, as the admin does through menu.tsx.
272
+ - A closed ⋯ has no layout (`menu-extras.css`: `.ui-menu:not([open]) > .ui-menu__list { display: none }`). A closed <details>
273
+ only skips painting: asked for geometry, its rows were laid out, so the admin's phone-width gate read a closed ListPage ⋯ at
274
+ 320px as rows cut by the left edge, and find-in-page matched them and opened the menu. menu-browser.test.ts case 23.
275
+ - `Pager` (+ `pageWindow`): the numbered pager (`ui-pager`, README "Long lists") as a React component, links (`href`, through
276
+ `linkAs`) or, for a list paged in state, buttons (`onPage`), `busy` while a page is on its way. With Chris's OK (24/10/2026)
277
+ the pager's rules moved out of kit-plain.css into `pager.css`, just before it in the core (same rules, same order, no new
278
+ weight; the cascade check paints 0 boxes differently); the buttons' look is the new `pager-extras.css` entry.
279
+ `pager-browser.test.ts`, four cases with negative controls. The admin's Products list uses it.
280
+
281
+ ### Before: the row ⋯ (step 2)
282
+
283
+ **The admin's row ⋯ is the kit's Menu** (23/10/2026, step 2 of 3: `RowMenu` in apps/admin swaps Polaris's Popover + ActionList for
284
+ `Menu`; step 3 is the "list page" component).
285
+
286
+ Added
287
+ - `Menu` takes `disabled` and `loading`: the ⋯ takes no click and no key and leaves the Tab order (`aria-disabled`, drawn by
288
+ ui.css); `loading` puts a ring in place of the dots and `aria-busy`. The ring (`.ui-menu__busy`) is in a new entry,
289
+ `menu-extras.css` (`@gemboss/ui/menu-extras.css`, imported by menu.tsx): menu.css is in the core and the frozen
290
+ gemboss-ui.css had no bytes left (+24 B gzip over), and the admin loads no kit-plain.css (its `.ui-spinner`). Turned off
291
+ while open, it closes, with focus that was in it back on ⋯; opened while off by anything but its button (find-in-page, a
292
+ script), it closes again. `menu-browser.test.ts` case 20, with a negative control.
293
+ - A long hint wraps (`menu-extras.css`): in a column of at most 32ch, under the label when the row has no room beside it, and
294
+ the list is never wider than the screen less 16px. One nowrap line of 80 characters made the list ~600px wide and ran it
295
+ past a phone screen. A short hint stays on one line right of the label. `menu-browser.test.ts` case 21.
296
+
297
+ Changed
298
+ - Escape that closes an open React menu from the page-wide listener (focus on the ⋯, or nowhere in the menu) is taken
299
+ (default prevented), as kit-plain.js already takes it, so a dialog listening after it does not close on the same Escape.
300
+ `menu-browser.test.ts` case 22.
301
+
302
+ **The ⋯ menu is ready to be the admin's row menu** (23/10/2026, step 1 of 3: the kit only; the admin's `RowMenu` moves onto it next).
303
+
304
+ Added
305
+ - `menu.css`, its own file (`@gemboss/ui/menu.css`), imported by `menu.tsx`: the `.ui-menu` rules (placement, the floated list,
306
+ the summary marker, `--end`), the hint, the separator, the disabled row and the icon button (`ui-btn--icon`, with its 44px
307
+ rules under a finger), moved out of `kit-plain.css` unchanged. The admin loads `ui.css` and the shell, never `kit-plain.css`,
308
+ so a `Menu` there had no placement and no square ⋯. The core carries the file where the rules stood, just before
309
+ `kit-plain.css` (`packages/ui/scripts/parts.mjs` CORE and the frozen copy in `packages/ui/scripts/parts-gate.mjs`: a split, not new weight), so
310
+ `parts/components.css` and `gemboss-ui.css` hold the same rules in the same order.
311
+ - A menu's semantics and keys, `menu-keys.ts`, shared by `Menu` and `LanguageSwitcher` (whose own key handler and `openMenu`
312
+ it replaces). The list is `role="menu"` named by the trigger's label, rows `menuitem` with `tabindex="-1"`, the trigger
313
+ `aria-haspopup`. An opening by a click, Enter or Space lands on the first row that can act (↓ on ⋯ the first, ↑ the last;
314
+ a script's `open` moves no focus), with or without the popover API. On a row (a field in the list keeps its own keys):
315
+ ↑ ↓ wrap and skip disabled rows; Home End; Space acts on a link row; Escape closes with focus back on ⋯ and is taken; Tab
316
+ closes and goes on. A chosen row runs with focus already back on ⋯ (a popup it opens returns there), then the menu
317
+ closes, link rows too. One menu open at a time, whatever opened the next one (a key is not a click outside); a menu that
318
+ holds the one opening stays open.
319
+ - `menu-plain.js` (`@gemboss/ui/menu-plain.js`), the same for plain markup: a SECOND script after `kit-plain.js`, which has no
320
+ room for it under its weight ceiling. It adds the roles the markup leaves out and runs by itself. **A plain surface that
321
+ wants a menu's keys adds this script** (or `import "@gemboss/ui/menu-plain.js"` after the kit-plain.js import); without it
322
+ a plain menu works as before.
323
+ - `menu-browser.test.ts` (`test:ui-browser`): 19 cases on `Menu` and on plain markup, each with a negative control: roles,
324
+ keys, where an opening lands, choosing a row, one open, a menu in a table row that opens on click, the last row of a
325
+ scrolling table, Escape and a selection, the admin's own sheets + `menu.css` against the core, a field in the list, a menu
326
+ in a menu or the account menu, a menu with no list, a popup's Tab trap, a prevented opening, no popover API, and a React
327
+ Menu on a page that also runs kit-plain.js + menu-plain.js, Tab from an open menu's ⋯, an Escape something else took, and
328
+ the plain LanguageSwitcher beside menu-plain.js. `plain-ssr.test.ts` (`test:packages`): every `*-plain.js` loads in Node
329
+ without throwing.
330
+ - Review of #5179: Tab from the ⋯ of an open menu closes it and focus goes on (its rows are out of the Tab order, so the list
331
+ stayed open over the page); the page-wide Escape leaves an Escape something else took (`defaultPrevented`: a dialog, a
332
+ combobox) alone; a close clears the one-open mark an opening left (an opening closed before its toggle let the next one skip
333
+ the rule); menu-plain.js leaves the plain LanguageSwitcher (`.gb-lang`, its own keys and checked-row focus) to
334
+ language-switcher-plain.js and only closes it with the others (two scripts put focus twice).
335
+ - editor-insert.css: the insert menu's "Ask AI: …" row (E2), in the accent colour, highlighted with the accent wash when
336
+ selected, and one line however long the request.
337
+ - Four pieces GemPress's redesign (approved by Chris 23/10/2026) drew with its own CSS, each its own entry, presentational
338
+ (no state, no inline style) and written by hand from plain HTML with the classes listed at the top of its file (README "Review
339
+ pieces"):
340
+ - `StagePath` (`stage-path.css`): stages that unlock in order, an `<ol>` of cards with a number (a green ✓ when
341
+ `done >= total`), the name, "3 / 35 pages approved" and a `<progress>` bar; the current stage (default the first not done)
342
+ has an ink outline and an ink number, `aria-current="step"`. `stagePathDone`.
343
+ - `StatusMatrix` (`status-matrix.css`): rows × columns on the kit table, each cell "live / total" with what waits under it
344
+ ("5 draft · 2 changed"), toned all live (green) or has drafts (amber), "—" where there is nothing to count.
345
+ `statusMatrixTone`.
346
+ - `TranslationRow` (`translation-row.css`): one string under review, key + state badge + who, source beside target (one
347
+ column under 900px or in a row narrower than 600px), the checks and the surface's action; `current` draws an ink border
348
+ and a 3px ink bar; focusable (`tabIndex={-1}`) for a J / K list. The editable control is the surface's (`target`, a node or
349
+ a function given the ids for `aria-describedby`). `TRANSLATION_STATE_LABELS`, `translationRowId`.
350
+ - `StatusList` (`status-list.css`): a quiet system-health strip, a dot (success / warning / danger, or an empty ring for
351
+ muted), a bold name and one muted sentence, a link when it has `href`.
352
+ - `CreateIcon`, `CreateStepper`, `CreateRail`, `CreateDoors`, `CreateFilter`, `CreateGrid`, `CreateCard`, `CreateParts`,
353
+ `CreatePath` (`create-shell.css`, its own entry): the create shell, one shape for making a page, a funnel or a section inside
354
+ the frame each already opens in: an icon tile and "Choose → Make it yours → Gem builds it" in the header, a rail with the doors
355
+ (ask the assistant, the library, blank: at most three) and chip questions ("Who it is for": cold, warm, ready, each with its
356
+ colour's dot; "What it does"), cards with a Stage picture, who it is for, a name, one line and what is inside. `CREATE_AUDIENCE`
357
+ holds the words for the three temperatures (23/10/2026, drawings A1/A3/A4).
358
+
359
+ Changed
360
+ - shell.css is the one owner of the menu row: `.gemboss-account-menu-item, .ui-menu__item` keep their shared declarations,
361
+ the account row stays `display: block`, and `.ui-menu__item` is the flex row (label, then the hint on the right; `gap: 8px`,
362
+ nowrap, the small radius) that app-shell.css used to lay over it. app-shell.css drops its `.ui-menu__item` rule. A plain
363
+ `details.ui-menu` on the core: 0 differences in 2.3 million computed values against main (bundle and parts, built and
364
+ minified; 1280 and 390, mouse and finger, light, dark, the `data-gb-menus` flag). In the admin, which loads shell.css and
365
+ not app-shell.css, the assistant dock's ⋯ rows become that flex row too (their boxes unchanged); the account menu's rows
366
+ do not change.
367
+ - `initMenus()` (kit-plain.js) puts focus back on a menu's button BEFORE a chosen row's own handler, then closes the menu as
368
+ before. Still opt-in: a page that never calls it keeps its menus open on a chosen row. `closeMenus(except)` leaves open a
369
+ menu that holds `except` (a kit menu in an open account menu).
370
+ - kit-plain.js: a popup's Tab trap leaves `tabindex="-1"` out (a menu's rows): counted as its last control, Tab from the real
371
+ last one left the popup.
372
+ - `escapeTaken` (selection.tsx, kit-plain.js): a menu or a dialog takes Escape when it is SHOWN (`checkVisibility`), not when
373
+ it has a box. A closed `<details>`' content keeps its boxes, so with every row's ⋯ list `role="menu"` the box test would
374
+ have handed every Escape in a selectable table to its closed menus.
375
+ - `Menu`: one page-wide set of listeners for every mounted menu (`registerMenu`: outside click, Escape, the float, one open),
376
+ not a click and a keydown listener per menu; the summary opens the menu itself with or without the popover API.
377
+ - kit-plain.js stays under its ceiling (8 784 B gzip of 9 189); menu-plain.js weighs 1 047 B (ceiling 1 559).
378
+ - collections-board.test.ts: the keyboard case loads menu-plain.js and walks the rows with ↓ (it walked them with Tab); the
379
+ two "no popover API" negatives open the menu by script, since a click now focuses its first row and, without the top
380
+ layer, that focus scrolls the table's frame to it (menu-browser.test.ts case 15 holds the click).
381
+
382
+ ## 0.49.0 (23/10/2026)
383
+
384
+ Fixed
385
+ - collections.css: a folded index row's primary cell wraps, as the fold always meant to. Its `white-space: normal` was
386
+ (0,2,1) and lost to the fold's own nowrap on every cell (0,2,2), so free text under a title (GemPress's "missing: …"
387
+ note) and an unlinked title stayed on one line, widened the row and scrolled the list sideways (384px at 320 on
388
+ GemPress). A linked title (`.ui-table__title`) and its second line keep their own nowrap and are cut as before; a token
389
+ too long for the row (a URL, a slug) breaks anywhere. A cell whose content fits is unchanged (gemcare People at
390
+ 320/390/768, 50 rows: no row taller).
391
+ - ui.css: `.ui-sr-only` is pinned on the inline axis (`left: 0`; also portal.css `.gb-sr-only`, team-chat.css
392
+ `.gb-tc-sr`, shell.css `.gemboss-assistant-sronly`, assistant.css `.gb-dock-sr`). It stood where it would have been in the
393
+ flow, so inside a frame that scrolls sideways (a table, a board, a segmented row) it could stand far past the frame and push
394
+ the PAGE sideways: the "Actions" header of a 2105px IndexTable, 792px at 1280; search-radar /aeo 428px; a bare
395
+ `ui-table-wrap` on a page with ui.css only, 1109px. It keeps its line, so a screen reader's cursor stays by the row.
396
+ (#5176 had made `.ui-table-wrap` `position: relative` instead and put `noreferrer` on a row's Cmd-click; both are withdrawn
397
+ before release: a positioned frame paints over an earlier dropdown or sticky bar with no z-index, and the referrer is the
398
+ page's to set, see the README's collection rules.)
399
+ - shell.css: the topbar's actions column never goes narrower than what it holds (`minmax(max-content, 1fr)`, and
400
+ `max-content` under 1120px), and the search column gives way instead (`minmax(0, …)`). With a 200px minimum the admin's
401
+ right-hand chips (~512px) spilled left over the search: 160px at 1280, 239 at 1121 (22/10/2026). The brand column is
402
+ unchanged (a surface's tabs there keep their scroller); with room to spare the search is centred as before. The
403
+ `max-width: 1040px` topbar rule, which the base rule after it always overrode, is removed.
404
+
405
+ Added
406
+ - `@gemboss/ui/editor-insert.css` (23/10/2026), its own entry: the page editor's insert menu, the + on a picked element (admin
407
+ `InsertElementMenu`). It is a list to search, with the row in focus described beside it, 32px rows (44px under a finger), and a
408
+ sheet along the bottom under 640px. It's not in editor.css because every editor surface loads that.
409
+ - IndexTable `flush` (root `.ui-index--flush`): inside a card that is already the frame, as DataTable's and ResourceList's. The
410
+ table drops its own border, radius and shadow; the bulk bar covers the 37px header and draws its rule; folded, the bar sits on
411
+ the first row and the sort chips are inset 12px like the rows. partner-radar and talent-radar drew two frames (23/10/2026).
412
+ - `Segmented` takes `scroll`: text tabs keep one line and the group scrolls sideways inside itself when it is wider than its
413
+ room, what kit-plain.css already does for plain surfaces. Set as layout styles on the component (gemboss-ui.css had no
414
+ bytes left under its weight ceiling); opt-in; first user the admin's Plugins filter (five tabs broke to three lines each at
415
+ 390, 22/10/2026).
416
+ - `AssistantHost` takes `waiting`: the chat's last answer ends on choices only the person can make. The status bar and the
417
+ header say "Waiting on you" with an amber dot (`--gemboss-warning`, set on the dot: the bundle is at its gzip ceiling), ahead of "Done" and "Ready". It is a prop, not dock
418
+ state, so the plain frame's reducer copy is unchanged. New label `waiting`.
419
+ - assistant-chat.css `.gemboss-ec-decide` / `-decide-label`: the box that holds a waiting question's choices over the message box
420
+ (22/10/2026).
421
+ - `Stage`, `StageWindow`, `StageTile`, `StageBubble`, `StageLine` (`stage.css`, its own entry): the one way the app draws a
422
+ picture, taken from gemboss.ai's mega menu: a night-blue stage lit with iris, a dot grid fading out, glass tiles (one picked,
423
+ white and glowing), white windows lifted off it showing a real screenshot. Its colours are named once on `.ui-stage`
424
+ (an illustration may light itself, website/DESIGN-LANGUAGE.md §3). A stage is hidden from screen readers unless
425
+ `decorative={false}` (a panel holding words a reader needs); `StageWindow` then takes `alt` for its screenshot.
426
+ - `EmptyStage` (`empty-stage.css`, its own entry): an area with nothing in it yet, centred like an admin empty state: a
427
+ Stage picture drawn from the area's own nouns, a name, one line, the page's own buttons (`.ui-empty-stage__row` lays tiles
428
+ side by side). Replaces the picture-less empty states (22/10/2026).
429
+ - `StartingPoint` (`starting-point.css`, its own entry): "Choose your starting point", the same three doors wherever something new
430
+ is made: ask the assistant (a two-line chat on the stage), a template (two real pages fanned on the stage, `images`), blank (an
431
+ empty window with "+ Add a section"). Each door is a picture, a name, one line and a button; at most three. Learned from
432
+ Replo's Plans, Tasks, Skills and reports (22/10/2026).
433
+ - `ChatStarter` takes `sub` (one line under the label) and `icon`; a list where any starter has either is drawn as a column
434
+ of cards (`.gb-chat-starters-cards`: icon in an iris tile, label, the line under it). Pills are unchanged.
435
+ - `firstBlank(text)` and `selectBlank(textarea, text)`: a starter with `fill` now selects the first `[…]` in its prompt, so
436
+ typing replaces it ("Build a funnel for [which product?]"); with no blank the caret goes to the end (22/10/2026).
437
+
438
+ Changed
439
+ - collections.css: an index table's header is the data table's (the surface, 13px regular, 12px above and below: 45 tall,
440
+ opaque) and its cells 8px 6px (a one-line row 37), taken from the data table's rules in ui.css rather than restated. It was Polaris IndexTable's grey band, 12px / 550, 36 tall, over 6px cells: two
441
+ looks for one thing, the heavier one on the lists people open (Chris 23/10/2026: "GemPress's table reads lighter than
442
+ Funnels"). Its bulk bar is 46 (the wrap's top line + the header), 45 flush, 38 folded below 768, wherever in the index
443
+ it sits; a resource list's stays 38. The admin's unselectable Polaris IndexTables take the same (gemboss #5185).
444
+ - `SessionRail` (and `sessionRail` in session-rail-plain.js): a conversation's `preview` follows its time on the same line,
445
+ "3 hr ago · Nothing is published yet…", one line cut with an ellipsis (`.gemboss-assistant-thread-meta`, shell.css). The
446
+ admin now sends the answer's closing sentence as `preview`, how the conversation ended (23/10/2026, learned from Replo).
447
+ - editor.css: the page editor's column (`.gemboss-pageedit .gemboss-ec-dock-body`: its section list and the element settings) is
448
+ 44px tall under a finger and at a phone's width only; under a mouse from 48em its buttons, fields and selects are the kit's own
449
+ sizes, as the same settings panel on the canvas (they were 44 at every width: 44 against 32 for the same panel, 22/10/2026).
450
+ - editor.css: the page editor's icon buttons (`.gemboss-pageedit .gemboss-pv-device`: ↶ ↷, ⋯) are 44 × 44 under a finger and
451
+ at a phone's width only; under a mouse from 48em they are the kit's 28 × 28, as on every other editor bar (they were 44 at
452
+ every width, 21/10/2026).
453
+
454
+ **The briefing card leaves its picture out when the card is too narrow to hold it** (Market, 22/10/2026: with the assistant pinned beside the page the
455
+ card was 693px wide and 510px tall, the gem under the buttons).
456
+
457
+ Changed
458
+ - `.ui-briefing` is a size container (`container-type: inline-size`) and `@container (max-width: 631px)` hides `.ui-briefing__art`. 631 is the
459
+ content width the picture's row needs (380 text + 32 gap + 220 picture = 632) less one: a container query measures the content box, so it
460
+ is the card's 720px at the desktop padding. It is the CARD that is measured, not the screen: the same card is wide on a desktop and
461
+ narrow beside a pinned panel. Measured in Chromium at a 1440px window: picture beside the text at 720px and wider, none at 719px and
462
+ narrower, and the card 258px tall at 693px instead of about 430. `briefing-card.test.tsx` holds the rule.
463
+
7
464
  ## 0.48.0 (21/10/2026)
8
465
 
9
466
  **LanguageSwitcher: what its first three surfaces had to work around** (21/10/2026; GemCommunity #333, GemNews #2,