fix(sdk): show nuxt install failures

[cyq1017]

Fixes #5008.

Problem:

• The Nuxt runtime-compat harness ran both npm install steps with --silent, so transient registry/install failures could exit without the useful npm error text in CI logs.

Change:

• Remove --silent from the Nuxt runtime install steps so npm failure details remain visible.
• Add a shell-level regression test with a fake npm that verifies install failures from either install step are surfaced.

Verification:

• bash libs/sdk-typescript/runtime-tests/test-nuxt-install-diagnostics.sh
• git diff --check origin/main...HEAD
• sensitive scan over changed files

---

Summary by cubic

Show npm error output during Nuxt runtime installs in CI by removing --silent, so transient registry/install failures are visible. Adds a regression test with a temporary fake npm to ensure failures from either install step surface their messages.

• Bug Fixes
  • Removed --silent from both npm install calls in libs/sdk-typescript/runtime-tests/nuxt/run.sh to keep error output.
  • Added libs/sdk-typescript/runtime-tests/test-nuxt-install-diagnostics.sh that injects a fake npm via PATH and asserts the failure message appears when the first or second install fails.

^{Written for commit e495f12. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 2 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>