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.22",+  "version": "0.3.23",   "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",

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Adom Hydrogen (platform base)",   "brief": "Layer Hydrogen's workspace onto a standard Adom workstation.",-  "version": "0.3.22",+  "version": "0.3.23",   "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": [

@@ -79,10 +79,19 @@ 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.+**Client timeouts: 45 seconds for targeted calls, 120 for the `new:true` composite.**+Opening drives the editor (extension command, dual detection, tab placement) and its+internal create cap alone is 60s 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. On a create-timeout error, follow the response's+`_hints`: poll GET /ai-threads for your staged name/tags (a late tab claims them), then+deliver by `tid`; a blind retry opens a duplicate.++**Adopt semantics (1.0.143+):** when an idle EMPTY Claude tab already exists, the+composite delivers into it (`adopted_empty_tab: true`) instead of asking the editor for+a new tab, which is deterministic where the editor's own "new conversation" may reuse an+arbitrary tab. Every /ai-threads response also now carries `_hints` telling the calling+AI what happened and how to recover; surface that text in your failure UI.  Name one explicitly only when your feature is genuinely AI-specific: