Homeboy releases omit platform CLI archives

## Problem

WP Codebox releases built through the canonical Homeboy component publish the WordPress plugin ZIP and npm workspace tarball, but omit the platform CLI archives that the WordPress extension's default managed-release setup consumes.

Observed after releases `v0.24.1` and `v0.24.2`:

```
Installing WP Codebox CLI from managed release artifact wp-codebox-cli-linux-x64.tar.gz...
WP Codebox release artifact is unavailable from the configured authority; falling back to source install
```

The `v0.24.2` GitHub release contains only:

- `wp-codebox.zip`
- `wp-codebox-workspace-0.24.2.tgz`

Yet `scripts/package-release-artifact.ts` already defines `wp-codebox-cli-${platform}-${arch}.tar.gz`, and the Homeboy WordPress extension defaults to `releases/latest/download/wp-codebox-cli-${platform}-${arch}.tar.gz`.

## Impact

Every extension setup falls back to cloning, installing, and building WP Codebox from `main`. This is slower, loses immutable release-asset authority, and leaves the configured release path perpetually unavailable even though setup eventually succeeds.

## Expected behavior

The canonical release publishes supported platform CLI archives as authoritative GitHub release assets, including at least `wp-codebox-cli-linux-x64.tar.gz`, with provenance that the managed WordPress installer accepts.

## Acceptance criteria

- Homeboy release packaging invokes the existing platform CLI artifact builder or otherwise declares its outputs as release assets.
- Supported platform archive names match installer expectations.
- Archives include accepted version/build provenance and the runtime packages required by the CLI.
- Release package coverage verifies all declared CLI archives.
- A fresh WordPress extension setup installs in managed release mode without source fallback.

Start with scripts/package-release-artifact.ts and trace how the canonical Homeboy component declares and publishes release outputs. Compare its outputs with the WordPress extension's default managed-release archive names and run the release package coverage checks plus a fresh extension setup. Done means supported CLI archives contain accepted provenance and dependencies, and setup no longer falls back to a source install.

Written by the indexing model from the issue text.