skalpel 3.0.4 → 3.0.6

package/INSTALL.md

@@ -71,11 +71,11 @@ A user who has rolled back to a previous version (by running `npm install -g ska
 
 ## Uninstall
 
-`npm uninstall -g skalpel` removes both binaries. There is no separate uninstall command for `skalpeld`; the package is the unit of removal. Before npm removes the binaries it fires the package's `preuninstall` hook, which invokes `node postinstall/index.js --uninstall`; that pass removes the rc-file managed-block injected on install (so the user's shell stops pointing at the now-defunct local proxy port) and unregisters the per-OS service entry (so `launchctl`, `systemctl --user`, or `schtasks` stops trying to start a daemon whose binary is about to vanish). The shim and registration cleanup happen before the binaries themselves are removed; an interrupted uninstall leaves a coherent intermediate state.
+`skalpel uninstall` is the one-liner for a clean removal. It unregisters the per-OS service entry (launchd / systemd user / Task Scheduler), removes the managed shell-rc block, and deletes `auth.json`, `config.toml`, `skalpeld.lock`, and `logs/` from the per-OS configuration directory. To preserve user data (engine toggles, active org, cached auth), pass `--keep-data`. `--dry-run` previews every action without writing anything. The command does not remove the npm package itself; after running `skalpel uninstall`, finish with `npm uninstall -g skalpel`.
 
-`npx skalpel` users have no global install to uninstall; the npx cache is cleaned by npm on its own schedule. For an `npx`-only user who wants to clean up shell rc-file and service registration without waiting on cache eviction, running `node postinstall/index.js --uninstall` from the package directory performs the same cleanup the `preuninstall` hook would.
+`npm uninstall -g skalpel` on its own removes both binaries. There is no separate uninstall command for `skalpeld`; the package is the unit of removal. Before npm removes the binaries it fires the package's `preuninstall` hook, which invokes `node postinstall/index.js --uninstall`; that pass removes the rc-file managed-block injected on install (so the user's shell stops pointing at the now-defunct local proxy port) and unregisters the per-OS service entry (so `launchctl`, `systemctl --user`, or `schtasks` stops trying to start a daemon whose binary is about to vanish). The shim and registration cleanup happen before the binaries themselves are removed; an interrupted uninstall leaves a coherent intermediate state. The `preuninstall` hook deliberately preserves user data on disk so that `npm uninstall -g skalpel` followed by `npm install -g skalpel` is a non-destructive reinstall; the `skalpel uninstall` one-liner above is the path for users who want a full wipe.
 
-User data is **not** removed by uninstall. The configuration directory (`config.toml` and `auth.json`) persists on disk after the binaries are gone. This is deliberate: a user reinstalling Skalpel on the same machine should find their engine toggles and active organization preserved. To remove user data manually, delete the per-OS configuration directory named in `SPEC.md` §7.
+`npx skalpel` users have no global install to uninstall; the npx cache is cleaned by npm on its own schedule. For an `npx`-only user who wants to clean up shell rc-file and service registration without waiting on cache eviction, `skalpel uninstall` performs the same cleanup the `preuninstall` hook would, plus the user-data wipe.
 
 ## Version coupling
 

package/npm-bin/skalpel.js

@@ -181,11 +181,91 @@ function resolveBinary(name, argv) {
   return candidate;
 }
 
+// runUninstall handles the `skalpel uninstall` subcommand: shells out
+// to postinstall/index.js with --uninstall (+ --cleanup-data by default)
+// and prints a follow-up hint pointing at `npm uninstall -g skalpel` for
+// removing the package itself. The Go binary has no awareness of the
+// postinstall code (which lives in node_modules), so the shim is the
+// only place this command can live.
+function runUninstall(rest) {
+  let cleanupData = true;
+  let dryRun = false;
+  let showHelp = false;
+  for (const a of rest) {
+    switch (a) {
+      case '--keep-data':
+        cleanupData = false;
+        break;
+      case '--dry-run':
+        dryRun = true;
+        break;
+      case '--help':
+      case '-h':
+        showHelp = true;
+        break;
+      default:
+        break;
+    }
+  }
+  if (showHelp) {
+    const colored = process.stdout.isTTY && !process.env.NO_COLOR;
+    const head = colored ? theme.bold(theme.lilac('skalpel uninstall')) : 'skalpel uninstall';
+    const dim = colored ? theme.dim : (s) => s;
+    process.stdout.write(
+      `${head} — clean up skalpel state on this machine\n\n` +
+      `usage: skalpel uninstall [--keep-data] [--dry-run]\n\n` +
+      `By default, removes:\n` +
+      `  • per-OS service entry (launchd / systemd user / Task Scheduler)\n` +
+      `  • managed shell-rc block injected on install\n` +
+      `  • auth.json, config.toml, skalpeld.lock, and logs/ (use --keep-data to preserve)\n\n` +
+      `${dim('Does not remove the npm package itself. To finish removal, run:')}\n` +
+      `  npm uninstall -g skalpel\n`
+    );
+    return 0;
+  }
+
+  const postinstall = path.join(__dirname, '..', 'postinstall', 'index.js');
+  if (!fs.existsSync(postinstall)) {
+    emitError(
+      process.stderr,
+      'postinstall script missing',
+      `Expected ${postinstall} but it does not exist.`,
+      `→ Reinstall: \`npm install -g skalpel\``
+    );
+    return 1;
+  }
+  const args = ['--uninstall'];
+  if (cleanupData) args.push('--cleanup-data');
+  if (dryRun) args.push('--dry-run');
+
+  const result = spawnSync(process.execPath, [postinstall, ...args], {
+    stdio: 'inherit',
+  });
+  if (result.error) {
+    emitError(process.stderr, 'Uninstall failed', result.error.message, '→ Try `npm uninstall -g skalpel`.');
+    return 1;
+  }
+  if (result.status !== 0) {
+    return result.status === null ? 1 : result.status;
+  }
+
+  const colored = process.stdout.isTTY && !process.env.NO_COLOR;
+  const dim = colored ? theme.dim : (s) => s;
+  const ok = colored ? theme.mint('✓') : '✓';
+  process.stdout.write(`\n${ok} skalpel state removed from this machine.\n`);
+  process.stdout.write(`${dim('To finish removal, also run:')}\n`);
+  process.stdout.write(`  npm uninstall -g skalpel\n`);
+  return 0;
+}
+
 if (require.main === module) {
+  const argv = process.argv.slice(2);
+  if (argv[0] === 'uninstall') {
+    process.exit(runUninstall(argv.slice(1)));
+  }
   if (isFirstRun()) {
     emitBanner(process.stdout, platformLabel());
   }
-  const argv = process.argv.slice(2);
   const binary = resolveBinary('skalpel', argv);
   const result = spawnSync(binary, argv, {
     stdio: 'inherit',
@@ -197,4 +277,4 @@ if (require.main === module) {
   process.exit(result.status === null ? 1 : result.status);
 }
 
-module.exports = { resolveBinary, PLATFORM_PACKAGES, renderWelcome, renderError, flagFilePath };
+module.exports = { resolveBinary, runUninstall, PLATFORM_PACKAGES, renderWelcome, renderError, flagFilePath };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "skalpel",
-  "version": "3.0.4",
+  "version": "3.0.6",
   "description": "Skalpel — local proxy and TUI for coding agents (skalpel + skalpeld bundle).",
   "license": "Apache-2.0",
   "homepage": "https://skalpel.ai",
@@ -54,10 +54,10 @@
     "x64"
   ],
   "optionalDependencies": {
-    "@skalpelai/skalpel-darwin-arm64": "3.0.4",
-    "@skalpelai/skalpel-darwin-x64": "3.0.4",
-    "@skalpelai/skalpel-linux-arm64": "3.0.4",
-    "@skalpelai/skalpel-linux-x64": "3.0.4",
-    "@skalpelai/skalpel-win32-x64": "3.0.4"
+    "@skalpelai/skalpel-darwin-arm64": "3.0.6",
+    "@skalpelai/skalpel-darwin-x64": "3.0.6",
+    "@skalpelai/skalpel-linux-arm64": "3.0.6",
+    "@skalpelai/skalpel-linux-x64": "3.0.6",
+    "@skalpelai/skalpel-win32-x64": "3.0.6"
   }
 }