KiCad - the KiCad Bridge

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

@@ -637,7 +637,13 @@ the house toggle, two-click Restore defaults, optimistic 5s-bounded saves. `dashboard/ui/assets/shots/` are 1:1 crops of AdomLapper's actual taskbar in each state (bar painted via desktop_taskbar, flash via FlashWindowEx, badge via the overlay verb). NEVER replace them with a drawing; re-capture with-`tools/capture_taskbar_shots.py` after putting the button in the state. Win11+`tools/capture_taskbar_shots.py` after putting the button in the state.+TRAP (John caught it as "grainy, did you fake this?"): `desktop_screenshot_screen`+returns a DOWNSCALED frame (1568 px from a 2560 px display), so a crop of it is+~0.6x of the real pixels, not 1:1. The tool captures on the box with a+DPI-aware CopyFromScreen and pulls the PNG; the modal then sizes each image at+naturalWidth / devicePixelRatio so it renders at the taskbar's own physical+size on a HiDPI screen instead of being upscaled by the browser. Win11 keeps the attention tint after FLASHW_STOP: hide/re-show the window (never foreground it) to clear it. Backend trap fixed the same day: set_settings bool()'d every key, so the enum persisted as True.