molecule-publish

@@ -1,6 +1,6 @@ --- name: molecule-publish-description: Publish a molecule OR a generic KiCad/EAGLE board to the Adom wiki - one publisher, two shapes — runs the OCCT molecule-mode conversion (anchored GLB + footprint + symbol with stats gates), assembles the component package, and publishes via adom-wiki. The EDA-agnostic middle of the pipeline; companion to adom-molecule-import (which does wiki → Hydrogen). Use when the user says "publish this molecule to the wiki", "upload molecule bundle", "convert and publish my molecule", "publish my board" (plain, non-molecule boards use BOARD MODE - no anchoring gates), or an EDA export skill (kicad-export-molecule, fusion-export-molecule, altium-export-molecule) hands off here after exporting. Every publish also emits the render/ assets (including APM's per-version render archive behind the board version selector) and component dependencies adom-project-manager (APM) reads.+description: Publish a molecule OR a generic KiCad/EAGLE board to the Adom wiki - one publisher, two shapes — runs the OCCT molecule-mode conversion (anchored GLB + footprint + symbol with stats gates), assembles the component package, and publishes via adom-wiki. The EDA-agnostic middle of the pipeline; companion to adom-molecule-import (which does wiki → Hydrogen). Use when the user says "publish this molecule to the wiki", "upload molecule bundle", "convert and publish my molecule", "publish my board" (plain, non-molecule boards use BOARD MODE - no anchoring gates), or an EDA export skill (kicad-export-molecule, fusion-export-molecule, altium-export-molecule) hands off here after exporting. Every publish also emits the render/ assets (including Nucleus's per-version render archive behind the board version selector) and component dependencies adom-nucleus reads. user-invocable: true argument-hint: "<name> --step <f.step> --board <f.kicad_pcb|f.brd> --sch <schematic> [--pin medium|large] [--silk-top png --silk-bottom png] [--org adom]" ---@@ -24,11 +24,11 @@ EDA export skill        THIS SKILL                     adom-molecule-import | Convert | `--molecule --board` (anchor/gold/footprint, ALL stats gates) | plain `step2glb convert` (no molecule flags, no anchor gates) | | Tag | `molecule` | `board` | | Footprint/symbol JSON | required (wire attach points) | not applicable |-| render/ + deps (APM) | yes | yes |+| render/ + deps (Nucleus) | yes | yes |  Decide by the board itself: Adom machine pins + MP1-MP4 markers -> molecule; otherwise board. Both shapes get `<slug>.glb` from step2glb (never an-EDA-native GLB), `model_3d_path` pointing at it, and the APM stages below.+EDA-native GLB), `model_3d_path` pointing at it, and the Nucleus stages below.  ## Contract — inputs vs the published set @@ -44,8 +44,8 @@ JSON are never user-supplied: they come out of the OCCT conversion below. |---|---|---| | yes | STEP (`.step`) | exported ON the design machine so all 3D models (machine pins, contacts, MP markers) are baked in | | yes | Board/layout (`.kicad_pcb` or `.brd`) | what footprint+symbol generation parses |-| yes | Schematic — `.kicad_sch` (EVERY sheet: root + sub-sheets) or `.sch` | source completeness + APM's hierarchical schematic view renders from these |-| board shape | `.kicad_pro` + any `.kicad_sym`/`.pretty` used | APM render sources |+| yes | Schematic — `.kicad_sch` (EVERY sheet: root + sub-sheets) or `.sch` | source completeness + Nucleus's hierarchical schematic view renders from these |+| board shape | `.kicad_pro` + any `.kicad_sym`/`.pretty` used | Nucleus render sources | | generated | GLB | OCCT conversion output — never user-supplied, always published | | generated | Metadata | OCCT footprint/symbol JSONs + the authored `package.json` | | optional | Silk PNGs (top/bottom) | white artwork on transparent |@@ -141,10 +141,10 @@ your anchored GLB is the one `model_3d_path` resolves to.  ## Stage 2.5 — Component dependencies (AUTOMATED, BEFORE publish) -APM lists a board/molecule's components from `package.json.dependencies`+Nucleus lists a board/molecule's components from `package.json.dependencies` (one-hop expand). This stage is NOT optional and NOT the user's job — a publish that skips it produces a board that looks successful but shows up-in APM with no BOM panel (#247, the Taprite carriers). Do it every publish:+in Nucleus with no BOM panel (#247, the Taprite carriers). Do it every publish:  1. **Parse the BOM** (BOM CSV beside the sources, else the `.kicad_sch`). 2. **Electrical rows only** — skip logos, silkscreen art, fiducials,@@ -155,11 +155,11 @@ in APM with no BOM panel (#247, the Taprite carriers). Do it every publish: 4. **MERGE** owner-qualified refs into the Stage 2 `package.json` — before    Stage 3's publish, so each publish cycle produces exactly ONE registry    version (a deps-only follow-up publish creates an extra version whose-   renders are identical: harmless under APM's dedup, but noise in the+   renders are identical: harmless under Nucleus's dedup, but noise in the    version selector).  - Mapping helper: `skills/publish-board/kicad_board_bundle.py` on the-  `adom/adom-project-manager` page (`adom-wiki repo clone adom/adom-project-manager`).+  `adom/adom-nucleus` page (`adom-wiki repo clone adom/adom-nucleus`).   Mind its Value-fallback caveat: value-named symbols like `R_4.3K_0402` are   NOT component slugs — resolve the real MPN. - Write owner-qualified refs (`adom/<slug>`) into `dependencies`. **MERGE,@@ -223,18 +223,18 @@ Verify before declaring done: - the registry tarball is the **source of record per version**: Stage 2's   layout means every publish carries the full board source, and   `adom-wiki pkg install <owner>/<slug>@<version>` delivers any past-  version's files (APM's version selector relies on this for "give me the+  version's files (Nucleus's version selector relies on this for "give me the   source of an older version" — render/ is previews only, never source). -## Stage 3.5 — APM render assets + version archive (AFTER publish, every time)+## Stage 3.5 — Nucleus render assets + version archive (AFTER publish, every time) -APM shows PCB + hierarchical schematics + the board **version selector**-from a pre-rendered `render/` folder; without it, boards trip APM's red+Nucleus shows PCB + hierarchical schematics + the board **version selector**+from a pre-rendered `render/` folder; without it, boards trip Nucleus's red "missing render folder" bar and fall back to slow live rendering.  ```bash-adom-wiki pkg install adom/adom-project-manager   # once per container (needs >= 0.4.1)-adom-project-manager --render-board <slug>        # push-only: writes ONLY render/+adom-wiki pkg install adom/adom-nucleus   # once per container (needs >= 0.4.1)+adom-nucleus --render-board <slug>        # push-only: writes ONLY render/ ```  **Ordering is load-bearing: run this AFTER Stage 3's `pkg publish` + repo@@ -242,7 +242,7 @@ push.** `--render-board` stamps the archive with the version it reads from the PUBLISHED `package.json` on the page — run it before the publish and it stamps the previous version. -`--render-board` (APM >= 0.4.0) **fully owns the version archive** — never+`--render-board` (Nucleus >= 0.4.0) **fully owns the version archive** — never write `render/<version>/` or edit `render/manifest.json` yourself (double-writing fights its content dedup). On each run it: - renders + pushes the top-level `render/*` = current version (including@@ -260,8 +260,8 @@ Verify after the run:  Re-run on every content update so it never goes stale. KiCad sources render today; EAGLE/Fusion (`.brd`/`.sch`) pages report "nothing rendered" and skip-gracefully — APM shows a static version label for them (Fusion rendering is-landing in APM; nothing changes on this side when it does).+gracefully — Nucleus shows a static version label for them (Fusion rendering is+landing in Nucleus; nothing changes on this side when it does).  ## Publish completion checklist (a publish is NOT done until all pass)