Adom UI Design System

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

@@ -127,6 +127,13 @@ container-proxy tab is not evidence about the dock.** Neither is a page you load outside the card's own launch.  - Verify in the ah webview that YOUR DOCK CARD opened, on the instance the dock installed.+- **AH'S WEBVIEW, NEVER HC'S.** Your cloud container runs its own Hydrogen (hc), and+  `adom-cli hydrogen webview ...` from inside that container reaches **hc**, not the user's+  ah. A tab you open there is invisible to the user, proves nothing about their dock, and+  leaves litter in a workspace nobody asked you to touch. (John's ruling, 2026-08-25, after+  an app put a tab into hc by mistake.) Everything you do on the user's machine goes through+  the bridge with an explicit target: `adom-bridge --target <Box> hd_api ...`. If you did not+  name their box, you are not on their box. - 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)