app
KiCad - the KiCad Bridge
Public Made by Adomby adom
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.
← Commit history
autorouting guide: cache-bust the recut video src so browsers drop the old 91 s file
1 file changed
+3−3
docs/autorouting.md+3−3@@ -8,10 +8,10 @@ The short version for the AI lives in the [kicad-autorouting skill](../skills/ki 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>+<video width="100%" controls poster="/blob/app/kicad-bridge/docs/videos/routing-three-engines-poster.jpg?v=21s">+ <source src="/blob/app/kicad-bridge/docs/videos/routing-three-engines.mp4?v=21s" type="video/mp4"></video> -[Watch the three-engine cut](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?v=21s) 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.