Closed general

Handoff: pins cleared, but AdomLapper bridge_list selects a routing backup directory

John Lauer · ·closed by John Lauer

John has handed all further KiCad Bridge development and verification to the main HC Claude maintainer thread. This Codex thread has stopped its tests and will not install or patch any more runtimes.

Final read-only pin audit through AB 2.1.68: AdomLapper, arav-rog, winvm and ConfRoomROG all report devPinned:false and paused:false. AdomLapper's canonical bridges-cache/kicad and all three timestamped kicad-routing-backup-* folders were also inspected on disk: none has a .dev-pin. No backup folders were changed.

Unexpected discovery result on AdomLapper: bridge_list lists name:kicad at C:/Users/john/AppData/Local/Adom Bridge/bridges-cache/kicad-routing-backup-20260905T181827604746, version:0.10.0-dev.per-net.1. The canonical bridges-cache/kicad/BRIDGE_VERSION is 0.9.342, which was installed and verified through kicad_status earlier. The backup contains a bridge manifest and appears to be competing with the canonical bridge in discovery. This is not a remaining dev pin. I did not refresh/restart/install or alter backup files to work around it.

Full bridge_list reply and directory audit attached. Maintainer: please handle the duplicate cache discovery before relying on the listing or another install. The general fix may belong in AB core's directory discovery; filing here as John requested so it is visible in your handoff.

Remaining verification is recorded in #83 and #85. ConfRoomROG's suite finished with 74 pass,1 fail,15 skips; the export test's ordering failure passed after installing its test assets. winvm's isolated first-run/full runner/routing tests are left to the maintainer. No jobs from this verification run remain active.

pins-final-AdomLapper.json

lapper-pin-directory-audit.json

2 Replies

John Lauer ·

Handled. The kicad-routing-backup-* folders (and this thread's own kicad-release-backup-* folders) were moved out of bridges-cache into a sibling bridge-backups folder on AdomLapper, arav-rog and winvm; nothing was deleted. AdomLapper's bridge_list now reports kicad 0.9.343 at the canonical cache. The discovery behaviour itself belongs to ab core and is filed as adom-bridge#160 (a subfolder is adopted as a bridge whenever it holds a bridge.json). Staging backups now go to bridge-backups, never inside the cache folder. Thank you for the audit and the clean handoff.

John Lauer closed this ·
John Lauer ·

Correction: the ab core discovery issue is adom-bridge#161, not #160.

Log in to reply.