@gemboss/ui 0.70.2 → 0.73.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 (141) hide show
  1. package/CHANGELOG.md +633 -3
  2. package/README.md +170 -11
  3. package/catalog/editor.html +1 -1
  4. package/catalog/index.html +48 -46
  5. package/gemboss-ui.css +4 -4
  6. package/package.json +32 -1
  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-nav.css +1 -1
  11. package/src/app-shell.css +1 -1
  12. package/src/assistant/chat-cards.tsx +118 -19
  13. package/src/assistant/chat.tsx +209 -22
  14. package/src/assistant/composer-menus.tsx +7 -2
  15. package/src/assistant/dock.ts +97 -10
  16. package/src/assistant/figures.tsx +119 -0
  17. package/src/assistant/gallery.tsx +67 -0
  18. package/src/assistant/hold.ts +51 -0
  19. package/src/assistant/host.tsx +258 -137
  20. package/src/assistant/ideas.tsx +90 -0
  21. package/src/assistant/index.ts +12 -3
  22. package/src/assistant/plus.tsx +61 -0
  23. package/src/assistant/provider.tsx +121 -24
  24. package/src/assistant/sessions.tsx +54 -20
  25. package/src/assistant/window-host.tsx +215 -0
  26. package/src/assistant/window.ts +120 -0
  27. package/src/assistant-chat.css +1 -1
  28. package/src/assistant-figures.css +1 -0
  29. package/src/assistant-hold.css +1 -0
  30. package/src/assistant-places.css +1 -0
  31. package/src/assistant-plain.js +1 -1
  32. package/src/assistant-plus.css +1 -0
  33. package/src/assistant-window-plain.js +1 -0
  34. package/src/assistant-window.css +1 -0
  35. package/src/assistant.css +1 -1
  36. package/src/auth-extras.css +1 -1
  37. package/src/auth-footer.css +1 -1
  38. package/src/auth-steps.css +1 -1
  39. package/src/auth.css +1 -1
  40. package/src/board-move.ts +2 -1
  41. package/src/chat-attachments.css +1 -1
  42. package/src/chat-cards-drawn.css +1 -0
  43. package/src/chat-cards-float.css +1 -0
  44. package/src/chat-cards.css +1 -1
  45. package/src/chat-composer-menus.css +1 -1
  46. package/src/chat-composer.css +1 -1
  47. package/src/chat-plain.js +6 -6
  48. package/src/chat-shortcuts.css +1 -0
  49. package/src/chat-voice.css +1 -1
  50. package/src/chat.css +1 -1
  51. package/src/chips-drawn.css +1 -0
  52. package/src/collections.css +1 -1
  53. package/src/collections.tsx +4 -2
  54. package/src/create-shell.css +1 -1
  55. package/src/dialog.css +1 -1
  56. package/src/editor/choice-cards.tsx +8 -5
  57. package/src/editor/controls.tsx +36 -9
  58. package/src/editor/field-control.tsx +17 -3
  59. package/src/editor/field-spec.ts +17 -4
  60. package/src/editor/index.ts +2 -0
  61. package/src/editor/media-words.ts +21 -0
  62. package/src/editor-color.css +1 -1
  63. package/src/editor-empty.css +1 -0
  64. package/src/editor-insert.css +1 -1
  65. package/src/editor-inspector-frame.css +1 -1
  66. package/src/editor-media.css +1 -1
  67. package/src/editor-picker-grid.css +1 -1
  68. package/src/editor-picker.css +1 -1
  69. package/src/editor-popover.css +1 -1
  70. package/src/editor-repeater.css +1 -1
  71. package/src/editor-tiles.css +1 -1
  72. package/src/editor.css +1 -1
  73. package/src/email-canvas.css +1 -0
  74. package/src/email-card.tsx +44 -0
  75. package/src/email-editor/canvas.tsx +109 -0
  76. package/src/email-editor/editor.tsx +45 -4
  77. package/src/email-editor/index.ts +2 -1
  78. package/src/email-editor/model.ts +9 -1
  79. package/src/email-editor.css +1 -1
  80. package/src/email-parts.css +1 -0
  81. package/src/email-parts.tsx +81 -0
  82. package/src/email-thumb.css +1 -0
  83. package/src/email-thumb.tsx +206 -0
  84. package/src/feedback-dialog.css +1 -0
  85. package/src/feedback-dialog.tsx +122 -0
  86. package/src/flow-strip.css +1 -0
  87. package/src/flow-strip.tsx +50 -0
  88. package/src/gemboss-field-drawn.css +1 -0
  89. package/src/gemboss-field.css +1 -1
  90. package/src/gems.css +1 -1
  91. package/src/icon-frame.tsx +31 -0
  92. package/src/icons.tsx +9 -9
  93. package/src/index.ts +12 -0
  94. package/src/job-card.css +1 -1
  95. package/src/kit-plain.css +1 -1
  96. package/src/kit-plain.js +1 -1
  97. package/src/language-switcher.css +1 -1
  98. package/src/list-page.css +1 -1
  99. package/src/list-page.tsx +6 -3
  100. package/src/list-toolbar.css +1 -1
  101. package/src/media-card.css +1 -0
  102. package/src/members.css +1 -1
  103. package/src/menu-extras.css +1 -1
  104. package/src/menu-layer.ts +2 -0
  105. package/src/menu-select.css +1 -1
  106. package/src/menu.css +1 -1
  107. package/src/menu.tsx +9 -4
  108. package/src/narration.css +1 -1
  109. package/src/pager-extras.css +1 -1
  110. package/src/pager.css +1 -1
  111. package/src/picture-actions.css +1 -0
  112. package/src/picture-actions.tsx +23 -0
  113. package/src/portal.css +1 -1
  114. package/src/question-card.css +1 -1
  115. package/src/rail-fold.css +1 -1
  116. package/src/reactions.css +1 -1
  117. package/src/reader-dialog.css +1 -1
  118. package/src/report-charts.css +1 -1
  119. package/src/segmented.tsx +6 -0
  120. package/src/service-switcher.css +1 -1
  121. package/src/session-rail-plain.js +1 -1
  122. package/src/settings-dialog.css +1 -1
  123. package/src/setup-guide.css +1 -1
  124. package/src/sheet.css +1 -1
  125. package/src/shell.css +1 -1
  126. package/src/shell.tsx +9 -2
  127. package/src/site.css +1 -1
  128. package/src/skill-card.css +1 -1
  129. package/src/skill-flow.css +1 -1
  130. package/src/skill-pages.css +1 -1
  131. package/src/skill-view.css +1 -1
  132. package/src/stage-path.css +1 -1
  133. package/src/stat-tile.css +1 -0
  134. package/src/stat-tile.tsx +39 -0
  135. package/src/status-list.css +1 -1
  136. package/src/team-chat.css +1 -1
  137. package/src/tray-plain.js +1 -0
  138. package/src/tray-search.tsx +116 -0
  139. package/src/tray.css +1 -0
  140. package/src/tray.tsx +250 -0
  141. package/src/ui.css +1 -1
package/CHANGELOG.md CHANGED
@@ -4,6 +4,637 @@ 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.73.0 (16/11/2026)
8
+
9
+ **Every chip in `.ui-chips` is drawn at its mouse 30 in the finger tier, toggles and phone widths included** (16/11/2026; Chris 13/11:
10
+ "vẽ 28, khối 44", then "làm đi" on the chips). 0.72.0's chips-drawn.css drew only a link chip and only under a coarse pointer: a toggle
11
+ chip (`.ui-chips > button.ui-tag--chip`, kit-plain.css: GemCommunity's member directory and access pickers) still drew its whole 44, and
12
+ a mouse at phone width (the kit's finger tier is `(pointer: coarse), (max-width: 47.9975em)`) got no drawing at all.
13
+ - `chips-drawn.css` now works in the kit's finger tier, on every `.ui-chips > .ui-tag--chip` (a link, a toggle, a static chip beside
14
+ them), and gives a link chip its 44 floor there too, as a toggle already had (ui.css floors a link only under a coarse pointer; a
15
+ surface that added the width itself, as GemCommunity's globals.css, can drop it).
16
+ - The drawing is placed `clamp(-1px, 50% - 15px, 6px)` from the padding edge instead of 6px: a 44 box draws 30, a chip nobody floored
17
+ (a static 26) draws its whole box instead of 12px less, a label on two lines keeps 7px around it.
18
+ - `chips-drawn-size-browser.test.ts` adds the toggles, a two-line label, a static chip and a mouse at 390; run on 0.72.0's rules it
19
+ fails on the toggle (`[44, null]`, drawn whole). Measured 394 B gzip; its ceiling stays 831.
20
+
21
+ **The toast's action and ✕ are 44 and 48px boxes, drawn at their desktop size** (15/11/2026; "vẽ 28, khối 44", Chris 13/11). On a
22
+ phone the admin's "Open Pages on a computer. · Send the link" toast is the way to a computer's screen; at 390 with touch its action
23
+ was 99×26 and its ✕ 24×24. In the base rules, not a finger-only block (a bigger box under a mouse draws nothing different, and a media
24
+ block cost more than `gemboss-ui.css` had left). Every number on the space scale (the typography gate refused 10 and −9): the ✕ is 48
25
+ with 12px around its chip and `margin: -12px`, so its margin box is the old 24px chip, painted in the content box, and its hover sets
26
+ `background-color` so the chip stays clipped; the action is 44 with `margin-block: -8px`, so the pill grows 2px. `toast-drawn-size-browser.test.ts`
27
+ measures it as written and through the admin's cssnano. `gemboss-ui.css` ceiling 23523 → 23540 B gzip (on node 24 as CI: main 23510, with
28
+ these rules 23530, +20 B), Chris's OK 15/11.
29
+
30
+ ## 0.72.0 (15/11/2026)
31
+
32
+ Never published: npm goes 0.71.0 → 0.73.0, which carries everything below as well. Read both sections when upgrading.
33
+
34
+ **The email editor draws the real email on its stage: `EmailCanvas`, `canvas="real"`, the brand row; products keep `layout` and
35
+ `button_style`** (15/11/2026; canvas NqQGmVzRJMjv536LLbMGaT Q1, Q2, J1 G31; gemreach #183). The editor drew the mail itself: the store's
36
+ name where the brand kit has a logo, black buttons where the brand's are green, columns without their pictures; only "As sent" was the email.
37
+ - `EmailCanvas` (`@gemboss/ui/email-editor`, its own entry `email-canvas.css`): the sender's HTML in `<iframe srcdoc sandbox="allow-same-origin">`
38
+ (no script; the same origin lets the editor read where each block stands and hear a click), each `data-gr-block` pickable, the picked
39
+ one ringed on its own box with its name and Edit · ↑ · ↓ · Delete outside it (a heading's ring never covers the logo), Desktop at 640,
40
+ Mobile at 390 in a phone's frame, Dark through the frame's colour scheme, a new build dimming the last.
41
+ - `EmailEditor` `canvas="real"` draws the stage with it under the envelope once `sent.html` is there; "As sent" then only hides the
42
+ picking. `brandRow` puts the brand kit's logo, its button colour and Edit at the top of Sections.
43
+ - `ProductsBlock` `layout` (`grid` | `card`; `list` is the default, never stored) and `button_style` (`secondary`), offered in the block's
44
+ settings (Layout · Buttons); an edit elsewhere keeps them, so a save no longer turns a grid back into a list.
45
+ - `email-canvas-browser.test.tsx` holds it in Chromium (a click picks the block and the ring is its box below the logo, a link goes
46
+ nowhere, the frame is the email's height, no script runs; negative control: a click outside every block picks nothing).
47
+
48
+ **Emails as themselves: `EmailThumb`, `EmailCard`, `PictureActions`, `ThumbCell`, `FlowStrip`, `StatTile`, `EmailParts`** (15/11/2026;
49
+ Chris approved canvas NqQGmVzRJMjv536LLbMGaT, "bám sát mà làm", and J2 Q9: real thumbnails from an iframe first). GemBoss Reach and
50
+ GemReach's Ops console drew every email as the same drawn envelope (G30, G32); the boards draw the store's real emails, and mark six
51
+ pieces "kit cần thêm". Each is its own entry, with its ceiling: email-thumb.css, picture-actions.css, flow-strip.css,
52
+ stat-tile.css, email-parts.css (README "Emails as themselves").
53
+ - `EmailThumb`: the email's HTML in `<iframe srcdoc sandbox="">`, laid out at 664px and scaled into a card (4:3), a 96×72 row or a
54
+ 56×42 one; lazy (200px before the screen, four at a time, kept per `cacheKey`), the skeleton sheen until it draws.
55
+ - `EmailCard`: MediaCard at 4:3 + EmailThumb + PictureActions. `PictureActions`: Preview · Edit · More on a light scrim on hover, a
56
+ secondary button on a picture drawn white. `ThumbCell`: a cell with a picture, a name, its context and one more line.
57
+ - `FlowStrip`: start, waits, emails and splits in a row joined by arrows. `StatTile`: label, number, one line, sparkline.
58
+ - `EmailParts`: the top and the foot of the real email beside the Email brand card (R1), the foot ringed while the address waits (R2).
59
+ - **`media-card.css` (needs Chris's OK, the core is frozen):** the media card's rules move out of kit-plain.css to their own file just
60
+ before it, same rules, same order, no new weight (as menu.css, pager.css and report-charts.css did): the admin never loads
61
+ kit-plain.css, so a `MediaCard` there had no picture frame, no 4:3 and no title link over the card. `EmailCard` imports it.
62
+
63
+ **`AppNav` speaks the rail's words** (15/11/2026; Chris 14/11 kept the plugin's own column over tabs, "khó mở rộng", and left the rest
64
+ to us; canvas https://claude.ai/artifact/Bef9bXC2ezokroNzB9rBLw, way 2). The column, its grey, its header and its foot stay. In
65
+ `app-nav.css`:
66
+ - a group's heading is drawn as the rail's "Advanced" (`rail-fold.css` `.gnav-head`): `--gemboss-fs-micro`, 600, `.02em`, muted,
67
+ the word as written, no longer in capitals at `.04em`;
68
+ - the open row keeps its white fill and ring and carries the rail's "you are here" bar (`shell.css` `.gnav-subitem.active::before`:
69
+ 3×15, `--gemboss-primary`), 4px in from its edge. Not on a phone, where the open row is already a filled chip.
70
+ - `app-nav.test.tsx` holds both to the rail's own rules. `packages/ui/src/app-nav.css` stays under its ceiling (1.8 of 2.2 KB gzip).
71
+
72
+ **`consumeEscape` is exported** (14/11/2026, gemboss #7567). The kit's own layers already used it (Dialog, Popover, the pickers): it
73
+ stops an Escape's keydown AND the keyup after it, because a Polaris Modal closes on the keyup. The admin's update box, now frosted
74
+ whenever it is up, takes Escape at the window and needed the same, so a Polaris Modal behind its grey does not close with it.
75
+
76
+ **`AssistantChat` takes `shortPlaceholder`** (14/11/2026) and hands it to `ChatComposer`, which swaps to it when the full placeholder
77
+ does not fit the field (a ✦ or a chip in the lead takes room) and goes to two rows when even that does not. Found rolling 0.71.0 into
78
+ gemreach: its line was cut ("…reset khô") at every width, 130–275 px of field under a 307–367 px line. `chat-plain.js` already did this.
79
+
80
+ **A segmented control under a thumb is drawn at its desktop size, in 44px boxes** (14/11/2026; Chris 13/11: "vẽ 28, khối 44",
81
+ the control after the button). Measured on production at 390 with touch: groups were 46 tall.
82
+ - `ui.css`: under `(pointer: coarse), (max-width: 47.9975em)` each segment keeps its 44px box; the group's line is its `::before`, 28
83
+ tall in its middle, and a segment's fill, divider and picked line are the segment's `::before` at its declared height (26),
84
+ inheriting what the cascade gives the segment (hover, picked, a surface's colours). The group no longer clips (`overflow:
85
+ visible`); a picked segment is rounded on its own. Its clip is `!important`, as the button's: the picked and hovered rules set
86
+ `background` with the shorthand.
87
+ - ON UPGRADE: a surface whose segmented group WRAPS into rows draws a grid, not a 28 line: opt it out as the admin's link picker
88
+ does (gemboss-shell.css: group `overflow: clip; border-image: none`, both `::before` `content: none`, its segments' clip and
89
+ border-image back with `!important`). A segment that sets its own `height` (the editor's device switch, 44) is drawn at it.
90
+ - `segmented-drawn-size-browser.test.ts` reads it off the pixels (icons, words, links, the screen switch, the studio bar's 26 boxes,
91
+ the link picker's wrapped tabs), from the source and as next build minifies it, with its negative control.
92
+ - weight-budget.json: each ceiling moves by what this block adds, measured against main without it, so its slack is kept:
93
+ `gemboss-ui.css` 23,234 → 23,364 B gzip (+130), `parts/components.css` 8,889 → 9,017 (+122, and +6 for the outline fix, #7536),
94
+ `packages/ui/src/ui.css` 4,703 → 4,834 (+125, and +6 for #7536). Same reason as the button's: Chris chose this way knowing it adds CSS.
95
+
96
+ **Questions to try, at the end of a conversation** (13/11/2026, Chris: "a button that always suggests five more questions, so sellers
97
+ discover more"). On a phone the admin is Gem's chat, so asking is how a seller finds what is there.
98
+ - `ChatIdeasChip`: "Suggest questions", a 28px pill in the shape of Research's (44px under a finger), never gold. `aria-expanded`,
99
+ `aria-controls` when the tray is on the page.
100
+ - `ChatIdeasTray`: "Try asking", the chat's own chips (`.gemboss-ec-chip`, 44px always; a press is the surface's to send), "5 more" and a
101
+ close (both 44px under a finger). The surface owns the questions and what it has shown.
102
+ - Not in ChatComposer's strip: measured at 390 under a finger, "+", ✦, Research, the microphone and send leave 33px, and a chip there
103
+ was cut under the microphone. Styles in chat-composer-menus.css, which every Gem chat already loads.
104
+
105
+ **One vocabulary for picking a picture or a video** (13–14/11/2026, Chris on a library section's Video field: "chưa đúng chuẩn control";
106
+ gemboss #7449, #7483). New CSS-free entry `@gemboss/ui/editor/media-words` (re-exported by `@gemboss/ui/editor`):
107
+ - `MEDIA_PASTE_LABEL` ("Paste a URL"), now the default of MediaCard's `pasteLabel` (optional); `ImageControl` passes none.
108
+ - `mediaPickLabel(glyph, holds)`: a card's chip, "Select image" / "Select video", "Replace" once it holds media.
109
+ - `mediaActionLabel(glyph, holds)`: where the media is named (a menu row, a dialog's title), "Select image" / "Replace image".
110
+ editor-media.css: a broken VIDEO thumb is the video's icon struck through (`[data-thumb=broken][data-glyph=video]`); the broken rule set the
111
+ image's struck icon on every card. editor.css: `.gemboss-ei-hint--error`, a field's error line in the error tone (`--gemboss-danger-strong`,
112
+ EdField's error state); by class, not `[role=alert]` (some alert hints are notices, and a standing problem is no alert).
113
+
114
+ **The words typed in the composer take the panel's colour** (13/11/2026, Chris: "khi chuyển sang màu đen thì cái input text chữ nó ko
115
+ thành màu trắng"). chat.css `.gemboss-ec-input textarea` sets `color: inherit`: a textarea does not inherit colour (the browser gives it
116
+ `fieldtext`), so on Gem Plus's black Research panel the words were drawn rgb(0, 0, 0) on #17140f. Measured in Chromium: black panel
117
+ rgb(0, 0, 0) → rgb(242, 236, 223); the gold and the plain panels draw them in their text colour (rgb(48, 48, 48)) instead of pure black.
118
+ `font: inherit` replaces `font-family: inherit` (the size and line height are set after it): the words typed take the panel's weight,
119
+ 450 like every line of the conversation, where the textarea alone was 400; and the rule stays inside the frozen bundle's ceiling.
120
+
121
+ **Full screen wears Gem Plus's look** (13/11/2026, Chris: "giao diện chat khi chuyển sang full nó ko toàn bộ đen theo … hoặc vàng").
122
+ assistant-plus.css: `.gb-dock--plus` and `.gb-dock--gold` restate `--gemboss-app-bg`, the colour `.gb-dock-full` paints. Measured in
123
+ Chromium, full screen: rgb(255, 255, 255) → rgb(20, 18, 14) black, rgb(255, 252, 245) gold.
124
+
125
+ **The Research chip sits beside send, and the words keep their row** (13/11/2026, Chris: "cái research đẹp nhưng hơi tốn không gian của
126
+ input, có lẽ nó nên nằm về bên phải cạnh nút enter", then "làm đi").
127
+ - `ChatPlusChip` goes in ChatComposer `tools` (on the right, before the microphone and send), out of `leading`.
128
+ - **ChatComposer marks `stacked`** with `data-stacked` on its box, so a gate reading the box tells two rows on purpose from a box that
129
+ wrapped. The admin's Assistant stacks its box, one line tall while empty: the words take the box's whole width (357px in a 400px
130
+ panel, against 90–135px beside the chip), the toolbar under them ("+", ✦ on the left; the chip, the microphone and send on the right).
131
+
132
+ **The page behind a popup is frosted** (13/11/2026, Chris: "the design system has a frosted glass background under an overlay").
133
+ - `dialog.ui-modal::backdrop` (`Dialog`, `ConfirmDialog`, `FeedbackDialog`, the portal's search; `dialog.css` and `kit-plain.css`) and
134
+ `.ui-overlay` (`openModal`, `ui.css`) draw the ink at .22 under the kit's frost, `blur(14px) saturate(1.4)`. They were black .5
135
+ with no blur (0.7.3, Polaris's number).
136
+ - Two shapes keep a plain scrim and turn the frost off by name: the side panel, `Sheet` (`rgba(0,0,0,.3)`, as before), and the
137
+ popup the size of a screen, `ReaderDialog` and `SettingsDialog` (`rgba(0,0,0,.5)`, as before).
138
+ - ON UPGRADE: a surface's own popup on `dialog.ui-modal` or in `.ui-overlay` (`openModal`) gets the frost. One that is a side panel
139
+ or the size of a screen turns it off in its own sheet (`backdrop-filter: none`, prefixed too; for `openModal`, on its
140
+ `overlayClass`); a dark surface keeps a darker fill there. README "What lies behind a popup" has the table, the two snippets and
141
+ the tests that hold it.
142
+ - weight-budget.json: the frozen bundle `gemboss-ui.css` 22,949 → 22,987 B gzip (+38, nearly all of it the frost's text standing
143
+ once in `ui.css` for the overlay; with the dialog's rule alone it measured +3). Every other file is inside its ceiling. Chris's
144
+ OK, 13/11/2026 ("bạn quyết cho tôi", asked with the number).
145
+
146
+ **ChatComposer decides one row or two again when a web font lands** (13/11/2026, gemboss #7382: the admin's composer gate red at 1366,
147
+ "an empty box with room for its words is two rows", twice in three runs).
148
+ - `packages/ui/src/assistant/chat.tsx`: the rows and the density listen to `document.fonts` `loadingdone` (and `ready`). The lead's
149
+ chips and the short placeholder were measured in the fallback font (DejaVu on Linux, wider than Inter); a box that chose two rows kept
150
+ them once Inter left room for one, since nothing it watched changed size on two rows. Test:
151
+ `packages/ui/src/assistant/composer-rows-browser.test.tsx` (a font stood in by a stylesheet; red without the listener).
152
+ - Not in `packages/ui/src/chat-plain.js` yet: it has the same gap, and it sits at its weight ceiling to the byte (the smallest fix is
153
+ +2 B gzip).
154
+
155
+ **An outlined button keeps its outline under a thumb, as the admin ships it** (14/11/2026, fix of the entry below). next build's
156
+ minifier (cssnano-simple) merged `::before`'s three border longhands into `border: inherit`, which also inherits the button's empty
157
+ `border-image`: on production every outlined kit button ("Start a funnel" on Home at 390) drew no outline on a phone. `::before`
158
+ now declares `border-image: none` after them, which survives the merge.
159
+ - ON UPGRADE: nothing to do.
160
+ - `button-drawn-size-browser.test.ts` now also reads the file as next build minifies it, with a negative control (the minified rule
161
+ without `border-image: none` draws no outline). The source alone passed while production was broken.
162
+
163
+ **A button under a thumb is drawn at its desktop size, in its 44px box** (14/11/2026; Chris 13/11: "các control trên mobile cũng
164
+ phải chuẩn như trên desktop… nó bị to hơn", then, of two ways, "vẽ 28, khối 44").
165
+ - `ui.css`: under `(pointer: coarse), (max-width: 47.9975em)` a `.ui-btn` keeps its 44px box (the floors are unchanged: the target
166
+ is the button, and two buttons never share one), but its fill, border and corners are drawn by `::before` at the size the button
167
+ declares (`width`/`height`: 28, or 32 where the admin sets 32), centred. The button's own fill is clipped to its words and its
168
+ border is an empty `border-image`; `::before` inherits both, so variants, hover, ON and a surface's override follow by themselves.
169
+ - ON UPGRADE: nothing to do. A surface that draws its own `::before` on a `.ui-btn` loses it under a thumb (none in the fleet,
170
+ 14/11/2026). A `.ui-btn` on `<input>` would lose its fill there: use `<button>`.
171
+ - `button-drawn-size-browser.test.ts` reads it off the pixels in Chromium (a finger at 1366, a mouse at 390, a mouse at 1366
172
+ unchanged) with its negative control; seen the same in WebKit.
173
+ - weight-budget.json: `gemboss-ui.css` 23,038 → 23,154 B gzip (+116, the rule itself). Chris chose this way knowing it adds CSS;
174
+ the ceiling moves by what it measured.
175
+
176
+ **The account chip under a thumb is drawn at its desktop 32, in its 44px box** (14/11/2026, the next control of the entry above).
177
+ Measured on production at 390 with touch: the top bar's account circle was a 44px circle with its line, the one control of the
178
+ phone bar drawn bigger than on a desktop.
179
+ - `shell.css`: where the chip is a 44 box (`(pointer: coarse)`, and 306–460px), `::before` draws its 32 circle, inheriting its fill
180
+ and line so hover and the open menu follow; the chip paints its fill only under its letters and its line as an empty
181
+ `border-image`. `border-image: none` on `::before` survives next build's minifier (the outline fix, gemboss #7536).
182
+ - The admin's own top bar Gem door (`gb-tb-btn`, apps/admin gemboss-shell.css) declares 32 on a phone, so the kit draws it lit and
183
+ pressed at 32, not 44.
184
+ - `top-bar-drawn-size-browser.test.ts` reads both off the pixels, from the source and as next build minifies it, with a negative
185
+ control (the rules as they were draw the whole 44).
186
+ - weight-budget.json: `gemboss-ui.css` 23,154 → 23,234 B gzip (+80: this rule +74, and the outline fix +6, measured together so the
187
+ two do not turn main red once both land). Same reason as the entry above: Chris chose this way knowing it adds CSS.
188
+
189
+ **The chat's own controls under a thumb are drawn at their mouse 28, in 44px boxes** (14/11/2026; Chris 13/11: "vẽ 28, khối 44",
190
+ the controls after the button, the top bar and segmented). Measured on production at 390 with touch: New chat, Talk to a person,
191
+ ⋯, "+", Suggest questions and Send were drawn 44 (desktop 28).
192
+ - `chat.css`: under `(pointer: coarse), (max-width: 47.9975em)` the dock's `.gb-dock-shrink` and full-screen New chat, Send, Stop,
193
+ the paperclip, the mic and Suggest questions keep a 44px box; their fill, line and corners are their `::before` at the size they
194
+ declare (28), inheriting what the cascade gives them. Their touch rules (`assistant.css`, `chat-composer.css`,
195
+ `assistant-chat.css`, `chat-voice.css`, `chat-composer-menus.css`) keep the 28 declared and put 44 in the minimums; the bigger
196
+ touch glyphs and words went with it (drawn as under a mouse). "+" and ✦ are kit buttons (ui.css draws them); the box-shadow
197
+ hairline of "+" and of Suggest questions moves to the drawing; the mic's listening ring is 28.
198
+ - ON UPGRADE: a surface that sized one of these controls to 44 itself under a thumb is drawn at that 44: declare the mouse size and
199
+ 44 in the minimums instead.
200
+ - `chat-drawn-size-browser.test.ts` reads it off the pixels (390 with a mouse, the composer under a finger at 1366), from the
201
+ source and as next build minifies it, with its negative control. Research's pill (assistant-plus.css) follows once #7526 lands.
202
+ - weight-budget.json: `gemboss-ui.css` 23,364 → 23,523 B gzip (+159, what this adds, measured against main without it, so its
203
+ slack is kept). `packages/ui/src/chat.css` grows 207 B inside its own ceiling. Same reason as the button's: Chris chose this way
204
+ knowing it adds CSS.
205
+
206
+ **`RailCount` takes `dot`** (13/11/2026, Chris: "ở home chỉ là dấu chấm… inbox mới hiển thị số… để nhìn ko bị overlap duplicate").
207
+ - The folded rail's 8px dot in the full rail too, its count read as its label. For a row whose number is on the sub-row that opens
208
+ it: the admin's Home shows a dot for what needs the seller, Home › Inbox the number.
209
+
210
+ **Gem Plus's mode is Research; AssistantHost `gold`** (13/11/2026, Chris: "một mode là research bật lên là nó thành màu đen", "bản
211
+ growth là ai assistant dát vàng rồi").
212
+ - `ChatPlusChip` says Research (`CHAT_PLUS_LABELS`) with a magnifier.
213
+ - `AssistantHost gold`: `gb-dock--gold`, the plan's chat while Research is off: an ivory ground, a gold rule under the header, gold
214
+ accents and primary button (text accent #8f6514, AA on white), the seller's bubble cream, the Research chip outlined in gold. `plus`
215
+ wins over it. In `packages/ui/src/assistant-plus.css`, within its ceiling.
216
+
217
+ **Gem Plus: `ChatPlusChip` and AssistantHost `plus`** (13/11/2026, Chris on the Gem Plus boards, artifact DmPeQEJDAZXdiTxzmFv5UL: "đúng
218
+ chính xác rồi làm đi"; gemboss: the Assistant's composer and panel).
219
+ - `ChatPlusChip` (`@gemboss/ui/assistant`): Plus in the composer's chip strip, `locked` / `off` / `on`; locked is a door to the
220
+ surface's dialog, off / on a switch. `CHAT_PLUS_LABELS` are its words.
221
+ - `AssistantHost plus`: `gb-dock--plus` on the panel, the Plus look (obsidian and gold) by restating the chat's tokens.
222
+ - A new entry, `assistant-plus.css` (scripts/parts.mjs ENTRIES, export `./assistant-plus.css`), imported by plus.tsx and host.tsx;
223
+ weight-budget.json: `packages/ui/src/assistant-plus.css` 1578 B gzip (measured 1066 + 512 slack), a new component's own ceiling.
224
+
225
+ **`ChatComposerProps.stacked`: a box that is always two rows** (13/11/2026, gemboss New: "describe what I want" on top of New, "cao 2
226
+ dòng cho input cho sướng"). The text over the toolbar whatever the words' length, so an empty box shows its whole placeholder and does
227
+ not grow a row on the first wrap; nothing is measured for it. Off by default: every chat keeps one row while its words fit.
228
+ - Its text box is two lines tall unless `rows` says otherwise (`rows ?? (stacked ? 2 : 1)`), and changing `stacked` lays the box out
229
+ again.
230
+ - With an empty lead (no "+", no chips) it stands beside send as every bare box does, still two lines tall: no surface draws one,
231
+ and a CSS rule to put it over the toolbar pushed the admin dashboard's first load over its budget (gemboss #7380).
232
+ - chat-plain.js has no `stacked` yet: no plain caller needs one, and its 24 B would pass chat-plain.js's 9645 B ceiling.
233
+
234
+ **editor.css drops the theme editor's page picker trigger** (14/11/2026, gemboss #7504: the admin's theme editor is the try door's, its
235
+ seller's bar and PagePicker gone). `.gemboss-pagepicker`, `.gemboss-pagepicker > .gemboss-pagepicker-trigger`, its picture rules and its
236
+ 44px touch rule are removed; nothing draws them (the admin's `a-tap-target-rule-outlived-its-markup` caught the touch rule). The note
237
+ (`.gemboss-pagepicker-note`, `-note-link`) stays: the canvas's product picker draws it. ON UPGRADE: nothing, unless a surface drew its own
238
+ `.gemboss-pagepicker-trigger`.
239
+
240
+ **AssistantHost: full screen with no way back** (13/11/2026, Gems/CLAUDE.md §16, Chris: on a phone or a tablet the admin "chỉ có giao
241
+ diện chính là chat thôi").
242
+ - `onShrink` is optional. Absent, full screen draws no "Shrink to popup" (or "Back to the side panel") button, the small screen's ⋯
243
+ has no such row, and the ⋯ itself is not drawn when nothing else is in it. Every host that passes it today is unchanged.
244
+
245
+ **A menu's list is as wide as its rows** (13/11/2026, the Inbox's filter: "bóp nhỏ vào theo tiêu chuẩn nào đó … nhìn thưa rời rạc").
246
+ - menu-select.css: the list had a 280px floor for every select, so the Inbox's five one-word filters opened 280 wide from a 63px field.
247
+ It is now as wide as its longest row (as Polaris draws a Popover: no floor), never narrower than its field (a browser's own select
248
+ list), at most 420 unless the field is wider, never wider than the screen less its 8px edges. Rows with a line under their words
249
+ (MenuItem `description`: New moment, Who sees what) keep the 280 column.
250
+ - menu.css: a ⋯ menu's list is as wide as its longest row (it had a 220px floor, a "Mark all read" alone in a 220px box). Polaris
251
+ sets no floor. The core loses the declaration (gemboss-ui.css sits at its ceiling; a 112 floor gzipped 4 B over it).
252
+ - menu-layer.ts `floatMenu` and kit-plain.js set `--ui-menu-trigger` (the trigger's width) on every list they float: in the top layer
253
+ the list is fixed, and `100%` would be the screen's width. menu-select.css is the one reader today.
254
+
255
+ **ChatComposer decides its rows again when a stylesheet lands** (13/11/2026). A CSS chunk that loads after the box first measured (the
256
+ admin's Assistant in a production build) left it without the one-row rules (assistant-chat.css `[data-rows="1"]`): the toolbar sat under
257
+ the text, the box chose two rows with room for one, and nothing it watches changed when the rules arrived. The admin's composer gate read
258
+ it as "an empty box with room for its words is two rows" on six PRs from 13/11 13:44 UTC, the first 14 minutes after #7382 merged. Now
259
+ a `load` of a `<link rel="stylesheet">` (caught on capture) refits the rows and steps the chips' density again, as a web font's
260
+ `loadingdone` does. Reproduced in a rig that served those rules 1.2 s
261
+ late: two rows 12/12 before, one row 12/12 after; `composer-rows-browser.test.tsx` holds it, red without the listener.
262
+
263
+ **`ChatFigures`: figures under a chat answer** (13/11/2026, Gem Plus slice 2; boards artifact DmPeQEJDAZXdiTxzmFv5UL).
264
+ - `ChatFigures`, `CHAT_FIGURES_LABELS`, `figurePct` (`@gemboss/ui/assistant`): shares drawn under an answer as `ui-metrics` tiles and
265
+ `ui-barlist` rows (a compared row: the group's share as the bar, everyone's beside it), a caption per figure (what it measures, its
266
+ base as a floor), the source line.
267
+ - A new entry, `assistant-figures.css` (scripts/parts.mjs ENTRIES, export `./assistant-figures.css`), imported by figures.tsx after
268
+ report-charts.css; weight-budget.json: `packages/ui/src/assistant-figures.css` 764 B gzip (measured 252 + 512 slack).
269
+
270
+ **`ChatPageGallery`: real pages under a chat answer** (13/11/2026, Gem Plus slice 3).
271
+ - `ChatPageGallery`, `CHAT_GALLERY_LABELS` (`@gemboss/ui/assistant`): two to a row, picture (4:5, its top), label, line, and a real
272
+ link "Use this layout" (`onUse(href)` on a plain press). Its frame joins `assistant-figures.css` (parts.mjs `by` gains gallery.tsx):
273
+ 252 → 454 B gzip, under its 764 B ceiling.
274
+
275
+ **ChatComposer `shortcuts`: "/" lists questions** (13/11/2026, Gem Plus slice 4; board C3 "Gõ / ra lối tắt").
276
+ - `shortcuts` (`ChatShortcut`: label, prompt, sub) and `shortcutsLabel`: a "/" at the start of the box lists them over the text box
277
+ (a row of its own, as the note above), filtered by every word after the slash, six at most; ↑/↓ move, Enter or Tab (or a press)
278
+ put the question in the box to edit or send, Escape closes the list at that text. `aria-autocomplete="list"`, the list a listbox
279
+ the text box points at (`aria-controls`, `aria-activedescendant`). `shortcutMatches` is the filter. Absent: "/" is a character.
280
+ - A new entry, `chat-shortcuts.css` (parts.mjs ENTRIES, export `./chat-shortcuts.css`), imported by chat.tsx: the list's rules, out of
281
+ chat-composer-menus.css, which "Suggest questions" (#7459) brought to its 1288 B ceiling; weight-budget.json 891 B (measured + slack).
282
+ A row is 44px under a finger.
283
+
284
+ **Board: a card can be `fixed`** (BoardCard, 14/11/2026, Operator › Tasks: a running job beside the seller's ideas).
285
+ - It is drawn without the drag and the keyboard pick-up while its neighbours keep both, and the board's drag never lifts a card that
286
+ is not draggable (a link inside it is, by default). src/board-fixed.test.tsx.
287
+
288
+ **"Gem is waiting on you" stands out, says how it is answered, and takes several picks** (14/11/2026, Chris: "nên có màu khác … để nó
289
+ nổi lên trên cái chat này … vẫn thẩm mỹ và theo design system"; "các lựa chọn luôn phải có Something else"; one answer is a radio,
290
+ several are tick boxes, and a tick can come with words of one's own).
291
+ - `.gemboss-ec-decide` is Gem's iris instead of white with a gold line: `accent-wash` ground, `accent-tint` edge, QuestionCard's 3px
292
+ `accent-soft` ring; its line `accent-strong` after an iris dot. A question is not a warning, so the warning gold is gone. No motion.
293
+ - `ChatDecide` takes `how` ("Pick one", "Pick any"), drawn after the line, quieter, outside the group's name.
294
+ - `ChatChoices` takes `pick: "one" | "many"`. "one": a round mark on every row of a poll (a chip among the cards becomes a row), a press
295
+ answers as before. "many" with `onSend(picked, other)`: real check boxes behind their rows, Something else a tick whose row opens a
296
+ `gemboss-field`, a count and Send (`sendLabel`, `pickedLabel`); Enter in the field sends; a new question starts unticked.
297
+ - `other` (Something else) is now drawn on a chip row too, as its last chip (`.gemboss-ec-chip-other`, dashed), not on polls only.
298
+ - A choice's label wraps an unbroken word (`overflow-wrap: anywhere`): a product title or URL pushed a 320px panel sideways.
299
+ - Several picks answer once per question (a double press, or Enter then Send, before the surface turns busy sends nothing more), and a
300
+ press on Something else's caption unticks it without hiding the words typed there (typing ticks it again).
301
+ - The box's whole look moved to ChatDecide's own sheet, `chat-cards.css` (one owner, CLAUDE.md §9.3); `assistant-chat.css` keeps only
302
+ where it sits against the message box. A surface that re-themes the accent (Growth's gold panel) re-themes the box with it.
303
+ - Weight: `chat-cards.css` 2.4 of its 2.4 KB ceiling, `assistant-chat.css` 1.3 of 1.4 KB. No ceiling raised.
304
+
305
+ **A switch with nothing chosen marks the option the page draws** (14/11/2026, editor standard layer 5: an empty field says what the
306
+ page draws; an element's Letter case is two chips, None · AA, with no box to say it in). `SegmentedOption.drawn` / `SegOption.drawn`:
307
+ not pressed, that chip wears the empty field's face, a dashed ring inside it in `--ui-text-muted` (editor-empty.css `.ui-seg>[data-drawn]`),
308
+ and says "Not set: what the page draws now" (`aria-description`), as an empty list says the drawn value greyed. `FieldSpec` segmented
309
+ takes `drawn` (the option's value); FieldControl marks it only while nothing is stored, and a value the chips do not offer marks none.
310
+
311
+ **`.gemboss-page-draft-status` removed from editor.css** (14/11/2026). The admin's page opening (PageOpening) was the last markup
312
+ carrying it; it now draws the canvas's board, where every way into a page lands (gemboss, New opens on the canvas). No other repo used it.
313
+
314
+ **Gem Plus is the plan, not a mode: one Plus look, a chip that says Plus** (14/11/2026, Chris: "giao diện vàng là được rồi còn ko cần
315
+ phải bật tắt research mode, đổi cái label research đó thành Plus", then "merge cái màu đen với cái màu vàng làm một… và phân biệt với
316
+ cái màu trắng (chưa upgrade)").
317
+ - `ChatPlusChip`: named **Plus**, two states, `locked` (a lock) and `on` (gold); `off` is gone. A press opens what Plus is in both
318
+ (`aria-haspopup="dialog"`), it switches nothing (no `aria-pressed`). `CHAT_PLUS_LABELS` is `{ name, locked, on }`; the icon is ✦.
319
+ - `AssistantHost`: `gold` is gone with the ivory gold panel (`.gb-dock--gold`); `plus` is the one Plus look, obsidian and gold, for a
320
+ store whose plan has it. A store without it keeps the white panel. assistant-plus.css: 1.1 KB gzip, smaller.
321
+
322
+ **The Plus chip under a thumb is drawn at its mouse 28, in its 44px box** (15/11/2026; Chris 13/11: "vẽ 28, khối 44", the composer's
323
+ last control drawn 44: measured on production at 390 with touch, after the chat's own controls went to 28).
324
+ - `packages/ui/src/assistant-plus.css`: under `(pointer: coarse), (max-width: 47.9975em)` the chip keeps its declared 28, its mouse
325
+ padding and its 12px words, and puts 44 in its minimum; its fill is clipped to its words and its ring dropped, and its `::before`,
326
+ at the declared 28, inherits the fill (locked white, the gold, either hover) and wears the ring of its state (the hairline locked,
327
+ the gold line and glow on). As Suggest questions beside it is drawn; here because this sheet is the chip's one owner.
328
+ - `chat-drawn-size-browser.test.ts` reads it off the pixels (locked and on, at 390 and under a mouse at 1366), from the source and as
329
+ next build minifies it, with its negative control (main's rule before this, `height: 44px`, draws the 44 whole).
330
+ - assistant-plus.css: 1.2 KB gzip, under its 1,578 B ceiling.
331
+
332
+ **A chat CTA and a page card's Open under a thumb are drawn at their mouse size, 38 and 32, in their 44px box** (15/11/2026; Chris
333
+ 13/11: "vẽ 28, khối 44"). Measured on production at 390 with touch: "Open in Tests" was drawn 44 under a composer drawn 28.
334
+ - New entry `packages/ui/src/chat-cards-drawn.css` (`@gemboss/ui/chat-cards-drawn.css`), imported by `chat-cards.tsx` after
335
+ chat-cards.css (and by the admin's FunnelBuildPanel). Born an entry: in chat-cards.css these rules put it 190 B gzip over its
336
+ ceiling, so chat-cards.css is untouched. Its ceiling: 912 B gzip (measured + slack).
337
+ - The button's fill is clipped to its words, its line and glow dropped (`!important`), and its `::before`, inset by half the
338
+ difference, inherits the fill and the line and wears the glow. The glow is `--gemboss-ec-cta-glow`: chat-cards-drawn.css restates
339
+ chat-cards.css's value, and `packages/ui/src/assistant-plus.css` now draws Gem Plus's gold one through the same variable.
340
+ - `chat-drawn-size-browser.test.ts` reads it off the pixels (ghost, primary, Gem Plus's primary, a page card's Open; 390 and a mouse
341
+ at 1366), holds the glow under a finger equal to the glow under a mouse, and its negative control draws the 44 whole without the entry.
342
+
343
+ **The question waiting on the person floats over the thread** (15/11/2026; Chris: "nó là popup… hiệu ứng gương mờ đè lên content bên
344
+ dưới", "tối ưu không gian", "nếu dài có scroll ko"). New entry `chat-cards-float.css`, imported by `chat-cards.tsx` after
345
+ `chat-cards.css` (that sheet was at its weight ceiling). `ChatDecide` placed last in the thread's scroll (`.gemboss-ec-scroll >
346
+ .gemboss-ec-decide`) sticks to its foot, frosted with the dock's numbers (blur 14px, saturate 1.4, the wash at 82%; solid where
347
+ `backdrop-filter` is missing), never taller than `min(55vh, 420px)` (the choices scroll inside, the line and the question stay), its
348
+ choices in a grid (3 in one row at 1366, one per row on a phone). Measured before at 1366×900 with the box under the thread: 3 choices
349
+ took 246px and left the thread 401px, 8 left it 81px. ON UPGRADE: put the box inside your thread's scroll to get the float; outside it, it
350
+ keeps its place and only gains the frost, the cap and the grid. `assistant-chat.css` drops `.gemboss-ec-decide + .gemboss-ec-input`.
351
+ On a Mac, End in "Something else"'s field scrolls the choices (a scrolled view); ⌘→ goes to the end.
352
+
353
+ **A field made of parts under a thumb or at a phone's width is drawn at a Polaris field's size there, in its 44px box** (15/11/2026;
354
+ Chris 13/11: "vẽ 28, khối 44", the field after the button; 36 on a phone chosen under his delegation, as the admin draws Polaris's
355
+ TextField and Select, gemboss #7639). Measured on production at 390 with touch: Settings' "Search settings" was drawn 44 above
356
+ Account's Polaris fields.
357
+ - New entry `packages/ui/src/gemboss-field-drawn.css` (`@gemboss/ui/gemboss-field-drawn.css`, born an entry: gemboss-field.css is in
358
+ the frozen bundle, and these rules would have raised `gemboss-ui.css` by 119 B and `parts/components.css` by 125 B over their
359
+ ceilings). A surface that draws `.gemboss-field--group` links it: the admin's SettingsDialog imports it (the one group on its phone
360
+ screens). Not an @import in gemboss-shell.css, whose imports some 30 harnesses read by name. Its ceiling: 942 B gzip (430 measured + slack). The frozen bundle does not move.
361
+ - Under `(pointer: coarse), (max-width: 47.9975em)` a `.gemboss-field--group` keeps its 44 box and is drawn 36 (its words are 16px
362
+ there), and 32 under a finger from 48em; its fill is clipped to its words and its border hidden (`!important`, as a kit button's),
363
+ and its `::before` inherits them, so hover, focus and an error follow. The focus ring moves to the drawing; the group no longer
364
+ clips. Not a group with a colour swatch (the swatch is the whole 44 target) nor the editor's colour group (its hairline is full
365
+ height). A bare `input.gemboss-field` has no `::before` and is drawn 44 still.
366
+ - `gemboss-field-drawn-size-browser.test.ts` reads it off the pixels (390 with a finger and a mouse, 1024 with a finger, 1366 with a
367
+ mouse; an error, the focus ring; the two that keep their box), from the source and as next build minifies it, with its negative
368
+ control (the field's sheet alone draws the 44 whole).
369
+
370
+ **A link chip under a thumb is drawn at its mouse 30, in its 44px box** (15/11/2026; Chris 13/11: "vẽ 28, khối 44", then "làm đi" on
371
+ the chips). `.ui-chips > a.ui-tag--chip` is 30 tall under a mouse at every width and got a 44 floor under a coarse pointer, which drew
372
+ the whole 44: filter rows on GemCommunity, GemFeedback, GemReach and the toolkits looked a size bigger on a phone.
373
+ - New entry `packages/ui/src/chips-drawn.css` (`@gemboss/ui/chips-drawn.css`), born an entry: ui.css is in the frozen bundle
374
+ (gemboss-ui.css 7 B under its ceiling). Its ceiling: 831 B gzip (measured + slack). The bundle does not move.
375
+ - ON UPGRADE: link `@gemboss/ui/chips-drawn.css` after gemboss-ui.css (or the parts) on a surface that draws `.ui-chips`. Without it
376
+ the chips stay as they were (drawn 44 under a finger).
377
+ - Under `(pointer: coarse)` the chip keeps its 44 box; its own fill is clipped to its words and its line hidden (`!important`), and
378
+ its `::before`, 7px in top and bottom, inherits them, so the picked tone and hover follow; the focus ring moves to the drawing. A
379
+ chip shorter than 44 stays 44 wide (its floor), drawn as wide.
380
+ - `chips-drawn-size-browser.test.ts` reads it off the pixels (under a finger: 44 box, drawn 30, the page outside the drawing, the
381
+ picked tone inside it, the ring on it; under a mouse at 1366 and 390: its own 30), from the source and as next build minifies it,
382
+ with its negative control (ui.css alone draws the 44 whole).
383
+
384
+ ## 0.71.0 (13/11/2026)
385
+
386
+ **A hover tint only where a pointer hovers; the chat's markdown in every engine; the left panel's seam within reach** (13/11/2026,
387
+ reviews of the 0.70.2 rollout and of the Gem chat display modes; Chris on the live admin: "stick on the left cũng phải có resize như
388
+ stick on the right").
389
+ - On a touch screen a tap leaves the tapped element `:hover` until the next tap, so a `.ui-seg` cell, a menu row and every other
390
+ hover tint stayed lit after the finger left. Every `:hover` rule of the package now sits in `@media (hover: hover)` (220 rules in
391
+ 58 sheets); a selector list that also names a state a finger has (`:focus-visible`, `:active`, `[open]`, pressed, `.on`) keeps it
392
+ where it was, and its `:hover` part gets a copy of the block in the media rule. Focus rings and pressed looks are unchanged. Left
393
+ outside on purpose: hovers that SHOW something (row and thread actions, the tooltip, the rail's flyout, the resizer's grip, the
394
+ editor's tree actions, the table's sort arrow), where the tap is a finger's only way in, and the disabled menu-select's rest look.
395
+ `hover-only-where-a-pointer-hovers.test.ts` keeps it so (a new bare `:hover` is red; the exemptions only shrink; a finger's state
396
+ wrapped with a hover is red too, as the inspector's open "?" was before review).
397
+ - The chat's markdown without `color-mix()` (Safari before 16.2): the three colours chat.css gives every message's markdown
398
+ (`--gemboss-ec-md-ink/-line/-fill`) were dropped where used, so the table head's tint, inline code's and the code block's fills
399
+ went transparent and every line took the text's full colour. assistant-chat.css now sets the line and the fill to mid-grey with
400
+ alpha under `@supports not (color: color-mix(…))` (one class heavier than chat.css' rule, so either load order works). A
401
+ fallback declaration before a custom property cannot do this: the custom property accepts the unknown function and wins.
402
+ - The code block's language and its "Show all N lines" bar take the message's own colours (ink, line, and the fill on hover)
403
+ instead of the light bubble's muted grey, divider and 3% black, which glared on the seller's dark fill and in dark theme and
404
+ did not show on hover there.
405
+ - The side panels' resize seam reaches 8px further over the PAGE under a mouse (`(pointer: fine)`, assistant-places.css): a 13px band
406
+ instead of 5px, the grip shown anywhere in it. Measured in the real admin dock before the change, the left panel's seam already
407
+ dragged, took the arrow keys and remembered its width like the right one's; what differed is its neighbour inside the panel, the
408
+ chat log's scrollbar, flush against the border (on the right panel that edge is padding), so a press a few pixels in scrolled
409
+ the log instead.
410
+ - weight-budget.json (needs Chris's OK, the file's rule): gemboss-ui.css 22743 → 22949 B gzip (main measures 22686, this change
411
+ 22949: +263), src/collections.css 5222 → 5246 (5216 → 5246: +30). src/editor.css grows 9043 → 9129 and stays under its 9243.
412
+ Each wrapped rule costs ~3 B gzip (gathering them into one block per file measured heavier: the rules lose the context they
413
+ compress against); a page pays for the few sheets it loads.
414
+
415
+ **The Assistant's thread rail is a tray: drag its right edge** (13/11/2026, Chris: "cái chat ở full mode ko có resize cái panel bên
416
+ trái danh sách chat ấy"). In full screen the list of conversations now has the Inbox tray's seam on its right edge (the fleet's one
417
+ `.ui-resizer`): drag it, or focus it and use the arrows (16px, Shift 64), Home and End; a double-click puts it back. 240–480px, never
418
+ past the chat's 360px floor, opening at 264 as it always has; the width is kept per browser (`SessionRail` `widthKey`, default
419
+ `SESSION_RAIL_WIDTH_KEY` "gemboss.assistant.rail") and comes back on the next open and after a reload. No seam on the collapsed 60px
420
+ strip, at 760px and under (the strip), or in full screen on a phone (one New chat button).
421
+ - `tray.tsx`: `useTrayWidth` (the width, the kept width, the room beside the page's floor, the drag and keys) and `TrayEdge` (the seam),
422
+ taken out of `TrayLayout`, which now draws with them; the Inbox's tray is unchanged (tray.browser.test.ts, 7/7). A kept width is put on
423
+ the element before the first measure, so an eased width does not slide from the opening one.
424
+ - `SessionRail` draws `TrayEdge` last, after its footer, and its width from `--gb-tray-w`; `tray.css` places both
425
+ (`.gemboss-assistant-rail`, from 761px, not collapsed). `SESSION_RAIL_SIZE`, `SESSION_RAIL_WIDTH_KEY`, label `resize`.
426
+ - `tray-plain.js` (new, `gembossUI.trayEdge`): the same seam for a page with no React. `session-rail-plain.js` uses it when it is loaded
427
+ (otherwise the plain rail is as before); the page links `tray.css`. Its own file and ceiling (1776 B gzip): session-rail-plain.js has
428
+ the room and assistant-plain.js has none, and a plain rail without a full screen does not pay for it.
429
+ - Tests: assistant-plain-browser.test.ts holds the plain rail's seam to SessionRail's step by step (keys, double-click, drag), and measures
430
+ both frames in full screen (1280: the hairline, a drag, the range, kept, a reload; the keys; 900: the chat's floor; 760, 390, collapsed:
431
+ no seam), with two negative controls (tray.css without the rail's width rule; without the rule that keeps the seam off a narrow rail).
432
+
433
+ **TraySearch: the full Assistant's search box, one for every tray** (13/11/2026, gemboss #7363: the Inbox's search "giống như bên ai
434
+ assistant có icon search bấm vào reveal ra search", "dùng lại component của bên ai assistant ở full mode").
435
+ - `TraySearch` and `openTraySearch` (`@gemboss/ui/tray-search`, also from `@gemboss/ui/tray`): the box SessionRail drew, lifted. Same
436
+ classes (`.gemboss-assistant-search gemboss-field gemboss-field--group`, its × and its key hint), so the look is shell.css's as before.
437
+ SessionRail draws it; the admin's Inbox list opens it from an icon in its head.
438
+ - Left empty, the box now closes once a press is over, not when the press takes its focus (it leaving mid-press lifted the list under
439
+ the pointer and the press came up on the next row). It watches presses only while drawn.
440
+ - `returnTo`: where Escape and × put the focus (SessionRail `searchReturnTo`); `openTraySearch` draws and focuses the box inside the
441
+ press that asked, so a touch screen shows its keyboard.
442
+ - shell.css: the ≤760px rule that hides the rail's box is scoped to `.gemboss-assistant-rail` (the Inbox's box shows on a phone);
443
+ under a finger the box is 44px tall and its × 44px wide; the box's mark is muted whatever icon draws it.
444
+ - gems.css: a count in a rail sub-row (`.gnav-subitem`) and in a folded rail's flyout row (`.gnav-flyout-sub`) is ruby too;
445
+ rail-fold.css lays the flyout row out as a row, so a count sits at its end.
446
+
447
+ **The assistant's header: its controls 8px apart and below the grip; a short placeholder when the line does not fit** (12/11/2026,
448
+ gemboss #7350: "the icons need even 8px gaps", the phone sheet's grip drawn over the "Gem · Gem team" switch, "How's my stor" at 390
449
+ under a finger).
450
+ - `.gb-dock-actions` is `gap: 8px`, and `.gb-dock-action`'s 8px right margin is gone: +, ⋯ and × stand an even 8px apart (they stood
451
+ 10px, then 2px), in AssistantHost and assistant-plain.js alike (same classes). The header's own gap is 8px too. + loses the
452
+ `gb-dock-action` class, which had no other rule.
453
+ - `.gb-dock-grip + .gb-dock-header { padding-top: 10px }`: the grip's bar is drawn 5–9px into the header's top band, and a 44px control
454
+ under a finger started at 2px. Every control now starts below the bar (popup / phone sheet only: the side panel and the window have
455
+ no grip).
456
+ - `ChatComposerProps.shortPlaceholder` (and chat-plain.js `shortPlaceholder`): said instead of `placeholder` when the placeholder's
457
+ width in the box's own font is more than the field's, measured on each fit (a new width, a new lead, a new value), so a narrow panel
458
+ on a desktop gets it too. One canvas, kept.
459
+ - One row or two: the row kept without measuring is now decided by the words, not their length: two rows stay while the new words
460
+ start with the old (they only grew at the end), one row while the old start with the new (they only shrank). A paste over a
461
+ selection or an edit in the middle is measured (a two-line message replaced by "abcd" stayed two rows: it was not shorter).
462
+ ChatComposer's ResizeObserver and lead observer are made once, not on every key.
463
+ - An empty box given a `shortPlaceholder` that is wider than its one-row field even so is two rows (`composerRows(box, ta, least)`,
464
+ chat-plain.js `rowsFor`): at 320 under a finger the one-row field is 34px and "Ask Gem…" showed cut; the same width under a mouse
465
+ was two rows already. A box without `shortPlaceholder` is unchanged (empty is one row).
466
+ - weight-budget.json: chat-plain.js 9458 → 9645 B gzip. 9458 → 9604 (+146, the short placeholder and the row rule) approved for Chris
467
+ by the coordinator, 13/11/2026; +41 for the two-row rule above, added after.
468
+
469
+ **Full screen's buttons are the kit's button** (12/11/2026, Chris: "cái button Shrink to popup … to hơn bình thường với style tròn ko giống
470
+ các thành phần còn lại của chatbot"). `.gb-dock-shrink` (Shrink to popup / Back to the side panel, Talk to a person, a surface's `fullActions`)
471
+ and the ⋯ beside them (`.gb-dock-menu-pill`) were 46px pills at every width. They are now `.ui-btn`'s shape: 28px under a mouse
472
+ (`--ui-btn-h`), 8px corners, a 1px border, caption type at 550, level with the Ask / Tell switch (`.ui-seg`, 28px); 44px under a finger
473
+ and at phone width (`(pointer: coarse), (max-width: 47.9975em)`, §9.1). `.gb-dock-fullchrome` sits at 18px under a mouse (10px under a
474
+ finger) so the buttons' middle is the admin's 56px strip's middle. The phone's lifted New chat is a 44px square with 8px corners, like them.
475
+
476
+ **`MenuItem standalone`: a menu's row in a list that is not a Menu** (13/11/2026, first caller: the admin rail's New, a list in the editor
477
+ Popover beside the rail). The same row (mark, label over its line, hint), a plain button or link in the Tab order with no `menuitem`
478
+ role: a Menu's rows leave the Tab order and take ↑ ↓, and a list with no Menu around it has no keys of its own. A disabled standalone
479
+ link still leaves the Tab order. Rows without the prop are unchanged.
480
+
481
+ **The composer: one row while the words fit, "+" and send equally inset, a switch row in "+"** (12/11/2026, Chris: "cả input bên dưới
482
+ cũng nên là một dòng; nếu viết dài thì nó dãn ra thành 2 dòng như hiện tại", "cái icon magic sao ấy cần sát lề trái hơn để cân khoảng
483
+ cách từ nút enter đến lề phải").
484
+ - ChatComposer with something in its lead ("+", ✦, a chip) is ONE row while the words fit one line: lead, text, tools, send
485
+ (`data-rows="1"` on `.gemboss-ec-input`). Once they need a second line it is the two rows it was (`data-rows="2"`), and back to one
486
+ when they fit again. Only CSS changes between them (assistant-chat.css: the toolbar is `display: contents` on one row), so the text
487
+ box is the same element and keeps the caret, the focus and the selection. Measured, not counted (`composerRows`): the words' height
488
+ in the one-row layout against one line, always measured there (so the wider second row never decides), with 24px to spare before
489
+ it goes back to one row. Empty is one row; a lead that leaves the words under 48px, or pushes them onto a line of their own, is
490
+ two rows. An empty lead is the one-row layout it already had (chat-composer.css `:has(lead:empty)`). The toolbar's density steps
491
+ count a one-row box whose words have no room as crowded.
492
+ - chat-plain.js does the same (`rowsFor`): a plain page that links assistant-chat.css (gemcare does) gets the one row with no change.
493
+ - The first control of the lead ("+", else ✦, else a chip) has no margin of its own: it stands the box's 8px from the left side, as
494
+ send does from the right (it stood 17px in, where the typed words start). Both tiers, both rows.
495
+ - A "+" row may be a switch (`ChatAddItem.checked`): `menuitemcheckbox`, the kit's check before it while on; its `onSelect` turns it.
496
+ New marks for "+" rows: `screen` (eye) and `document`.
497
+ - weight-budget.json: chat-plain.js 9080 → 9458 B gzip (+378, the plain composer's rows). Needs Chris's OK (the file's rule).
498
+
499
+ **Gem chat display modes, slice 1: on the left, the chat button, the place switcher** (12/11/2026, Chris: "ai chat mặc định mở, nằm ở
500
+ bên trái, sidebar menu sẽ collapse lại; tắt ai chat thì menu tự động expand ra… thêm một kiểu hiển thị", "collapse lại là thành hình
501
+ button chat chứ không phải cái panel"; canvas board GemDockModes, page 3.1, screens 1–3 and 5).
502
+ - A new place, `left`: the side panel's column on the LEFT of the page, beside the rail and under the topbar, resized on its right edge
503
+ (ArrowRight widens), same width and clamps as the side panel (one `sideWidth`). The page makes room (`<prefix>-left` on <body>,
504
+ `.gemboss-platform-main` margin-left = `--gb-rail-w` + `--gb-assistant-left-w`). Opt-in: `AssistantHost allowLeft` (off by default),
505
+ `openLeft()`, `leftAllowed`, events `left` / `left-allowed`; under 1100px it is off and the popup stands in, as for the side panel.
506
+ A working shape: `floatShape` and the stored place (`<prefix>.place`, below) take "left". Where the left panel is not offered (a
507
+ narrow window, a page an editor covers) it stands in as the side panel when that one is offered, else as the popup. A person whose place is the left panel finds it open on load
508
+ where it fits (not on the full page, not after closing it in that tab: `<prefix>.presentation` in sessionStorage).
509
+ - `useAssistantPresentation()`: where the assistant is drawn, from its own context, for a shell that lays itself out around it (the
510
+ admin folds its rail while it is `left`). `sideAvailable(left)` measures from `--gb-rail-w` with the left panel up.
511
+ - `defaultShape` (provider option): the place a person who never chose one gets. The kit's default stays the side panel; the admin
512
+ passes "left", which also opens on load. Open on load opens only INTO the left panel, decided by the host's first word on whether it
513
+ offers it (event `open-left-on-load`, state `opensLeft`), never a stand-in popup over a screen nobody opened the assistant on.
514
+ - The chosen place is stored under `<prefix>.place`, written only by the place switcher. It replaces `<prefix>.shape`, which Ask Gem
515
+ and Draft with Gem also wrote ("side", with no place chosen): an old "dock" is carried over as a choice, an old "side" is not read.
516
+ - `LEFT_WIDTH_VAR` (`--gb-assistant-left-w`): the left panel's width on <body>, its own variable, since right-anchored overlays read
517
+ `--gb-assistant-side-w` as "a panel on the right".
518
+ - `AssistantHost leftOffReason`: the left panel offered on this surface but not right now, and why (the admin: an editor covers the
519
+ page). The place stays in the switcher, off, with that reason.
520
+ - `isPanelShape(p)` / `isOpenShape(p)` in dock.ts: the two questions every "is Gem beside the page / open" check asks, so a shape
521
+ added later is counted everywhere at once.
522
+ - Folded (`mini`) is the chat button: a round black 52px button bottom right (16px from the corner on a phone), the kit's `chat`
523
+ glyph, a dot for Working (iris, pulsing), a failure (red), a question waiting (amber), an answer waiting (green), and its name
524
+ says the same ("Reopen the Gem assistant: Working · 0:12"). A press reopens the last place. The status bar, its × and its chevron
525
+ are gone (their labels stay in `AssistantHostLabels` so a surface's `labels` still type-check).
526
+ - `failed` (prop): the last run failed; "Something went wrong" and a red dot in the header and on the chat button, ahead of
527
+ `waiting`.
528
+ - The place switcher in the panel's header: On the right · On the left · Floating window · Full screen, the current one pressed
529
+ (`aria-pressed`). It replaces the header's full-screen button and the ⋯ rows "Pin to the side" / "Float as a popup"; ⋯ keeps
530
+ the surface's rows and "Fold into the chat button". A place the host does not offer is not drawn; one the window cannot fit is
531
+ `aria-disabled` and its tooltip says "Needs a window at least 1100px wide". 28px under a mouse from 768px (§9.1's mouse tier),
532
+ 44px under a finger, where the pressed one gives its room to the title; on a phone the two panels are not drawn. Under a mouse the
533
+ header's + ⋯ × are 32px too, so the narrowest panel (380) keeps 100px for its title. New labels `places`, `placeSide`, `placeLeft`,
534
+ `placeDock`, `placeFull`, `placeNeedsWidth`, `backToLeft`, `failed`; `minimizeTitle`, `closeBusy`, `closeBusyTitle` now say "Fold into
535
+ the chat button". (Slice 2 moved the places into ⋯, below.)
536
+ - Icons: `panelLeft`, `popup` (chat frame set).
537
+ - CSS: a new entry `assistant-places.css` (host.tsx imports it after assistant.css). **A plain page with assistant-plain.js must link
538
+ it beside assistant.css** (or gemboss-ui.css): the folded state's look moved there, and assistant.css lost the status bar's rules
539
+ (gemboss-ui.css is lighter by them). Without it the folded frame is an unstyled box.
540
+ - The place switcher marks the person's place (`floatShape`) pressed, not what stands in for it; the chat button's name says the
541
+ state ("…: Working"), its tooltip adds the run's clock (the name no longer changes every second).
542
+ - assistant-plain.js draws the same: `allowLeft`, `openLeft()`, the switcher, the chat button (not `waiting` / `failed`, as before).
543
+ Its ceiling rises 7740 → 8779 B gzip (8528 measured): the parity tests hold the plain frame to AssistantHost element by element,
544
+ so the switcher and the chat button cannot stay out of it (approved by Claude on Chris's behalf, 12/11/2026).
545
+ - The left panel's place held from the first paint: `assistantLeftHoldScript({ storagePrefix, defaultShape, fullPath })` (new module
546
+ `assistant/hold.ts`, no "use client", so a server layout gets the string) is a script for the markup BEFORE the shell. It asks what
547
+ the provider will ask on load and, where the left panel will open, marks <html> (`ASSISTANT_HOLD_ATTR`, `data-gb-assistant-hold`)
548
+ with the panel's width. The new entry `assistant-hold.css` (brought by hold.ts) then draws the rail folded, the page beside the panel
549
+ and the panel's empty column from the first frame; the provider takes the mark away once the load's open is decided. Opened after
550
+ the paint, the panel moved the page on every load (the admin rig: CLS 0.119 at 1440, 0.130 at 1280; with the hold 0.0001, as for a
551
+ person who keeps the popup). A surface that passes `defaultShape: "left"`, or whose people choose the left panel, writes the script.
552
+ The stored `sideWidth` is now restored against the room of the place it opens in (`sideAvailable(true)` for a left place).
553
+
554
+ **Gem chat display modes, slice 2: the floating window** (12/11/2026, Chris: "ở dạng floating thì nó thực sự là floating popup có thể
555
+ move khắp màn hình như cái window"; canvas board GemDockModes, page 3.1, screens 4, 6, 7 and 8).
556
+ - Under a mouse from 768px (not `(pointer: coarse), (max-width: 47.9975em)`, `WINDOW_OFF_QUERY`) the popup (`dock`) is a window: the
557
+ frame gets `gb-dock-window` and its place and size inline (`left`, `top`, `width`, `height`, through the style prop / CSSOM, never a
558
+ style attribute). Under a finger or on a phone the popup is what it was (glued to the bottom, its height from the top edge, slid
559
+ sideways); none of the below applies there.
560
+ - Where it first opens: where the popup opened, 460 wide and 12px under the top bar, now 24px in from the right AND the bottom
561
+ (`defaultWindow`). The board's 400 × 600 outline is an example ("Số và tên trong màn là ví dụ"); the opening height stays the rule Chris
562
+ chose on 04/10 ("gần hết màn").
563
+ - Moved by its header: the bare strip, or the ⋮⋮ at its start (`gb-dock-move`, a 28px button: "Move the window: drag it, or use the
564
+ arrow keys"; arrows move it 16px, Shift 64px). Resized from its four edges and four corners (`gb-dock-rs-*`, 8px bands, 16px corners);
565
+ the bottom-right corner is a 24px button (WCAG 2.5.8 under a mouse) that arrow keys resize too. Never smaller than 360 × 480, never larger than the viewport, and
566
+ always wholly inside it, 8px from each edge (`clampWindow`, `moveWindow`, `resizeWindow`): re-fitted when the browser window
567
+ resizes, and the place asked for comes back when it grows again. Remembered per person as `<prefix>.window` ("x,y,w,h");
568
+ `setWindow(rect)` on the plain frame.
569
+ - Docking by a drag (screen 7): while it is moved, the pointer over the rail (or within 32px of the left edge) is the left panel's zone,
570
+ within 32px of the right edge the side panel's (`dropZoneAt`), only where the host offers that panel (`leftAllowed` / `sideAllowed`).
571
+ The zone lights where the panel will stand (`gb-dock-drop`, dashed iris, under the window, never taking the pointer) with what
572
+ releasing does ("Release to dock on the left" / "…on the right"; labels `dropLeft`, `dropSide`), and a 12px band marks each other
573
+ edge it could dock to (`gb-dock-edgehint`). Released there it docks into that panel and keeps its window place as it was before the
574
+ drag, so Floating window brings it back there. Released anywhere else it stays a window. No zone, nothing docks.
575
+ - The window's status word stands down, as in the two panels (the dot says it; the word stays for a screen reader): at 360 its header
576
+ also holds the ⋮⋮.
577
+ - The conversation is never re-parented: only class names and inline geometry change (the same `<textarea>` and its draft through every
578
+ move, dock and undock, measured in the admin rig).
579
+ - The window's place is the window's chrome's own: kept in `window-host.tsx`, read and written as `<prefix>.window` (the provider
580
+ exposes `storagePrefix`), fitted to the viewport where it is drawn and re-fitted on a resize. Its geometry (`clampWindow`,
581
+ `defaultWindow`, `placeWindow`, `moveWindow`, `resizeWindow`, `dropZoneAt`, `parseWindow`, `formatWindow`, `dockViewport`, the
582
+ `WINDOW_*` numbers) is `assistant/window.ts`. Nothing of the window is in the provider or `dock.ts`, which every admin screen loads:
583
+ there it put the admin's dashboard 0.8 KB brotli over its first-load budget (#7320).
584
+ - The left panel's held place (`assistant/hold.ts`) is given back by the hold script itself `ASSISTANT_HOLD_GIVE_UP_MS` (5 s) after the
585
+ first paint, if the provider has not given it back by then: a host that never says whether it offers the panel (its code failed to
586
+ load) left `opensLeft` set and the empty column with it, for good. In the script, which is the page's markup, not in the provider,
587
+ which is in every admin screen's first-load JS. The panel still opens if the host comes later. `hold.browser.test.ts` mounts no host
588
+ (red without the timer).
589
+ - The header's dot says a failure or a question waiting by class (`gb-dock-dot-failed`, `gb-dock-dot-waiting`, in assistant-places.css),
590
+ in AssistantHost and the plain frame alike, not by an inline colour: that was for assistant.css's frozen bundle, which the places entry
591
+ is not in, and the plain frame at its weight ceiling writes one class where it wrote a style.
592
+ - CSS: a new entry `assistant-window.css`, imported by the window's chrome (`assistant/window-host.tsx`) after assistant-places.css.
593
+ - Plain pages: a new script `assistant-window-plain.js` (load it with assistant-plain.js and link assistant-window.css): the same window,
594
+ its geometry held to `dock.ts` over random inputs, the frame held to AssistantHost step by step at 1440/900/390. Without it the plain
595
+ frame draws the popup. `assistant-plain.js` now also says `waiting` / `failed` (options, or `frame.update({ waiting, failed })`), as
596
+ AssistantHost does. Its ceiling is unchanged (8779 B gzip; measured 8729): everything about the window lives in the new file
597
+ (3237 B gzip, its own ceiling), which the frame plugs in at four points (`frame`, `dress`, `paint`, `on`); it adds `api.setWindow` itself. Words the plain frame no longer draws are gone from its defaults (`minimize`, `tablist`, `primaryTab`:
598
+ it has no second tab; `minimizeTitle`, with ⋯'s fold row, below); a surface passing them in `labels` is unaffected.
599
+ - **The places leave the header for ⋯** (12/11/2026, Chris on production: "danh sách các layout options các thứ cũng tốn không gian nhìn
600
+ ko được clean, cái top bar đó ko ổn đâu nhìn rối"). The panel's header is the title, +, ⋯ and ×, nothing else. ⋯ is a menu
601
+ (`role="menu"`): its first group is where it sits (On the right · On the left · Floating window · Full screen, `menuitemradio`, the
602
+ person's place `aria-checked` with a check mark), then the surface's rows and Clear history after a separator (`AssistantMenuItem` is
603
+ a `menuitem` there; `menuItems` works as before). A place the host does not offer is not drawn; one the window cannot fit is
604
+ `aria-disabled` (focusable, a press does nothing, the menu stays open) and its row says why on a second line ("Needs a window at least
605
+ 1100px wide", or the host's `leftOffReason`), in muted ink rather than the kit menu's half fade, so the reason reads; below 1100px the person's own place stays checked while off, the popup standing in.
606
+ Keys: ↓ from ⋯ to the first row, ↓ ↑ Home End move and wrap, Enter takes a place and closes onto ⋯, Escape closes onto ⋯. A
607
+ place taken from the menu keeps the draft (the same `<textarea>`). Measured in the admin rig (its "Gem" heading with ←): the header's
608
+ controls 236 → 108px; the name's room at a 380 panel 57 → 201px, in a 360 window 10 → 154px (it was cut to "G"), in a 400 window
609
+ 50 → 194px. The header's switcher CSS is gone; the menu rows' is in assistant-places.css.
610
+ - **No "Fold into the chat button" row** (Chris: "option fold into chat button ko cần thiết vì nó là 1 mà"): × does it (a working
611
+ assistant folds into the chat button; an idle one closes, and the admin's chat corner stays). `minimize()` and the `minimize` event
612
+ stay (the admin's Reach and editors fold it so); the labels `minimize` and `minimizeTitle` are deprecated, not drawn.
613
+ - **The header's dot only for a state**: Working, a failure, a question waiting, an answer waiting; nothing when ready (a grey dot
614
+ beside the title read as a stray mark), so the room goes to the title. AssistantHost and the plain frame alike.
615
+ - **The popup and the floating window are solid**, as the two panels are: `.gb-dock.gb-dock-dock` paints `--gemboss-surface` with no
616
+ backdrop blur (assistant-places.css; assistant.css's frosted base is in the frozen bundle). The rail's rows and the page showed
617
+ through the frost behind the messages. Measured: `rgb(255, 255, 255)` / `none`, against `color(srgb 1 1 1 / 0.93)` /
618
+ `blur(14px) saturate(1.4)` before.
619
+ - **The places wear their marks** (12/11/2026): each row carries the mark the header's switcher had (`panelRight`, `panelLeft`, `popup`,
620
+ `expand`) in the kit menu's icon slot (`.ui-menu__icon`, 16px, muted; AssistantHost now imports menu-extras.css), the name taking the
621
+ row and the check at its end. **On a plain page the marks come with assistant-window-plain.js** (its `dress` puts them in, for every
622
+ shape), since assistant-plain.js is at its ceiling: a plain page without the window script has the rows without marks. Plain pages
623
+ load that script for the floating window anyway; link menu-extras.css for the slot.
624
+ - **"On the left"**: the admin no longer says "On the left (the menu folds)" (the longest row of ⋯); the rail folding shows for itself,
625
+ and the drop zone still says "Release to dock on the left. The menu folds."
626
+ - **`onButtonPress`** (AssistantHost prop, and the plain frame's option of the same name, 13/11/2026): the folded chat button calls it
627
+ first; when it returns `true` the host does not reopen its last place (the surface opened something itself), and when it returns
628
+ nothing, or there is no hook, the button reopens as before. For the admin to open the Gem team from the black button.
629
+ - assistant-plain.js draws all of the above (8777 B gzip, its ceiling 8779 unchanged: the row code shares one "close onto ⋯" helper);
630
+ assistant-window-plain.js 3532 B gzip (ceiling 3754).
631
+ - ⋯'s keys pass a row they cannot land on (Clear history with nothing to clear is `disabled`), and in the plain frame ↑ on the first
632
+ row wraps to the last (it threw). The window's drag reads the viewport once at the press and selects no text along the way.
633
+
634
+ **`editor.css` drops three rules only the page editor drew** (12/11/2026, gemboss #7316): `.gemboss-pageedit-notice`,
635
+ `.gemboss-pageedit-scope` and `.gemboss-pageedit-standing`. The admin's page editor, the one surface that wore them, was deleted
636
+ after Page mode went (#7243). A surface that pinned the kit and used them keeps them only in older versions.
637
+
7
638
  ## 0.70.2 (12/11/2026)
8
639
 
9
640
  **The account menu's rows can carry a mark, a second line and a hint: `AccountMenuRow`** (11/11/2026, first caller: the admin's top bar,
@@ -33,13 +664,13 @@ probe whenever a new one found the same state, so a paired bridge's engines neve
33
664
  machine stayed as it was until Check again), on ✦ opening (`refresh`) and in the background probes alike. Same state now takes
34
665
  the new probe's data and keeps the user's notes (lost, off, wrong, dismissed); nothing new, the same object.
35
666
 
36
- ## 0.70.1 (12/11/2026)
37
-
38
667
  **Gem answers in plain words** (12/11/2026, canvas board ChatKit: "Người dùng: bong bóng đen bên phải. Gem: chữ trơn bên trái,
39
668
  không bong bóng"; Chris left the choice to Claude). The answer bubble (`.gemboss-ec-msg.assistant .gemboss-ec-bubble`) has no fill,
40
669
  border or corner and starts at the column's edge, in line with its step rows; the seller's message keeps its bubble. A surface
41
670
  that draws a message as a card (the admin Inbox) gives it its own fill and border.
42
671
 
672
+ ## 0.70.1 (12/11/2026)
673
+
43
674
  **The plain chat under a strict CSP; the heartbeat's hologram does not pulse** (12/11/2026, found moving gemcare onto 0.69.0).
44
675
  chat-plain.js and engine-plain.js set a `style` through CSSOM (`style.cssText`), not `setAttribute("style")`: a page whose CSP
45
676
  has no inline styles (gemcare's inbox: `style-src 'self'`) refused the attribute, so the heartbeat's hologram drew at 32px beside
@@ -491,7 +1122,6 @@ counted from `main` (already at 56) and drew 56px low, over the embedded editor'
491
1122
  landed on a nav tab). `overflow: clip` cuts the same overflow without being a scroll container. Chromium test
492
1123
  `embedded-editor-under-sticky-nav-browser.test.ts`, with `hidden` restored as its negative control.
493
1124
 
494
-
495
1125
  - `FieldFrame` / `PartsFrame` `labels` (`FrameClusterLabels`): a host's own name for a cluster where the kit's (Look · Layout · Visibility ·
496
1126
  Code) would say the wrong thing; the plugin kernel's settings name theirs Look and Behavior (one control set 08/11/2026).
497
1127