AI Flow

--- a/README.md+++ b/README.md@@ -1,221 +1,243 @@⋯ 139 unchanged lines ⋯ KiCad Bridge today. Next backends: the Altium bridge, the Fusion bridge, then Adom's own web apps (adom-schematic, adom-2dboard, adom-3dboard). The board model and the bridge crate are the only ones that know KiCad; the flow, the spec, the ledger and the analyses do not change when the backend does.  +## Optional: try AI Flow: Routing beside the flow++[`adom/adom-aiflow-routing`](https://wiki.adom.inc/adom/adom-aiflow-routing) is a separate whole-board router to try next to this flow. It is not a step of AI Flow, nothing here depends on it, and `route` stays the flow's router. It is offered for comparison on real boards.++It is a dynamic skill by the same rules as this page: it suggests the next step, reports what it found with `OK:` and `Hint:` lines, and never blocks. It searches exact 0/45/90 degree paths instead of a grid, routes in the designer's order (pairs, data, power, the rest), and says why each connection it could not make failed.++```bash+adom-wiki pkg install adom/adom-aiflow-routing+adom-aiflow-routing route placed.kicad_pcb -o routed.kicad_pcb   # a new file; the input is never changed+adom-aiflow-routing check routed.kicad_pcb                      # then KiCad's DRC with zones refilled+```++What to know before trying it:++- Inside a measured run, wrap the command in `adom-aiflow exec --` so its time is on the clock.+- It works on board files (a placed `.kicad_pcb` with its `.kicad_pro`), not through the KiCad Bridge.+- It does not write the plan JSON that `gate --plan` and `land route --plan` take, so its copper does not land through the flow yet. Route a copy of the placed board and put the result beside the flow's own.+- On 22 public wiki boards stripped and routed again, 19 come out clean in KiCad. It does not finish a two-layer power board with many small pours, and two dense boards keep 4 or 5 connections open. The pictures and data are on its page.++Findings from a trial are welcome as issues on that page.+ ## Roadmap  Everything below is what John has asked for, in the order it is likely to land. 0.1 is what this page describes; nothing here is built until its version says so.⋯ 73 unchanged lines ⋯ ## Automatic progress dashboard  AIFlow opens its Hydrogen timeline automatically when a run starts or resumes, for every AI engine. Existing tabs are reused; each project gets its own server identity. Closed tabs and stopped servers recover on the next command. UI failures are reported separately from design checks. Use `timeline open` to bring it forward explicitly, or `AIFLOW_DASHBOARD=off` for headless automation.+