← Commit history

2.6.1 (doc only, module bytes unchanged): the mechanism is 'run the code against your page and report what it does', not 'tell me if you disagree'

John Lauer ·c9f2f1011a ·1mo ago ·parent 9945338
2 files changed +17−3
package.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "adom-ui-design",-  "version": "2.6.0",+  "version": "2.6.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": {},
skills/newbie-panel/SKILL.md+16−2
@@ -408,8 +408,22 @@ these bugs lived in an assumption the fixtures shared with the checker**, becaus person authored both. The matrix above is the right instrument and it still has that property: every row is a structure someone already knew about. **The rows that catch the next bug are the ones nobody has thought to write**, and they come from apps testing the check against a-real page rather than against a fixture. Publish the check, invite the disagreement, and treat-a considered pushback as a test case you did not have.+real page rather than against a fixture.++**The mechanism is specific, and "invite disagreement" understates it.** Nobody disagreed with+the prose here: it read fine all four times. What caught every bug was reading the+IMPLEMENTATION against a page that already existed, with its real CSS. **An assumption a+fixture shares with its checker is invisible in prose by construction**, so asking "tell me if+you disagree" cannot surface it. What to ask for instead:++> Here is the code. Run it against your page and report what it does.++And when the answer comes back as reasoning rather than a measurement, **keep the label on+it.** parts-search insisted its fourth catch be recorded as a code read, not a measurement,+because a code read that happens to be right is still a code read: had it been wrong about how+the fallback resolved, the identical confident prose would have read the same. Separating the+two is what makes the next prediction worth acting on. Then put a ruler on it: 16 and 31 are+worth more measured than predicted, to both parties.  **⛔ WHEN A CHECK FAILS, ASK WHETHER IT IS FAILING THE CORRECT IMPLEMENTATIONS.** pup's framing, and it is the sharpest hazard on this page: a check that is wrong at random is noise,