AI Flow

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

@@ -159,8 +159,22 @@ Placement checks compare individual native DRC findings with the baseline, not j  Component library footage: keep the full `library-tour` separate. A reviewed five-second `library-overview` artifact may enter compose, with `--review` binding the exact selected STEP/GLB variants, current board, clip and native readback/screenshot. See [the review contract](https://wiki.adom.inc/adom/adom-aiflow/files/docs/library-overview-review.md). Never claim native model matching from a tour alone. +## Native editor readiness++`capture open` must confirm native IPC for the exact board, not only a visible window. KiCad may give its single IPC server to the first editor. On `board_mismatch`, read `capture-open-ipc.json` or `place-land-log.json`, save and gracefully close only your task-owned conflicting editors, and reopen the intended board first. Never close another user's work or restart a shared bridge. Permanent identity refusals are not retryable. Reject a static failed take and record the reason before re-taking it.++Tours use the complete pinned canonical viewer release, served locally with the tour. On a viewer load error, rebuild with `tools/library-tour.py build --manifest <selection.json> --out <tour-dir>` and inspect the explicit error before recording. Native variants and tour selection must agree, including pin-one markers and the chosen LED/MPN state.++Zone ownership comes only from successful native creation item IDs recorded by this run. Never infer ownership because a zone was absent from intake, has a familiar name, or has the same area. Preserve unowned zones and resolve name conflicts explicitly. The current bridge applies the complete owned plan in one native transaction; there is no separate delete/create fallback. Inspect any post-commit failure before resuming.+ ## Optional conducting heatsinks and signal checks  Fields 0.4.0 supports specified rectangular conducting blocks, per-layer copper thickness, and a Signals view. Read its `docs/heatsinks-and-signals.md` before adding `heatsinks`, `copperUmByLayer`, or `signals` to the run spec. Model only real proposed assembly geometry with justified conductivity/contact and dielectric data. Never invent a heatsink or change the load to make a gate pass. Re-solve after spec changes so input hashes remain valid.  For high-speed nets, explicitly define capacitance or differential-pair checks with consistent stackup and reference copper. `adom-fields ui --port 8874 view --quantity signals` shows the results. Record unsupported cases and limitations; a screening estimate is not manufacturing or signal-integrity qualification. Native EDA model/text/zone primitives remain bridge-owned; pending bridge PRs are not deployed capabilities.++## Native zone ownership and refill++`land pours` delegates the complete owned-zone plan to KiCad Bridge in one native transaction. Never replace another tool's zones or infer ownership from names, areas or absence in the intake board. Use Bridge 1.0.24+; no legacy delete/create fallback. An unchanged plan is not a DRC-clean certificate.++Refill acknowledgement is asynchronous. Request it once, then read without refill until two delayed revision/area snapshots agree. This proves observed stability, not a native completion event. Do not use the acknowledgement's old geometry; do not replay a timed-out or post-commit-failed mutation. Inspect the saved response, exact board and current revision. Measurement failure must remain a failed outcome. See docs/native-zone-landing.md.

@@ -0,0 +1,3 @@+# AI Flow 0.1.32++Same runtime changes and acceptance as [0.1.31](release-0.1.31.md), with the root skill synchronized to the installed AI Flow skill and the bundled page metadata version synchronized to the package. Discovery fields are preserved. This corrects packaging drift found by the publication linter; it adds no new native capability claim.

@@ -1,7 +1,7 @@ {   "slug": "adom-aiflow",   "type": "app",-  "version": "0.1.31",+  "version": "0.1.32",   "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 today; Altium, Fusion and 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.1.31",+  "version": "0.1.32",   "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 today; Altium, Fusion and 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.",@@ -86,4 +86,4 @@     "name": "John Lauer",     "email": "[email protected]"   }-}\ No newline at end of file+}

@@ -165,7 +165,7 @@ Component library footage: keep the full `library-tour` separate. A reviewed fiv  Tours use the complete pinned canonical viewer release, served locally with the tour. On a viewer load error, rebuild with `tools/library-tour.py build --manifest <selection.json> --out <tour-dir>` and inspect the explicit error before recording. Native variants and tour selection must agree, including pin-one markers and the chosen LED/MPN state. -Zone ownership comes only from successful native creation item IDs recorded by this run. Never infer ownership because a zone was absent from intake, has a familiar name, or has the same area. Preserve unowned zones and resolve name conflicts explicitly. Current fallback replaces owned zones using separate remove/create operations; inspect a partial failure before resuming.+Zone ownership comes only from successful native creation item IDs recorded by this run. Never infer ownership because a zone was absent from intake, has a familiar name, or has the same area. Preserve unowned zones and resolve name conflicts explicitly. The current bridge applies the complete owned plan in one native transaction; there is no separate delete/create fallback. Inspect any post-commit failure before resuming.  ## Optional conducting heatsinks and signal checks