KiCad - the KiCad Bridge

The latest published manifest of adom/kicad-bridge (1.0.17) declares dependency adom/adom-desktop@^1.9.0. Since adom-desktop was renamed to adom-bridge (now at 2.0.7), the registry resolves this as adom/adom-bridge@^1.9.0, which conflicts with every package that wants ^2.x (e.g. adom/[email protected] declares adom/adom-bridge@^2.0.3). Result: 'adom-wiki pkg install adom/kicad-bridge' fails with DEPENDENCY_CONFLICT (specs: latest, ^2.0.3, ^1.9.0) on any container that has adom-bridge 2.x, and kicad-bridge cannot be installed at all. Fix: republish kicad-bridge with the dependency renamed to adom/adom-bridge@^2.0.0. Note: adom/[email protected] also still references the old name (adom/adom-desktop@'*'); the wildcard doesn't conflict but should be renamed too while you're in there. Found on container galliaApril (adom-wiki CLI 2.49.0) while debugging why the adom-core auto-update hook failed. Related cleanup we had to do locally: old-slug packages (adom-desktop-puppeteer-bridge, adom-desktop-kicad-bridge, adom-browser-extension, hd-bootstrap) left stale ^1.9.x pins in adom_modules/.lock.json even after uninstall, which kept the resolve failing until the lockfile entries were pruned by hand -- possibly a second bug (uninstall should prune lock entries).