@vincentt-xr/cli 0.12.1 → 0.12.3

package/dist/cli/args.d.ts

@@ -51,3 +51,22 @@ export declare function refusedFlag(args: string[]): string | undefined;
  * the worst kind for an identifier that decides which project a folder points at.
  */
 export declare function positionalArgs(args: string[]): string[];
+/**
+ * Does this `create` invocation name a folder that `--dir` already points at?
+ *
+ * `--dir` says WHERE TO WORK; the positional says WHAT TO CREATE INSIDE it. They
+ * compose, so `--dir ~/apps/foo foo` writes `~/apps/foo/foo` — correct by the
+ * rules and almost never what was meant. The help said `--dir <path> (project
+ * dir)` under "Common options", which reads as *the project's own directory*
+ * rather than *the parent of it*, so an agent handed a folder path and a name
+ * passes both and gets a doubled path.
+ *
+ * Returns the resolved `--dir` when the collision is present, so the caller can
+ * name both correct forms; `undefined` otherwise.
+ *
+ * EXACT match on the last path segment only. A near miss (`foo-app` in `foo/`)
+ * is left alone: inferring intent from a similar name would refuse work that was
+ * never ambiguous. Trailing separators are normalised by `resolve` first, so
+ * `--dir ~/apps/foo/` behaves the same as without.
+ */
+export declare function createDirCollision(dirFlag: string | undefined, name: string, resolve: (p: string) => string, basename: (p: string) => string): string | undefined;

package/dist/cli/args.js

@@ -142,3 +142,27 @@ export function positionalArgs(args) {
     }
     return out;
 }
+/**
+ * Does this `create` invocation name a folder that `--dir` already points at?
+ *
+ * `--dir` says WHERE TO WORK; the positional says WHAT TO CREATE INSIDE it. They
+ * compose, so `--dir ~/apps/foo foo` writes `~/apps/foo/foo` — correct by the
+ * rules and almost never what was meant. The help said `--dir <path> (project
+ * dir)` under "Common options", which reads as *the project's own directory*
+ * rather than *the parent of it*, so an agent handed a folder path and a name
+ * passes both and gets a doubled path.
+ *
+ * Returns the resolved `--dir` when the collision is present, so the caller can
+ * name both correct forms; `undefined` otherwise.
+ *
+ * EXACT match on the last path segment only. A near miss (`foo-app` in `foo/`)
+ * is left alone: inferring intent from a similar name would refuse work that was
+ * never ambiguous. Trailing separators are normalised by `resolve` first, so
+ * `--dir ~/apps/foo/` behaves the same as without.
+ */
+export function createDirCollision(dirFlag, name, resolve, basename) {
+    if (dirFlag === undefined)
+        return undefined;
+    const resolved = resolve(dirFlag);
+    return basename(resolved) === name ? resolved : undefined;
+}

package/dist/cli/index.js

@@ -48,7 +48,7 @@ import { nudgeFor } from "../dx/nudge.js";
 import { FETCH_TIMEOUT_MS, isFresh, updateNotice } from "../dx/updateCheck.js";
 import { fetchLatest, loadCache, saveCache } from "../dx/updateCheckIo.js";
 import { verbOf } from "../dx/skeleton.js";
-import { createSourceFlagRefusal, fromFlagConflict, isHelpInvocation, isVersionInvocation, positionalArgs, refusedFlag, } from "./args.js";
+import { createDirCollision, createSourceFlagRefusal, fromFlagConflict, isHelpInvocation, isVersionInvocation, positionalArgs, refusedFlag, } from "./args.js";
 import { parseSourceRef } from "../lib/sourceRef.js";
 import { printCreateSourceFlagRefusal, printFlagConflict, printSourceRefFailure, } from "../lib/sourceRefCopy.js";
 import { registerAfterScaffold } from "../lib/initFrom.js";
@@ -291,6 +291,34 @@ async function create() {
             process.exitCode = 1;
             return;
         }
+        // `--dir` says WHERE TO WORK; the positional says WHAT TO CREATE INSIDE it.
+        // They compose, so `--dir ~/apps/foo foo` writes `~/apps/foo/foo` — correct
+        // by the rules and almost never what was meant.
+        //
+        // Refused rather than silently resolved, because both readings are defensible
+        // and the CLI cannot tell them apart: someone who genuinely wants a nested
+        // `foo/foo` has a way to say so (below), and someone who does not gets the
+        // mistake at the moment it is cheap instead of after a scaffold and a
+        // registration.
+        //
+        // This fires on an EXACT match of the last path segment only. A near miss is
+        // left alone: guessing at intent from a similar name would refuse work that
+        // was never ambiguous.
+        const collided = createDirCollision(flag("--dir"), safe, path.resolve, path.basename);
+        if (collided !== undefined) {
+            const parent = path.dirname(collided);
+            print(`✗ That would create "${safe}" inside a folder already called "${safe}".`);
+            print("");
+            print("  --dir is where to work; the name is the folder to create inside it.");
+            print("");
+            print(`  For ${path.join(parent, safe)}:`);
+            print(`    vincentt create --dir ${parent} ${safe}`);
+            print("");
+            print(`  For ${path.join(collided, safe)}, which is what this asked for:`);
+            print(`    cd ${collided} && vincentt create ${safe}`);
+            process.exitCode = 1;
+            return;
+        }
         dir = safe;
     }
     const interactive = Boolean(process.stdin.isTTY) && Boolean(process.stdout.isTTY);

package/dist/cli/usage-text.js

@@ -21,7 +21,12 @@ export const USAGE_TEXT = `Vincentt CLI — local-first AR dev loop\n\n` +
     `                       [--from <owner>/<repo>@<tag>] Clone a gallery template\n` +
     `                       and register it   [--name <s>] [--slug <s>]\n` +
     `  create [name]      Register a project and reserve its address; scaffolds first\n` +
-    `                       if the folder is empty   [--name <s>] [--slug <s>]\n` +
+    `                       if the folder is empty. The name is a NEW folder created\n` +
+    `                       inside the working dir, not the working dir itself:\n` +
+    `                         vincentt create my-app              -> ./my-app\n` +
+    `                         vincentt create --dir ~/code my-app -> ~/code/my-app\n` +
+    `                       Omit the name to use the current folder as-is.\n` +
+    `                       [--name <s>] [--slug <s>]\n` +
     `                       [--org <s>] [--preview] [--force] [--no-install]\n` +
     `  link <project-id>  Link this folder to an existing project\n` +
     `  unlink             Disconnect this folder from its project\n` +
@@ -93,5 +98,6 @@ export const USAGE_TEXT = `Vincentt CLI — local-first AR dev loop\n\n` +
     `                       disable it, and is shown on \`vincentt dx\` and\n` +
     `                       \`vincentt version\` while on.\n` +
     `  dx disable         Turn that off again.\n\n` +
-    `Common options: --dir <path> (project dir, default cwd)\n` +
+    `Common options: --dir <path> (where to work, default cwd — for \`create\` this is\n` +
+    `                              the PARENT of the new folder, not the folder itself)\n` +
     `                --allow-custom-api  honor a binding's apiUrl override\n`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vincentt-xr/cli",
-  "version": "0.12.1",
+  "version": "0.12.3",
   "description": "Vincentt CLI — the vincentt command-line dev loop (login, create, publish, preview, diagnostics, feedback, relay)",
   "license": "UNLICENSED",
   "type": "module",
@@ -24,7 +24,7 @@
     "qrcode": "^1.5.4",
     "ws": "^8.18.0",
     "zod": "^3.23.8",
-    "@vincentt-xr/harness": "1.3.0"
+    "@vincentt-xr/harness": "1.4.0"
   },
   "devDependencies": {
     "@types/qrcode": "^1.5.5",