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

[github-actions]

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

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 45.2 days ago (budget 14d), while the tree is at 0.5.1512 -- 292 unreleased patch bumps behind
@perryts/perry-darwin-arm64	npm's latest is 0.5.1220, published 45.2 days ago (budget 14d), while the tree is at 0.5.1512 -- 292 unreleased patch bumps behind
@perryts/perry-darwin-x64	npm's latest is 0.5.1220, published 45.2 days ago (budget 14d), while the tree is at 0.5.1512 -- 292 unreleased patch bumps behind
@perryts/perry-linux-arm64	npm's latest is 0.5.1220, published 45.2 days ago (budget 14d), while the tree is at 0.5.1512 -- 292 unreleased patch bumps behind
@perryts/perry-linux-arm64-musl	npm's latest is 0.5.1220, published 45.2 days ago (budget 14d), while the tree is at 0.5.1512 -- 292 unreleased patch bumps behind
@perryts/perry-linux-x64	npm's latest is 0.5.1220, published 45.2 days ago (budget 14d), while the tree is at 0.5.1512 -- 292 unreleased patch bumps behind
@perryts/perry-linux-x64-musl	npm's latest is 0.5.1220, published 45.2 days ago (budget 14d), while the tree is at 0.5.1512 -- 292 unreleased patch bumps behind
@perryts/perry-win32-arm64	the registry has no package @perryts/perry-win32-arm64 at all (HTTP 404) -- it has never been published, or it was removed, while npm/ still ships a package.json.tmpl for it
@perryts/perry-win32-x64	npm's latest is 0.5.1220, published 45.2 days ago (budget 14d), while the tree is at 0.5.1512 -- 292 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.