Bug

openclaw update (and openclaw plugins install acpx) fails to install the acpx plugin because @openclaw/acpx does not exist on the npm registry:

Downloading @openclaw/acpx…
Failed to install acpx: npm pack failed:
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@openclaw%2facpx - Not found
npm error 404  '@openclaw/acpx@*' is not in this registry.

The unscoped package acpx (v0.1.15) exists and is published, but the plugin installer resolves the scoped name @openclaw/acpx which 404s.

Steps to reproduce

1. openclaw update (from 2026.2.26 to 2026.3.2)
2. Plugin download phase attempts @openclaw/acpx from npm registry
3. Fails with E404

Expected behavior

The acpx plugin should install successfully, either via:

• Publishing the scoped @openclaw/acpx package to npm, or
• Defaulting the acpx plugin to local install (same fix as [Bug]: Unable to download @openclaw/googlechat (404) #9189 / PR Fix: Use local plugins for unpublished npm packages #9196 for googlechat, mattermost, line, tlon)

Context

This is the same class of issue as #9189, where several plugin defaultChoice values were changed from 'npm' to 'local' because the scoped packages weren't published. The acpx plugin was not included in that fix, likely because it was added to the plugin list after PR #9196 landed.

Environment

• OpenClaw 2026.3.2 (85377a2)
• macOS (npm install via global node_modules)
• npm view @openclaw/acpx → 404
• npm view acpx → 0.1.15 (exists, published)