Adom UI Design System

@@ -1,6 +1,6 @@ {   "slug": "adom-ui-design",-  "version": "1.23.0",+  "version": "1.24.0",   "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": {},

@@ -77,6 +77,31 @@ disabled `Demo running` state, per **newbie-panel**): [ ⏮ ] [ ⏯ ] [ ⏭ ]   [ 🔇 ]   step 3/8   [ ✕ ] ``` +### Captions appear WHERE THE ACTION IS++Resolved 2026-08-24, when the ah-only verification rule appeared to collide with this+skill's "captions are ab captions on the desktop". It does not, once the question is asked+properly: **a caption belongs on the surface the demo is actually driving.**++- **A demo that drives the DESKTOP** (pup opening a browser window, kicad opening the+  Schematic Editor, fusion driving a modelling session) paints **ab captions on the desktop**,+  at the bridge default size and position. That is where the user's eyes are, and a caption+  trapped in a webview would be narrating something happening elsewhere.+- **A demo that drives things INSIDE YOUR OWN PAGE** (a search running, a table filling, a+  panel opening) paints its captions **in-page**, inside the webview, styled from the same+  tokens. Putting those on the desktop would drop your app's narration over whatever else the+  user has on screen, for a demo they can already see in full.+- **Never mix within one demo.** If a demo crosses surfaces, the caption follows the step:+  desktop while the desktop is driven, in-page once the action returns to your dashboard.++The consistency the fleet cares about is that captions LOOK the same and are TIMED the same,+not that they all live on one surface. Bridge-default size and position still bind wherever+you paint, and the never-a-custom-size rule is unchanged.++And the boundary that never moves: **captions outside ah belong to an explicit user click,+never to a verification step.** Verifying your dashboard happens inside ah, always (see+`dock-dashboard`).+ **Typography, and this is not optional: NEVER a monospace or Courier face anywhere in the demo UI.** Pup shipped its toolbar and step counter in Courier and it read as a terminal bolted onto a designed page. The toolbar uses the body face at **12.5px** for the step