KiCad - the KiCad Bridge

@@ -10,6 +10,21 @@ unnamed. These entries were reconstructed after the fact from the work they contain, which is exactly the situation the mandatory-notes gate now prevents. Treat them as accurate but secondhand. +## 0.9.347  (2026-09-07 19:10 UTC)++kicad_close honours unsaved work (#84); verified footprint rescan (#51)++## 0.9.347 (2026-09-07): kicad_close honours unsaved work (#84), footprint rescan verified (#51)++- `kicad_close` no longer force-kills an editor that is asking "Save changes?": it reports+  errorCode unsaved_changes with the dialog text and leaves the window open. `discardChanges:true`+  presses Discard for the caller and keeps the close graceful; `force:true` is still the only kill.+  The graceful wait per window is 8 s (was 5 s).+- `kicad_rescan_libraries` takes footprints:["Lib:Name", ...] and loads each in the Footprint Editor after+  the tree refresh, so `verified` is measured (the last one stays shown). Measured on 0.9.343: a footprint installed two hours after+  pcbnew started loads after the in-place refresh, no restart. The stale-editor wording on+  `kicad_install_footprint` now says that instead of demanding a process restart.+ ## 0.9.343  (2026-09-07 18:29 UTC)  Footprint loads with two pcbnew processes; list_footprints reads the fp-lib-table (#81)