@qaping/cli 0.1.4 → 0.1.5

package/bin/qaping

@@ -22,6 +22,11 @@ const { spawnSync } = require("child_process");
 
 const QPKG = path.resolve(__dirname, "..");
 
+// The name npm actually serves. The bare `qaping` is refused by the registry's
+// similarity rule (petition open, QAPING_PLAN.md §8), so every global install —
+// the wrapper's own and the one the kit's setup performs — must use this.
+const NPM_PACKAGE = "@qaping/cli";
+
 // The kit is a normal npm dependency when qaping is installed, and a workspace
 // sibling in the monorepo checkout (where node_modules may not be linked yet)
 // — resolve the package, never a hardcoded install path.
@@ -55,7 +60,7 @@ function qapingWrapper() {
     brand: "qaping",
     // npm registry name ≠ bin name: the similarity rule blocks bare "qaping"
     // (petition open, QAPING_PLAN §8), so the global install pulls @qaping/cli.
-    installPackage: "@qaping/cli",
+    installPackage: NPM_PACKAGE,
     appUrl: process.env.QAPING_APP_URL || undefined,
     mcpPath: "/api/mcp/qaping",
     serverKey: "qaping",
@@ -122,6 +127,32 @@ function defaultIO(kitDir) {
 
 const VALID_CLIENTS = ["claude-desktop", "claude-code", "cursor", "codex"];
 
+// The kit's setup step 2 installs the global bin as `npm i -g <brand>` unless
+// it is handed an installPackage — and a PUBLISHED kit older than that option
+// ignores it, so it runs `npm i -g qaping`, a name npm's similarity rule
+// refuses to host (404). Hit live on a fresh machine: setup configured every
+// MCP client and reused the login, then reported "Setup incomplete" over that
+// one 404.
+//
+// So the wrapper installs its OWN bin first, under the name npm serves. Once
+// `qaping` is on PATH the kit's step finds it and logs "already installed
+// globally", whatever kit version is underneath. npx runs from a cache dir
+// that is NOT a persistent install — exactly the case that step exists for —
+// so a cache/tmp path does not count as already installed.
+function ensureGlobalBin(io) {
+  if (isSourceCheckout()) return;
+  const existing = io.which("qaping");
+  const persistent =
+    existing && !/[\\/](_npx|_cacache|npm-cache|Temp|tmp)[\\/]/i.test(existing);
+  if (persistent) return;
+  io.log(`Installing the qaping command (npm i -g ${NPM_PACKAGE})…`);
+  const r = io.run("npm", ["i", "-g", NPM_PACKAGE]);
+  if (!r || r.error || r.status !== 0) {
+    io.log(`⚠ could not install the qaping command — run it yourself: npm i -g ${NPM_PACKAGE}`);
+    io.log("  (setup continues; the MCP tools your agent calls do not need it, but `qaping publish-build` does)");
+  }
+}
+
 async function cmdSetup(argv) {
   const kitDir = resolveKitDir();
   const { setup } = require(path.join(kitDir, "harness", "setup.js"));
@@ -129,7 +160,9 @@ async function cmdSetup(argv) {
   // accepts both the positional form (`setup cursor`) and `setup --client cursor`
   const args = argv.filter((a) => a !== "--force");
   const client = ((args[1] === "--client" ? args[2] : args[1]) || "").toLowerCase();
-  const r = await setup(defaultIO(kitDir), {
+  const io = defaultIO(kitDir);
+  ensureGlobalBin(io);
+  const r = await setup(io, {
     home: os.homedir(),
     sourceCheckout: isSourceCheckout(),
     resolveToken,

package/package.json

@@ -1,6 +1,7 @@
 {
   "name": "@qaping/cli",
-  "version": "0.1.4",
+  "version": "0.1.5",
+  "homepage": "https://qaping.dev",
   "description": "qaping: automatic QA for your game. Your coding agent authors and maintains the QA plan, ships each patch's build to real human playtesters, and reports what broke.",
   "keywords": [
     "qaping",