@deftai/directive-content 0.73.1 → 0.74.0

package/skills/deft-directive-setup/SKILL.md

@@ -24,6 +24,22 @@ Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 - User asks to create USER.md, PROJECT-DEFINITION.xbrief.json, or a specification
 - User clones a deft-enabled repo for the first time with no config
 
+## Consumer-first default (#1813)
+
+! Assume the operator is **using Deft in their project** (consumer path). Proceed directly to the Pre-Cutover Detection Guard and Phase 1 — do NOT open with a contributor-vs-consumer fork.
+
+~ The overwhelming majority of setup sessions are consumer installs; contributor onboarding is a separate, opt-in path (see below).
+
+## Contributor / framework-maintainer path (secondary)
+
+? Only enter this branch when the user **explicitly** says they are working on Deft itself (framework source checkout, `deftai/directive` clone, or maintainer tooling).
+
+When that happens:
+
+1. ! Tell the user: "Contributor setup lives in [`CONTRIBUTING.md`](../../../CONTRIBUTING.md) and this repo's root [`AGENTS.md`](../../../AGENTS.md). Use the maintainer installer: `deft-install --yes --upgrade --maintainer --repo-root . --json`."
+2. ⊗ Continue the consumer USER.md / PROJECT-DEFINITION interview — the maintainer path does not use the first-session consumer flow.
+3. **Stop here** unless the user explicitly asks to continue with consumer setup anyway.
+
 ## Pre-Cutover Detection Guard
 
 ! Before proceeding with any setup phase, detect whether the project uses the pre-v0.20 document model and redirect to migration if so.

package/tasks/engine.yml

@@ -28,12 +28,21 @@ tasks:
             process.exit(2);
           }
           const pkg=JSON.parse(fs.readFileSync(pkgPath,'utf8'));
+          // Cross-platform probe (#2415): do NOT use Unix `sh -c 'command -v'` —
+          // Windows native Task often has no `sh` on PATH, so Corepack.cmd was
+          // invisible after #2411. Prefer a direct spawn (POSIX / real binaries);
+          // fall back to shell:true so PATHEXT resolves .cmd/.exe on win32.
           const hasCmd=(name)=>{
             try{
-              execFileSync('sh',['-c','command -v '+name],{stdio:'ignore'});
+              execFileSync(name,['--version'],{stdio:'ignore'});
               return true;
             }catch{
-              return false;
+              try{
+                execFileSync(name,['--version'],{stdio:'ignore',shell:true});
+                return true;
+              }catch{
+                return false;
+              }
             }
           };
           const run=(cmd,args)=>{
@@ -100,12 +109,21 @@ tasks:
             const script='build';
             const pkgPath=root+'/package.json';
             const pkg=JSON.parse(fs.readFileSync(pkgPath,'utf8'));
+            // Cross-platform probe (#2415): do NOT use Unix `sh -c 'command -v'` —
+            // Windows native Task often has no `sh` on PATH, so Corepack.cmd was
+            // invisible after #2411. Prefer a direct spawn (POSIX / real binaries);
+            // fall back to shell:true so PATHEXT resolves .cmd/.exe on win32.
             const hasCmd=(name)=>{
               try{
-                execFileSync('sh',['-c','command -v '+name],{stdio:'ignore'});
+                execFileSync(name,['--version'],{stdio:'ignore'});
                 return true;
               }catch{
-                return false;
+                try{
+                  execFileSync(name,['--version'],{stdio:'ignore',shell:true});
+                  return true;
+                }catch{
+                  return false;
+                }
               }
             };
             const run=(cmd,args)=>{