Adom Hydrogen (platform base)

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Adom Hydrogen (platform base)",   "brief": "Layer Hydrogen's workspace onto a standard Adom workstation.",-  "version": "0.3.21",+  "version": "0.3.22",   "description": "Hydrogen's PLATFORM-GENERIC workspace layer on top of adom/core. Installs adom/core for the full Adom ecosystem, then adds everything common to running inside Hydrogen on ANY platform: the runtime-neutral hydrogen-* skills and the generic editor configuration (Claude Code CLI + extension, VS Code settings, trusted domains). Platform-specific layers depend on THIS: adom/hydrogen-windows-bootstrap (WSL2), adom/hydrogen-mac-bootstrap, adom/hydrogen-ubuntu-bootstrap. The reference design other orgs copy to build their own bootstrap on adom/core.",   "org": "adom",   "platform": "any",@@ -31,4 +31,4 @@     "hydrogen editor configuration",     "where do hydrogen skills come from"   ]-}+}\ No newline at end of file

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Adom Hydrogen (platform base)",   "brief": "Layer Hydrogen's workspace onto a standard Adom workstation.",-  "version": "0.3.21",+  "version": "0.3.22",   "description": "Hydrogen's PLATFORM-GENERIC workspace layer on top of adom/core. Installs adom/core for the full Adom ecosystem, then adds everything common to running inside Hydrogen on ANY platform: the runtime-neutral hydrogen-* skills and the generic editor configuration (Claude Code CLI + extension, VS Code settings, trusted domains). Platform-specific layers depend on THIS: adom/hydrogen-windows-bootstrap (WSL2), adom/hydrogen-mac-bootstrap, adom/hydrogen-ubuntu-bootstrap. The reference design other orgs copy to build their own bootstrap on adom/core.",   "org": "adom",   "tags": [

@@ -62,6 +62,28 @@ required to have, so the fallback is always something the user actually has inst - `from_default: true` means it came from the setting rather than your request. - `via: "keybinding"` means it opened without flashing the command palette at the user. +**THE RESPONSE CARRIES NO THREAD ID, EVER** (`sid: null, tid: null`, explicit since+1.0.143): a new thread has no identity until its first submitted prompt, and the tab+itself settles in a background task after this call returns. Do NOT open-then-target:+`new` followed by `run-prompt {sid}` always fails because there is no sid to pass.+To open a thread AND deliver a first prompt, use the ONE-CALL composite:++```bash+curl -sX POST "$BASE/ai-threads/run-prompt" -H 'content-type: application/json' \+  -d '{"new": true, "prompt": "Search Mouser for STM32G474", "submit": true,+       "name": "Parts - say it", "tags": ["dock:my-app"]}'+```++`name` and `tags` stage exactly as they do on `/new` (1.0.143+) and attach when the+sid appears; the response verifies delivery against the on-disk transcript+(`delivered_to`). To find a thread you opened earlier, poll `GET /ai-threads` for your+staged name/tags to attach, never guess by position.++**Client timeouts: give `new` and `run-prompt` 45 seconds.** Opening drives the editor+(extension command, dual detection, tab placement) and legitimately takes 10-30s on a+busy workbench; every CDP touch also serializes through one gate, so calls queue behind+each other rather than failing. A 5-10s client timeout manufactures phantom failures.+ Name one explicitly only when your feature is genuinely AI-specific:  ```bash