Problem

The update checker in src/infra/update-channels.ts hardcodes https://registry.npmjs.org/openclaw/... and does not respect the user's npm registry configuration (e.g., registry.npmmirror.com).

This causes fetch timeouts in regions with poor connectivity to the official npm registry.

Current behavior

When checking for updates, the gateway always fetches from https://registry.npmjs.org, ignoring:

• npm config get registry
• ~/.npmrc configuration
• any mirror settings

Expected behavior

The update checker should use the same registry as the package manager (respect npm config get registry or the $npm_config_registry environment variable).

Workaround

Manually patching update-check-*.js files in the pnpm store to replace registry.npmjs.org with a mirror URL — but this gets reverted on every update.

Suggested fix

In src/infra/update-channels.ts, read the registry URL from:

1. process.env.npm_config_registry, or
2. fall back to the hardcoded default only as last resort

Environment

• openclaw version: 2026.5.3-1
• pnpm global store: ~/.local/share/pnpm/global/5/.pnpm/
• npm registry config: https://registry.npmmirror.com