heyspex 0.2.5 → 0.2.7

package/bin/postinstall.mjs

@@ -1,88 +0,0 @@
-#!/usr/bin/env node
-// Root postinstall guard. The dev-machine setup steps (PM control-center deps,
-// Claude Code hooks, CommandCode update) live under scripts/, which
-// .vercelignore excludes from the Vercel upload — so on Vercel (or any CI, or
-// any environment where scripts/ is absent) this must exit 0 instead of
-// crashing `npm install` with MODULE_NOT_FOUND. Lives in bin/ (uploaded to
-// Vercel) precisely so the guard itself always resolves.
-import { existsSync } from "node:fs";
-import { spawnSync } from "node:child_process";
-import { dirname, join } from "node:path";
-import { fileURLToPath, pathToFileURL } from "node:url";
-
-const repoRoot = dirname(dirname(fileURLToPath(import.meta.url)));
-
-// Installed as somebody else's dependency (HS-ZJSP): the published `heyspex`
-// package ships this file because npm runs the `postinstall` script for every
-// consumer, but NONE of the dev-machine setup below belongs in a customer's
-// install — and printing a "skipping" line at them is noise, not information.
-// A package installed from the registry always lands under a node_modules/
-// directory; a clone of this repo never does. Exit silently in the former case.
-if (repoRoot.replace(/\\/g, "/").includes("/node_modules/")) {
-  process.exit(0);
-}
-
-const steps = [
-  ["scripts/ensure-pm-cc-deps.mjs"],
-  ["scripts/install-claude-code-hooks.mjs"],
-  // Cursor's two install surfaces. `.cursor/mcp.json` is gitignored (it is
-  // machine-local), so without this step a fresh clone opens in Cursor with no
-  // heyspex MCP server at all; `.cursor/hooks.json` is tracked but merges
-  // idempotently, and the installer also retires superseded registrations.
-  ["scripts/install-cursor-mcp.mjs"],
-  ["scripts/install-cursor-hooks.mjs"],
-  ["scripts/install-commandcode.mjs", "--update"],
-  ["scripts/sync-skills.mjs"],
-  // Git hooks (.git/hooks/ is never cloned) — installs pre-commit + pre-push so a
-  // single `npm install` on a fresh clone is enough, with no second `npm run setup`.
-  // No --force: an idempotent re-run no-ops on the HeySpex hook and refuses to
-  // clobber a foreign pre-commit (exit 1 surfaces that rather than silently replacing).
-  ["scripts/install-git-hooks.mjs"],
-];
-
-if (process.env.VERCEL || process.env.CI) {
-  console.log("[postinstall] VERCEL/CI detected — skipping dev-machine setup.");
-  process.exit(0);
-}
-
-for (const [script, ...args] of steps) {
-  const abs = join(repoRoot, script);
-  if (!existsSync(abs)) {
-    console.log(`[postinstall] ${script} not present — skipping dev-machine setup.`);
-    process.exit(0);
-  }
-  const { status } = spawnSync(process.execPath, [abs, ...args], {
-    cwd: repoRoot,
-    stdio: "inherit",
-  });
-  if (status !== 0) process.exit(status ?? 1);
-}
-
-// Advisory only, never fatal, and deliberately NOT `npm link` itself: a
-// postinstall that mutates the machine's global npm prefix would repoint `hs`
-// away from whatever clone owned it, silently, on every install. `npm install`
-// completing clean while `hs` resolves nowhere is exactly the fresh-machine
-// failure in [[HS-BFXF-WBJU-DIAG-hs-never-resolves-on-a-fresh-machine]] — so
-// say so here, where a new operator is already looking, and let `npm run
-// doctor` carry the full check. Imported dynamically so the published package
-// (which ships this file but not scripts/) can never fail to resolve it.
-const hsLinkLib = join(repoRoot, "scripts/lib/hs-link.mjs");
-if (existsSync(hsLinkLib)) {
-  try {
-    const { describeHsLink } = await import(pathToFileURL(hsLinkLib).href);
-    const link = describeHsLink(repoRoot);
-    if (link.status !== "linked") {
-      const what = {
-        missing: "does not resolve on PATH",
-        foreign: `resolves to an unrelated tool (${link.target})`,
-        "other-checkout": `resolves to a DIFFERENT checkout (${link.target})`,
-        unreadable: `resolves to ${link.shim}, whose target could not be read`,
-      }[link.status];
-      console.log(`[postinstall] heads up: \`hs\` ${what}.`);
-      console.log("[postinstall] Run `npm link` once from this repo root to put hs/heyspex/heyspex-mcp on PATH.");
-      console.log("[postinstall] Until then use `node bin/hs.mjs …` — never `npx hs` (unrelated package). Details: `npm run doctor`.");
-    }
-  } catch {
-    // An advisory that crashes the install would be worse than no advisory.
-  }
-}