Make v0.13 release artifacts installable and platform-correct

[chubes4]

Problem

Both v0.13.0 release assets failed as local CLI installation sources while recovering an Intelligence release:

1. 02-wp-codebox-workspace-0.13.0.tgz runs patch-package from postinstall, but that dev-only binary is absent. Installing with --ignore-scripts then fails because @php-wasm/util@3.1.46 is unavailable from the configured registry.
2. 01-wp-codebox.zip contains vendor/wp-codebox-cli, but its workspace links under node_modules/@automattic are absent after standard ZIP extraction, so the CLI cannot resolve @automattic/wp-codebox-core. Its bundled vendor/node/bin/node is Linux and fails with Exec format error on macOS arm64.

The published ZIP digest was verified as 0682b7ac37646fdfb505acb598664ab717c100d24f2dab37c79ebb8117804407.

Expected

• The thin tarball installs globally without development hooks or unpublished dependencies.
• The self-contained CLI artifact preserves/resolves workspace packages without symlink-dependent ZIP behavior.
• Release assets are platform-specific, or the wrapper rejects an incompatible bundled Node binary and uses the host runtime.
• CI installs each published artifact into a clean environment and runs wp-codebox --version plus wp-codebox commands on supported platforms.

Temporary recovery

A source-built v0.13.0 runtime passed both CLI probes and reclaimed the stale Playground lock, allowing the original release workflow to continue.