KiCad - the KiCad Bridge

@@ -4,14 +4,16 @@ 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 all three in 90 seconds+## Watch all three in 21 seconds -The three takes below, ganged into one narrated video: each recording at 10x, held on its result while the narration explains it, captions in the Adom fonts over the live screen. Nothing else was added to the frames.+The three takes below cut to the action only, in real time: nothing sped up, the idle seconds before, between and after the commits removed, and the real duration of each engine's work stated on screen. Narration is written to the measured length of the cut, so it neither pads nor runs over.  <video width="100%" controls poster="/blob/app/kicad-bridge/docs/videos/routing-three-engines-poster.jpg">   <source src="/blob/app/kicad-bridge/docs/videos/routing-three-engines.mp4" type="video/mp4"></video> -[Watch the three-engine video](https://wiki.adom.inc/api/pages/adom/kicad-bridge/files/docs/videos/routing-three-engines.mp4)+[Watch the three-engine cut](https://wiki.adom.inc/api/pages/adom/kicad-bridge/files/docs/videos/routing-three-engines.mp4)++What the real times mean: Freerouting's 3.2 s is one `kicad_autoroute` call end to end. The 25 s (Fable) and 28 s (Astra) are six `kicad_route_net` round trips through the relay to the desktop, about four seconds each, of which the copper landing is a single frame; the rest is the call and the deliberate 1.5 s pause between nets so a viewer can follow, and that is the idle the cut removes.  ## Watch both engines on camera 

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯