← Commit history

1.9.4: un-park checklist, verify the tag literal in the INSTALLED tarball not the source tree

John Lauer ·a194305ec2 ·1mo ago ·parent d43a2e6
2 files changed +13−1
package.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "adom-ui-design",-  "version": "1.9.3",+  "version": "1.9.4",   "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/say-strip/SKILL.md+12
@@ -116,6 +116,18 @@ Until the ah build thread certifies the panel fix and the un-park is broadcast:  The section below is the contract that resumes on the un-park broadcast. +**UN-PARK CHECKLIST** (do all four, in order):++1. Restore the real send path behind your park flag.+2. Confirm the tag literal is `dock:<wiki page slug>` per the TAG RULE below. Most apps+   parked by deleting or short-circuiting the send body, so the tag may exist only in a+   comment right now: a correct string in dead code is not a correct string.+3. Verify in the **INSTALLED TARBALL** from a clean `pkg install`, not in your source tree:+   grep the installed tool for the live `/ai-threads` call and the tag literal. This is how+   the fleet verified the park itself, and it is the only check that catches a fix that+   never made it into the package.+4. Only then report ready for cold-verify.+ ## Send to AI: the server side  The page never talks to the panel directly; its backend does, via the workspace control