@ryuenn3123/agentic-senior-core 6.16.3 → 6.16.5

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/divergence.md

@@ -86,7 +86,7 @@ Slop is not static. As soon as AI models are instructed to avoid one set of clic
 
 ```
 ┌────────────────────────────────────────────────────────┐
-│           THE THREE WAVES OF AI DESIGN TELLS           │
+│           THE FOUR WAVES OF AI DESIGN TELLS            │
 ├────────────────────────────────────────────────────────┤
 │ Wave 1 (2023–2024): The Neon Starter Pack              │
 │ Violet/cyan gradients, glassmorphism, floating drop    │
@@ -100,16 +100,26 @@ Slop is not static. As soon as AI models are instructed to avoid one set of clic
 │ Yellow-cream parchment (#FDFBF7) + terracotta/rust,   │
 │ giant italic serif display, broadsheet newspaper grids,│
 │ performative index numbers (01 / 02), fake coordinates.│
+├────────────────────────────────────────────────────────┤
+│ Wave 4 (2026): The Geek / Terminal Cosplay             │
+│ ASCII art charts, pseudo-telemetry consoles, fake dark │
+│ terminal frames forced onto non-developer products.    │
 └────────────────────────────────────────────────────────┘
 ```
 
 ### 5.1 Defending Against Wave 3 (Editorial Slop)
-The remedy published for Wave 1 and 2 was "warm it up and make it editorial". Models adopted this wholesale, making warm editorial the most instantly recognizable AI tell of 2026:
+The remedy published for Wave 1 and 2 was "warm it up and make it editorial". Models adopted this wholesale, making warm editorial an instantly recognizable AI tell:
 - **Terracotta & Cream Monoculture:** Banned as an unprompted AI reflex. Warmth must come from low-chroma stone, authentic product photography, or deep rich ink—not default yellow-cream backgrounds paired with rust orange.
 - **Oversized Italic Serif Cliché:** Do not use italic serif display as a superficial shortcut to "luxury" or "premium" unless the client's actual brand specifically requires it.
 - **Broadsheet Cosplay:** Hairline 1px borders dividing zero-radius dense columns to mimic an 1890s newspaper is an artificial costume. Structure must emerge from clear spatial scale and tonal contrast.
 - **Performative Agency Metadata:** Banned decorative index numbering (`01`, `02`, `(001)`), fake coordinates (`37.77° N`), and version stamps (`©2026 — Scroll`) that convey zero operational data.
 
+### 5.2 Defending Against Wave 4 (Geek & Terminal Cosplay)
+When models are forbidden from building generic cards or warm editorial broadsheets, they frequently overcorrect by turning *every* application into a cyberpunk or terminal telemetry dashboard:
+- **Hard Ban on Non-Developer Terminals:** Never enclose ordinary educational, institutional, or business data inside a fake terminal window with prompt symbols (`$`, `>`).
+- **No ASCII Charts or Brackets:** Never generate ASCII art radar charts (`/\`, `[■■■□□]`), pseudo-status brackets (`[STATUS: 112]`), or terminal line-drawings. Use semantic HTML5 `<progress>` elements, styled SVG bars, and clean tabular typography.
+- **Zero Pseudo-Telemetry Jargon:** Never label normal administrative or assessment features with fake aerospace/hacker jargon ("telemetry console", "neural assessment engine", "quantum telemetry"). Call it what it is plainly in human language.
+
 ---
 
 ## 6. Substance Over Restraint (Anti-Sterile Empty Voids)
@@ -124,4 +134,26 @@ Stripping away slop ornaments (cards, borders, badges, gradients) is only the fi
 2. **Full-Field Color Anchors:** Instead of scattering small floating cards, ground layouts with full-bleed background tone shifts (e.g., transitioning from a clean light canvas into a deep, tinted section floor).
 3. **Authentic Interface Fragments:** For software products, construct working, interactive HTML/CSS UI components (a data table with real rows, an interactive calculation filter, or live code tabs) rather than empty illustrations or placeholder diagrams.
 
+---
+
+## 7. The Card-Soup Syndrome & Unified Spatial Canvas
+
+The most prevalent tell of generative AI frontends in 2026 is **The Card-Soup Syndrome (Archipelago of Floating Cards)**.
+
+### 7.1 What is Card-Soup?
+Because LLMs are trained on millions of generic Tailwind and component library examples, their immediate probabilistic reflex when laying out any section is to wrap it inside:
+`<div class="bg-white rounded-xl border border-slate-200 p-6 shadow-sm">`
+
+When applied across a full screen, the layout collapses into 5–8 disconnected white boxes floating on a grayish background. To human eyes, this immediately screams "low-effort AI template".
+
+### 7.2 The Structural Rule: Cards vs. Spatial Architecture
+- **Cards are strictly for discrete, interchangeable, dynamic items:** Product catalog grids, kanban task cards, or gallery thumbnails.
+- **Cards are FORBIDDEN as structural section wrappers:** Never wrap an application header, tab bar, left workflow rail, or primary data table in separate, floating rounded boxes!
+
+### 7.3 The Unified Spatial Canvas Invariant
+In professional human-crafted software (Linear, Stripe, Vercel, GitHub):
+1. **Single Cohesive Plane:** The application is housed in a unified spatial sheet or integrated rails, not an archipelago of floating islands.
+2. **Hairline Boundaries:** Spatial separation is established through clean 1px borders (`border-r border-slate-200`, `divide-y divide-slate-100`) and subtle background tonal shifts (`#f8fafc` canvas background $\to$ `#ffffff` primary sheet $\to$ `#fcfcfd` auxiliary rail).
+3. **High Data-to-Padding Ratio:** Tables must not be padded with bloated 24px–32px empty space. Use compact, scannable cell heights ($10\text{px}–14\text{px}$ vertical padding) with tabular monospace figures (`font-mono tabular-nums`).
+
 

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/modes/genre-calibration.md

@@ -0,0 +1,89 @@
+# Domain & Genre Calibration (Anti-Geek Cosplay)
+
+> **Core Invariant:** The real-world problem domain dictates visual posture, NEVER generic AI trends. A school evaluation system must look like an educational instrument; an accounting app must look like a ledger; only actual developer tools should ever look like a terminal.
+
+---
+
+## 1. The 4 Target Genres & Aesthetic Contracts
+
+Before laying out a single component or proposing a visual design, classify the project into one of four real-world genres:
+
+```
+┌────────────────────────────────────────────────────────────────────────┐
+│                       THE 4 REAL-WORLD GENRES                          │
+├────────────────────────────────────────────────────────────────────────┤
+│ 1. Civic, Institutional & Educational (Gov, School, NGO, Compliance)  │
+│ 2. Enterprise & B2B Operational (ERP, CRM, Accounting, Inventory)     │
+│ 3. Commercial SaaS & Conversion (Public Landing, Pricing, Product)    │
+│ 4. Developer Tools & Infrastructure (SDKs, CLIs, Observability, APIs)  │
+└────────────────────────────────────────────────────────────────────────┘
+```
+
+### Genre 1: Civic, Institutional & Educational
+*Examples: SAURAN evaluation, academic portals, scouting/youth accreditation, public services, municipal audit.*
+
+- **Visual Tone:** Dignified, calm, accessible, structured, and trustworthy.
+- **Surface & Palette:** Clean neutral ground (pure white or soft stone background), crisp 1px borders (`border-border`), high-contrast dark foreground text, semantic status pills (e.g. emerald for *Terverifikasi*, amber for *Butuh Revisi*, slate for *Pending*).
+- **Core Components:**
+  - Clear rubric tables with explicit weight/point columns.
+  - Category assessment cards showing actual scores vs targets.
+  - Step progress indicators for verification workflows.
+  - Summary scorecard with clear totals and action buttons.
+- **ABSOLUTE PROHIBITIONS (Second-Order Slop):**
+  - **NO Terminal / CLI Cosplay:** Never put evaluation data inside a faux terminal, command prompt window, or ASCII box.
+  - **NO ASCII Art or Pseudo-Radars:** Never draw ASCII charts (`/\`, `[■■■□□]`, `[2026]`). Use semantic progress bars (`<progress>` or standard div progress) and proper tabular rows.
+  - **NO Dark Cyberpunk Mode:** Never force dark mode or neon glow on institutional workflows.
+  - **NO Jargon Injections:** Never label an assessment tool with pseudo-sci-fi phrases ("telemetry console", "evaluation engine", "neural scanner", "quantum monitor"). Call it what it is: *Ringkasan Evaluasi*, *Rubrik Penilaian*, *Status Verifikasi*.
+
+---
+
+### Genre 2: Enterprise & B2B Operational
+*Examples: Internal operations, HR portals, supply chain management, financial reporting.*
+
+- **Visual Tone:** Compact, data-dense, predictable, and keyboard-efficient.
+- **Surface & Palette:** Neutral surfaces, subtle divider lines, minimal elevation shadows (flat or `shadow-sm`), clear focus rings.
+- **Core Components:**
+  - Data tables with sticky headers, sortable columns, and filter bars.
+  - Master-detail side rails or drawers for drilling into row details.
+  - Monospace only for aligned financial values (`font-mono tabular-nums`).
+- **ABSOLUTE PROHIBITIONS:**
+  - **NO Misplaced Heroes:** Never place giant marketing hero sections, splash banners, or promotional copywriting inside an operational dashboard.
+  - **NO Decorative Metric Clutter:** Every stat card must correspond to an actual query or measurable KPI. Omit generic "Welcome back, User!" filler.
+
+---
+
+### Genre 3: Commercial SaaS & Conversion
+*Examples: Marketing landing pages, product launch pages, pricing tiers.*
+
+- **Visual Tone:** Sharp, decisive, persuasive, authentic conviction.
+- **Surface & Palette:** Generative typographic scale contrast ($Display \ge 3.5\times Body$), tight leading (`leading-[1.05]`), full-bleed background anchor, authentic product screenshots or functional interactive calculators.
+- **ABSOLUTE PROHIBITIONS:**
+  - **NO Cliché Gradients:** Saturated purple-to-indigo or cyan-to-violet linear gradients.
+  - **NO Symmetrical 3-Card Grid:** Identical cards with Lucide icons in pastel rounded squares.
+  - **NO Fabricated Proof:** Fake partner logos or manufactured customer testimonials.
+
+---
+
+### Genre 4: Developer Tools & Infrastructure
+*Examples: CLI tools, API documentation, log viewers, query consoles.*
+
+- **Visual Tone:** High technical precision, compact syntax highlighting, dark/slate neutral grounding or clean technical whiteprint.
+- **Core Components:** Copyable command blocks, real interactive code playgrounds, keyboard shortcut prompts.
+- **ABSOLUTE RULE:** This developer aesthetic is **RESERVED EXCLUSIVELY FOR DEVELOPER PRODUCTS**. Never leak terminal conventions into Genre 1, 2, or 3.
+
+### Specialized Real-World Sub-Domains (Mapped in `craft/themes-catalog.md`)
+When working in Healthcare, Physical Commerce/Hospitality, Editorial/EdTech, or Industrial/Field Logistics, select their dedicated domain pair in `references/craft/themes-catalog.md` (`Pharmacy Calm` / `Clinical Precision`, `Atelier Gallery` / `Kinetic Grid`, `Studio Proof` / `Botanical Field`, `Formwork Concrete` / `Meridian Survey`) rather than flattening them into generic corporate SaaS.
+
+---
+
+## 2. The Purpose-Gate (Zero Unearned Widgets)
+
+Every component, widget, badge, or section must pass the Purpose-Gate:
+
+> **The Purpose-Gate Test:**
+> *"What concrete user decision or task does this element directly enable?"*
+
+1. If the element exists solely to "look high-tech", "fill empty space", or "make the page look interactive" without real underlying data $\to$ **DELETE IT**.
+2. Never invent simulated consoles, fake real-time feeds, or unprompted sliders.
+3. If the user asks for an evaluation summary, provide clear, functional assessment cards and tables—never decorative cosplay.
+

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/modes/operate.md

@@ -51,3 +51,29 @@ Use for: Dashboards, data grids, admin consoles, editors, settings, financial le
 - **Zero Decorative Halos:**
   - Never wrap status dots or cards in glowing radial blurs (`shadow-[0_0_12px_#10b981]`). Keep indicators solid and functional.
 
+---
+
+## 4. Audit & Inspection Finding Rows (Action Affordance Invariant)
+
+- **Interactive Row Contract:**
+  - Finding rows, audit line items, and checklist items must never be rendered as dead, static text blocks.
+  - Every finding row (e.g. `FT-01: Bukti fisik belum dilampirkan`) must provide:
+    1. **Primary Action Affordance:** Explicit inline trigger button (e.g. `Periksa Bukti`, `Minta Rincian`, or expandable chevron).
+    2. **Attachment Badge:** File type badge (`PDF`, `XLSX`), byte size, and upload timestamp.
+    3. **Status Pill:** High-contrast semantic pill (`Perlu Tindak Lanjut`, `Menunggu Konfirmasi`, `Selesai`).
+    4. **Hover State:** `hover:bg-muted/40 transition-colors` across the entire row bounding box.
+
+---
+
+## 5. Dual-Navigation De-Confliction (Lenses vs Lifecycle)
+
+- **Separation of Mental Models:**
+  - **Horizontal Tabs**: View-Port Filter Lenses (switching data views, e.g. *Ringkasan*, *Rubrik Domain*, *Temuan*, *Riwayat*). These change what information is rendered on the stage.
+  - **Vertical Rail**: Immutable Lifecycle Progression (e.g. *1. Unggah Dokumen $\to$ 2. Verifikasi $\to$ 3. Penilaian $\to$ 4. Konfirmasi Fisik $\to$ 5. Rangkuman*). This reflects where the entity is in its operational state.
+- **Accenting Active Lifecycle Step:**
+  - Never let the current active step in the lifecycle rail look identical to future unstarted steps.
+  - Active step: highlighted with high-contrast accent ring or filled circle (`bg-primary text-primary-foreground`) with an active descriptor ("Tahap aktif verifikasi").
+  - Completed steps: clear muted checks (`text-emerald-600` with subtle strike or timestamp).
+  - Pending steps: muted borders (`border-border text-muted-foreground`).
+
+

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/modes/persuade.md

@@ -30,7 +30,7 @@ When building or redesigning a Persuade surface, never let the LLM default to th
 │    offset against an interactive preview, ROI calculator, or live UI. │
 │ 2. The Monolith Ledger: Single-column dense reading measure with       │
 │    full-bleed horizontal rows, hairline dividers, and deep ink.        │
-│ 3. Product-Led Canvas: Live application interface or CLI terminal     │
+│ 3. Product-Led Canvas: Live application interface or workflow canvas   │
 │    dominates the first viewport; copy recedes to tightly frame it.     │
 │ 4. Kinetic Proof Stream: Alternating proof blocks driven by verifiable │
 │    benchmarks, architectural diagrams, and real data payloads.         │
@@ -38,7 +38,7 @@ When building or redesigning a Persuade surface, never let the LLM default to th
 ```
 
 - **Posture Selection Protocol:**
-  - If real software or CLI exists $\to$ **Posture 3 (Product-Led Canvas)**.
+  - If real software interface exists $\to$ **Posture 3 (Product-Led Canvas)**.
   - If quantitative savings or enterprise value proposition $\to$ **Posture 1 (Asymmetric Stage)**.
   - If technical documentation, whitepaper, or architectural manifesto $\to$ **Posture 2 (The Monolith Ledger)**.
   - If performance benchmarks, protocol comparisons, or telemetry proof $\to$ **Posture 4 (Kinetic Proof Stream)**.
@@ -52,7 +52,7 @@ When building or redesigning a Persuade surface, never let the LLM default to th
   - Subtitle: `text-lg text-muted-foreground max-w-xl`
   - Actions: `flex flex-wrap items-center gap-4 pt-2`
 - **Right Artifact (5 cols):** `lg:col-span-5`
-  - Authentic artifact, interactive widget, or live ROI card: `rounded-2xl border border-border/80 bg-card p-6 shadow-sm`
+  - Authentic artifact, interactive widget, or live score/ROI card: `rounded-2xl border border-border/80 bg-card p-6 shadow-sm`
   - Zero equal-weight card grids below.
 
 #### Posture 2: The Monolith Ledger
@@ -67,8 +67,8 @@ When building or redesigning a Persuade surface, never let the LLM default to th
 - **Compact Hero Frame:** `max-w-2xl space-y-4 mb-10`
   - Headline: `text-4xl sm:text-6xl font-extrabold tracking-tight`
   - 1-sentence value claim + 1 primary action.
-- **Hero Canvas (70% Viewport Lead):** `w-full rounded-2xl border border-border/80 bg-slate-950 p-2 shadow-2xl`
-  - Real interface fragment or live demo canvas dominating the first viewport.
+- **Hero Canvas (70% Viewport Lead):** `w-full rounded-2xl border border-border/80 bg-card p-3 shadow-xl`
+  - Real interface fragment or live demo canvas dominating the first viewport. Respect project theme tokens; never force artificial dark backgrounds or terminal frames unless the target product is an actual CLI/developer tool.
 
 ---
 
@@ -80,15 +80,16 @@ When building or redesigning a Persuade surface, never let the LLM default to th
     - *Flagship Feature:* Full-width container or asymmetric 8/4 split showing the primary capability in action.
     - *Supporting Capabilities:* Compact 2-column checklist or a structured comparison table.
 - **The Signature Element:**
-  - Every Persuade surface must feature exactly **one memorable signature element** on the first screen:
-    - An interactive pricing slider that recalculates savings in real time.
-    - A live terminal code editor running the SDK quickstart.
+  - Every Persuade surface may feature at most **one memorable signature element** on the first screen that directly reflects the product domain:
+    - An interactive calculator or estimator that recalculates results in real time.
     - An unedited, high-resolution product screenshot showing real user data.
+    - A live interactive UI fragment (e.g., an assessment scorecard preview for educational tools, a filterable ledger row for accounting tools).
+  - **Hard Ban on Faux-Terminal Cosplay:** Never inject terminal prompts, ASCII art, or pseudo-telemetry consoles into non-developer products.
   - A giant counter of marks or animated numbers is a decorative reflex, not a signature.
 
 ---
 
-## 3. Material Honesty & Proof of Reality
+## 4. Material Honesty & Proof of Reality
 
 - **Zero Fabricated Evidence:**
   - Never invent customer quotes, fake partner logos ("Acme Corp, Pied Piper"), or fabricated performance metrics ("10,000+ teams trust us").

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/redesign-audit.md

@@ -25,15 +25,10 @@ When executing a **Full Redesign** on an existing template or page (`.blade.php`
    - Separate product truth (names, prices, verified claims) from discarded markup.
 2. **Step 2: Isolate / Discard Old Markup**
    - Treat the old layout as an anti-reference. Do not perform incremental class swapping on it.
-3. **Step 3: Author Standalone HTML Prototype & Preview**
-   - Create an ephemeral standalone prototype in the brain directory: `<appDataDir>/brain/<id>/preview.html`.
-   - Select 1 of the 4 Structural Postures (`references/modes/persuade.md` or `operate.md`).
-   - Use Tailwind via CDN and realistic sample data.
-   - Run zero-dependency visual capture:
-     ```bash
-     asc preview <path_to_preview.html>
-     ```
-     Inspect the captured image at `%TEMP%/asc-preview-active.png` (or pass `--open` to view in OS browser). Verify typographic scale ($Display \ge 3.5\times Body$) and full-field grounding.
+3. **Step 3: Author Isolated Prototype / Structural Layout**
+   - When building a complex new surface, draft the isolated DOM layout first using 1 of the 4 Structural Postures (`references/modes/persuade.md` or `operate.md`).
+   - Use design tokens and realistic sample data.
+   - Verify typographic scale ($Display \ge 3.5\times Body$) and full-field spatial grounding before production injection.
 4. **Step 4: Re-inject Data Contracts into Production**
    - Transfer the proven clean geometry into the project file (`welcome.blade.php`, `Page.tsx`).
    - Re-bind the dynamic data loops, Blade/React variables, and event handlers.

package/bin/agentic-senior-core.js

@@ -25,17 +25,20 @@ function printUsage() {
   console.log('Plugin install (always-on, no per-project files):');
   console.log('  Claude Code:  /plugin marketplace add fatidaprilian/Agentic-Senior-Core');
   console.log('  Codex CLI:    codex plugins install agentic-senior-core\n');
-  console.log('Global install (all projects, zero project files):');
-  console.log('  asc global --antigravity --codex --cline --roo --kilocode --kiro --openhands --windsurf --copilot --all\n');
+  console.log('Global install (auto-detects installed tools, zero project files):');
+  console.log('  asc global');
+  console.log('  asc global --all\n');
   console.log('Adapter install (one file per project):');
   console.log('  asc adapter --cursor --devin --cline --copilot --kiro --continue --zed --aider --kilocode --roo --openhands --windsurf --all\n');
   console.log('Commands:');
+  console.log('  global            Auto-detect and install rules to user-level (global) locations');
   console.log('  adapter           Generate instruction-tier adapter files');
-  console.log('  global            Install rules to user-level (global) locations');
+  console.log('  status            Show detected IDEs and install hints');
+  console.log('  dedup             Scan codebase for duplicate code blocks (Rule of Three)');
+  console.log('  bootstrap         List or seed anti-slop preference rules');
   console.log('  install-git-hook  Install Git pre-commit hook for duplicate code enforcement');
   console.log('  uninstall         Remove ASC adapter files and git hooks from this project');
   console.log('  clean             Remove v4 per-project artifacts');
-  console.log('  status            Show detected IDEs and install hints');
   console.log('  preview           Render zero-dependency multi-browser snapshot or preview');
   console.log('  --version         Show version');
   console.log('  --help            Show this help');
@@ -91,6 +94,18 @@ async function main() {
     return;
   }
 
+  if (commandArgument === 'dedup') {
+    const { runDedupCommand } = await import('../lib/cli/commands/dedup.mjs');
+    await runDedupCommand(commandArguments);
+    return;
+  }
+
+  if (commandArgument === 'bootstrap') {
+    const { runBootstrapCommand } = await import('../lib/cli/commands/bootstrap.mjs');
+    await runBootstrapCommand(commandArguments);
+    return;
+  }
+
   if (commandArgument === 'preview') {
     const { runPreviewCommand } = await import('../lib/cli/commands/preview.mjs');
     await runPreviewCommand(commandArguments);

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "agentic-senior-core",
-  "version": "6.16.3",
+  "version": "6.16.5",
   "description": "Universal AI coding rules. Write code like a staff engineer.",
   "author": "fatidaprilian",
   "license": "MIT",
@@ -14,5 +14,5 @@
   "skills": [
     ".agents/plugins/agentic-senior-core/skills/"
   ],
-  "hooks": ".agents/plugins/agentic-senior-core/hooks.json"
+  "hooks": ".agents/plugins/agentic-senior-core/hooks/hooks.json"
 }

package/lib/cli/ascx/runtime.mjs

@@ -10,6 +10,7 @@ import { compressRgOutput } from './adapters/rg.mjs';
 import { buildAscxFooter, shouldWriteSafetyTee } from './formatter.mjs';
 import { classifyAscxInvocation, parseAscxCommand } from './lexer.mjs';
 import { writeRawTeeFile } from './tee-writer.mjs';
+import { prepareSpawnInvocation } from './windows-spawn.mjs';
 
 const ADAPTERS = {
   'git-diff': compressGitDiffOutput,
@@ -21,20 +22,6 @@ const ADAPTERS = {
   'rg': compressRgOutput,
 };
 
-function buildCommandEnvironment(baseEnvironment, parsedCommand) {
-  const commandEnvironment = { ...baseEnvironment };
-
-  for (const assignment of parsedCommand.environment) {
-    const separatorIndex = assignment.indexOf('=');
-    const variableName = assignment.slice(0, separatorIndex);
-    const variableValue = assignment.slice(separatorIndex + 1);
-
-    commandEnvironment[variableName] = variableValue;
-  }
-
-  return commandEnvironment;
-}
-
 function runSpawnedCommand(parsedCommand, options = {}) {
   const {
     cwd = process.cwd(),
@@ -43,19 +30,10 @@ function runSpawnedCommand(parsedCommand, options = {}) {
   } = options;
 
   return new Promise((resolve) => {
-    const useWindowsNpmShell = process.platform === 'win32'
-      && parsedCommand.executable === 'npm'
-      && shell === false;
-    const executable = shell
-      ? parsedCommand.commandText
-      : parsedCommand.executable;
-    const args = shell ? [] : parsedCommand.args;
-    const childProcess = spawn(executable, args, {
-      cwd,
-      env: buildCommandEnvironment(env, parsedCommand),
-      shell: shell || useWindowsNpmShell,
-      windowsHide: true,
-    });
+    const prepared = prepareSpawnInvocation(parsedCommand, { cwd, env, shell });
+    const childProcess = prepared.args === undefined
+      ? spawn(prepared.command, prepared.options)
+      : spawn(prepared.command, prepared.args, prepared.options);
     let stdout = '';
     let stderr = '';