Adom UI Design System

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

@@ -94,6 +94,23 @@ So: **Ralph-test:** list every HTTP surface your app serves. If more than one of them renders something a user would call "the dashboard", you have this bug. +### And verify on the instance the DOCK runs, not the one you develop against++There are usually TWO INSTALLS of your app: the copy you develop against (your cloud+workspace container) and the copy the dock installs into the user's own workspace. Same+port, same version, DIFFERENT FILESYSTEMS, so different settings files and different+localStorage. **"Works on mine" is not evidence about theirs.**++Measured on parts-search, 2026-08-24: the user's instance had `showSayStrip:false` persisted+(left behind by a duplicate-listener bug that flipped the strip off), so his dashboard+rendered with NO prompts panel at all while the developer's container copy showed it+perfectly. It was caught only because the panel was missing from a screenshot about to be+published.++So when you verify: read the state from the instance the dock actually launched (its own+`/api/settings`, its own localStorage), and if you fix persisted state, fix it THERE. A+capture of your own container proves nothing about the user's page.+ ## The token stub (copy-paste, then never hardcode again)  ```css