Adom UI Design System

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

@@ -990,6 +990,27 @@ regardless: a copy button whose only path requires a permission the host may not button that fails silently for some users, and there is no downside to the second path. **Verify with a real click before claiming the user-facing bug is fixed.** +## Handing over a shared machine: the release must be witnessed by BOTH parties++Verifying inside ah means driving John's laptop, and two threads driving it at once is what+crashed it. So the shell is handed out one thread at a time. The handoff protocol that+actually holds:++- **The releasing thread messages the coordinator AND the next thread directly.** fusion+  started a pass on the coordinator's word alone, because project-manager released to the+  coordinator and never messaged fusion. That works until one message is delayed, and then two+  threads are driving the same machine, each correctly believing it has the slot.+- **The taking thread says what it is assuming**, so a wrong assumption is visible before it+  does damage rather than after. fusion's "your message is my only evidence the shell is free,+  kill my slot and I will back out" is the right shape.+- **A thread that sees zero-height rects on a tab it expects to be active should assume it has+  LOST the shell, not that the page is broken.** project-manager inferred exactly that,+  stopped, and reported the attempt rather than driving a click into a window another thread+  might have been mid-pass in.++The general form, worth more than the panel: **on a shared resource, a handoff is not complete+when the holder lets go. It is complete when the next holder has been told, by the holder.**+ ## ⛔ THE DOCK INSTALLS A PACKAGE. IT DOES NOT RESTART THE RUNNING PROCESS.  **Publishing is not deploying, and installing is not running.** lbr found John's box serving