create-agentic-workspace 0.2.1 → 0.2.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-agentic-workspace",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "The pre-session bootstrap wizard for an Agentic Foundry workspace: declares (never grants) the permission floor, absorbs foundry-bootstrap.sh's out-of-session identity wiring, and scaffolds a seven-file schema-valid workspace. Zero dependencies, no lifecycle scripts, no telemetry.",
   "license": "MIT",
   "type": "module",
@@ -34,7 +34,7 @@
     "marketplace_name": "agentic-foundry",
     "marketplace_repo": "lukasrepublic/agentic-foundry",
     "plugin_name": "foundry",
-    "plugin_version": "1.2.1",
+    "plugin_version": "1.2.2",
     "pins_researched": "2026-08-02"
   }
 }

package/permission-floor.json

@@ -1,7 +1,7 @@
 {
   "schema_version": 1,
   "plugin_root_glob": "~/.claude/plugins/cache/*/foundry/*",
-  "generated_for_plugin_version": "1.2.1",
+  "generated_for_plugin_version": "1.2.2",
   "entries": [
     {
       "rule": "Bash(~/.claude/plugins/cache/*/foundry/*/scripts/foundry-acceptance-contract-validate.py:*)",

package/src/preview.mjs

@@ -23,12 +23,29 @@ export function renderPreview({ plan, machineScopeWrites, map }) {
   return lines.join('\n');
 }
 
-export const TRUST_HANDOFF_TEXT = (dir) => `
+// `isGitRepo` is computed by the CALLER and passed in, so this module stays pure (it renders text;
+// it does not probe the filesystem).
+//
+// WHY THE GIT STEP IS PRINTED AND NOT PERFORMED. A workspace that is not a git repository is a
+// dead end: the factory's whole discipline is branch-per-atom → PR → merge floor, and the setup
+// path tells the reader to apply branch protection a few steps later — which needs a repo AND a
+// remote. This CLI ALREADY writes a `.gitignore`, which means nothing without one.
+//
+// It is still printed rather than run. This CLI's contract is that it writes exactly the files it
+// previewed and nothing else; `git init` would be an un-previewed side effect, and the choice of
+// remote is genuinely the reader's. `create-vite` prints its next steps the same way, for the same
+// reason. Telling keeps the promise; doing would quietly break it.
+export const TRUST_HANDOFF_TEXT = (dir, { isGitRepo = true } = {}) => `
 The workspace has been written. The permission floor above is a declaration, not a grant: the
 platform's trust dialog is the consent ceremony, and the \`allow\` rules take effect only after
 you accept it — the dialog lists them.
 
-  cd ${dir}
+  cd ${dir}${isGitRepo ? '' : `
+  git init && git add -A && git commit -m 'workspace seed'
+  # ^ this directory is NOT a git repository yet. The factory works through
+  #   branch-per-atom → PR → the merge floor, so it needs a repo and a remote.
+  #   Create the remote too (e.g. \`gh repo create <you>/<project>-handbook --private --source=. --push\`)
+  #   before you reach the branch-protection step.`}
   claude
   > (accept the trust dialog when prompted)
   > /foundry:init

package/src/run.mjs

@@ -194,7 +194,12 @@ export async function runCli(argv, { cwd, isTTY, input, output, homeDir, pkgDir
       for (const f of findings) print(`  [${f.class}] ${JSON.stringify(f)}`);
     }
 
-    print(TRUST_HANDOFF_TEXT(targetRoot));
+    // Probed here, not inside preview.mjs, which renders text and never touches the filesystem.
+    // `.git` is a DIRECTORY in a normal clone and a FILE in a worktree/submodule, so `existsSync`
+    // on the path is the check that covers both — a directory-only test would tell a worktree user
+    // to re-init a repository they already have.
+    const isGitRepo = fs.existsSync(path.join(targetRoot, '.git'));
+    print(TRUST_HANDOFF_TEXT(targetRoot, { isGitRepo }));
 
     return { exitCode: exitCodeForPlan(plan), output: lines.join('\n') };
   } catch (e) {