Codex

@@ -31,6 +31,13 @@ The videos below are real KiCad window recordings. Astra runs in the Adom Hydrog  This establishes explicit per-net/per-trace control. The crossover fixture uses a constructed routing algorithm; it is not evidence of arbitrary-board autorouting. +### Public Adom board: first routing pass++<video controls playsinline preload="metadata" src="https://wiki.adom.inc/api/pages/adom/codex/files/videos/03-public-adom-solenoid-first-pass-3x.mp4" style="width:100%;max-width:1100px"></video>++[Download the preview](https://wiki.adom.inc/api/pages/adom/codex/files/videos/03-public-adom-solenoid-first-pass-3x.mp4). Uses the public [Adom Teazzers Solenoid Driver RP2040 v1.1](https://wiki.adom.inc/adom/teazzers-solenoid-driver-rp2040-v1-1), with 94 footprints and five channels. Astra calculates paths independently, then commits them live through Adom Bridge. Precomputed geometry and 3x playback are labeled. This first pass adds 60 connections as 106 segments, reducing native open items from 118 to 60. Five baseline errors remain. **Full routing is still in progress.**++ ## Real Adom boards: next comparison  A copy of [Adom's Pinch toolboard](https://wiki.adom.inc/adom/workcell-control-toolboard-pinch-v1) has been inspected: 162 footprints, 1,697 trace segments, 405 vias and 51 zones. Baseline KiCad DRC reports 29 errors and 483 warnings, with no missing-connection errors. Those findings are recorded before any changes. Independent rerouting has not yet been demonstrated on this board.

@@ -1,5 +1,5 @@ # Codex follow-up work  - [ ] Give every sub-readme a substantial visual pass: many real screenshots, annotated steps, demo stills, and consistent layouts. Deferred at John's request while the complicated KiCad board takes priority.-- [ ] Independently route a stripped copy of the Pinch toolboard, validate it against the human baseline, then record and caption the live KiCad comparison.+- [ ] Independently route a stripped copy of a verified public Adom board (Teazzers solenoid driver selected), validate against its published baseline, then record and caption the live KiCad comparison. Private development boards are excluded from showcase media. - [ ] Implement the Codex Desktop bridge and dock installation flow.

@@ -36,3 +36,21 @@ Draft review: https://wiki.adom.inc/adom/kicad-bridge/prs/2 These recordings use `0.10.0-dev.per-net.1`. The source is in development, not merged to main. The separate Adom Bridge development-pin protection fix is not represented by these routing videos as deployed.  The original recordings and detailed call evidence are preserved separately in the development workspace. The scripts and caption files make the edits reproducible.++## Public Adom board: visible first pass++The third clip uses Adom's public Teazzers Solenoid Driver RP2040 v1.1. Both the page and source archive were verified accessible without authentication. The reference was preserved; a separate copy had all 542 track/via items removed, retaining all 94 footprints. Private development boards are excluded from this showcase.+++### Public Adom board: first routing pass++<video controls playsinline preload="metadata" src="https://wiki.adom.inc/api/pages/adom/codex/files/videos/03-public-adom-solenoid-first-pass-3x.mp4" style="width:100%;max-width:1100px"></video>++[Download the preview](https://wiki.adom.inc/api/pages/adom/codex/files/videos/03-public-adom-solenoid-first-pass-3x.mp4). Uses the public [Adom Teazzers Solenoid Driver RP2040 v1.1](https://wiki.adom.inc/adom/teazzers-solenoid-driver-rp2040-v1-1), with 94 footprints and five channels. Astra calculates paths independently, then commits them live through Adom Bridge. Precomputed geometry and 3x playback are labeled. This first pass adds 60 connections as 106 segments, reducing native open items from 118 to 60. Five baseline errors remain. **Full routing is still in progress.**+++The planner reads pads and nets from the stripped board, tries straight and diagonal/orthogonal paths, and checks other-net copper, pads, keepouts and board-edge clearance. The accepted batch was checked with native KiCad DRC before recording. No external autorouter generated these paths.++`kicad_routing_state` verifies the empty live board and obtains its revision. Sixty `kicad_route_net` calls with `expectedRevision` and `validate:false` commit the already checked paths. The last call saves the copy. Native `kicad-cli pcb drc --refill-zones` then checks the actual saved board through Adom Bridge `run_script`. Recording uses `desktop_record_window_start` and `desktop_record_window_stop`. Idle startup is trimmed, retained action is 3x, and the final frame is held.++The recorded board has 60 open items and five baseline errors: two courtyard overlaps, two starved thermals and one zone intersection. No new track-clearance or crossing errors were introduced. The published reference itself has three open items and 27 errors under KiCad 10; it is not described as perfect. Full routing and electrical review remain unfinished.

@@ -8,12 +8,20 @@ Parent skill: codex-adom. Read the installed adom-bridge-recording skill for the  ## Record the real editor +For a public showcase, verify both the source page and the design files are publicly accessible before recording. Record only the selected public design window. Keep private development boards and their captures out of the published package and edit inputs. Preserve the published reference and route a separate copy.+ Discover the target, editor HWND, active board, development bridge version and revision. Prepare an isolated board copy and fit it for viewing. Foreground once when the user requested a visible demonstration; preserve their control afterward. Do preparation before recording where possible.  Use Adom Bridge's native window recorder: desktop_record_window_start with the actual hwnd, fps, audio preference, bounded maxDurationMs and reason. Save its recordingId. Start/stop in try/finally, and save the final path. Capture the intended window, not an unrelated browser recorder or the whole desktop.  Log routing calls and their start/end timestamps. Inspect semantic errors, update revisions after each mutation, and validate the finished native board. The KiCad demo dry-ran each complete net and then committed those exact segments/vias visibly. That does not establish that every partial intermediate board passes DRC. Adapt to the actual Fusion bridge contract instead of assuming KiCad verbs exist there. +## Validate complex board routing before claiming completion++For a stripped copy of a real board, refill copper zones before measuring connectivity. Cached pours can make a board appear connected after its traces were removed. Run the human reference and generated candidate with the same project rules and zone-refill settings; report new errors separately from pre-existing errors. Do this on disposable snapshots, preserving the reference and live editor.++A falling unconnected count is not enough: reject crossings, shorts, drill-spacing and edge-clearance regressions. Explicit planners must check against both existing and newly generated copper. Preserve checkpoints and native DRC reports so a failed planning pass can be discarded without losing verified work. USB and other sensitive nets also need their electrical constraints assessed; geometric connectivity alone is not signal-integrity signoff.+ ## Edit for a team audience  Preserve the raw take. Find action intervals from the recording and call log, then visually verify boundaries. Remove idle startup, calculations and validation waits as appropriate. State that waits were removed; this is edited playback, not elapsed runtime.

⋯ 1 unchanged line ⋯