← Commit history

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)

Colby Knox ·850bd3ff3e ·13d ago ·parent d520b30
7 files changed +7−6
README.md+1
@@ -158,6 +158,7 @@ Decisions so far (proposals from the KiCad and Fusion bridges, 2026-10-27; issue  ## Status +Version 0.8.1: the engine (0.5.1)'s marking font draws D and B so they read as D and B, not "IO" and 8 (PR #3). Version 0.8.0: the engine (0.5.0) writes a part's 3D body as STEP from its package dimensions (`generate_body`, from the Altium bridge's body3d.rs, PR #2, #20); it matches Fusion's generator on a 0603, SOIC-8, QFN-32 and QFP-48. Version 0.7.1: the engine (0.4.1)'s `placement_check` lists a part under a raised one (an Adom molecule on pins) as
engine/Cargo.lock+1−1
@@ -4,7 +4,7 @@ version = 4  [[package]] name = "adom-eda-checks"-version = "0.5.0"+version = "0.5.1" dependencies = [  "roxmltree",  "serde_json",
engine/Cargo.toml+1−1
@@ -1,6 +1,6 @@ [package] name = "adom-eda-checks"-version = "0.5.0"+version = "0.5.1" edition = "2021" description = "The EDA Bridge Standard's checks and board-file writers, computed from the board model JSON: no bridge calls, no tool." license = "MIT"
engine/README.md+1−1
@@ -89,7 +89,7 @@ adom-eda-checks import_svg --svg logo.svg --args '{"at": [10, 10], "widthMm": 20  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.5.0"`), so a bridge reports the engine it runs without writing the version by hand.+(`"adom-eda-checks 0.5.1"`), so a bridge reports the engine it runs without writing the version by hand.  ## Tests 
package.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "eda-bridge-standard",-  "version": "0.8.0",+  "version": "0.8.1",   "type": "skill",   "title": "EDA Bridge Standard: one way for an AI to drive every PCB tool",   "description": "The standard every Adom EDA bridge follows so one AI can drive Altium, KiCad, Fusion 360 and any future PCB tool the same way: shared verb names in tiers, the board model JSON, reply and refusal conventions, and a coverage table of each bridge against the Altium reference.",
verbs/coverage.json+1−1
@@ -1,5 +1,5 @@ {- "standard": "0.8.0",+ "standard": "0.8.1",  "reference": {   "bridge": "altium",   "version": "0.2.79"
verbs/standard.json+1−1
@@ -1,5 +1,5 @@ {- "standard": "0.8.0",+ "standard": "0.8.1",  "reference": {   "bridge": "altium",   "version": "0.2.79"