@gemboss/ui 0.70.2 → 0.71.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 (97) hide show
  1. package/CHANGELOG.md +257 -2
  2. package/README.md +25 -9
  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 +17 -1
  7. package/parts/components.css +2 -2
  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.tsx +118 -16
  13. package/src/assistant/composer-menus.tsx +7 -2
  14. package/src/assistant/dock.ts +97 -10
  15. package/src/assistant/hold.ts +51 -0
  16. package/src/assistant/host.tsx +231 -124
  17. package/src/assistant/index.ts +4 -2
  18. package/src/assistant/provider.tsx +121 -24
  19. package/src/assistant/sessions.tsx +54 -20
  20. package/src/assistant/window-host.tsx +215 -0
  21. package/src/assistant/window.ts +120 -0
  22. package/src/assistant-chat.css +1 -1
  23. package/src/assistant-hold.css +1 -0
  24. package/src/assistant-places.css +1 -0
  25. package/src/assistant-plain.js +1 -1
  26. package/src/assistant-window-plain.js +1 -0
  27. package/src/assistant-window.css +1 -0
  28. package/src/assistant.css +1 -1
  29. package/src/auth-extras.css +1 -1
  30. package/src/auth-footer.css +1 -1
  31. package/src/auth-steps.css +1 -1
  32. package/src/auth.css +1 -1
  33. package/src/chat-attachments.css +1 -1
  34. package/src/chat-cards.css +1 -1
  35. package/src/chat-composer-menus.css +1 -1
  36. package/src/chat-composer.css +1 -1
  37. package/src/chat-plain.js +6 -6
  38. package/src/chat-voice.css +1 -1
  39. package/src/chat.css +1 -1
  40. package/src/collections.css +1 -1
  41. package/src/create-shell.css +1 -1
  42. package/src/editor/controls.tsx +28 -4
  43. package/src/editor/field-control.tsx +11 -2
  44. package/src/editor/field-spec.ts +6 -2
  45. package/src/editor-color.css +1 -1
  46. package/src/editor-empty.css +1 -0
  47. package/src/editor-insert.css +1 -1
  48. package/src/editor-inspector-frame.css +1 -1
  49. package/src/editor-picker-grid.css +1 -1
  50. package/src/editor-picker.css +1 -1
  51. package/src/editor-popover.css +1 -1
  52. package/src/editor-repeater.css +1 -1
  53. package/src/editor-tiles.css +1 -1
  54. package/src/editor.css +1 -1
  55. package/src/email-editor.css +1 -1
  56. package/src/feedback-dialog.css +1 -0
  57. package/src/feedback-dialog.tsx +122 -0
  58. package/src/gemboss-field.css +1 -1
  59. package/src/gems.css +1 -1
  60. package/src/icon-frame.tsx +31 -0
  61. package/src/icons.tsx +9 -9
  62. package/src/index.ts +1 -0
  63. package/src/job-card.css +1 -1
  64. package/src/kit-plain.css +1 -1
  65. package/src/language-switcher.css +1 -1
  66. package/src/list-page.css +1 -1
  67. package/src/list-toolbar.css +1 -1
  68. package/src/members.css +1 -1
  69. package/src/menu-extras.css +1 -1
  70. package/src/menu-select.css +1 -1
  71. package/src/menu.tsx +9 -4
  72. package/src/narration.css +1 -1
  73. package/src/pager-extras.css +1 -1
  74. package/src/pager.css +1 -1
  75. package/src/portal.css +1 -1
  76. package/src/question-card.css +1 -1
  77. package/src/rail-fold.css +1 -1
  78. package/src/reactions.css +1 -1
  79. package/src/report-charts.css +1 -1
  80. package/src/service-switcher.css +1 -1
  81. package/src/session-rail-plain.js +1 -1
  82. package/src/settings-dialog.css +1 -1
  83. package/src/setup-guide.css +1 -1
  84. package/src/shell.css +1 -1
  85. package/src/site.css +1 -1
  86. package/src/skill-card.css +1 -1
  87. package/src/skill-flow.css +1 -1
  88. package/src/skill-pages.css +1 -1
  89. package/src/skill-view.css +1 -1
  90. package/src/stage-path.css +1 -1
  91. package/src/status-list.css +1 -1
  92. package/src/team-chat.css +1 -1
  93. package/src/tray-plain.js +1 -0
  94. package/src/tray-search.tsx +116 -0
  95. package/src/tray.css +1 -0
  96. package/src/tray.tsx +250 -0
  97. package/src/ui.css +1 -1
package/CHANGELOG.md CHANGED
@@ -4,6 +4,261 @@ 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.71.0 (13/11/2026)
8
+
9
+ **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,
10
+ 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ư
11
+ stick on the right").
12
+ - 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
13
+ hover tint stayed lit after the finger left. Every `:hover` rule of the package now sits in `@media (hover: hover)` (220 rules in
14
+ 58 sheets); a selector list that also names a state a finger has (`:focus-visible`, `:active`, `[open]`, pressed, `.on`) keeps it
15
+ 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
16
+ outside on purpose: hovers that SHOW something (row and thread actions, the tooltip, the rail's flyout, the resizer's grip, the
17
+ 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.
18
+ `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
19
+ wrapped with a hover is red too, as the inspector's open "?" was before review).
20
+ - The chat's markdown without `color-mix()` (Safari before 16.2): the three colours chat.css gives every message's markdown
21
+ (`--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
22
+ 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
23
+ alpha under `@supports not (color: color-mix(…))` (one class heavier than chat.css' rule, so either load order works). A
24
+ fallback declaration before a custom property cannot do this: the custom property accepts the unknown function and wins.
25
+ - 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)
26
+ 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
27
+ did not show on hover there.
28
+ - The side panels' resize seam reaches 8px further over the PAGE under a mouse (`(pointer: fine)`, assistant-places.css): a 13px band
29
+ instead of 5px, the grip shown anywhere in it. Measured in the real admin dock before the change, the left panel's seam already
30
+ dragged, took the arrow keys and remembered its width like the right one's; what differed is its neighbour inside the panel, the
31
+ chat log's scrollbar, flush against the border (on the right panel that edge is padding), so a press a few pixels in scrolled
32
+ the log instead.
33
+ - weight-budget.json (needs Chris's OK, the file's rule): gemboss-ui.css 22743 → 22949 B gzip (main measures 22686, this change
34
+ 22949: +263), src/collections.css 5222 → 5246 (5216 → 5246: +30). src/editor.css grows 9043 → 9129 and stays under its 9243.
35
+ Each wrapped rule costs ~3 B gzip (gathering them into one block per file measured heavier: the rules lose the context they
36
+ compress against); a page pays for the few sheets it loads.
37
+
38
+ **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
39
+ 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
40
+ `.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
41
+ past the chat's 360px floor, opening at 264 as it always has; the width is kept per browser (`SessionRail` `widthKey`, default
42
+ `SESSION_RAIL_WIDTH_KEY` "gemboss.assistant.rail") and comes back on the next open and after a reload. No seam on the collapsed 60px
43
+ strip, at 760px and under (the strip), or in full screen on a phone (one New chat button).
44
+ - `tray.tsx`: `useTrayWidth` (the width, the kept width, the room beside the page's floor, the drag and keys) and `TrayEdge` (the seam),
45
+ 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
46
+ the element before the first measure, so an eased width does not slide from the opening one.
47
+ - `SessionRail` draws `TrayEdge` last, after its footer, and its width from `--gb-tray-w`; `tray.css` places both
48
+ (`.gemboss-assistant-rail`, from 761px, not collapsed). `SESSION_RAIL_SIZE`, `SESSION_RAIL_WIDTH_KEY`, label `resize`.
49
+ - `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
50
+ (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
51
+ the room and assistant-plain.js has none, and a plain rail without a full screen does not pay for it.
52
+ - Tests: assistant-plain-browser.test.ts holds the plain rail's seam to SessionRail's step by step (keys, double-click, drag), and measures
53
+ 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:
54
+ 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).
55
+
56
+
57
+ **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
58
+ assistant có icon search bấm vào reveal ra search", "dùng lại component của bên ai assistant ở full mode").
59
+ - `TraySearch` and `openTraySearch` (`@gemboss/ui/tray-search`, also from `@gemboss/ui/tray`): the box SessionRail drew, lifted. Same
60
+ classes (`.gemboss-assistant-search gemboss-field gemboss-field--group`, its × and its key hint), so the look is shell.css's as before.
61
+ SessionRail draws it; the admin's Inbox list opens it from an icon in its head.
62
+ - 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
63
+ the pointer and the press came up on the next row). It watches presses only while drawn.
64
+ - `returnTo`: where Escape and × put the focus (SessionRail `searchReturnTo`); `openTraySearch` draws and focuses the box inside the
65
+ press that asked, so a touch screen shows its keyboard.
66
+ - 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);
67
+ under a finger the box is 44px tall and its × 44px wide; the box's mark is muted whatever icon draws it.
68
+ - 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;
69
+ rail-fold.css lays the flyout row out as a row, so a count sits at its end.
70
+
71
+ **The assistant's header: its controls 8px apart and below the grip; a short placeholder when the line does not fit** (12/11/2026,
72
+ 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
73
+ under a finger).
74
+ - `.gb-dock-actions` is `gap: 8px`, and `.gb-dock-action`'s 8px right margin is gone: +, ⋯ and × stand an even 8px apart (they stood
75
+ 10px, then 2px), in AssistantHost and assistant-plain.js alike (same classes). The header's own gap is 8px too. + loses the
76
+ `gb-dock-action` class, which had no other rule.
77
+ - `.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
78
+ under a finger started at 2px. Every control now starts below the bar (popup / phone sheet only: the side panel and the window have
79
+ no grip).
80
+ - `ChatComposerProps.shortPlaceholder` (and chat-plain.js `shortPlaceholder`): said instead of `placeholder` when the placeholder's
81
+ 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
82
+ on a desktop gets it too. One canvas, kept.
83
+ - 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
84
+ 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
85
+ selection or an edit in the middle is measured (a two-line message replaced by "abcd" stayed two rows: it was not shorter).
86
+ ChatComposer's ResizeObserver and lead observer are made once, not on every key.
87
+ - An empty box given a `shortPlaceholder` that is wider than its one-row field even so is two rows (`composerRows(box, ta, least)`,
88
+ 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
89
+ was two rows already. A box without `shortPlaceholder` is unchanged (empty is one row).
90
+ - weight-budget.json: chat-plain.js 9458 → 9645 B gzip. 9458 → 9604 (+146, the short placeholder and the row rule) approved for Chris
91
+ by the coordinator, 13/11/2026; +41 for the two-row rule above, added after.
92
+
93
+ **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
94
+ 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`)
95
+ 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
96
+ (`--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
97
+ and at phone width (`(pointer: coarse), (max-width: 47.9975em)`, §9.1). `.gb-dock-fullchrome` sits at 18px under a mouse (10px under a
98
+ 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.
99
+
100
+ **`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
101
+ 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`
102
+ 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
103
+ link still leaves the Tab order. Rows without the prop are unchanged.
104
+
105
+ **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
106
+ 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
107
+ cách từ nút enter đến lề phải").
108
+ - ChatComposer with something in its lead ("+", ✦, a chip) is ONE row while the words fit one line: lead, text, tools, send
109
+ (`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
110
+ when they fit again. Only CSS changes between them (assistant-chat.css: the toolbar is `display: contents` on one row), so the text
111
+ box is the same element and keeps the caret, the focus and the selection. Measured, not counted (`composerRows`): the words' height
112
+ in the one-row layout against one line, always measured there (so the wider second row never decides), with 24px to spare before
113
+ 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
114
+ two rows. An empty lead is the one-row layout it already had (chat-composer.css `:has(lead:empty)`). The toolbar's density steps
115
+ count a one-row box whose words have no room as crowded.
116
+ - chat-plain.js does the same (`rowsFor`): a plain page that links assistant-chat.css (gemcare does) gets the one row with no change.
117
+ - 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
118
+ send does from the right (it stood 17px in, where the typed words start). Both tiers, both rows.
119
+ - A "+" row may be a switch (`ChatAddItem.checked`): `menuitemcheckbox`, the kit's check before it while on; its `onSelect` turns it.
120
+ New marks for "+" rows: `screen` (eye) and `document`.
121
+ - weight-budget.json: chat-plain.js 9080 → 9458 B gzip (+378, the plain composer's rows). Needs Chris's OK (the file's rule).
122
+
123
+ **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 ở
124
+ 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
125
+ button chat chứ không phải cái panel"; canvas board GemDockModes, page 3.1, screens 1–3 and 5).
126
+ - 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
127
+ (ArrowRight widens), same width and clamps as the side panel (one `sideWidth`). The page makes room (`<prefix>-left` on <body>,
128
+ `.gemboss-platform-main` margin-left = `--gb-rail-w` + `--gb-assistant-left-w`). Opt-in: `AssistantHost allowLeft` (off by default),
129
+ `openLeft()`, `leftAllowed`, events `left` / `left-allowed`; under 1100px it is off and the popup stands in, as for the side panel.
130
+ A working shape: `floatShape` and the stored place (`<prefix>.place`, below) take "left". Where the left panel is not offered (a
131
+ 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
132
+ where it fits (not on the full page, not after closing it in that tab: `<prefix>.presentation` in sessionStorage).
133
+ - `useAssistantPresentation()`: where the assistant is drawn, from its own context, for a shell that lays itself out around it (the
134
+ admin folds its rail while it is `left`). `sideAvailable(left)` measures from `--gb-rail-w` with the left panel up.
135
+ - `defaultShape` (provider option): the place a person who never chose one gets. The kit's default stays the side panel; the admin
136
+ 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
137
+ offers it (event `open-left-on-load`, state `opensLeft`), never a stand-in popup over a screen nobody opened the assistant on.
138
+ - The chosen place is stored under `<prefix>.place`, written only by the place switcher. It replaces `<prefix>.shape`, which Ask Gem
139
+ 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.
140
+ - `LEFT_WIDTH_VAR` (`--gb-assistant-left-w`): the left panel's width on <body>, its own variable, since right-anchored overlays read
141
+ `--gb-assistant-side-w` as "a panel on the right".
142
+ - `AssistantHost leftOffReason`: the left panel offered on this surface but not right now, and why (the admin: an editor covers the
143
+ page). The place stays in the switcher, off, with that reason.
144
+ - `isPanelShape(p)` / `isOpenShape(p)` in dock.ts: the two questions every "is Gem beside the page / open" check asks, so a shape
145
+ added later is counted everywhere at once.
146
+ - Folded (`mini`) is the chat button: a round black 52px button bottom right (16px from the corner on a phone), the kit's `chat`
147
+ glyph, a dot for Working (iris, pulsing), a failure (red), a question waiting (amber), an answer waiting (green), and its name
148
+ says the same ("Reopen the Gem assistant: Working · 0:12"). A press reopens the last place. The status bar, its × and its chevron
149
+ are gone (their labels stay in `AssistantHostLabels` so a surface's `labels` still type-check).
150
+ - `failed` (prop): the last run failed; "Something went wrong" and a red dot in the header and on the chat button, ahead of
151
+ `waiting`.
152
+ - The place switcher in the panel's header: On the right · On the left · Floating window · Full screen, the current one pressed
153
+ (`aria-pressed`). It replaces the header's full-screen button and the ⋯ rows "Pin to the side" / "Float as a popup"; ⋯ keeps
154
+ 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
155
+ `aria-disabled` and its tooltip says "Needs a window at least 1100px wide". 28px under a mouse from 768px (§9.1's mouse tier),
156
+ 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
157
+ header's + ⋯ × are 32px too, so the narrowest panel (380) keeps 100px for its title. New labels `places`, `placeSide`, `placeLeft`,
158
+ `placeDock`, `placeFull`, `placeNeedsWidth`, `backToLeft`, `failed`; `minimizeTitle`, `closeBusy`, `closeBusyTitle` now say "Fold into
159
+ the chat button". (Slice 2 moved the places into ⋯, below.)
160
+ - Icons: `panelLeft`, `popup` (chat frame set).
161
+ - CSS: a new entry `assistant-places.css` (host.tsx imports it after assistant.css). **A plain page with assistant-plain.js must link
162
+ it beside assistant.css** (or gemboss-ui.css): the folded state's look moved there, and assistant.css lost the status bar's rules
163
+ (gemboss-ui.css is lighter by them). Without it the folded frame is an unstyled box.
164
+ - The place switcher marks the person's place (`floatShape`) pressed, not what stands in for it; the chat button's name says the
165
+ state ("…: Working"), its tooltip adds the run's clock (the name no longer changes every second).
166
+ - assistant-plain.js draws the same: `allowLeft`, `openLeft()`, the switcher, the chat button (not `waiting` / `failed`, as before).
167
+ Its ceiling rises 7740 → 8779 B gzip (8528 measured): the parity tests hold the plain frame to AssistantHost element by element,
168
+ so the switcher and the chat button cannot stay out of it (approved by Claude on Chris's behalf, 12/11/2026).
169
+ - The left panel's place held from the first paint: `assistantLeftHoldScript({ storagePrefix, defaultShape, fullPath })` (new module
170
+ `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
171
+ the provider will ask on load and, where the left panel will open, marks <html> (`ASSISTANT_HOLD_ATTR`, `data-gb-assistant-hold`)
172
+ 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
173
+ 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
174
+ 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
175
+ person who keeps the popup). A surface that passes `defaultShape: "left"`, or whose people choose the left panel, writes the script.
176
+ The stored `sideWidth` is now restored against the room of the place it opens in (`sideAvailable(true)` for a left place).
177
+
178
+ **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ể
179
+ move khắp màn hình như cái window"; canvas board GemDockModes, page 3.1, screens 4, 6, 7 and 8).
180
+ - Under a mouse from 768px (not `(pointer: coarse), (max-width: 47.9975em)`, `WINDOW_OFF_QUERY`) the popup (`dock`) is a window: the
181
+ frame gets `gb-dock-window` and its place and size inline (`left`, `top`, `width`, `height`, through the style prop / CSSOM, never a
182
+ 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
183
+ sideways); none of the below applies there.
184
+ - 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
185
+ (`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
186
+ chose on 04/10 ("gần hết màn").
187
+ - 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
188
+ arrow keys"; arrows move it 16px, Shift 64px). Resized from its four edges and four corners (`gb-dock-rs-*`, 8px bands, 16px corners);
189
+ 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
190
+ always wholly inside it, 8px from each edge (`clampWindow`, `moveWindow`, `resizeWindow`): re-fitted when the browser window
191
+ resizes, and the place asked for comes back when it grows again. Remembered per person as `<prefix>.window` ("x,y,w,h");
192
+ `setWindow(rect)` on the plain frame.
193
+ - 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,
194
+ within 32px of the right edge the side panel's (`dropZoneAt`), only where the host offers that panel (`leftAllowed` / `sideAllowed`).
195
+ The zone lights where the panel will stand (`gb-dock-drop`, dashed iris, under the window, never taking the pointer) with what
196
+ releasing does ("Release to dock on the left" / "…on the right"; labels `dropLeft`, `dropSide`), and a 12px band marks each other
197
+ 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
198
+ drag, so Floating window brings it back there. Released anywhere else it stays a window. No zone, nothing docks.
199
+ - 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
200
+ also holds the ⋮⋮.
201
+ - The conversation is never re-parented: only class names and inline geometry change (the same `<textarea>` and its draft through every
202
+ move, dock and undock, measured in the admin rig).
203
+ - The window's place is the window's chrome's own: kept in `window-host.tsx`, read and written as `<prefix>.window` (the provider
204
+ exposes `storagePrefix`), fitted to the viewport where it is drawn and re-fitted on a resize. Its geometry (`clampWindow`,
205
+ `defaultWindow`, `placeWindow`, `moveWindow`, `resizeWindow`, `dropZoneAt`, `parseWindow`, `formatWindow`, `dockViewport`, the
206
+ `WINDOW_*` numbers) is `assistant/window.ts`. Nothing of the window is in the provider or `dock.ts`, which every admin screen loads:
207
+ there it put the admin's dashboard 0.8 KB brotli over its first-load budget (#7320).
208
+ - 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
209
+ 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
210
+ 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,
211
+ 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
212
+ (red without the timer).
213
+ - 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),
214
+ in AssistantHost and the plain frame alike, not by an inline colour: that was for assistant.css's frozen bundle, which the places entry
215
+ is not in, and the plain frame at its weight ceiling writes one class where it wrote a style.
216
+ - CSS: a new entry `assistant-window.css`, imported by the window's chrome (`assistant/window-host.tsx`) after assistant-places.css.
217
+ - Plain pages: a new script `assistant-window-plain.js` (load it with assistant-plain.js and link assistant-window.css): the same window,
218
+ 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
219
+ frame draws the popup. `assistant-plain.js` now also says `waiting` / `failed` (options, or `frame.update({ waiting, failed })`), as
220
+ AssistantHost does. Its ceiling is unchanged (8779 B gzip; measured 8729): everything about the window lives in the new file
221
+ (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`:
222
+ it has no second tab; `minimizeTitle`, with ⋯'s fold row, below); a surface passing them in `labels` is unaffected.
223
+ - **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
224
+ 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
225
+ (`role="menu"`): its first group is where it sits (On the right · On the left · Floating window · Full screen, `menuitemradio`, the
226
+ person's place `aria-checked` with a check mark), then the surface's rows and Clear history after a separator (`AssistantMenuItem` is
227
+ a `menuitem` there; `menuItems` works as before). A place the host does not offer is not drawn; one the window cannot fit is
228
+ `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
229
+ 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.
230
+ Keys: ↓ from ⋯ to the first row, ↓ ↑ Home End move and wrap, Enter takes a place and closes onto ⋯, Escape closes onto ⋯. A
231
+ place taken from the menu keeps the draft (the same `<textarea>`). Measured in the admin rig (its "Gem" heading with ←): the header's
232
+ 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
233
+ 50 → 194px. The header's switcher CSS is gone; the menu rows' is in assistant-places.css.
234
+ - **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
235
+ assistant folds into the chat button; an idle one closes, and the admin's chat corner stays). `minimize()` and the `minimize` event
236
+ stay (the admin's Reach and editors fold it so); the labels `minimize` and `minimizeTitle` are deprecated, not drawn.
237
+ - **The header's dot only for a state**: Working, a failure, a question waiting, an answer waiting; nothing when ready (a grey dot
238
+ beside the title read as a stray mark), so the room goes to the title. AssistantHost and the plain frame alike.
239
+ - **The popup and the floating window are solid**, as the two panels are: `.gb-dock.gb-dock-dock` paints `--gemboss-surface` with no
240
+ backdrop blur (assistant-places.css; assistant.css's frosted base is in the frozen bundle). The rail's rows and the page showed
241
+ through the frost behind the messages. Measured: `rgb(255, 255, 255)` / `none`, against `color(srgb 1 1 1 / 0.93)` /
242
+ `blur(14px) saturate(1.4)` before.
243
+ - **The places wear their marks** (12/11/2026): each row carries the mark the header's switcher had (`panelRight`, `panelLeft`, `popup`,
244
+ `expand`) in the kit menu's icon slot (`.ui-menu__icon`, 16px, muted; AssistantHost now imports menu-extras.css), the name taking the
245
+ 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
246
+ shape), since assistant-plain.js is at its ceiling: a plain page without the window script has the rows without marks. Plain pages
247
+ load that script for the floating window anyway; link menu-extras.css for the slot.
248
+ - **"On the left"**: the admin no longer says "On the left (the menu folds)" (the longest row of ⋯); the rail folding shows for itself,
249
+ and the drop zone still says "Release to dock on the left. The menu folds."
250
+ - **`onButtonPress`** (AssistantHost prop, and the plain frame's option of the same name, 13/11/2026): the folded chat button calls it
251
+ first; when it returns `true` the host does not reopen its last place (the surface opened something itself), and when it returns
252
+ nothing, or there is no hook, the button reopens as before. For the admin to open the Gem team from the black button.
253
+ - assistant-plain.js draws all of the above (8777 B gzip, its ceiling 8779 unchanged: the row code shares one "close onto ⋯" helper);
254
+ assistant-window-plain.js 3532 B gzip (ceiling 3754).
255
+ - ⋯'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
256
+ 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.
257
+
258
+ **`editor.css` drops three rules only the page editor drew** (12/11/2026, gemboss #7316): `.gemboss-pageedit-notice`,
259
+ `.gemboss-pageedit-scope` and `.gemboss-pageedit-standing`. The admin's page editor, the one surface that wore them, was deleted
260
+ after Page mode went (#7243). A surface that pinned the kit and used them keeps them only in older versions.
261
+
7
262
  ## 0.70.2 (12/11/2026)
8
263
 
9
264
  **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 +288,13 @@ probe whenever a new one found the same state, so a paired bridge's engines neve
33
288
  machine stayed as it was until Check again), on ✦ opening (`refresh`) and in the background probes alike. Same state now takes
34
289
  the new probe's data and keeps the user's notes (lost, off, wrong, dismissed); nothing new, the same object.
35
290
 
36
- ## 0.70.1 (12/11/2026)
37
-
38
291
  **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
292
  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
293
  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
294
  that draws a message as a card (the admin Inbox) gives it its own fill and border.
42
295
 
296
+ ## 0.70.1 (12/11/2026)
297
+
43
298
  **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
299
  chat-plain.js and engine-plain.js set a `style` through CSSOM (`style.cssText`), not `setAttribute("style")`: a page whose CSP
45
300
  has no inline styles (gemcare's inbox: `style-src 'self'`) refused the attribute, so the heartbeat's hologram drew at 32px beside
package/README.md CHANGED
@@ -63,6 +63,9 @@ its CSS out of the build with it (`sideEffects`). gzip of the minified file, as
63
63
  | auth-footer | `@gemboss/ui/auth-footer.css` | `packages/ui/src/auth-footer.css` | `AuthFooter`: theme, language, Help · Terms · Privacy under the sign-in card (24/10/2026) | 0.5 KB | `AuthFooter` imports it (and, through ThemeToggle and LanguageSwitcher, portal.css, theme-dark.css, language-switcher.css) |
64
64
  | auth-steps | `@gemboss/ui/auth-steps.css` | `packages/ui/src/auth-steps.css` | `AuthSteps`, `AuthStepActions`, `AuthChoices`, `AuthChips`: a sign-up of several steps (24/10/2026) | 1.0 KB | those components import it, with auth.css |
65
65
  | assistant | `@gemboss/ui/assistant.css` | `packages/ui/src/assistant.css` | the dock and the launcher | 2.2 KB | `AssistantHost`, the launcher import it |
66
+ | assistant-places | `@gemboss/ui/assistant-places.css` | `packages/ui/src/assistant-places.css` | where the assistant sits (12/11/2026): the left panel, ⋯'s places, the chat button (folded); the popup and window solid | 1.2 KB | `AssistantHost` imports it after assistant.css; a plain page links it beside assistant.css |
67
+ | assistant-window | `@gemboss/ui/assistant-window.css` | `packages/ui/src/assistant-window.css` | the floating window (12/11/2026): its ⋮⋮, its edges and corners, the drop zones while it is dragged | 1.0 KB | `AssistantHost` brings it (through `assistant/window-host.tsx`), after assistant-places.css; a plain page links it with assistant-window-plain.js |
68
+ | tray | `@gemboss/ui/tray.css` | `packages/ui/src/tray.css` | `TrayLayout`: a list docked left, its seam, one pane where only one fits (12/11/2026, the Inbox); the Assistant's thread rail's width and seam (13/11/2026) | 0.5 KB | `TrayLayout` and `SessionRail` import it; a plain page with `tray-plain.js` links it |
66
69
  | portal | `@gemboss/ui/portal.css` | `packages/ui/src/portal.css` | `TopbarNav`, `SearchDialog`, `Avatar`, `Leaderboard`, `Podium`, the `ThemeToggle` button | 2.1 KB | those components import it |
67
70
  | topnav-fold | `@gemboss/ui/topnav-fold.css` | `packages/ui/src/topnav-fold.css` | `TopbarNav`'s folded menu after the frozen bundle (unreleased): `foot`, `foldAt={760}`, `gb-topnav-unfolded`, the open tab's ellipsis | 0.3 KB | `TopbarNav` imports it (after portal.css) |
68
71
  | site | `@gemboss/ui/site.css` | `packages/ui/src/site.css` | the public site layer (0.40.0): the bar, the lockup at the site size, links, buttons, the footer | 1.0 KB | `SiteHeader` / `SiteBrand` import it; a plain-HTML page links it |
@@ -418,7 +421,8 @@ its top edge and slides along the bottom, by pointer or keyboard, and remembers
418
421
 
419
422
  The side panel is the DEFAULT shape since 0.8.0 (Chris, 04/10/2026): a browser that never chose opens the assistant
420
423
  there, and `allowSide` defaults to true — a surface whose layout cannot make room passes `allowSide={false}` and gets
421
- the popup. The popup header has "Pin to the side", and the panel carries "Float as a popup" back; the choice is kept
424
+ the popup. ⋯'s places (12/11/2026; "Pin to the side" / "Float as a popup" rows of ⋯ before, a switcher in the header for a day) move it between
425
+ the popup, the side panel, the left panel (`allowLeft`) and full screen; the choice is kept
422
426
  under `<prefix>.shape` (the older `floatShape` key recorded the old default for everyone, so it is not read). The rail
423
427
  link reopens in that shape unless the person last worked full screen. A popup opens as tall as the window allows,
424
428
  12px under the topbar (it was min(480, viewport − 176)); a height the person dragged to is kept, and dragging it back
@@ -469,10 +473,17 @@ Its styles are the `gemboss-assistant-*` rules in `packages/ui/src/shell.css` (t
469
473
  @imports too), and they reach you through `gemboss-ui.css` together with `gemboss-field.css`. The admin passes a second tab ("Talk to a person", gemcare) through `secondTab` and its button
470
474
  through `fullActions`; a surface without those leaves them out.
471
475
 
472
- **The header's ⋯ menu (0.31.0).** The header shows four controls: + (`onNewChat`), full screen, ⋯ and ×. ⋯ holds
473
- what is used once in a while: your rows (`menuItems`, as `AssistantMenuItem`s), "Clear history" when you pass
474
- `onClearHistory` (greyed out with `canClearHistory={false}`; confirm inside your handler), then pin / float and
475
- minimise. Full screen's chrome shows ⋯ too when you pass either. Do not draw a Clear button of your own in the body.
476
+ **The header's ⋯ menu (0.31.0) and where it sits (12/11/2026).** The header shows the title, + (`onNewChat`), ⋯ and ×, nothing
477
+ else. ⋯ is a menu: first where it sits (On the right · On the left with `allowLeft` · Floating window · Full screen, the current one
478
+ checked; a place the window cannot fit is off and its row says why), then your rows (`menuItems`, as `AssistantMenuItem`s) and "Clear
479
+ history" when you pass `onClearHistory` (greyed out with `canClearHistory={false}`; confirm inside your handler). ↓ ↑ Home End move,
480
+ Enter presses, Escape closes onto ⋯. × folds a working assistant into the chat button and closes an idle one. Full screen's chrome
481
+ shows ⋯ too when you pass rows. Do not draw a Clear button of your own in the body.
482
+
483
+ **On the left (12/11/2026).** `allowLeft` offers a full-height panel on the left of the page, beside the rail; the page makes room
484
+ (`<prefix>-left` on <body>). A shell that should fold its rail while it is there reads `useAssistantPresentation()` (the admin does).
485
+ Folded, every place becomes the round chat button in the bottom-right corner, with a dot for what Gem is doing. A press reopens the last
486
+ place, unless `onButtonPress` (a prop; the plain frame's option) returns `true`: the surface opened something itself.
476
487
 
477
488
  ```tsx
478
489
  <AssistantHost title="Radar Assistant" onNewChat={reset} onExpand={expand} onShrink={shrink}
@@ -481,10 +492,12 @@ minimise. Full screen's chrome shows ⋯ too when you pass either. Do not draw a
481
492
  ```
482
493
 
483
494
  **A page with no React (0.44.0): `assistant-plain.js`.** The same frame for a server-rendered page (GemFactory's board,
484
- gemcare): the five shapes, `dock.ts`'s rules copied in ES5, the provider's storage keys, `<prefix>-side` and
495
+ gemcare): the six shapes, `dock.ts`'s rules copied in ES5, the provider's storage keys, `<prefix>-side` and
485
496
  `--gb-assistant-side-w` on `<body>`, the rail link's reopen, the ⋯ menu, the grips and their keys, and the same markup,
486
497
  so `assistant.css` draws it. `assistant-plain-browser.test.ts` holds it to `AssistantProvider` + `AssistantHost`: the same
487
- steps on both, the `.gb-dock` element compared after each one. A classic script after `kit-plain.js`:
498
+ steps on both, the `.gb-dock` element compared after each one. The floating window (12/11/2026) is a second script,
499
+ `assistant-window-plain.js`, loaded beside it with `assistant-window.css`: without it the frame draws the popup. A classic script after
500
+ `kit-plain.js`:
488
501
 
489
502
  ```html
490
503
  <script src="kit-plain.js"></script><script src="chat-plain.js"></script><script src="assistant-plain.js"></script>
@@ -505,7 +518,9 @@ Not in the plain frame yet: `secondTab`, page facts and the popup's open-chat ta
505
518
  **The thread rail, with no React (0.47.0): `session-rail-plain.js`.** `SessionRail` for the same pages: the same
506
519
  markup and classes (shell.css draws both), the search box (case and Vietnamese marks folded), the recency groups, inline
507
520
  rename, the ⋯ menu and its two-step delete. The sessions, and what opening, renaming, pinning or deleting one does, stay
508
- the page's. Hand it to the frame as `rail` and the frame builds the admin's `AssistantWorkspaceLayout` around the body:
521
+ the page's. With `tray-plain.js` loaded before the rail is made (and `tray.css` linked) its right edge is the tray's seam, as
522
+ `SessionRail`'s (13/11/2026): dragged, or the arrows (16, Shift 64), Home and End; a double-click back to 264; 240–480 and never
523
+ past the chat's 360px floor; kept per browser under `widthKey` (default `gemboss.assistant.rail`). Not on the 60px strip, not at 760 and under. Hand it to the frame as `rail` and the frame builds the admin's `AssistantWorkspaceLayout` around the body:
509
524
  the rail in full screen only, `is-dock` in the popup and the panel, the body never moved. `frame.setSwitching(true)` dims
510
525
  the page while the next thread loads; `gembossUI.fullChromeRoom(chatEl)` keeps the first message out from under the
511
526
  full-screen buttons (as `useFullChromeRoom` does for `AssistantChat`). The rail is its own file and its own ceiling (4.5 KB gzip), so a page with no full-screen
@@ -513,7 +528,8 @@ assistant does not pay for it. `assistant-plain-browser.test.ts` holds it to `Se
513
528
  the menu, rename, pin, delete, collapse, an empty list) and the framed layout to `AssistantHost` + `AssistantWorkspaceLayout`.
514
529
 
515
530
  ```html
516
- <script src="kit-plain.js"></script><script src="session-rail-plain.js"></script><script src="assistant-plain.js"></script>
531
+ <link rel="stylesheet" href="tray.css">
532
+ <script src="kit-plain.js"></script><script src="tray-plain.js"></script><script src="session-rail-plain.js"></script><script src="assistant-plain.js"></script>
517
533
  <script>
518
534
  const rail = gembossUI.sessionRail({ sessions, activeId, onNewChat, onOpen: openThread, onRename: rename,
519
535
  onDelete: remove, titleMaxLength: 120, storageKey: "gemfactory.assistant.railCollapsed" });
@@ -8,7 +8,7 @@
8
8
  .cat-code summary{padding:10px 16px;font-size:13px;cursor:pointer;color:var(--gemboss-text-muted);border-top:1px solid var(--gemboss-divider);min-height:24px}
9
9
  .cat-code pre,.cat-api{margin:0;padding:12px 16px;overflow:auto;background:#0f1012;color:#e8e8e6;font-size:12px;line-height:1.5;border-radius:0}
10
10
  .cat-api{border-radius:12px;margin:0 0 16px}</style></head><body><div class="cat">
11
- <h1>@gemboss/ui 0.70.2 · Editor</h1>
11
+ <h1>@gemboss/ui 0.71.0 · Editor</h1>
12
12
  <p>Khung của mọi editor: <code>EditorFrame</code> (cột trái · khe kéo · preview · cột phải dock trên mép phải preview) và <code>EditorTopbar</code> (← · tiêu đề · cụm giữa · cụm phải · dòng trạng thái). Là đúng khung của theme / page / section editor trong admin. Gói chỉ vẽ KHUNG; chat, Configure, canvas, page picker, menu, Publish là của editor, đi vào bằng slot. Trang HTML thuần nạp <code>editor.css</code> + <code>editor-plain.js</code> rồi gọi <code>gembossUI.initEditorFrame()</code>: kéo khe (chuột, chạm, phím mũi tên / Home / End), đổi thiết bị, mở ⋯ và Publish ▾, ẩn cột trái, Chat | Preview trên điện thoại. <a href="index.html">← Catalog</a></p>
13
13
  <h2>React</h2><pre class="cat-api"><code>import &quot;@gemboss/ui/editor.css&quot;;
14
14
  import { EditorFrame, EditorTopbar, EditorBack, EditorChatToggle, EditorPaneTabs, EditorSaveState, DeviceToggle } from &quot;@gemboss/ui/editor&quot;;