ci: the gate's step 8 says how to check the registry, not how to fix it - #33

ci/sdk-suites.sh already tells a reader whose npm install failed that npm config get registry is the first thing to check, and that an unreachable registry fails the gate rather than silently producing a partial one. Both true — and it stops one step short of the remedy.

Behind a corporate proxy the step fails twice over, and neither message points anywhere useful: ENOTFOUND against an internal mirror with the VPN down, then CERT_HAS_EXPIRED against the same host with it up. Reading either, the natural conclusion is that the mirror is broken and there's nothing to be done.

In fact exporting the proxy for the run fixes it outright — and the gate then passes all eight checks, including the fourteen Node tests that otherwise skip while the run still exits 0. That's the state this repository shipped in until 0.42.1, which is why step 8 refuses to treat a missing dependency as a skip.

Working that out from the error text alone cost an afternoon. The remedy is now in the error text.

Two deliberate choices in the wording:

• The hosts named are one organisation's, and are labelled as such. What transfers is the shape — export for the run, change nothing persistent.
• It says explicitly that npm config set is not the advice. A gate that edits your tooling in order to pass is a gate nobody can trust afterwards.

Error-message text only; nothing executes on the passing path. bash -n clean.

I'll add the ci/gate.sh result before merge — an end2end verification run for 0.54.0 is using the machine and I didn't want the two competing, same as #31.

🤖 Generated with Claude Code