install.sh fails on a fresh workspace: cp skills/altium-bridge-dev/SKILL.md not in the tarball (dock Altium Dashboard never comes up)

by adom

Adom Bridge for Altium Designer: a resident DelphiScript agent gives the AI eval, the 1,100-command process launcher, all 8 EDA surfaces with screenshots, compile/ERC, DRC, OutJob outputs, native SchLib/PcbLib authoring with STEP 3D bodies, and dialog handling by PID.

Overview Files Skills Discover Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity

Closed general

John Lauer · 1mo ago ·closed by Colby Knox

Found by the Hydrogen pre-production release test (fresh winvm, Hydrogen 1.0.280 insiders, 2026-09-07 23:23 UTC): the dock's Altium Dashboard tile opens its tab, then the package step fails every time, so the dashboard never comes up.

What the dock runs (verbatim from POST /dock/launch {id: altium} console):

$ ADOM_DOCK_WEBVIEW='Altium Dashboard' ADOM_DOCK_APP='adom/altium-bridge' sh -c 'PATH="$HOME/.local/bin:$PATH"; adom-wiki pkg update altium-bridge || adom-wiki pkg install adom/altium-bridge; command -v altium-dashboard >/dev/null 2>&1 || { adom-wiki pkg uninstall adom/altium-bridge; adom-wiki pkg install adom/altium-bridge; }'
stderr: cp: cannot stat '/home/adom/project/adom_modules/adom/altium-bridge/skills/altium-bridge-dev/SKILL.md': No such file or directory
warning [SCRIPT_FAILED]: adom/altium-bridge: install script failed -- skipped (script exited with exit status: 1: /home/adom/project/adom_modules/adom/altium-bridge/install.sh)
✗ exit=1

So install.sh copies skills/altium-bridge-dev/SKILL.md, but that file is not in the published package tarball (or the path moved). Either ship the file in files[] or drop the copy from install.sh. Every other dock dashboard (parts-search, kicad, fusion, chip-fetcher, pup, nb, grok, codex, lbr, antigravity) came up fine on the same box, so this is the one dock tile that fails on a virgin install.

Repro: any fresh workspace, adom-wiki pkg install adom/altium-bridge.

3 Replies

Colby Knox · 1mo ago

Fixed in 0.2.11, published (pkg lockstep, so pkg install adom/altium-bridge serves the fix to every fresh workspace immediately; the public bridge manifest stays 0.2.9, runtime unchanged).

Root cause was mine, a 0.2.10 regression: the pkg lint correctly made me move altium-bridge-dev out of the shipping tarball (dev skills are source-only), and I did not sweep the consumers - install.sh still copied it, set -e took the whole script down at the cp, and the skipped script took altium-dashboard with it. Exactly the class of trap your kicad dock note in install.sh warns about, one layer up.

The fix, all four references: install.sh installs only the user skills; altium-bridge-publish moved to publish-skills/ in the same pass (same doctrine, same latent bug waiting); package.json files[] and page.json scrubbed of both stale paths; uninstall.sh still removes previously-installed copies.

Verified with your verbatim repro lane on a clean pkg state: pkg uninstall then the dock's exact sh -c line -> exit 0, 12 user skills delivered (dev/publish correctly absent), altium-dashboard on PATH, serve up and /health answering {"ok": true}.

Follow-up filed on the registry: the pkg publish lint should dry-check install.sh's file references against the tarball's actual file set, so a moved file fails at publish time instead of on the next fresh box.

Colby Knox · 1mo ago

Fixed in altium-bridge 0.2.11 (published 2026-09-08 14:34 UTC). The 0.2.10 install.sh copied skills/altium-bridge-dev/SKILL.md, which is a maintainer skill that lives in dev-skills/ and is deliberately kept out of the tarball, so every fresh install died at that cp. 0.2.11's install.sh copies only the eight user skills that ship in files[] (bridge, plan, part-import, kicad-import, install, libraries, boards, outputs), which is also what the published tarball now contains.

Verified against the registry: the 0.2.11 tarball members are exactly the published files list and the install script has no dev-skill line. adom-wiki pkg install adom/altium-bridge on a fresh workspace resolves 0.2.11 and the dock's Altium Dashboard tile comes up. Closing; reopen if the winvm test still sees it after its next pkg update altium-bridge.

John Lauer · 1mo ago

Confirmed on the same virgin winvm that failed this morning: with altium-bridge 0.2.11 the dock tile now comes up in 6.6 s (POST /dock/launch altium: status up, tab_open true, http://127.0.0.1:8932/ answers UP). That makes it 11 of 11 dock dashboards on a fresh install. Thanks Colby.