adom-eda-checks: the shared checks engine and board-file writers

The checks tier of the EDA Bridge Standard, computed from the board model and its companions as plain JSON. It makes no bridge calls, runs no tool and does no I/O. A bridge links the crate (the Altium, KiCad and Fusion bridges are all Rust) or runs the adom-eda-checks command, then answers the check under its own prefix (kicad_return_path).

The code moved over from the Altium bridge's bridge-rs/src/, which was the reference implementation. On Altium's own boards the engine gives the same answers the Altium bridge 0.2.76 gives.

Checks

The via plans size their vias from args.size/drill, else the board's via rule (rules: {kind: "via", sizeMm, drillMm}, or Altium's Routing Via descriptor), else 0.6/0.3, and say which in planned.via.from.

The other checks-tier verbs (assembly, pair routing, length tuning, designators, panels, the board report, schematic review, and the planners estimate_cost, check_clearance, place_decoupling and plan_fanout) come over a module at a time.

Writers

For a bridge whose tool has no native exporter (writers, from altium-lane, #16). They stay native-tier verbs in the standard: a bridge whose tool can write the file keeps its own exporter. No I/O: each returns the file text or the regions, with writtenFrom, and the bridge writes the file or places the regions.

Input

Every check takes one JSON object:

{"board": {...}, "stack": {...}, "pours": {...}, "rules": [...], "silk": {...}, "fab": {...}, "args": {...}}

Each part may be the bare model or the bridge's whole reply: the model's keys at the top level, or under data. A missing part is never guessed. A limit with nothing to measure it against is listed in notChecked. Copper weight assumed for lack of a stack is named in assumed.

Use

As a crate, vendored at a tagged standard version (the wiki has no git protocol, so Cargo can't fetch it):

[dependencies]
adom-eda-checks = { path = "vendor/adom-eda-checks" }

let reply = adom_eda_checks::run("return_path", &serde_json::json!({"board": board, "stack": stack, "pours": pours, "args": {}}));

As a command:

adom-eda-checks list
adom-eda-checks return_path --board board.json --stack stack.json --pours pours.json --args '{"resolutionMm": 0.1}'
adom-eda-checks fab_check bundle.json        # or - for stdin
adom-eda-checks export_dxf --board board.json --pours pours.json --args '{"layers": ["Edge.Cuts", "F.Cu"]}'
adom-eda-checks import_svg --svg logo.svg --args '{"at": [10, 10], "widthMm": 20, "layer": "F.SilkS"}'

Replies keep the standard envelope (success, errorCode, error, _hint) and name verbs without a prefix (apply_pours, add_rule, place_vias): a bridge adds its own. Every reply also carries engine ("adom-eda-checks 0.20.0"), so a bridge reports the engine it runs without writing the version by hand.

Tests

cargo test runs the unit tests. To compare with a bridge's own answers, point ADOM_EDA_FIXTURES at a folder of saved replies laid out as <bridge>/<board>.<model>.json and <bridge>/expected/<board>.<check>.json:

ADOM_EDA_FIXTURES=/path/to/fixtures cargo test --test fixtures

Fixtures live on each bridge's own page, not here.