Adom UI Design System

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

@@ -134,6 +134,12 @@ outside the card's own launch.   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.+- **AND ASSERT IT IN CODE, not just in operator habit.** Any code path that shells out to+  `adom-cli hydrogen ...` with no target is correct on the user's machine and silently drives+  **hc** if it ever runs in a cloud container. Most apps gate this behind `ADOM_DOCK_WEBVIEW`+  (which only the dock sets), and that gate is what keeps it honest, so make it explicit:+  check the variable, or check that you are inside the user's workspace, BEFORE calling+  `adom-cli`. Every app that claims its webview the same way carries the same latent bug. - **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

@@ -151,6 +151,17 @@ Until the ah build thread certifies the panel fix and the un-park is broadcast: That was the park. It is over. </details> +**UN-PARK BY DELETING THE PARKED BRANCH, NEVER BY FLIPPING A FLAG TO FALSE.** cf's insight,+2026-08-25, and it explains why three of six apps carried a broken send path without knowing:++> The parked early-return means the broken path CANNOT FAIL IN TESTING, so "we tested it"+> means nothing until the flag is gone. An app that un-parks by flipping a flag to false+> ships whatever was behind it, live and unexercised.++A flag turns dead code into a loaded gun: the branch behind it has never run, never failed,+and never been read since it was written. Delete the const and the early return, then read+the code the deletion exposes as if it were new, because to your test suite it is.+ **UN-PARK CHECKLIST** (do all four, in order):  1. Restore the real send path behind your park flag.