smashspace 0.1.4 → 0.1.6

package/README.md

@@ -17,6 +17,10 @@ agents work through the CLI, MCP, and HTTP API on the *same* data. See
 npm i -g smashspace
 ```
 
+> **Using [Volta](https://volta.sh)?** Install with `volta install smashspace`
+> instead. A global `npm i -g` under Volta leaves a stale shim that later fails
+> with `Volta error: Could not execute command` — `volta install` avoids it.
+
 ## Sign in (approve in the browser — no copy/paste)
 
 ```bash

package/dist/smash.mjs

@@ -3593,7 +3593,10 @@ back to the **\`smash\` CLI**. Do **not** hit the HTTP API with \`curl\` or a ra
 browser \u2014 the CLI and MCP are the supported surfaces and they resolve auth and
 the target board for you.
 
-- CLI install: \`npm i -g smashspace\` (then \`smash --help\`)
+- CLI install: \`npm i -g smashspace\` (then \`smash --help\`).
+  **If the machine uses Volta** (\`command -v volta\` succeeds), install with
+  \`volta install smashspace\` instead \u2014 \`npm i -g\` under Volta leaves a stale
+  shim that fails with "Volta error: Could not execute command".
 - MCP server: \`smashspace-mcp\` (exposes \`smash_*\` tools, same token as the CLI)
 - Sign in once per machine: \`smash login\` (browser approval; token saved to
   \`~/.config/smash/credentials.json\` and reused by MCP)
@@ -3742,7 +3745,10 @@ Verify \`Review\` cards and move verified work to \`Done\`.
 ## Fallbacks
 
 - Prefer \`smashspace-mcp\` MCP tools. If unavailable, use the \`smash\` CLI.
-- If the CLI is not installed: \`npm i -g smashspace\`, then \`smash login\`.
+- If the CLI is not installed: \`npm i -g smashspace\` (or \`volta install smashspace\`
+  on a Volta machine), then \`smash login\`.
+- \`smash\` fails with "Volta error: Could not execute command"? A stale Volta
+  shim \u2014 fix with \`volta install smashspace\` (do NOT \`npm i -g\` under Volta).
 - If a board returns "Sign-in required": run \`smash login\`, or set \`SMASH_TOKEN\`
   for a headless/CI agent.
 
@@ -4525,8 +4531,30 @@ program2.command("login").description(
 ).option(
   "--token <token>",
   "Skip the browser flow and save the provided token directly"
+).option(
+  "-f, --force",
+  "Re-issue a token even if a valid one is already saved"
 ).action(async (opts) => {
   const baseUrl = resolveBaseUrl();
+  if (!opts.token && !opts.force) {
+    const existing = await resolveToken(baseUrl);
+    if (existing) {
+      const check = await fetch(new URL("/api/usage/me", baseUrl), {
+        headers: { Authorization: `Bearer ${existing}` }
+      }).catch(() => null);
+      if (check?.ok) {
+        const me2 = await check.json();
+        show(
+          { baseUrl, userId: me2.userId, alreadySignedIn: true },
+          [
+            `\u2713 already signed in as ${me2.userId} on ${baseUrl} \u2014 saved token is valid, nothing to do.`,
+            `  (use 'smash login --force' to re-issue)`
+          ]
+        );
+        return;
+      }
+    }
+  }
   let token = opts.token?.trim();
   if (!token) {
     try {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "smashspace",
-  "version": "0.1.4",
+  "version": "0.1.6",
   "description": "SmashSpace CLI + MCP — operate SmashSpace boards from your terminal, Claude Code, Cursor, and Codex.",
   "type": "module",
   "bin": {