@gemboss/ui 0.53.0 → 0.55.1

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.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,58 @@ 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.55.1 (25/10/2026)
8
+
9
+ Fixed
10
+ - Settings › AI & engines, Install or update: the blocks of a surface's `setup.steps` sit 8px apart. 0.55.0 took the section's
11
+ paragraph margins (they were what spaced a hint from what follows it), so a hint touched its Allow button (gemfactory on prod,
12
+ and bridgePickerProps' permission case on every radar), and a hint touched the pairing form (GemFeedback, bridgePickerProps'
13
+ unpaired case). The blocked case's list touched Check again before 0.55.0 too. `.gb-engine-steps` is a grid with an 8px gap
14
+ (engine-plain.js's slot is display:contents, so its children are the grid's); a bare `.ui-btn` (button or link) keeps its own
15
+ width, the pairing form the full one. So `setup.steps` is blocks: a sentence mixing text and inline elements goes in a `<p>`.
16
+ BridgePairForm is a `.gb-engine-actions` row instead of a `ui-toolbar` (a page toolbar's 20px below it had opened 28px), and
17
+ bridge.tsx imports assistant-engine.css for it. Tests in Chromium for the four shapes and the plain slot; negatives: without
18
+ the grid rule the gaps read 0, without the own-width rule the button is the steps' width, the old toolbar form reads 28px.
19
+ assistant-engine.css stays under its ceiling (2479 B).
20
+
21
+ ## 0.55.0 (25/10/2026)
22
+
23
+ **Settings › AI & engines, cleaner** (25/10/2026, Chris: the chip's old popup "design khá đẹp", bring that look into Settings
24
+ with pictures; then "clean và thẩm mỹ… phương án đầu an toàn nhất", so the layout stays and only the details change).
25
+
26
+ Changed
27
+ - Each engine row starts with a small picture: its mark (`EngineChoice.mark`, else an id the kit has artwork for), else
28
+ its initial by code point (`EngineRowMark`). Never another engine's logo. Monochrome, as the chip's mark. The admin's grouped
29
+ engines too. The chip and the row pick the picture by ONE rule, `engineMarkOf` (new export): an engine with the id `claude`
30
+ and no `mark` now has its mark on the chip as well, when the composer is narrow. Rows stay 44px.
31
+ - The bridge card's state is a dotted badge in its head (`BridgeStateBadge`, classes `gb-engine-state--ok|warn|down|idle`
32
+ in assistant-engine.css itself: the kit's ui-badge tones are in kit-plain.css, which the admin does not load); the "State"
33
+ row is gone. The callout carries the
34
+ surface's `detail` only (it no longer opens with "Bridge on your machine: outdated.", which the badge says), and there is no
35
+ callout without a detail. Label `state` is optional and deprecated (nothing draws it).
36
+ - `.gb-engine-settings` packs its cards at the top (`align-content: start`) and owns their margins and its paragraphs'
37
+ margins: in the catalog, a page's own `section` and `section > p` margins had opened 64px between the cards.
38
+ - `engine-plain.js`: the same, its marks drawn with `gembossUI.engineMark` (chat-plain.js, which every page with the chip loads).
39
+
40
+ ## 0.54.0 (25/10/2026)
41
+
42
+ **A product's own GemBoss door on the kit's button** (25/10/2026). GemCommunity's sign-in drew "Continue with GemBoss" by
43
+ hand in the kit's classes, because `AuthContinueWithGemBoss` only linked to the fleet door (Chris, 24/10/2026: "signup signin
44
+ phải cùng ui kit với các page login").
45
+
46
+ Added
47
+ - `AuthContinueWithGemBoss` `href`, in place of `service`: a door the product runs itself (GemCommunity's handoff through
48
+ admin.gemboss.ai/api/community/sso). The link goes there as given and nothing of the fleet door applies: it never goes by
49
+ itself on `gb_sso=1` (the fleet's cookie), and a `?sso=` reason is the product's to say in its own words.
50
+ - `label`, `goingLabel` and `or` (null for none: a page that says "or" itself, above several doors), in the page's language.
51
+ Left out, they are the words the button had.
52
+ - `PickerList` `pinned`: rows that do not come from the source (an empty value that is a choice), first and pickable in every state,
53
+ with the source's state said under them. Before, the product picker put such a row in `items`: an empty catalogue behind it said
54
+ nothing (the kit's empty state shows only for an empty list), and a failed read hid it (gemboss #5415). In `reloading` only the
55
+ source's rows dim (`.gemboss-ei-pick-row.is-stale`).
56
+
57
+ Unchanged: `auth-sso-plain.js` keeps the fleet door only. No page without React draws a product's door.
58
+
7
59
  ## 0.53.0 (25/10/2026)
8
60
 
9
61
  **The engine chip's popup is gone: Settings › AI & engines is the only place the engine is chosen** (Chris's condition for the
package/README.md CHANGED
@@ -484,9 +484,13 @@ const picker = useEnginePicker({ onOpenSettings: () => openSettings("ai") });
484
484
  - **The section**: `EngineSettingsSection` draws what the chip on the page was given (`engine-settings-store.ts`: the chip
485
485
  publishes its props, the section reads them), so the surface hands its engine props to the chip only and changes
486
486
  nothing else. Two cards, one under the other: **Engine** (the engines as radios, or each with its own models; model;
487
- effort; `notes`) and **Bridge on your machine** (one callout for outdated / offline / unpaired, the State / Version /
488
- Starts at sign-in rows, `statusActions`, then "Install or update": the steps, the command with Copy, the pairing code,
489
- the note). With no chip on the page it says the assistant has not loaded yet (`empty` replaces that line).
487
+ effort; `notes`) and **Bridge on your machine** (its state as a dotted badge in the card's head; one callout with the
488
+ surface's `detail` for outdated / offline / unpaired, none without a detail; the Version / Starts at sign-in rows,
489
+ `statusActions`, then "Install or update": the steps, the command with Copy, the pairing code, the note).
490
+ Since 0.55.0 each engine row starts with a small picture: its mark (`EngineChoice.mark`, else an id the kit has
491
+ artwork for: `claude`, `codex`), else its initial. Never another engine's logo: "Claude via API" with the id `api` gets a
492
+ "C", not Claude's mark. `engine-plain.js` draws the marks with `gembossUI.engineMark` from `chat-plain.js`, which every
493
+ page with the chip loads. With no chip on the page it says the assistant has not loaded yet (`empty` replaces that line).
490
494
  `EngineSettings` takes the props itself, for a surface that holds them where its settings are drawn, and the catalog.
491
495
  - **`picker.open`** is the section being SEEN (an IntersectionObserver), not mounted: the kit's SettingsDialog keeps its
492
496
  sections mounted while it is closed, and a surface that probes the bridge while `picker.open` would poll for ever.
@@ -1743,6 +1747,9 @@ an icon) · `.gemboss-ei-pick-text` › `.gemboss-ei-pick-head` (`.gemboss-ei-pi
1743
1747
  - States: `loading` (skeleton rows, a first read), `reloading` (the last answer's rows kept, dimmed and `aria-busy`, nothing
1744
1748
  pickable from them while the next search is read), `error` (the kit's danger notice, Try again with `onRetry`), no match
1745
1749
  (Clear search, the focus back in the box), `empty`, `more` (Show more, after the list).
1750
+ - `pinned` (25/10/2026): rows that do not come from the source, such as an empty value that is a choice ("This page's product"):
1751
+ first and pickable in every state, with the source's own state under them (its skeleton, error, empty or no-match words). In
1752
+ `reloading` only the source's rows dim (`.is-stale`). Leave them out while words are typed if they are no match for words.
1746
1753
 
1747
1754
  Its own part (`editor-picker.css`, 1.0 KB gzip).
1748
1755
 
@@ -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.53.0 · Editor</h1>
11
+ <h1>@gemboss/ui 0.55.1 · 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;;