KiCad - the KiCad Bridge

@@ -0,0 +1,34 @@+# Prompt for Codex Astra: record your own routing take and send it back++Paste everything below the line into Codex (GPT-6 Astra) in Hydrogen. It produces a screen recording of Astra routing the same six-net fixture the guide uses, publishes the video, and files a wiki issue on adom/kicad-bridge so the bridge's maintainer thread sees it and can add it to the guide.++---++You are GPT-6 Astra in Codex inside Hydrogen. John wants a video of you routing a KiCad board through the Adom KiCad Bridge's AI routing verbs, as a companion to the two recordings on the bridge's autorouting guide. Do all of it yourself and finish by posting a wiki issue with the video link. Do not ask John to do any step you can do.++Read first:+- The guide: https://wiki.adom.inc/adom/kicad-bridge/files/docs/autorouting.md (the section "Live run on ConfRoomROG" and the videos).+- Install the skills so you have the verb contracts: `adom-wiki skills install adom/kicad-bridge`, then read the kicad-bridge and kicad-autorouting skills.++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":"..."}`.++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.+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.+5. Record the monitor, not the window: `desktop_record_start {"monitor": 0, "audio": false, "fps": 30, "reason": "Astra routing video"}`. Window-mode capture shows a white canvas for KiCad's OpenGL surface.+6. Route with the AI engine: `kicad_routing_state {"filePath": B}` for the revision, pads and nets. Plan every trace yourself from the pad positions; do not copy the waypoints in the guide. Land each net with `kicad_route_net {"filePath": B, "expectedRevision": R, "net": "NET_n", "points": [...], "width": 0.25}` (use `paths` for the branched NET_6, and change layer with a via on at least one net). Pause about 1.5 seconds between nets so a viewer sees each one land. Finish with `kicad_routing_validate {"filePath": B}`; it must report `errors: 0` and `unconnected: 0`. If a call returns `drc_rejected`, fix the plan and try again; that is part of the video.+7. `desktop_record_stop {"recordingId": ...}`, then `pull_file` the MP4 into the container. Check it: extract frames with ffmpeg at 2 s, mid-take and the end, and confirm the traces are visible. Transcode to 1920 wide H.264 (`ffmpeg -i in.mp4 -vf scale=1920:-2 -c:v libx264 -crf 22 -pix_fmt yuv420p -movflags +faststart -an out.mp4`) and make a poster frame.+8. Publish the video on the adom/codex page: `adom-wiki repo push adom/codex --files docs/videos/astra-routing-six-net.mp4 docs/videos/astra-routing-six-net-poster.jpg -m "Astra routing video: six-net fixture through kicad_route_net"`, then confirm `curl -s -o /dev/null -w "%{http_code}" https://wiki.adom.inc/api/pages/adom/codex/files/docs/videos/astra-routing-six-net.mp4` prints 200.+9. File the issue so the kicad-bridge thread gets it:+```+adom-wiki issue create adom/kicad-bridge --category show-and-tell \+  --title "Astra routing video: the six-net fixture through kicad_route_net" \+  --body "<video URL>, the poster URL, the desktop name, KiCad and bridge versions, the per-net kicad_route_net results (items, revision, drc), the kicad_routing_validate output, the exact commands you ran, and what a viewer should look for in the video. No em dashes."+```+10. Close KiCad with `kicad_close {"discardChanges": true}` (the fixture is throwaway) and tell John the issue URL and the video URL.++The kicad-bridge maintainer thread watches that issue tracker and will add your video next to the Freerouting and Claude Fable 5.1 takes on the guide.

@@ -4,6 +4,28 @@ The Adom KiCad Bridge routes a board two ways, and the user picks. The AI engine  The short version for the AI lives in the [kicad-autorouting skill](../skills/kicad-autorouting/SKILL.md). The nine IPC routing verbs and their regression demo are in [demo/routing/README.md](../demo/routing/README.md). +## Watch both engines on camera++Recorded on arav-rog (KiCad 10.0.3, bridge 1.0.2, 2026-09-12) from the desktop's own monitor, with the PCB editor brought to the front on the idle box. The banner across the top of the canvas is Adom Bridge's recording notice, which stays visible for the whole take so the person at the desk always knows the screen is being captured.++**Freerouting, 12 s.** One `kicad_autoroute {"engine":"freerouting"}` call: DSN written, Freerouting run headless, nine segments landed as native Undo steps, DRC clean.++<video width="100%" controls poster="/blob/app/kicad-bridge/docs/videos/routing-freerouting-poster.jpg">+  <source src="/blob/app/kicad-bridge/docs/videos/routing-freerouting.mp4" type="video/mp4"></video>++[Watch the Freerouting take](https://wiki.adom.inc/api/pages/adom/kicad-bridge/files/docs/videos/routing-freerouting.mp4)++**Claude Fable 5.1, 38 s.** Six `kicad_route_net` calls, one per net, each a native Undo step with a snapshot DRC before it lands: NET_3 changes layer through two vias, NET_6 is the branched net with the spur to J3, and the DRC's "missing connection" count walks down from six to zero as the nets land. `kicad_routing_validate` at the end: 0 errors, 0 unconnected.++<video width="100%" controls poster="/blob/app/kicad-bridge/docs/videos/routing-fable-5-1-poster.jpg">+  <source src="/blob/app/kicad-bridge/docs/videos/routing-fable-5-1.mp4" type="video/mp4"></video>++[Watch the Claude Fable 5.1 take](https://wiki.adom.inc/api/pages/adom/kicad-bridge/files/docs/videos/routing-fable-5-1.mp4)++**GPT-6 Astra in Codex.** A third take is Astra's to make: [the prompt to paste into Codex](autorouting-astra-prompt.md) has Astra route the same fixture, publish its video on the adom/codex page and file a show-and-tell issue on this page so the video gets added here.++The fixture both takes use is [live-routing.kicad_pcb](https://wiki.adom.inc/api/pages/adom/kicad-bridge/files/docs/autorouting/live-routing.kicad_pcb).+ ## What Freerouting is, and why it is optional  - **Who made it.** Freerouting was written by Alfons Wirtz in 2004 as a shape-based autorouter and open-sourced in 2014. Since 2018 it has been maintained by Andras Bodor at [freerouting.org](https://www.freerouting.org/) and [github.com/freerouting/freerouting](https://github.com/freerouting/freerouting), GPL-3.0. It is not a KiCad project; KiCad removed its own autorouter years ago and points users at Freerouting through the Specctra DSN and SES files both sides understand.

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯