AI Flow

@@ -89,6 +89,7 @@     "email": "[email protected]"   },   "confirmed_user_skills": [-    "aiflow-simulate"+    "aiflow-simulate",+    "aiflow-test-plan"   ] }\ No newline at end of file

@@ -97,24 +97,3 @@ For a short silkscreen population video, prefer a fixed full-board camera with F - After reopening the editor, start the clip with `capture start` (0.1.38 finds the reopened editor window); check the clip is recording before the first label. - Read the saved board back: every label at its designed position, layer and rotation, then the gate's native DRC and a native render of each face (`kicad-cli pcb render --side top|bottom`). - The dashboard replay opens in a Hydrogen webview on the user's machine; when the work has to stay on the test box, leave board.json and events.jsonl in the run for a later replay and say so.--## Board changes from probing (test points and their labels)--When the probing stage (adom-aiflow-probing) sends a board back, it writes `probing-flow/board-change-request.md`. The request covers:-- the test points or contacts to add: footprint, pad size, net and KiCad position, each one proven against the probing workcell's geometry;-- every label: text, KiCad position, height and stroke;-- the fab rules to check against.--Make the whole request, labels included:-- **A test point without its label is not done.** Each new test point and contact gets its reference, and its net where it fits.-- **Labels use the smallest readable text the fab prints.** That is the project's `min_text_height`, never under 4 x `min_text_thickness`, because KiCad caps the stroke at a quarter of the height. That gives 0.32 mm high and 0.08 mm stroke on the 3rd party fab profile.-- **Labels go beside the pad,** off pads, off other text, off silkscreen lines and off part bodies.-- **A label marked "with a short leader"** has no room beside its pad: find the nearest open spot and draw the leader to the pad's rim (see the leader rules above).-- **Pad size:** the request's pad size is the probing cell's minimum that still grades ok. Any size from there up is fine where it fits.--Apply with `kicad_silk_text_batch`:-1. A dry run first, so KiCad's DRC rejects any new finding.-2. One label per call, so the step clip shows each one.-3. Save, then DRC with zones refilled.--After the change, run the silkscreen audit and DRC, and hand the board back to probing (access, coverage, compile, collide, margins).