☰
standard 0.13.0: engine 0.10.0 fixes from fusion-lane (#21, #22); kicad 1.0.75, fusion 1.13.5
standard 0.12.0: engine 0.9.0 adds estimate_cost, prices from a dated record
standard 0.11.0: engine 0.8.0 adds plan_fanout (KiCad's place_tools) with board-wide conflicts
standard 0.10.0: engine 0.7.0 adds check_clearance and place_decoupling (KiCad's place_tools)
standard 0.9.1: engine 0.6.1, plan_route takes the board's width and via rules (altium-lane PR #4)
standard 0.9.0, engine 0.6.0: plan_route in the engine, from fusion-bridge's grid search (#12, #14): any listed copper…
standard 0.8.1, engine 0.5.1: generate_body's marking font draws D and B so they read as D and B (PR #3)
standard 0.8.0, engine 0.5.0: wire generate_body (PR #2, #20) into the writers: STEP AP214 from a package family and it…
regenerate after altium-lane (reference/altium-0.2.79.json, insiders: engine 0.4.1 for 7 checks and 3 writers): Altium…
regenerate after fusion-lane (generate_body: pins is the total for any family; D2/E2 are the exposed pad) (#20)
regenerate after kicad-lane (reference/kicad-1.0.72.json, insiders: thermal_vias, via_fence, height_check, placement_ch…
standard 0.7.1, engine 0.4.1: placement_check lists a part under a raised one as stacked, not a courtyard overlap, when…
regenerate after fusion-lane (reference/fusion360-1.13.3.json, public: engine 0.4.0, height_check and placement_check n…
regenerate after kicad-lane (reference/kicad-1.0.71.json, insiders: library_views, set_layer_visibility): KiCad 202 of…
standard 0.7.0, engine 0.4.0: height_check and placement_check move into the engine from the Altium bridge's bodies.rs…
standard 0.6.0, engine 0.3.0: thermal_vias and via_fence move into the engine from the Altium bridge's features.rs (pla…
regenerate after kicad-lane (reference/kicad-1.0.70.json, insiders: build_schematic; engine 0.2.1): KiCad 191 of 236
regenerate after fusion-lane (reference/fusion360-1.13.2.json, public, engine 0.2.1 writers): Fusion still 158 of 236
standard 0.5.1, engine 0.2.1: GenCAD keeps one shape per footprint pattern and pad geometry (same name, other pads: NAM…
regenerate after fusion-lane (reference/fusion360-1.13.1.json, public: 12 more verbs, 4 partial; GenCAD MIRRORX): Fusio…
standard 0.5.0, engine 0.2.0: wire the shared board-file writers from PR #1 (#16) into run and the CLI (list, --svg), a…
regenerate after fusion-lane (reference/fusion360-1.13.0.json, public: 12 library-authoring verbs, 5 partial): Fusion 1…
regenerate after altium-lane 2869f67 (reference/altium-0.2.78.json, insiders: export_ipc356, export_dxf, export_gencad,…
regenerate after kicad-lane (reference/kicad-1.0.68.json, insiders: bom, assembly_check, jlcpcb_order, footprint_from_l…
regenerate after fusion-lane (reference/fusion360-1.12.8.json, public: KiCad's core and app proposals, 8 partial): Fusi…
regenerate after altium-lane f87664f (reference/altium-0.2.77.json, insiders: 13 proposed verbs under their names, engi…
regenerate after kicad-lane (reference/kicad-1.0.67.json, insiders: its own checks-tier verbs in the standard's shapes,…
standard 0.4.5, engine 0.1.4: current_capacity lists each pour layer once in poursOn (kicad-lane #15)
standard 0.4.4, engine 0.1.3: min_clearance counts only copper-to-copper clearance; rules naming the edge, mask, silk,…
regenerate after fusion-lane (reference/fusion360-1.12.7.json, public: export_odb, export_ipc356, export_gencad, export…
regenerate after kicad-lane (reference/kicad-1.0.66.json, public: teardrops, panelize): KiCad 166 of 236
standard 0.4.3, engine 0.1.2: a clearance rule as a value with its unit (Fusion's form), same-net rules left out (fusio…
regenerate after fusion-lane f87af98 (reference/fusion360-1.12.4.json; plan_route and edit_parts partial): Fusion 113 o…
standard 0.4.2, engine 0.1.1: stack_layers names copper layers by the stack entry's layer, or by place (In<n>.Cu), plan…
regenerate after kicad-lane (reference/kicad-1.0.65.json: compile, list_installed_libraries, replicate_layout, diff_pai…
regenerate after fusion-lane 8c6637c (reference/fusion360-1.12.3.json; its one new verb is not a standard one): Fusion…
regenerate after kicad-lane (reference/kicad-1.0.64.json: 17 standard verbs under their own names): KiCad 160 of 236
standard 0.4.1: coverage counts only what works: equivalents take [verb, match, note?] with match exact | partial | uns…
standard 0.4.0: the checks engine adom-eda-checks in engine/ (Rust crate + CLI, JSON in, no bridge calls): copper_balan…
standard 0.3.1: an internal plane is In<n>.Cu by its place in the copper stack, kind plane (agreed with altium-lane on…
regenerate after kicad-lane (reference/kicad-1.0.63.json; 16 equivalents dropped for standard-name aliases): 16 KiCad c…
regenerate after fusion-lane ef03646 (filePath on render_board_layers and plan_route; render_board_layers = fusion_expo…
standard 0.3.0: 33 agreed verbs from other bridges (kicad-lane 26: exports, render_board_3d, part and graphic edits, pr…
standard 0.2.1: one keeper (standard-lane) for docs and generated files, bridge threads push only their reference and e…
0.2.0: verbs from any bridge (tools/proposed.json, agreement gate, Altium measured too); batch 1: 21 schematic verbs fr…
Regenerate coverage against kicad-1.0.62 (the Fusion 1.12.1 push regenerated from a clone that predated reference/kicad…
KiCad bridge 1.0.62 reference (standard: 201 verbs (182 in the standard); kicad covers 92, fusion 56)
0.1.2: KiCad reference 1.0.61 (John's new verbs; the last commit credited them against 1.0.59), 22 more KiCad matches,…
KiCad bridge 1.0.59 reference: 63 of 182 standard verbs (was 55); board model conformance (#1)
0.1.1: settle #1 and #2: the y-down frame, isolatedCopper (pour islands not counted), fractured fills, custom pads with…