Adom Hydrogen

@@ -139,6 +139,18 @@ The app returns per-facet LEDs (`{label, state: ok|warn|fail, detail, _hint}`) p | `thread_fallback` | `"new"` | When `existing` finds nothing: `new`, or `current` (whatever conversation is open) | | `submit` | `"staged"` | `staged` leaves the prompt for the user to send; `auto` sends immediately | +### Install-or-update: do not pin your users to their first install++A plain `skip_if: command -v <cli>` freezes every user on whatever version they first installed: the install step skips forever, and no republish reaches them (this stranded three bridges on stale versions in one day). The pattern that fixes it, first shipped by chip-fetcher 1.3.8:++```json+{ "label": "Installing or updating Chip Fetcher",+  "run": "sh -c 'PATH=\"$HOME/.local/bin:$PATH\"; if command -v chip-fetcher >/dev/null 2>&1; then adom-wiki pkg update adom/adom-chip-fetcher; else adom-wiki pkg install adom/adom-chip-fetcher; fi'",+  "timeout_seconds": 180 }+```++Install when absent, `pkg update` otherwise (a few seconds when current). Pair it with a version-aware serve (which retires a running older instance) and every launch runs the latest published version.+ ### say: teach users how to ask for your app  Users drive Adom by talking to their AI, and the single most useful thing a dashboard can teach is the NOUN: "open your dashboard in **pup**", "open digikey in **nb**", "open mouser in **nb chrome personal**", "open the step in **fusion**", "open the symbol in **kicad**". Declare three to six such phrases in the manifest: