Adom UI Design System

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

@@ -117,6 +117,30 @@ is that you ASK rather than click, that is arguably the more honest demo; for an demo drives its own UI, keep the scripted runner and serve it from the same machine as the page. Decide deliberately rather than discovering it. +### ⛔ VERIFY ONLY INSIDE AH. Never in a pup window or a desktop browser.++John's standing rule, 2026-08-24: **"only test inside ah."**++The webview in ah is the surface your users actually see, so it is the only place a+verification counts. **A capture from a pup window, a Chrome or Edge window, or a+container-proxy tab is not evidence about the dock.** Neither is a page you loaded yourself+outside the card's own launch.++- Verify in the ah webview that YOUR DOCK CARD opened, on the instance the dock installed.+- Need a picture? Capture the ah window (`hd_shot region full`) and READ the image. Do not+  open a browser to look at your own page.+- Anything that paints outside ah (a desktop caption, a browser window, a taskbar badge)+  belongs to an explicit user action, never to a verification step. It lands on the user's+  screen over whatever they are doing.+- If something can ONLY be checked outside ah, say what and why rather than doing it.++This is not etiquette, it is the only test that can fail the way production fails. Three+separate defects on 2026-08-24 were missed or misdiagnosed for exactly this reason: an app+whose dashboard rendered perfectly in its container while the user's instance showed no+prompts panel at all; a pup capture published as though it were the ah view; and five+consecutive launch defects that were invisible in a developer's container and appeared only+on a real box.+ ### 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