KiCad - the KiCad Bridge

@@ -1,6 +1,6 @@ {   "slug": "kicad-bridge",-  "version": "1.0.46",+  "version": "1.0.47",   "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.",   "tags": [

@@ -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.46",+  "version": "1.0.47",   "tags": [     "kicad",     "pcb",

@@ -587,6 +587,18 @@ Implementation (win_taskbar.py):    window - the exact inverse of what it did before 0.9.230, both conclusions    derived from the same one-sentence meaning. +3. **Identity is not activity** (2026-08-23, caught on John's taskbar). The+   BASE icon (AUMID + iconPath, `_ensure_identity`) repairs the white-box shell+   cache we poisoned; it claims nothing about driving, so it must be+   UNCONDITIONAL: an always-on `_identity_sweeper` thread (20s) stamps every+   pcbnew/eeschema window, whoever opened it, verb or no verb. Before the+   sweeper, identity rode only on the badge path - so a window the user opened+   themselves (or one carrying the pre-.v2 stamp from an old bridge process)+   stayed a white box indefinitely, while a window a test verb had touched sat+   correct beside it. Badges and bars stay activity-gated; the base icon never+   is. Corollary: you cannot restamp identity by calling a passive verb -+   that's rule 1 working as designed; the sweeper is the mechanism.+ ### The footprint stale-cache remedy is a TREE REFRESH, not a restart (2026-08-22, #51)  `View > Refresh` (F5) on the Footprint Editor frame reloads the library TREE,