KiCad - the KiCad Bridge

@@ -12,10 +12,10 @@ Read first:  The board: the six-net fixture from the guide, 13 pads on three footprints, NET_6 branched (J1.6 to J2.6 with a spur to J3.1), two copper layers. Fetch it with `curl -sLo live-routing.kicad_pcb https://wiki.adom.inc/api/pages/adom/kicad-bridge/files/docs/autorouting/live-routing.kicad_pcb`-and send it to the desktop with `adom-bridge --ai-thread "<your thread name>" --target <box> send_files {"filePaths":["<container path>"],"dest":"C:/Users/<user>/Downloads/adom-gate/astra-routing","reason":"..."}`.+and send it to the desktop with `adom-bridge --ai-thread "<your thread name>" --target arav-rog send_files {"filePaths":["<container path>"],"dest":"C:/Users/arav/Downloads/adom-gate/astra-routing","reason":"..."}`.  Rules that are not optional:-1. Ask John which desktop to use (`adom-bridge targets` lists them) and confirm with `kicad_status` that its kicad-bridge is 1.0.2 or newer and KiCad is 10.0.1 or newer. Pass `--ai-thread` on every call.+1. Use the desktop arav-rog (`--target arav-rog`, Windows user `arav`, the box the two existing takes were recorded on). Confirm with `kicad_status` that its kicad-bridge is 1.0.2 or newer and KiCad is 10.0.1 or newer. Pass `--ai-thread` on every call. Do not ask John which desktop; only fall back to asking if arav-rog is not on the relay (`adom-bridge targets`). 2. Never save the fixture, never route on any other board, never install Freerouting (this take is the AI engine only), never kill KiCad. If KiCad is running, `kicad_close {}` first and stop if it reports unsaved work. 3. `kicad_ipc_api {}` must say enabled. If it does not, enable it with KiCad closed. 4. Open the board on screen: `kicad_open_board {"filePath": B, "foreground": true, "foregroundReason": "John asked for a screen recording of Astra routing; the canvas must be on screen for the recorder"}`. Maximize it with `desktop_ui_window {"hwnd": H, "action": "maximize"}`. Wait until the status bar no longer says "Loading Footprint Libraries". About 25 seconds after opening, the bridge's etiquette loop pushes a newly opened window behind the user's windows once; bring it back with `desktop_bring_to_front {"hwnd": H, "reason": "..."}` and it stays. Take `desktop_screenshot_screen {}` and look at it: the board must be visible and the canvas must not be white before you record.