Adom UI Design System

@@ -1,6 +1,6 @@ {   "slug": "adom-ui-design",-  "version": "1.9.2",+  "version": "1.9.3",   "type": "skill",   "description": "The Adom UI Design System plus a bundle of focused UI skills (tooltips, floating-windows, toasts, responsive-ui, app-shell, ai-driven-apps, clickable-paths, dark-default, input-feedback, settings-layout). One install drops the whole set of skill files onto your container, plus shared icon assets (the settings cog) so every Adom app draws the same glyph.",   "dependencies": {},

@@ -122,7 +122,7 @@ The page never talks to the panel directly; its backend does, via the workspace API (the URL in `~/.adom/hydrogen-control-url`):  1. `POST /ai-threads/new` with a staged `name` ("KiCad - say it") and `tags`-   (`["dock:kicad"]`, the app slug) - returns the new thread's `sid`. The staged name/tags+   (see the TAG RULE below) - returns the new thread's `sid`. The staged name/tags    have a 4h TTL, which a real send consumes immediately. 2. `POST /ai-threads/run-prompt` with `{ sid, prompt, submit: true }`. @@ -130,6 +130,25 @@ The backend endpoint is `POST /api/say-send { phrase }` answering `{ ok, sid }` `{ ok: false, why }` (CORS `*` like every /api/* route, per the dockbar guide). This replaces the parked `/api/say-try` contract. +### TAG RULE (exact literal, ruled 2026-08-24)++The tag is `dock:` plus the app's **wiki page slug**, which is the part after the owner:++| page | tag literal |+|---|---|+| adom/kicad-bridge | `dock:kicad-bridge` |+| adom/fusion-bridge | `dock:fusion-bridge` |+| adom/adom-chip-fetcher | `dock:adom-chip-fetcher` |+| adom/pup-bridge | `dock:pup-bridge` |+| adom/adom-lbr | `dock:adom-lbr` |+| adom/adom-parts-search | `dock:adom-parts-search` |+| adom/nb-bridge | `dock:nb-bridge` |++NOT the dock card id (`kicad`, `lbr`, `pup`), which is a dock-internal ordering key and is+not unique outside the curated list. The page slug is what identifies the package, the+issue tracker, and the dockbar manifest, so it is what a census query can rely on. One+string, fleet-wide: a census that has to guess between two spellings finds neither.+ **New threads ONLY.** Resuming or typing into EXISTING threads stays parked pending the platform certification; a dashboard never calls resume or targets a tid it found in the census. Tagging the new thread with the app slug is what lets the census find it later.