Chip Fetcher (cf)

@@ -89,11 +89,11 @@ past Cloudflare, the License Agreement form, retrieving the attachment via build-your-own fetcher for other providers, and the breadcrumb pattern that keeps chip-fetcher provider-agnostic, is documented in its own sub-README: -➡️ **[docs/jst-email-gated-cad.md](docs/jst-email-gated-cad.md)**, Email-delivered CAD: the JST flow (and how to add any email-gated manufacturer)+**[docs/jst-email-gated-cad.md](docs/jst-email-gated-cad.md)**, Email-delivered CAD: the JST flow (and how to add any email-gated manufacturer) -🏆 **[docs/jst-showcase.md](docs/jst-showcase.md)**, Showcase (with screenshots): how chip-fetcher cracked JST's Cloudflare + email gate end-to-end, and bundled the 5 most-common JST connectors with symbol + footprint + 3D.+**[docs/jst-showcase.md](docs/jst-showcase.md)**, the full JST story with screenshots: how chip-fetcher cracked JST's Cloudflare + email gate end-to-end, and bundled the 5 most-common JST connectors with symbol + footprint + 3D. -> ⚖️ **Note on JST files:** JST's download License Agreement (clause 2) prohibits redistributing their CAD to third parties, so we do **not** rehost JST's emailed STEP/IGES or datasheets. Connector component pages we publish use the **redistributable KiCad libraries** for symbol/footprint/3D and **link to JST** for any JST-authored model.+> **Note on JST files:** JST's download License Agreement (clause 2) prohibits redistributing their CAD to third parties, so we do **not** rehost JST's emailed STEP/IGES or datasheets. Connector component pages we publish use the **redistributable KiCad libraries** for symbol/footprint/3D and **link to JST** for any JST-authored model.  Agents: the same content lives in the skill as `playbooks/jst.md` + `playbooks/jst-email-retrieval.md`.