AI Flow

Found by the fusion-lane thread while running AI Flow end to end on a Fusion board. Fixed in AI Flow 0.2.22 (published).

Bug

gate refused every Fusion run with "N footprint(s) without a courtyard (F.CrtYd/B.CrtYd)". start --board B.brd --remote-board fusion:<Design> converts the EAGLE board into the run's own board-0.kicad_pcb. The gate then asked mechanical::applies about that converted file. It is not EAGLE, so the courtyard and body checks ran on a rendering that can never carry courtyards. AI Flow's own messages say those checks are skipped on a Fusion board ("check them in Fusion's DRC").

Fix

mechanical::applies also recognises the run's Fusion rendering by its header, (generator "adom-aiflow-fusion"), so the gate skips those checks and says so, as intended. Unit test: fusion_renderings_skip_the_courtyard_checks.

Verified live

On DESKTOP-BAR6S0F, with fusion-bridge 1.12.0 (dev build) and the routing fixture saved as a cloud design fl-aiflow-1:

• start --board fusion-routing.brd --remote-board fusion:fl-aiflow-1, then route (6 nets, 0 failed) and gate (passed: 0 new DRC errors, 0 unconnected, courtyards not checked on a Fusion board);
• land route landed 7 traces, one undo step each, every one guarded by the board's revision;
• read back with fusion_routing_state: 9 tracks, unconnected 0, and Fusion's own DRC reports 0 errors, 0 warnings, 0 airwires.

0.2.22 also keeps every 0.2.21 command: 69 top-level commands, with identical help.