npm publish freshness alert: 9 package(s) behind `0.5.1519`

[github-actions]

The npm registry is not serving what main is at (0.5.1519).

What this costs when it is ignored — #7491: users installed a month-old latest and hit a linker error (unresolved external symbol js_ext_http_client_request_is_handle) that had been fixed on main for weeks. Every CI gate was green; they all measure main, and main is not what npm serves.

package	problem
@perryts/perry	npm's latest is 0.5.1220, published 58.5 days ago (budget 14d), while the tree is at 0.5.1519 -- 299 unreleased patch bumps behind
@perryts/perry-darwin-arm64	npm's latest is 0.5.1220, published 58.5 days ago (budget 14d), while the tree is at 0.5.1519 -- 299 unreleased patch bumps behind
@perryts/perry-darwin-x64	npm's latest is 0.5.1220, published 58.5 days ago (budget 14d), while the tree is at 0.5.1519 -- 299 unreleased patch bumps behind
@perryts/perry-linux-arm64	npm's latest is 0.5.1220, published 58.5 days ago (budget 14d), while the tree is at 0.5.1519 -- 299 unreleased patch bumps behind
@perryts/perry-linux-arm64-musl	npm's latest is 0.5.1220, published 58.5 days ago (budget 14d), while the tree is at 0.5.1519 -- 299 unreleased patch bumps behind
@perryts/perry-linux-x64	npm's latest is 0.5.1220, published 58.5 days ago (budget 14d), while the tree is at 0.5.1519 -- 299 unreleased patch bumps behind
@perryts/perry-linux-x64-musl	npm's latest is 0.5.1220, published 58.5 days ago (budget 14d), while the tree is at 0.5.1519 -- 299 unreleased patch bumps behind
@perryts/perry-win32-arm64	npm serves 0.0.0 while the tree is 0.5.1519: a different x.y line, so the patch distance is not a commit count. Treated as stale
@perryts/perry-win32-arm64	published 0.0.0 but the launcher publishes 0.5.1220 -- a partial publish; npm install @perryts/perry cannot resolve this platform
@perryts/perry-win32-x64	npm's latest is 0.5.1220, published 58.5 days ago (budget 14d), while the tree is at 0.5.1519 -- 299 unreleased patch bumps behind

Cut a release with release-packages.yml (see docs/src/contributing/releasing.md), or widen the budget in scripts/npm_publish_freshness.json and say why in the same commit.

Maintained automatically by npm-publish-freshness.yml. Updated in place, never duplicated, and closed once the registry has caught up.

[proggeramlug]

r26 release-gate audit for candidate 7c9f6016987ea9fdce2d253fb8666428cf0c6d24 (Full CI run https://github.com/PerryTS/perry/actions/runs/33123474583):

• release blocker: net.listen receives NUL-contaminated host strings #8909 - fix NUL-contaminated host strings breaking two new parity tests
• release blocker: restore perry-runtime -D warnings cleanliness #8910 - restore -D warnings cleanliness
• release blocker: reconcile diagnostics thread-local policy inventory #8911 - reconcile the diagnostics raw-thread-local inventory
• release blocker: restore native-region compiler-output proof #8912 - restore native-region compiler-output proof and native-ABI evidence
• release blocker: test_gap_gc_alloc_point_no_move compile does not terminate #8913 - bound test_gap_gc_alloc_point_no_move compilation (gap/parity/compile-smoke timeouts)
• release blocker: full cargo-test cannot finish within 180 minutes #8914 - make Full cargo-test finish within 180 minutes
• release blocker: gc_repsel_matrix exceeds the 90-minute gc-stress budget #8915 - make the GC representation-selection matrix finish within 90 minutes

Derivative failures that do not need separate fixes:

• parity-aggregate failed because parity shard 10 timed out and no 12th report existed.
• full-suite-gate failed because the upstream jobs above failed/cancelled.

Release remains blocked until a new exact-SHA Full CI run and Simulator run are both green. Do not create the npm version/tag/GitHub Release before those gates and registry publication succeed.