KiCad - the KiCad Bridge

@@ -8,7 +8,7 @@ DRC/ERC, export manufacturing files, and screenshot any window back to the AI. > > | | **Release ZIP** (`adom-bridge-kicad-v*.zip`) | **Package** (`adom-wiki pkg install adom/kicad-bridge`) | > |---|---|---|-> | What it is | The **bridge runtime**: the actual Python server that drives KiCad | **Skills + docs only**, for a container/agent |+> | What it is | The **bridge runtime**: the native Rust `kicad-bridge.exe` that drives KiCad (the Python server it replaced is kept in the repo for reference) | **Skills + docs only**, for a container/agent | > | Who loads it | **Adom Bridge** downloads it automatically via `adom-bridge-kicad-manifest.json` | You, into a container, to teach an agent the `kicad_*` verbs | > | Contains | code, certs, UIA scripts, board template | `SKILL.md` files (no binaries, no images) | > | You install it manually? | **No**: Bridge handles it | Yes |@@ -257,3 +257,7 @@ The bridge binds `ADOM_BIND_HOST` on a Bridge-assigned port, never `0.0.0.0`. Au (architecture + hard-won findings), `kicad-bridge-publish` (release recipe), and `kicad-bridge-hero` (page hero recipe). Maintainers get them with the normal `pkg install`; everyday users are never offered them.*++## Contribute++This page's repo is the full source (`adom-wiki repo clone adom/kicad-bridge`): the Rust bridge, the skills, the docs and the release tooling. Hit a bug or a missing verb? File it with the verbatim reply, and if you fix it, send a branch PR off the current head; Adom merges PRs within minutes during business hours and ships to the insiders tier the same day. The recipe, the build commands and the rules that keep a PR mergeable are in the [kicad-bridge-contributing](skills/kicad-bridge-contributing/SKILL.md) skill and in [CONTRIBUTING.md](CONTRIBUTING.md).

@@ -481,3 +481,4 @@ Rules live on the wiki page adom/pcb-design-rules and are fetched at call time, - **The Adom PCM libraries** (symbols, footprints and 3D for every part on the Adom line): `kicad_pcm_install {"repositoryUrl":"https://wiki.adom.inc/api/v1/pages/kicad-pcm/files/repository.json","identifier":"inc.adom.kicad.basic-parts"}` (also `inc.adom.kicad.rp2040`). KiCad registers the libraries on its next start. - Never quote a wiki page you have not fetched: `aravk/in-s42ata`, an older example, no longer exists. +- **kicad-bridge-contributing**: you hit a bug or a missing verb: file it with the verbatim reply, disclose any workaround, and how to clone this page's repo, build, test and send a branch PR that gets merged within minutes.

@@ -1,8 +1,8 @@ {   "slug": "kicad-bridge",-  "version": "1.0.142",+  "version": "1.0.143",   "type": "app",-  "description": "Skills for your container so your AI knows how to drive the KiCad bridge. The bridge runtime itself is the release zip; Adom Bridge loads that.",+  "description": "Skills for your container so your AI knows how to drive the KiCad bridge, and how to contribute a fix back (kicad-bridge-contributing). The bridge runtime itself is the release zip; Adom Bridge loads that.",   "tags": [     "kicad",     "pcb",@@ -36,6 +36,7 @@     "skills/kicad-web-control/SKILL.md",     "skills/kicad-uia/catalog.json",     "skills/kicad-uia/SKILL.md",+    "skills/kicad-bridge-contributing/SKILL.md",     "skills/kicad-bridge-dev/SKILL.md",     "skills/kicad-bridge-publish/SKILL.md",     "skills/kicad-bridge-hero/SKILL.md",

@@ -4,7 +4,7 @@   "slug": "kicad-bridge",   "title": "KiCad - the KiCad Bridge",   "brief": "Reference implementation of the KiCad bridge: multi-instance Python server, forward path via kicad-cli, reverse path via in-process plugin. Most complex of the three bundled bridges.",-  "version": "1.0.142",+  "version": "1.0.143",   "tags": [     "kicad",     "pcb",@@ -71,7 +71,7 @@   "skills": [],   "author_name": "John Lauer",   "source_visibility": "public",-  "description": "Skills for your container so your AI knows how to drive the KiCad bridge. The bridge runtime itself is the release zip; Adom Bridge loads that.",+  "description": "Skills for your container so your AI knows how to drive the KiCad bridge, and how to contribute a fix back (kicad-bridge-contributing). The bridge runtime itself is the release zip; Adom Bridge loads that.",   "dependencies": {     "adom/adom-bridge": "^2.0.3"   },@@ -95,6 +95,7 @@     "skills/kicad-web-control/SKILL.md",     "skills/kicad-uia/catalog.json",     "skills/kicad-uia/SKILL.md",+    "skills/kicad-bridge-contributing/SKILL.md",     "skills/kicad-bridge-dev/SKILL.md",     "skills/kicad-bridge-publish/SKILL.md",     "skills/kicad-bridge-hero/SKILL.md",

@@ -182,3 +182,10 @@ When injecting a model reference for a non-standard component, the STEP model an - [ ] USB-C connector visible if present - [ ] LED packages visible and arranged in expected pattern - [ ] No error dialogs in KiCad++## Inspect every saved model binding++`kicad_model_check {"boardPath":"<saved board>"}` returns `modelBindings` for every footprint, including successful bindings and intentionally model-free footprints. Each row carries the footprint UUID, reference, layer and model resolution, transforms and hidden state. `limit` truncates only the warning list, never this inventory. Compare these bindings to the selected library variants before filming.++This is explicitly `evidenceSource: saved-board-file`: unsaved editor edits are not included. Save the exact intended board first. `renderVerified` remains false; inspect the native 3D viewer to verify placement, appearance and visibility. A resolved file is not proof of correct geometry or orientation.+

@@ -793,6 +793,11 @@ Implementation (win_taskbar.py):      version-detected). Effective at the next explorer restart/logon - the      repair never restarts explorer itself; AdomLapper needed one manual      explorer restart to pick it up, then rendered KiCad's real green icon.+   - NATIVE BUILD (1.0.30, 2026-09-19): the same repair is in process, no+     PowerShell: `crates/kicad-platform/src/win/shortcuts.rs`, run once at+     every bridge start from main.rs and on demand as `kicad_taskbar_repair`+     (one row per shortcut: written / already / missing / error). ConfRoomROG+     showed the white page again on 1.0.29 because the port had not carried it.    - Dead-end theories, so nobody re-walks them: shell icon cache (rebuilt,      no change), our old AUMID registrations (registry had none), dead      Program Files shortcuts (all targets exist), "it's upstream default,

@@ -65,10 +65,32 @@ The shunt's two sense taps are the case every pour gets wrong. The recipe that s 2. Write the pours as JSON, the `kicad_add_zone` shape: net, layers, polygon in mm, priority, connection. Draw each polygon from the pads it must cover (contacts, tabs, bulk capacitors), not from a guess; leave the sensitive parts above outside every non-ground polygon. 3. Gate offline: `tools/add_pours.py BOARD-routed.kicad_pcb --pours pours.json --drc --baseline BOARD-unrouted.kicad_pcb` splices the zones into a copy and runs KiCad's DRC with the zones filled: zero new errors, zero unconnected. 4. Land live: one `kicad_add_zone {"zones": [...]}` call per group (one undo step), or one per zone when the human should be able to undo them singly. The verb runs the same preflight on the editor's snapshot before anything lands and fills the new zones after.-5. Measure: `kicad_zone_state {"refill": true}` gives the filled copper per layer and the coverage. Report the numbers before and after the pours. That is the ablation metric.+5. Measure: `kicad_zone_state {"refill": true}` only requests the refill and answers an acknowledgement (`refillRequested:true`, no revision, no areas), because KiCad fills asynchronously. Wait a few seconds, then `kicad_zone_state {"refill": false}` gives the filled copper per layer and the coverage, with a revision you can use. Report the numbers before and after the pours. That is the ablation metric. 6. Validate: `kicad_routing_validate` on the live board: zero new errors, zero unconnected, and read the warnings (copper slivers, thermal reliefs that could not be made). 7. Second look at the layout: if a rail pour is choked to a neck by a trace crossing it, move the trace (rip it with `kicad_remove_route`, route it on the other layer); if a hot tab has no copper because a part sits beside it, move the part (`kicad_move_footprint`) and route again; if a pour cannot reach a tab because the current has to cross a signal bus, add a via row and a matching pour on the other layer. Then gate, land, measure again. This is the same going-back that got the board to 100 percent routed; the pour numbers tell you when it is worth it.  ## What to report  Per layer: filled copper before and after, in mm2 and as a percentage of the board; per pour: net, layer, area, connection style; the DRC result; and every judgement call above that applied (which nets were deliberately not poured and why). A pour count with no areas is not a report.++## Reconcile a complete owned plan++`kicad_apply_zone_plan` takes the exact `filePath`, a required `expectedRevision`,+explicit `ownedItemIds` (empty on the first call), and `zones` with unique nonempty+names. It preserves every unrelated zone, refuses ambiguous or unowned name+collisions, compares full definitions instead of area, DRC-checks the entire+candidate, then applies removals and additions as one native Undo operation.+Use `dryRun:true` first. Record returned `ownedItemIds` for the next call; neither+a name nor absence from an earlier board proves ownership. `zones:[]` removes+only the explicitly owned IDs. `save:true` is separate and opt-in.++A successful commit can carry `postCommitError` if a later refill, read or save+fails. It still reports committed/mutated and its item IDs: inspect native state+before retrying. An ambiguous transaction outcome must never be replayed blindly.+`kicad_zone_state.definitions` carries the full configuration, including outline+holes/arcs and settings, separately from filled-area summaries. Desired holes+and arcs are refused by the current polygon request schema, not silently omitted.+Unknown or extra native defaults may conservatively cause replacement rather than+an unchanged result. Native Windows acceptance of this new verb is required before+calling it a deployed capability.+