test: packed one-copy check installs with npm and no peers, as users do

Merged
AN
2d ago
+20-1

On 21 Oct the 2.2.2 release PR failed in the packed smoke because Bun resolved Pi's peer tree (pi-ai pulls the AWS SDK), and AWS had published client-bedrock-runtime and core before the @aws-sdk/types and credential-provider-process versions they require. npm with --omit=peer installs no AWS packages. The copy-count step now uses npm with --omit=peer --omit=dev --ignore-scripts, from the same packed tarballs, Core forced through overrides; the rest of the smoke stays on Bun. Still red when OpenCode pins claustrum-client 0.11.0 against Core's 0.12.0 (both copies named).

Summary by cubic

Switches the packed one-copy install smoke test from Bun to npm so it matches how users actually install OpenCode and Pi, making the check resilient to inconsistent registry states.

  • bun install --omit peer still resolves Pi's peer tree, which dragged in the AWS SDK and broke the 2.2.2 release when AWS published a package before its own dependencies.
  • The step now runs npm install --omit=peer --omit=dev --ignore-scripts --no-audit --no-fund from the same packed tarballs, with Core forced to its packed tarball through overrides.
  • The rest of the smoke stays on Bun.
  • The check is still red when OpenCode pins claustrum-client 0.11.0 against Core's 0.12.0.