Adom Hydrogen

@@ -139,6 +139,20 @@ 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 | +### 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:++```json+"say": [+  "open the symbol in kicad",+  "send this footprint to kicad",+  "show me the board in kicad 3d"+]+```++The dock shows them at the two moments the user is already looking: on the interstitial while your app starts (click copies the phrase) and in the card's hover preview. Your dashboard should carry the same lesson **at the very top**, above the status cards: a "Say it" strip with the phrases, copy on click, and ideally a "Try it" that stages the phrase into the app's own AI thread (your server can reach the Hydrogen control API, and the thread is findable by its `app:<owner/slug>` tag). Every phrase uses your app's noun exactly as users should say it; include the qualifier words they will need (which browser, which profile, which editor).+ ### The three rules that break every first attempt  Each of these was learned from a bundled bridge shipping it wrong: