Adom UI Design System

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

@@ -245,6 +245,15 @@ This caught two instruments in one day, both belonging to careful people:   was usable, and its adopters are told to run the negative controls rather than trust a green   first run. +**Break the property each row CLAIMS to watch, not just any property.** nb negative-tested+selfCheck one property at a time at dpr 1.5, restoring between each: background to #000, accent+edge to 9px, radius to 2px, phrase font to Courier. Each turned exactly its own row red and+nothing else, and the baseline went green again after. Breaking the background only proves the+harness runs; breaking the typeface proves the typeface row is wired to the typeface. **A check+can be green because it passes, or green because it is measuring the wrong thing, and only a+targeted red separates those.** Do this before pasting a green result as evidence: otherwise+what you are pasting is a screenshot of a function that might always return true.+ The same shape sank three other things here: a truncation instrument that measured the wrong element and reported 0 of 6 truncating on a panel visibly cutting words off; a conformance checker that failed every correct panel; and a fleet audit that reported an app had no panel