KiCad - the KiCad Bridge

@@ -1,6 +1,6 @@ {   "slug": "kicad-bridge",-  "version": "1.0.48",+  "version": "1.0.49",   "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.48",+  "version": "1.0.49",   "tags": [     "kicad",     "pcb",

@@ -602,17 +602,31 @@ Implementation (win_taskbar.py):    bakes tiles at button creation.    The overlay badge and progress bar NEVER needed an AUMID - ITaskbarList3    works per-hwnd on native buttons - so activity indication is unaffected.-   KNOW THE BASELINE before diagnosing: with all overrides removed, DEFAULT-   KiCad on Win11 with taskbar buttons combined shows a GENERIC WHITE icon for-   grouped standalone pcbnew/eeschema windows - a known upstream issue-   (kicad.info forum: "PCB Editor Icon turn white in taskbar if open as-   standalone app and using merge taskbar"). Verified on-box 2026-08-23: exe-   icon resource intact (ExtractAssociatedIcon renders), zero AUMIDs on any-   window, full icon-cache rebuild + explorer restart changed nothing, and no-   "Kicad.Kicad.*" string exists in any shipped binary - the installer stamps-   that AUMID onto the MAIN shortcut only, which is why kicad.exe's button-   renders and the editors' group doesn't. So a white editor-group icon is-   stock behaviour, not our damage; do not "fix" it without John asking.+   THE WHITE-ICON MECHANISM, solved end to end on John's taskbar 2026-08-23+   (read this before ever touching taskbar identity again):+   - Editors opened FROM the KiCad manager run inside kicad.exe, present the+     main AUMID (Kicad.Kicad.kicad.<ver>), and group under the main Ki button+     with its correct icon.+   - STANDALONE editor processes - which is how THIS BRIDGE launches pcbnew -+     present runtime-built AUMIDs (Kicad.Kicad.pcbnew.<ver>; read them from+     the taskbar buttons' UIA AutomationIds, the definitive probe). KiCad's+     installer writes the AUMID onto the MAIN shortcut only and leaves it+     BLANK on the standalone editor shortcuts, so the shell has no shortcut to+     resolve the editor group's icon from. Some machines then fall back to the+     window's own icon (ConfRoomROG rendered fine), others paint the generic+     white page (AdomLapper; the fallback difference is unexplained - exe icon+     intact, window HICONs intact, no registry overrides, icon-cache rebuild+     changed nothing).+   - THE FIX (upstream-shaped, no Adom identity): write KiCad's OWN AUMID+     onto KiCad's OWN user-level standalone shortcuts+     (`_repair_kicad_shortcut_aumids`, in the boot repair, idempotent,+     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.+   - 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,+     live with it" (ConfRoomROG disproved).  ### The footprint stale-cache remedy is a TREE REFRESH, not a restart (2026-08-22, #51)