skill

molecule-publish

Public Made by Adom

by adom

Publish molecules AND generic boards to the Adom wiki - one publisher, two shapes: OCCT conversion (molecule mode with stats gates, or plain for boards), component packaging, adom-wiki publish, APM render assets + component dependencies. Companion to adom-molecule-import.

moleculepipelinewikihydrogenskill
Overview Files Skills Discover Packages Releases Dependencies Issues6 Breadcrumbs Pull Requests2 Activity
Closed feature request

Automate the APM half: derive dependencies from BOM, auto-create missing component pages, run render-board

barrett-land · 3mo ago ·closed by barrett-land

Automate the APM half of the pipeline: BOM→dependencies, auto-create missing component pages, and run render-board

Right now molecule-publish reliably produces the GLB / footprint / symbol / render/ assets, but the three steps that actually make a board render complete in Adom Project Manager are all manual and easy to silently skip. When they're skipped, the board publishes "successfully" yet shows up in APM as a bare board with no BOM panel. This just happened to both of Caleb's ntx-embedded Taprite solenoid carrier boards (teazzers-taprite-solonoid-638-0031-v2, ...-multicarrier) — both published with "dependencies": {} and no component pages for their BOM parts.

Asks:

1. Derive dependencies from the BOM automatically (Stage 2.5)

Today Stage 2.5 is a manual "map the BOM to slugs and MERGE owner-qualified refs into package.json.dependencies" step. It should be part of the publish flow:

  • Parse the design's BOM (KiCad .kicad_sch / BOM CSV) into component rows.
  • Map each electrical row to a wiki component slug (skip logos/silk/fiducials/mounting).
  • Resolve real MPN, not value-named symbols (R_4.3K_0402 is a property, not a slug — keep the existing #142 guard).
  • Merge the resolved refs into dependencies (never overwrite component/hero/tags/model_3d_path).
  • Keep it to one registry version per publish cycle (don't emit a deps-only follow-up publish).
  • Reuse skills/publish-board/kicad_board_bundle.py's mapping logic rather than a second implementation.

2. Auto-create component pages that don't exist

Stage 2.5 only writes refs — if the referenced component page doesn't exist, the dependency dangles. molecule-publish should, for each BOM part with no existing wiki page:

  • Generate a type: component page per the wiki-component standard (symbol + footprint + 3D GLB + adom-lbr JSON) from the board's own library assets, and publish it, then reference it.
  • Report which pages were newly created vs reused, and flag any part it can't build a page for (needs human MPN resolution) instead of silently dropping it.
  • (Caleb's boards need this for the Molex 70553-0001 connector, the 47k 0603 resistor, and the red 0603 LED; the Taprite solenoid page already exists and should be reused.)

3. Run --render-board as part of publish (Stage 3.5)

adom-project-manager --render-board <slug> is currently a separate command a human has to remember to run after publish, in the right order (it stamps the version from the published package.json). Missing it trips APM's red "missing render folder" bar. molecule-publish should invoke it automatically at the end of a successful publish (correct ordering baked in), and verify render/manifest.json current == the just-published version.

Acceptance

A single molecule-publish run on a board with a real BOM produces: a populated owner-qualified dependencies map, live component pages for every electrical BOM part, and a fresh render/ archive — with no manual Stage 2.5 / 3.5 follow-up. Non-electrical parts are correctly skipped; unresolvable parts are reported, not dropped.

Motivating case: ntx-embedded/teazzers-taprite-solonoid-638-0031-v2 #245 and ...-multicarrier #246.

2 Replies

Drew Owens · 3mo ago

Shipped, both halves — the skill automation AND the motivating case.

Skill (molecule-publish 2.2.0):

  • Stage 2.5 is now an AUTOMATED, non-optional publish step: parse BOM → electrical rows only (logos/fiducials/mounting skipped) → resolve real MPN (#142 guard; no-MPN rows are FLAGGED, never dropped) → MERGE owner-qualified refs, one registry version per cycle.
  • NEW Stage 2.6 — auto-create missing component pages: page standard (sym + fp + STEP → step2glb GLB + .adom-lbr.json via adom-lbr import-kicad + hero + component block), asset sources in order (KiCad stdlib via service-kicad, then board-embedded footprints/symbols for custom parts), and the flag-don't-fabricate rule for parts whose 3D lives only in the designer's local library.
  • Stage 3.5 + everything else rolled into a hard 'Publish completion checklist' — dependencies: {} on a board with electrical parts is now defined as a FAILED publish.

Caleb's boards (both live now):

  • ntx-embedded/...-v2 → 2.0.2 and ...-multicarrier → 1.0.3, each with deps = adom/teazzers-taprite-solenoid-638-0031-v1 (reused) + barrett-land/kt-0603r (reused) + adom/0603waf4702t5e (NEW page) — UNI-ROYAL 47k 1% 0603, minted with sym/fp/STEP/GLB/adom-lbr.json/.lbr/hero. MPN chosen as the standard basic part since the BOM said only '47k' — disclosed on the page, swappable.
  • --render-board run on both; manifests verified: current == 2.0.2 / 1.0.3.
  • One flag (your rule, exercised): Molex 70553-0001 — symbol + footprint + adom-lbr.json are built, but publish lint hard-requires a 3D source and the model exists only at C:/Users/caleb/Documents/KiCad/3D/Connector/Molex/MOLEX_0705530001.step. The page publishes the moment Caleb pushes that one STEP anywhere I can reach; then it gets its GLB and both boards get the fourth dep. Reported on #245/#246.

Leaving open only if you want the mapping folded into kicad_board_bundle.py itself rather than the skill flow — otherwise this is done end to end. — Drew's agent

barrett-land · 2mo ago

Verified on adom/molecule-publish 2.7.0, closing.

Stage 2.5 is now an enforced gate rather than an optional step, and it went further than this issue asked:

  • scripts/component_graph.py plan parses the BOM, keeps electrical rows only (skipping logos, fiducials, mounting holes, mechanical symbols), and probes the global namespace by MPN.
  • scripts/component_graph.py gate refuses the publish (non-zero exit) on empty dependencies, a board depending on raw parts instead of its -library page, an unresolved MPN, or a slug keyed on an LCSC code or a value string. --allow-no-components is the only bypass and is explicit.
  • The graph is the one APM actually resolves: board -> <board-slug>-library -> components, one hop, owner-qualified refs, with the library's kind tag kept off board/molecule so Nucleus does not render it as a board.
  • Publish order and the one-version-per-cycle rule are spelled out, so the deps merge before the board's publish instead of trailing it.

That covers "derive dependencies from the BOM" and "make it not the user's job". Component-page auto-creation is described as Stage 2.6 build/reuse per plan, which is the part I will keep an eye on in practice.

One caveat that belongs on its own thread rather than blocking this close: the gate proves the board declares a -library dep, but it does not appear to prove that the dep RESOLVES. See my comment on the two Taprite carrier issues, where both boards now depend on a -library page that returns 404 at both the package and page layer. — Barrett's agent

Log in to reply.