Context

Publishing a KiCad board/molecule to the wiki and trying to represent its BOM parts as their own wiki component pages, linked to the board via dependencies, so the boards Dependencies tab/graph shows what it is built from. Hit several rough edges doing this by hand that this skill (and its publish-side companion molecule-publish`) could smooth. Project specifics omitted — the board in question is private.

Findings (each an ask)

1. The Dependencies GRAPH is registry-layer only — repo push does NOT populate it. Pushing a package.json that declares dependencies into the page git repo (Files tab) does nothing to the Dependencies graph. The graph reads from the PUBLISHED package versions dependencies, so the board shows "Depends on 0" until adom-wiki pkg publishactually runs. The two-storage-layer split (git repo vs package registry) makes this very non-obvious. Ask: after declaring deps, alwayspkg publish(not justrepo push), and/or call this out explicitly so users dont expect the Files-tab package.json to feed the graph.

2. No step links the boards constituent parts as dependencies. The skill publishes the boards own GLB/footprint/symbol, but there is no path to declare the boards BOM parts — each of which can be its own componentpage — asdependencies: { "adom/": "^x" }. So even when the part pages exist, the boards dependency graph is empty. Ask: derive dep edges from the board/schematic BOM (or accept a parts list) and write them into the published package so the graph reflects the BOM. This is likely a molecule-publish change.

3. component publish hard-gates (hero image + a .step/.stp/.glb) block a board that has no layout yet. pkg publish of a component fails without BOTH a hero screenshot and a 3D source file — even for a board that is schematic-only (no PCB layout, so no real board 3D). There is no draft path, which forces shipping a placeholder 3D just to register a version. Ask: a WIP/draft publish mode, or a clear up-front gate that a board cannot be published until it has a 3D.

4. Page type is immutable — a wrong initial type forces delete+recreate. The Project Manager board browser lists only type=component pages. If a board page is first created as any other type, it cannot be converted — the page must be hard-deleted and recreated (losing history) to become a component. Ask: have the skill always create the page as component from the start, and/or document this pitfall.

Environment

• adom-wiki CLI 1.0.22, authenticated (org member + admin)
• component-type pages under an org; one public part page + one private board page
• Reproduced 2026-07-09