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.
Timeout recovery hint points to plugin inventory instead of operation progress
KiCad bridge 0.9.348; KiCad 10.0.5; Adom Bridge 2.1.81 at initial observation (2.1.82 by follow-up); Hydrogen 1.0.297; Windows desktop with Linux CLI caller.
The bridge manifest declares statusVerb: "kicad_status", so the Adom Bridge recovery hint says: "Poll kicad_status until it reports done." Following that hint returns plugin inventory (plugins: [], summary: {alive: 0, total: 0}), with no operation identity, running/completed state or result. The same hint is returned on kicad_status itself.
Reproduction: invoke kicad_window_info {} or kicad_install_symbol {"filePath":"<valid native symbol file>"}; inspect _timeoutHint and statusVerb; invoke that status verb. Our symbol install completed successfully in 63.848 seconds; polling the recommended verb gave inventory rather than progress. We did not force a 130-second timeout and do not claim the install failed.
Expected: timeout recovery points at an actual operation/progress surface, with operation identity and terminal result or an explicit verification step. kicad_progress exists and issue #39 documents its active[] contract; please assess it as the manifest status verb, while making clear that an empty active list alone does not prove a specific operation succeeded. Keep plugin inventory as a separate diagnostic.
Observed current wiki bridge.json also declares kicad_status. This report belongs here because that manifest selects the hint target; the enclosing hint text is generated by Adom Bridge. Related #39 covers implementing progress and is closed; this report is about the manifest/recovery contract. No visual symptom; JSON evidence attached.