Adom Library

@@ -28,6 +28,39 @@ adom-lbr generate --sym part.kicad_sym --fp part.kicad_mod --model part.step -o  Then the **Fusion bridge attaches the 3D** (it can't be baked into the file). +## Ship gate — VALIDATE before you push (do this every time)++```bash+adom-lbr validate part.lbr    # must print: "valid EAGLE .lbr with complete deviceset"+```++**Never ship, publish, or `repo push` a `.lbr` that has not passed `adom-lbr+validate`.** Fusion's importer rejects the ENTIRE library over one bad part, so an+unvalidated `.lbr` on a page is worse than shipping none. A FAIL always names the fix:++- `[duplicate-pad-name]` — thermal vias, split exposed pads, or dual mounting pads+  share a pad name. **Regenerate with the current `adom-lbr`** (it auto-emits the+  EAGLE `@`-suffix convention `29`, `29@2`, … with a multi-pad `<connect>`). A `.lbr`+  built by an OLDER `adom-lbr` is rejected — the validator tightened over time.+- `[connect-pad-unresolved]` — symbol pin numbers ≠ footprint pad names (e.g. a+  `Connector:*` symbol on a `BarrelJack_*` / mounting-pad footprint). Either supply+  `--pin-map` / `pinmap.json`, or **regenerate footprint-only** (`adom-lbr generate+  --fp part.kicad_mod -o part.lbr`, drop `--sym`) to synthesize a placeable deviceset.+- `[illegal-pin-name]` (2.17.1) — a pin name with a space or other character EAGLE+  refuses (`GND (TAB)`); Fusion rejects the whole library with a generic "has errors"+  dialog. **Regenerate**: current `adom-lbr` sanitizes names on generate.+- `[invalid-align]` (2.26.0) — a group caption with an `align` value outside EAGLE's+  nine (`bottom-left` … `top-right`); Fusion warns per caption. **Regenerate**.+- `[pad-clearance]` as an ERROR (2.33.0) — two pads' copper genuinely OVERLAP (a+  mapping grew a pad into its neighbour, a short). Fix the source footprint or regenerate+  with current `adom-lbr`; a fine-pitch gap under 0.2 mm is only a WARNING and ships.++**After ANY `adom-lbr` version bump, re-validate an already-shipped QFN/thermal-pad+`.lbr` and a multi-mount-pad `.lbr`. If the validator tightened, the fix is not+optional: regenerate and repush every affected page** — the validator changing under+already-published `.lbr` files is exactly how a fleet ends up with silently-broken,+Fusion-unimportable libraries (24 such pages, Aug 2026).+ ## The four traps (this is why the skill exists)  1. **No `--fp` → a 2-column PLACEHOLDER, not the real footprint.** Without the