KiCad - the KiCad Bridge

@@ -10,6 +10,20 @@ 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. +## 1.0.77  (2026-10-28 21:57 UTC)++NATIVE (Rust) build. 1.0.77: fanout plans that are safe on a routed board, decoupling caps that leave room for the fanout, and the standard's engine 0.10.3.++- **kicad_plan_fanout:** now planned by the standard's engine, safe on a routed board (standard #22):+  - pins whose net already reaches the pad are skipped (includeRouted plans them anyway);+  - conflicts are measured against other nets' pads, tracks, arcs and vias;+  - an exposed pad's via grid steps round holes already there;+  - crossesPours names the pours the plan runs into.+  - Each call comes back ready for kicad_route_net. The old argument names still work.+- **kicad_place_decoupling:** leaves room for the IC's fanout (leaveFanout, default true): no cap pad lands on the escape stubs or vias of the IC's other pins. Checked on the ESC board's U5.+- **Fix:** 1.0.76's fanout conflict check missed every stub starting at a pad and measured a stub against a pad as an outline. It is now correct, with regression tests.+- **kicad_plan_route** (engine 0.10.3): avoidPours takes a list of nets, and pourCost makes crossing pours a soft cost.+ ## 1.0.76  (2026-10-28 21:31 UTC)  NATIVE (Rust) build. 1.0.76: fanout conflicts, routes that know the pours, the tour template back, and the standard's engine 0.10.0.