← Commit history

standard 0.27.1: coverage reads Fusion 1.13.30

Colby Knox ·ec0616aa65 ·11d ago ·parent 4ef2f69
5 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.27.1: coverage reads Fusion 360 bridge 1.13.30 (engine 0.22.0). Version 0.27.0: engine 0.22.0 ports kicad-bridge's design checks into `schematic_review` (I2C pull-ups, reset and enable pins, LED resistors, regulator and bulk capacitors, annotation, no-connect flags on wired pins, two names on one net) and its placement score into `placement_check` (0-100 and a grade; connectors far from the edge, decoupling far from its IC, ratsnest length) (#29). The reference is Altium bridge 0.2.85; coverage reads Fusion 360 bridge 1.13.29. Version 0.26.5: `sch_batch` (core) and `log_tail` (app) join the standard (#29). 247 verbs. Version 0.26.4: coverage reads KiCad bridge 1.0.91 (234 of 245: add_symbol_art, build_symbol_modes and cleanup_libs now real verbs).
docs/coverage.md+1−1
@@ -1,6 +1,6 @@ # Coverage: every standard verb on each bridge -Altium bridge 0.2.85 (the reference), KiCad bridge 1.0.91, Fusion 360 bridge 1.13.29. 62 verbs came from other bridges' proposals (tools/proposed/); they are marked *proposed*.+Altium bridge 0.2.85 (the reference), KiCad bridge 1.0.91, Fusion 360 bridge 1.13.30. 62 verbs came from other bridges' proposals (tools/proposed/); they are marked *proposed*. `exact` is the same job under the same or an equivalent name; `partial` does part of it or does it differently (`verbs/coverage.json` names what in `note`); `unsupported` answers `not_supported` for the whole job and is not counted; blank is missing. Generated by `tools/generate.py` from `verbs/coverage.json`; do not edit by hand. 
package.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "eda-bridge-standard",-  "version": "0.27.0",+  "version": "0.27.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+2−2
@@ -1,5 +1,5 @@ {- "standard": "0.27.0",+ "standard": "0.27.1",  "reference": {   "bridge": "altium",   "version": "0.2.85"@@ -7,7 +7,7 @@  "proposed": 62,  "compared": {   "kicad": "1.0.91",-  "fusion360": "1.13.29"+  "fusion360": "1.13.30"  },  "tiers": {   "core": "Read and edit the design. Every bridge provides these: they are how an AI sees and changes a board.",
verbs/standard.json+2−2
@@ -1,5 +1,5 @@ {- "standard": "0.27.0",+ "standard": "0.27.1",  "reference": {   "bridge": "altium",   "version": "0.2.85"@@ -7,7 +7,7 @@  "proposed": 62,  "compared": {   "kicad": "1.0.91",-  "fusion360": "1.13.29"+  "fusion360": "1.13.30"  },  "tiers": {   "core": "Read and edit the design. Every bridge provides these: they are how an AI sees and changes a board.",