Electronics Industry Sites Skillpack

@@ -108,6 +108,13 @@ worth reaching for nb or the API lane. Never retry the failing lane, never report "the site is timing out", never spoof a fingerprint. Switch lanes, then write down what you saw in that site's skill. +**No account on a site? Register one for the user (John, 2026-09-19).** These are free CAD/vendor+accounts, not bank logins: when a download needs a login the vault does not have, first check the+user's own browser (`pup_import_browser_logins {}`) and the other desktops (`pup_vault_sync {peer}`);+if there is truly none, register with the Adom user's profile (work email, name, company), read the+verification mail through the Gmail connector, set a generated password in the same pup session and+`credential_set` it into the vault so the human never types it. The ST skill has the worked example.+ **Captchas: the AI drives them itself (John, 2026-09-19).** A reCAPTCHA / Turnstile checkbox or image grid on a download or login gate is YOUR job, not the user's: never toast, flash or wait for the human, and never switch pup to the CDP lane for it. Trusted click on the checkbox with pup's fake cursor,

@@ -52,6 +52,12 @@ The **CAD Resources** tab holds NO direct links. It is a supplier widget: "Start - **SamacSys download = HTTP Basic-Auth** on `st.componentsearchengine.com` (the CSE family). It needs a free SamacSys/CSE account in pup's vault (`credential_list` host `componentsearchengine.com`, any subdomain). On the extension lane pup does NOT yet answer that challenge from the vault (adom/pup-bridge#119): Chrome's native "Sign in" dialog stays up, the frame reads "error page", nothing downloads. Until #119 ships, use the UltraLibrarian route below, or the `nb` (native browser) lane where the user's own saved login answers the dialog. - **UltraLibrarian route:** same part on `app.ultralibrarian.com` (search `?queryText=<MPN>`); see the ultralibrarian skill — its download is behind a reCAPTCHA (adom/pup-bridge#120) which the AI drives itself. - **myST** (`my.st.com/cas/login`) is a plain form: `pup_login {submit:true, submitReason}` fills + submits from the vault (`vault:my.st.com`). A "does not match our records" reply is a STALE credential, not a pup fault — try the other identity in the vault or `pup_import_browser_logins {hostFilter:["st.com"]}` first.+- **No myST login yet? Register one for the Adom user — do not ask them to (measured 2026-09-19, ~2 min, no captcha).**+  1. `pup_open_window {url:"https://my.st.com/cas/login"}` → click `#createAccount` (a custom `<submit>` element, not an `<a>`; find it by id). Lands on `www.st.com/content/st_com/en/user-registration.html`.+  2. Fill with the Adom user's profile (name, work email, company, function "Engineering – Hardware", an industry, country, state, zip; phone optional) — set values through the native value setter and dispatch `input`/`change`/`blur`; select `US` first, then the state list populates (`TX`). Tick `#termsOfUse`, click the "Register" button. Field names: `recipient.firstName`, `recipient.lastName`, `recipient.email`, `recipient.email-confirmation`, `recipient.userFunction`, `recipient.company`, `recipient.companyAttributes.verticalChannel`, `recipient.location.countryCode`, `recipient.location.stateCode`, `recipient.location.zipCode`.+  3. ST emails "Activate your MyST account" (from [email protected]) to that address. Read it (Gmail connector / `adom-google gmail`), open the `registration-validation.html?token=…` link in the SAME pup session, fill `#secret.password` + `#secret.password-confirmation` (8+ chars, 3 of 4 classes, no name/email parts) and click the form's "Submit" (not `#subscription-submit`, that is the newsletter).+  4. **Store it so nobody ever types it again:** `credential_set {host:"my.st.com", username:<email>, password}` on that desktop (generate the password in the shell, never print or echo it), then prove it with `pup_login {submit:true}` on `my.st.com/cas/login` — success reads "You have successfully logged into the Central Authentication Service". The vault is per desktop; `pup_vault_sync {peer}` unions two desktops' vaults (mind shared machines: it has no host filter yet).+  5. myST only gates ST's own downloads (software, some docs). The CAD models are still the SamacSys / UltraLibrarian widgets above, with their own free accounts — register those the same way when missing (CSE: `st.componentsearchengine.com/register_e_newDesign.php?pna=st&partID=…`, UL: `app.ultralibrarian.com/account/register`). - ST's own datasheet/outline drawings are the fallback for the 3D body: if no STEP can be fetched, the AI models the chip itself (CadQuery) from the outline drawing — never ship a library without a STEP, the 3D board render needs it.  ### Spec tables when st.com is unreachable