EDA Bridge Standard: one way for an AI to drive every PCB tool

@@ -61,11 +61,11 @@ verb by verb: [docs/coverage.md](docs/coverage.md). | Tier | Verbs | Altium | KiCad | Fusion 360 | |---|---|---|---|---| | **core** | 95 | 95 | 95 | 93 |-| **native** | 53 | 49 | 49 | 50 |+| **native** | 53 | 50 | 49 | 50 | | **checks** | 38 | 38 | 38 | 38 | | **app** | 66 | 65 | 54 | 57 | | **platform** | 18 | 18 | 0 | 1 |-| standard (all but platform) | 252 | 247 | 236 | 238 |+| standard (all but platform) | 252 | 248 | 236 | 238 | <!-- coverage:end -->  The **checks** tier is where the other bridges are furthest behind, and it is the cheapest to close: those verbs are@@ -158,6 +158,7 @@ Decisions so far (proposals from the KiCad and Fusion bridges, 2026-10-27; issue  ## Status +Version 0.29.2: Altium's `import_kicad` counts as `import_design` (partial, kicad only). Version 0.29.1: `tool_update` (app) and `import_step` (native) join from fusion-lane (#29). 252 verbs. Version 0.29.0: three verbs from fusion-lane join the standard (#29): `export_3d`, `import_design` and `edit_pours` (native). 250 verbs. Version 0.28.2: the reference is Altium bridge 0.2.86, which answers all 247 standard verbs (sch_batch and log_tail added).

@@ -7,11 +7,11 @@ Generated by `tools/generate.py` from `verbs/coverage.json`; do not edit by hand | Tier | Verbs | Altium | KiCad | Fusion 360 | |---|---|---|---|---| | **core** | 95 | 95 | 95 | 93 |-| **native** | 53 | 49 | 49 | 50 |+| **native** | 53 | 50 | 49 | 50 | | **checks** | 38 | 38 | 38 | 38 | | **app** | 66 | 65 | 54 | 57 | | **platform** | 18 | 18 | 0 | 1 |-| standard (all but platform) | 252 | 247 | 236 | 238 |+| standard (all but platform) | 252 | 248 | 236 | 238 |  ## core @@ -145,7 +145,7 @@ Wraps the EDA tool's own feature (its DRC, ERC, Gerbers, pours, Update PCB). Eve | `export_pdf` | Every sheet of a project as one PDF, plus on request the board's composite print, Altium's assembly drawings (top and bottom, designators on the parts) and... | `altium_export_pdf` | `kicad_export_pdf` | `fusion_export_pdf` (partial) | | `export_pos` *proposed* | Export the pick-and-place (component position, CPL) file of a board, optionally in a fab's assembly format (JLCPCB's columns). | `altium_export_pos` | `kicad_export_pos` | `fusion_export_cpl` (partial) | | `export_step` | Headless STEP export of a board. Default lane 'outjob': Altium's own ExportSTEP output run from a throwaway project in %TEMP% that points at the board - no... | `altium_export_step` | `kicad_export_step` | `fusion_export_step` |-| `import_design` *proposed* | Bring a design from another tool into a NEW native design with the parts instantiated: an EAGLE .sch with its paired .brd, a KiCad project, or an Altium... |  |  | `fusion_new_electronics_from_eagle` (partial) |+| `import_design` *proposed* | Bring a design from another tool into a NEW native design with the parts instantiated: an EAGLE .sch with its paired .brd, a KiCad project, or an Altium... | `altium_import_kicad` (partial) |  | `fusion_new_electronics_from_eagle` (partial) | | `import_step` *proposed* | Bring a STEP model in as 3D geometry placed with the board: an enclosure, a bracket or a mating part, for fit and clearance checks. Not a footprint's own... |  |  | `fusion_import_step` (partial) | | `install_library` | Register a library file in Altium's Installed Libraries (IntegratedLibraryManager.InstallLibrary) so its parts appear in the Components panel. | `altium_install_library` | `kicad_install_library` | `fusion_install_library_bundle` (partial) | | `install_library_bundle` | One-click install of a wiki library bundle (zip of .SchLib/.PcbLib): unpack, register, open the library, prove it with a frame. | `altium_install_library_bundle` | `kicad_install_library_bundle` | `fusion_install_library_bundle` |

@@ -1,6 +1,6 @@ {   "slug": "eda-bridge-standard",-  "version": "0.29.1",+  "version": "0.29.2",   "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.",

@@ -1,5 +1,5 @@ {- "standard": "0.29.1",+ "standard": "0.29.2",  "reference": {   "bridge": "altium",   "version": "0.2.86"@@ -2084,7 +2084,11 @@    "name": "import_design",    "tier": "native",    "source": "proposed",-   "altium": null,+   "altium": {+    "verb": "altium_import_kicad",+    "match": "partial",+    "note": "format kicad only (Altium's KiCad importer); EAGLE through the Import Wizard comes with altium_import_design"+   },    "kicad": null,    "fusion360": {     "verb": "fusion_new_electronics_from_eagle",

@@ -1,5 +1,5 @@ {- "standard": "0.29.1",+ "standard": "0.29.2",  "reference": {   "bridge": "altium",   "version": "0.2.86"