KiCad - the KiCad Bridge

@@ -45,15 +45,12 @@ zero unconnected items. Warnings are reported separately. It leaves edits unsave unless `--save` is supplied. Each call is a native Undo step. The board need not be foregrounded for IPC edits; visual evidence requires a window capture. -The current test host is AdomLapper, authorized while arav-rog runs another demo.-Before merging, run both modes on the authorized test host, verify vias/branches and native Undo,-exercise wrong-net/stale-revision/clearance rejection, and confirm the installed-ab fix preserves a pinned cache during refresh and explicit install attempts.+Acceptance for a release: run both modes on a test box, verify vias/branches and native Undo,+and exercise wrong-net/stale-revision/clearance rejection (see the verified results below). -The companion [ab source patch](ab-dev-pin-fix.patch) applies to ab commit-`792b5c0a` (2.1.38). It includes the production guard and its standalone Rust test-harness. It has not been built as a complete Windows application or deployed;-the explicit-install protection must not be claimed until that is done.+The companion [ab source patch](ab-dev-pin-fix.patch) targeted ab 2.1.38 and is historical:+ab 2.1.70 ships the explicit-install guard upstream (adom-bridge#159), verified on arav-rog+2026-09-07 with ab 2.1.71: bridge_install while dev-pinned returns errorCode dev_pinned.  All routing and recording run in the background. For UI verification, inspect `desktop_ui_tree` and invoke `desktop_ui_click`; use exact Win32 menu commands@@ -79,8 +76,13 @@ Pinned refresh returned `pinned_dev`; the live routing source hash was identical before and after. Explicit bridge_install protection landed upstream in ab 2.1.70 (adom-bridge#159), so the companion patch is historical. -The companion ab patch also passed `cargo check --locked` against current-2.1.39 source in an isolated Windows checkout on AdomLapper. All four pin guard-tests passed there as well as in the container. The running ab executable was-not replaced; live explicit-install rejection remains a deployment acceptance-check, and no signed/packaged ab release was built.+The companion ab patch passed `cargo check --locked` against 2.1.39 source and its four+pin-guard tests, but was never shipped; the upstream guard in ab 2.1.70 superseded it.++## Verified result (2026-09-07, arav-rog, release 0.9.340)++Both modes passed on arav-rog with KiCad 10.0.3, ab 2.1.66, Python 3.12 and the vendored+`routing_deps/cp312`: six nets, 13 pads, 20 segments, two vias, zero DRC errors, zero unconnected+(three warnings for the fixture's uninstalled library). Wrong-net, stale-revision and crossing-route+rejection, dry-run immutability, removal of all 22 items and native Undo/Redo passed. Evidence:+[evidence/arav-rog-2026-09-07.json](evidence/arav-rog-2026-09-07.json).