Unpublished @claude-flow/mcp alpha.10 pin blocks install-dependent CI

## Finding

The default branch declares an unpublished `@claude-flow/mcp@3.0.0-alpha.10` in two manifests while the lockfile resolves the published alpha.9. Fresh installation fails with `ETARGET`, preventing the root audit, test, type-check, integration, verification, and packaging jobs from running.

- Severity: **Medium functionality**, **High operational impact**
- Confidence: **High**
- Estimated effort: **under 1 day**
- Expected impact: restore installability and make security/test evidence attributable again.

## Confirmed evidence

Affected paths on current `main`:

- `package.json`: `"@claude-flow/mcp": "3.0.0-alpha.10"`
- `v3/@claude-flow/cli/package.json`: the same alpha.10 pin
- `package-lock.json`: root metadata and resolved node module remain on published `3.0.0-alpha.9`

The official npm package page exposed alpha.9 as the latest published `@claude-flow/mcp` version when checked on 2026-08-25.

On draft PR #3094, [CVE Audit Gate job 97709499633](https://github.com/ruvnet/ruflo/actions/runs/32817784142/job/97709499633) fails at `npm install --package-lock-only --ignore-scripts` before the root audit can execute. The same installation failure fans out into the main CI, V3, integration, and verification workflows. The PR's CodeQL, v3 audit, dependency review, and supply-chain checks pass, but 37 observed checks fail and install-dependent validation is absent.

No open issue specifically covering this alpha.10 manifest/lock mismatch was found. This is distinct from historical ETARGET reports for other packages.

## Reproduction

```sh
npm install --package-lock-only --ignore-scripts
```

Expected today: npm reports `ETARGET` / no matching version for `@claude-flow/mcp@3.0.0-alpha.10`.

## Acceptance test

- Root and CLI manifests reference an actually published, mutually compatible version.
- The lockfile resolves that same version with no manifest drift.
- Add or extend a release/helper idempotence guard so running preparation tooling cannot reintroduce an unpublished pin.
- `npm install --package-lock-only --ignore-scripts` succeeds from a clean checkout.
- Root audit and all install-dependent PR workflows run to completion.
- PR #3094 is re-evaluated only after these gates execute; its product-quantization result remains **INCONCLUSIVE** until then.

No dependency patch is proposed here because dependency/release surfaces require maintainer validation.

Start with package.json, v3/@claude-flow/cli/package.json, and package-lock.json, then inspect the release/helper preparation tooling and the failing CVE Audit Gate job. Run npm install --package-lock-only --ignore-scripts from a clean checkout. Done means both manifests and the lockfile agree on a published compatible version, preparation tooling cannot restore the unpublished pin, and install-dependent workflows can run.

Written by the indexing model from the issue text.