AI Flow

@@ -14,7 +14,7 @@ members = [ ]  [workspace.package]-version = "0.2.28"+version = "0.2.29" edition = "2021" license = "MIT" repository = "https://wiki.adom.inc/adom/adom-aiflow"

@@ -0,0 +1,9 @@+# AI Flow 0.2.29 (2026-10-31)++Fusion lane, issue #114 (with fusion-bridge#135):++- **The project library is written one element per line.** Fusion 2706 raises `PlacePartWorker.cpp ... Condition: assetAdded` on every ADD from a `.lbr` whose XML elements share one line (found by fusion-lane). AI Flow's own 3D injection wrote the library that way. `fusion library` now breaks it into lines. Only whitespace between elements changes, never an element's text or an attribute. Fusion bridge 1.13.47 also rewrites a compact library itself, so either side alone is enough.+- **`fusion schematic` keeps every bridge reply.** The import's `runId`, start reply and final status, and each full `fusion_schematic_run` reply, are saved in `<run>/fusion/schematic/`. `add_failed`, an `assetAdded` assertion and 1.13.46's `no_3d_package` each give the cause and the fix in words, with the saved file named.+- **No false "3D models went elsewhere" hint.** `fusion library` used to say the models went to "Adom AI Workspace" whenever the bridge's build result didn't name a project. It now says so only when the bridge names a different one, and keeps the build replies in `<run>/fusion/library/build3d.json`.++Checked live on the test laptop (Fusion 2706, fusion-bridge 1.13.47): `fusion library`, then `fusion schematic`, with a part that has no 3D model. Every ADD landed, with no Fusion error, every pin on its net, and the design saved.

@@ -1,7 +1,7 @@ {   "slug": "adom-aiflow",   "type": "app",-  "version": "0.2.28",+  "version": "0.2.29",   "title": "AI Flow",   "description": "Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board. One Rust binary with a crate per step (placement helpers, a grid router with Kelvin taps, pours with keepouts, KiCad's DRC gate, live landing through the KiCad Bridge, copper measurement, current and thermal analysis) and a finish line that refuses an unfinished board. Every command answers with hints for the AI; every turn, its thinking time and every rework loop go into run.jsonl, so Claude, Codex and any other engine are compared on the same flow. KiCad, Fusion 360 and Altium Designer today (the same steps and gates through each tool's bridge); Adom's own web apps next.",   "summary": "Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board. The AI thinks its way from placement through routing, pours, current and thermal analysis to a delivered video; the binary does the fast, deterministic parts of every step, hands back hints, and keeps a ledger of every turn, every return to an earlier step, and the clock from the prompt to done.",

@@ -1,7 +1,7 @@ {   "slug": "adom-aiflow",   "type": "app",-  "version": "0.2.28",+  "version": "0.2.29",   "title": "AI Flow",   "description": "Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board. One Rust binary with a crate per step (placement helpers, a grid router with Kelvin taps, pours with keepouts, KiCad's DRC gate, live landing through the KiCad Bridge, copper measurement, current and thermal analysis) and a finish line that refuses an unfinished board. Every command answers with hints for the AI; every turn, its thinking time and every rework loop go into run.jsonl, so Claude, Codex and any other engine are compared on the same flow. KiCad, Fusion 360 and Altium Designer today (the same steps and gates through each tool's bridge); Adom's own web apps next.",   "summary": "Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board. The AI thinks its way from placement through routing, pours, current and thermal analysis to a delivered video; the binary does the fast, deterministic parts of every step, hands back hints, and keeps a ledger of every turn, every return to an earlier step, and the clock from the prompt to done.",