Open general

wiki-component: require 'adom-lbr validate' as a hard gate before pushing the .lbr

Ray ·

The wiki-component skill's publish flow tells the AI to generate the CAD and "push the CAD files," but nothing makes validating the Fusion .lbr a hard gate before that push. Fusion's importer rejects the entire library over one bad part, so an unvalidated .lbr on a page is worse than shipping none.

This bit us for real: adom-lbr 2.12.7 tightened its validator (started enforcing the EAGLE @-suffix convention for duplicate pad names — thermal vias, split EPs, dual mounting pads). That silently invalidated 24 already-published wiki component pages whose .lbr had been generated by an older adom-lbr. They looked fine on the page but would not import into Fusion. Found + regenerated + repushed by hand.

Request: add a step to the wiki-component publish checklist (and the tools table, which currently shows adom-lbr generate --sym x.kicad_sym -o x.lbr — note it omits --fp, which yields a placeholder footprint):

  1. Generate with the footprint: adom-lbr generate --sym x.kicad_sym --fp x.kicad_mod --output x.lbr
  2. Gate: adom-lbr validate x.lbr must print "valid EAGLE .lbr with complete deviceset" before the repo push. A FAIL blocks the push.
    • [duplicate-pad-name] -> regenerate with current adom-lbr (auto @-suffix).
    • [connect-pad-unresolved] (symbol pins != footprint pad names, e.g. barrel jacks) -> footprint-only regen (--fp only, drop --sym).
  3. After any adom-lbr version bump, re-validate a thermal-pad and a multi-mount .lbr; regenerate + repush affected pages if the validator tightened.

The matching change to the adom-lbr side (making the "validate before you push" gate explicit in the fusion-export skill) is up as adom-inc/adom-lbr PR #2.

0 Replies

Log in to reply.