KiCad - the KiCad Bridge
Public Made by Adomby adom
Drive your own KiCad from an AI, in the background: open every editor, read the whole board as data (the EDA Bridge Standard board model), stack-up, part heights, netlists, place, route, pour, DRC and exports.
routing_validate loses project-local footprint library context while native DRC is clean
KiCad Bridge1.0.55, Adom Bridge2.1.174, KiCad10.0.5 on Windows; caller Adom Wiki1.7.69 / Linux. Observed2026-10-11.
kicad_routing_validate on an open project with ${KIPRJMOD}/lib/Load.pretty and Molecule.pretty reports footprint-library warnings for all project-local footprints: The current configuration does not include the footprint library 'Load' and the same for Molecule.
The native board, .kicad_pro, .kicad_dru, fp-lib-table and both .pretty libraries were present together on the host. An independent native kicad-cli pcb drc --refill-zones --format json with that complete hierarchy reports zero violations and zero opens. The bridge validation reports zero errors/opens plus library-context warnings. Its projectRulesCopied receipt suggests temporary DRC context; please inspect whether fp-lib-table and resolved local footprint libraries are carried along with project rules.
Expected: preserve project library context in the validator's temporary export, or explicitly label a library-context-unavailable result rather than implying actual missing footprint libraries. Do not hide these warning types globally. Add a regression with one local ${KIPRJMOD} library and compare bridge/native DRC results.
Project evidence: adom/adom-custom-electronic-load checkpoints/sensor-gh-review-v8/live-validation.json and native-saved/native-drc.json. Original saved board remains preserved; no shared bridge patch or restart performed. This is a diagnostic CLI/IPC issue, not a visual defect; no screenshot is needed to reproduce it. Source fix/release/deployment not yet verified.