fix(release): probe npm leaves for their declared platforms

[f0rr0]

Release 37427902628 published and verified its registries, then failed before GitHub draft promotion when the Linux consumer probe installed the macOS ARM64 runtime leaf as a required dependency.

Probe standalone npm platform entries with the repository's OS/CPU/libc profiles and optional dependencies, as npm 11.18 applies platform overrides only to optional dependencies. The checker still requires each exact entry package to be installed and every locked dependency to resolve. Treat both runtime portable and extension wasix-portable entries as platform independent. Record and validate the per-entry platforms; retain anonymous installs, disabled scripts, and receipt bindings.

Validation:

• Release implementation tests, JavaScript formatting and lint.
• Regression coverage for platform aliases, both portable target names, facade entries, unsupported targets, missing installed entries, and altered platform evidence.
• A real npm 11.18.0 negative probe confirmed that an incompatible optional entry can yield npm exit 0 but is still rejected by the checker because its exact package was not installed.
• Reproduced EBADPLATFORM before the fix with pinned npm 11.18.0; the patched probe passed all nine public npm entries and resolved all 18 locked npm carriers.
• All seven products passed the complete Cargo/npm/Maven/GitHub consumer check against the unchanged frozen lock. The 71 registry receipts validate, and seven GitHub drafts with 38 assets still match their receipt.

This is a publication-only controller repair. After merge and main's Required check, recover the existing candidate with release_commit=e6fb8a42190427363fd48b4dcb0ae10a76c6a78d and approval_run_id=37427902628; reuse its successful qualification and frozen artifacts.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
oliphaunt-docs	Skipped		Oct 6, 2026 10:39am UTC