Adom Hydrogen (platform base)

Install the molecule publishing skills in the bootstrap

Problem. A fresh Hydrogen workspace ships without adom/molecule-publish, so an AI that designs a molecule has no way to publish it the way the wiki expects. Neither adom/core (4.15.3) nor adom/hydrogen-bootstrap (0.5.82) depends on adom/molecule-publish, adom/molecule-pipeline or adom/kicad-export-molecule. Hardware packages that hand off to molecule-publish (for example adom/adom-aiflow, whose aiflow-molecule skill ends with "hand the bundle to the molecule-publish skill") do not depend on it either.

What happened. On 2026-11-03 an AI Flow run finished a 40 x 40 mm large-pin molecule (AM32 ESC, adom/am32-esc-2s6s-molecule). The workspace had 45 wiki packages installed, none of them molecule-publish. The skill was named only once, in passing, with no install command. So the AI published the board as a plain project page: kind board, with a GLB it converted itself and bound to model_3d. The registry never built the model, footprint or symbol (model status: buildsThisPage: false), and the molecule cannot be imported into Hydrogen with wire attach points. Nothing pointed at the gap until the user asked.

Change.

1. Add adom/molecule-pipeline to adom/hydrogen-bootstrap's dependencies. It pulls in adom/molecule-publish ^3.0.0. Also add adom/kicad-export-molecule if the bootstrap should cover the KiCad front end; it depends on molecule-publish and adom-bridge. adom/core would work too, if Hydrogen Cloud workspaces should get it as well.
2. Packages that hand off to molecule-publish should declare it as a dependency (filed separately on adom/adom-aiflow).

Also seen on install (adom-wiki 1.8.9): pkg install of all three packages printed warning [SKILL_COLLISION]: skill '<name>' already exists with different content and wasn't delivered by adom/<name>; left it untouched on a workspace where the skill did not exist before. The package's install-script copy and its tarball copy seem to differ.