Adom UI Design System

@@ -1,6 +1,6 @@ {   "slug": "adom-ui-design",-  "version": "1.29.0",+  "version": "1.29.1",   "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.+- **THIS RULE IS ABOUT WHERE YOU VERIFY, NOT WHICH API YOUR APP MAY CALL.** Your app is+  free to call `adom-cli hydrogen workspace add-tab` or `webview open-or-refresh` in its own+  product code: when a USER runs your CLI in their workspace, the tab is supposed to open in+  THEIR Hydrogen, and the dock's `ADOM_DOCK_WEBVIEW` takeover works precisely because that+  process runs on the user's machine. **Do not rip those calls out while enforcing this+  rule** — an app that stopped opening its own tab would be a regression. The ban is on YOU,+  the agent, opening a webview from your cloud container and calling it verification. - **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