@darkrei08/setup-ai 3.0.3 → 3.0.5

package/README.md

@@ -10,24 +10,24 @@ skill — each via its **official, current** method for your OS.
 
 ## Quick start
 
-One command. No install, no clone. It opens a menu to choose what to set up:
+One command — opens a menu to choose what to set up:
 
 ```bash
-npx github:darkrei08/setup-ai
+npx @darkrei08/setup-ai
 ```
 
-Prefer non-interactive? Same command, add a flag:
+Non-interactive:
 
 ```bash
-npx github:darkrei08/setup-ai --only pi,codex,opencode   # just these
-npx github:darkrei08/setup-ai --all                      # everything
+npx @darkrei08/setup-ai --only pi,codex,opencode   # just these
+npx @darkrei08/setup-ai --all                       # everything
 ```
 
 That's the whole thing. Three details worth knowing:
 
+- **Use the npm package above.** `npx github:darkrei08/setup-ai` also works, but many npm setups block git fetches (`EALLOWGIT`); the published package avoids that. Run it from any folder except the repo's own source dir.
 - **Windows PowerShell**: one command per line (no bash `\`). If node or git was just installed, open a **new terminal** so PATH refreshes.
-- **What it does**: detects your OS and runs `setup-ai.sh` (macOS/Linux) or `setup-ai.ps1` (Windows). Menu keys: ↑/↓ move · Space toggle · `a` all · Enter.
-- **Shorter name**: once it's on npm, drop `github:` → `npx @darkrei08/setup-ai` (run it from any folder except the repo's own source dir).
+- **What it does**: detects your OS and runs `setup-ai.sh` (macOS/Linux) or `setup-ai.ps1` (Windows). `--list` shows modules; menu keys: ↑/↓ move · Space toggle · `a` all · Enter.
 
 ### npm vs npx
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@darkrei08/setup-ai",
-  "version": "3.0.3",
+  "version": "3.0.5",
   "description": "Cross-OS installer for an AI coding toolchain (pi, codex, antigravity, opencode, herdr, gentle-ai, engram, Engineering Excellence) with an interactive module menu.",
   "type": "module",
   "bin": {

package/setup-ai.ps1

@@ -2,7 +2,7 @@
 <#
 ==============================================================================
  AI Dev Suite — Engineering Excellence Edition (Windows)
- Version: 3.0.0
+ Version: 3.0.5
 
  Windows-native installer, sibling of setup-ai.sh. Uses each tool's official
  Windows method: winget for language runtimes, the vendor install.ps1 scripts
@@ -41,7 +41,7 @@ try {
     if (Get-Command chcp -ErrorAction SilentlyContinue) { chcp 65001 | Out-Null }
 } catch { }
 
-$ScriptVersion = "3.0.3"
+$ScriptVersion = "3.0.5"
 $ScriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
 $LogDir = Join-Path $ScriptDir "logs"
 New-Item -ItemType Directory -Force -Path $LogDir | Out-Null
@@ -307,7 +307,9 @@ function Mod-Engram {
         }
     }
     if (-not (Test-Cmd pi)) { Write-Log WARN "engram" "pi_missing" "pi not found; skipped"; return }
-    Invoke-Step -Phase "engram" -Optional -Action { pi install npm:gentle-engram }
+    # `pi-engram init` is the single source of truth (adds pinned gentle-engram +
+    # wires the Engram MCP server). Do NOT also `pi install npm:gentle-engram` —
+    # that adds a second, unversioned entry and duplicates it every run.
     Invoke-Step -Phase "engram" -Optional -Action { pi install npm:pi-mcp-adapter }
     Invoke-Step -Phase "engram" -Optional -Action { npm exec --yes --package gentle-engram@latest -- pi-engram init }
     Write-Log INFO "engram" "enabled" "Engram enabled — RESTART pi, verify: mem_current_project / mem_doctor / 'engram tui'"

package/setup-ai.sh

@@ -2,7 +2,7 @@
 
 # ==============================================================================
 # AI Dev Suite — Engineering Excellence Edition
-# Version: 3.0.0
+# Version: 3.0.5
 #
 # Cross-platform (macOS + all major Linux distros) installer for an AI coding
 # toolchain. Windows is handled by the sibling setup-ai.ps1; the Node launcher
@@ -26,7 +26,7 @@
 set -Eeuo pipefail
 IFS=$'\n\t'
 
-SCRIPT_VERSION="3.0.3"
+SCRIPT_VERSION="3.0.5"
 
 SCRIPT_DIR="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd)"
 LOG_DIR="${SCRIPT_DIR}/logs"
@@ -762,9 +762,11 @@ mod_engram() {
             "engram binary not found after install; the pi extension needs it on PATH" 1
     fi
 
-    # 2. pi integration (in-process extension is the primary path; MCP adapter optional).
+    # 2. pi integration. `pi-engram init` is the single source of truth: it adds
+    #    the pinned gentle-engram to settings.json and wires the Engram MCP server
+    #    in mcp.json. Do NOT also `pi install npm:gentle-engram` — that adds a
+    #    second, unversioned entry and creates a duplicate on every run.
     if command -v pi >/dev/null 2>&1; then
-        run_optional "engram" pi install npm:gentle-engram
         run_optional "engram" pi install npm:pi-mcp-adapter
         run_optional "engram" npm exec --yes --package gentle-engram@latest -- pi-engram init
         log_event "INFO" "engram" "enabled" \