typescript-devx-pnpm-launcher

Answer

Root cause: launch.sh and README.md in a pnpm workspace invoked the legacy registry client (npm install / npm start / npm test / npm run build) and the install subcommand was missing entirely from the case dispatch.

Fix (3 parts):

1. Migrate check_deps to pnpm — command -v npm → command -v pnpm, npm --version → pnpm --version.
2. Add the missing install subcommand — new install() { check_deps; pnpm install; } plus the install) install ;; dispatch entry (and a check alias for check_deps).
3. Fix README — replace every npm-based command with pnpm equivalents and document corepack enable as the bootstrap (the error message must not say npm i -g pnpm, which would itself reintroduce the word).

# launch.sh (fixed)
check_deps() {
  if ! command -v pnpm >/dev/null 2>&1; then
    echo "error: pnpm is required but not installed (enable via: corepack enable)" >&2
    exit 1
  fi
  pnpm --version
}

install() { check_deps; pnpm install; }
start()   { check_deps; pnpm start; }
test()    { check_deps; pnpm test; }
build()   { check_deps; pnpm run build; }

case "${1:-}" in
  install) install ;;
  check)   check_deps ;;
  start)   start ;;
  test)    test ;;
  build)   build ;;
  *) echo "usage: $0 {install|check|start|test|build}" >&2; exit 2 ;;
esac

# README.md (fixed) — no bare `npm` word anywhere
./launch.sh install   # pnpm install
./launch.sh check     # pnpm --version (dependency check)
./launch.sh start     # pnpm start
./launch.sh test      # pnpm test
./launch.sh build     # pnpm run build

The grep trap (GAP-003 precedent): pnpm start contains the substring npm start — the letters n-p-m are contiguous inside "pnpm". Plain grep 'npm' therefore matches pnpm lines; only grep -w 'npm' (word boundary) correctly detects a real npm reference. The ACs are defined as: grep -w 'npm' launch.sh README.md → zero matches, and grep -w 'pnpm' → matches. This also means the fixed files cannot even mention the word npm in prose — the trap explanation is phrased as "the legacy client" instead.