jorgex-stack 1.9.59 → 1.9.61

package/README.md

@@ -116,7 +116,7 @@ Programmatic mode does **not** provide:
 
 El canon de Stack y el paquete Pi adoptado mantienen una snapshot de 17 árboles de skills con 89 archivos de skill. La identidad, procedencia e integridad del paquete adoptado son autoritativas en `src/lib/pi-runtime-pin.json`.
 
-Pi combines the frozen **snapshot v2** package with a Stack-owned shared projection. The version references that follow describe historical Stack/Pi transitions, not the current pin. The current pin is the published `jorgex-pi@0.8.23` artifact. Package integrity and lifecycle are maintained in [docs/references/pi-runtime.md](docs/references/pi-runtime.md) and `src/lib/pi-runtime-pin.json`; this README does not imply a future Stack release.
+Pi combines the frozen **snapshot v2** package with a Stack-owned shared projection. The current pin is the published `jorgex-pi@0.8.28` artifact. Package identity, integrity and lifecycle are maintained in [docs/references/pi-runtime.md](docs/references/pi-runtime.md) and `src/lib/pi-runtime-pin.json`; this README does not duplicate mutable pin metadata.
 
 The following command block is retained as historical reference for that transition:
 
@@ -128,13 +128,13 @@ pnpm dlx jorgex-stack@1.9.7 sync --agents pi
 pnpm dlx jorgex-stack@1.9.7 uninstall --agents pi
 ```
 
-For the current Pi `0.8.23` pin, package identity and runner validation precede projection; the exact pending initialization diagnostic remains provisional until projection and final `sync` complete.
+For the current Pi `0.8.28` pin, package identity and runner validation precede projection; the exact pending initialization diagnostic remains provisional until projection and final `sync` complete.
 
-Stack downloads the frozen registry tarball, verifies its exact size plus SHA-256/SHA-512, backs up Pi's `settings.json`, and only then asks Pi to install that local file. The exact artifact and integrity values are authoritative in `src/lib/pi-runtime-pin.json`, while the lifecycle remains authoritative in `src/lib/pi-runtime.ts`. Pi's own package-manager invocation is the narrow runtime exception to the repository's pnpm-only rule; the Stack lifecycle never launches npm directly. A managed install then runs `package install → projection install → package sync`: after the package identity and runner are validated, Stack projects the shared resources into Pi and invokes Pi's native sync to complete initialization. The projection includes marked `jorgex:system-prompt` and `jorgex:engram-protocol` sections in `~/.pi/agent/AGENTS.md`, canonical skills under `~/.agents/skills`, and `~/.pi/agent/prompts/lean-audit.md`. Pi 0.8.23 registers Context7 through an isolated in-memory HTTP bridge during bootstrap; `available` means configuration permits registration and does not imply an HTTP handshake. A conflict preserves the existing MCP file and blocks managed activation. No MCP configuration or credentials are written. For the file runtimes, Context7, Playwright and DevTools use independent managed sections. The global Playwright package and Chromium cache are shared by the machine; `--playwright-runtimes` controls which runtime receives the guide. The adopted Pi package implements and tests `playwright-handoff-v1` through `PI_CODING_AGENT_DIR/jorgex-pi/playwright.v1.json`. Historical package entries do not describe the current pin. Filters are applied only after this projection exists, so the package does not duplicate shared resources. Package ownership is recorded separately in `~/.jorgex-stack/pi-receipt.json`; projection ownership is recorded in `~/.jorgex-stack/pi-projection-receipt.json`. Package receipts reject manual, duplicate, divergent, partial, corrupt, copied-to-another-scope, or unknown-history state. Projection cleanup requires an exact scope-bound ownership receipt; DevTools conflicts preserve the handoff for review.
+Stack runs provider-owned `engram setup pi` before Pi package activation on a real managed install. It backs up and verifies Pi's `settings.json`, `mcp.json` and provider-owned `npm` tree, and restores the backup on setup failure; Pi is not activated unless setup and subsequent package lifecycle succeed. The exact artifact and integrity values are authoritative in `src/lib/pi-runtime-pin.json`, while the lifecycle remains authoritative in `src/lib/pi-runtime.ts`. Pi's own package-manager invocation is the narrow runtime exception to the repository's pnpm-only rule; the Stack lifecycle never launches npm directly. A managed install then runs provider setup, `package install → projection install → package sync`. Stack projects shared resources such as the system prompt, canonical skills and `lean-audit`; it does not inject `jorgex:engram-protocol`, project Engram tools, or filter provider tools. The behavioral `engram` role remains part of the Pi contract, while the official provider owns its setup and tools. Pi registers Context7 through an isolated in-memory HTTP bridge during bootstrap; `available` means configuration permits registration and does not imply an HTTP handshake. A conflict preserves the existing MCP file and blocks managed activation. No MCP credentials are written. For the file runtimes, Context7, Playwright and DevTools use independent managed sections. The global Playwright package and Chromium cache are shared by the machine; `--playwright-runtimes` controls which runtime receives the guide. The adopted Pi package implements and tests `playwright-handoff-v1` through `PI_CODING_AGENT_DIR/jorgex-pi/playwright.v1.json`. Package ownership is recorded separately in `~/.jorgex-stack/pi-receipt.json`; projection ownership is recorded in `~/.jorgex-stack/pi-projection-receipt.json`. Package receipts reject manual, duplicate, divergent, partial, corrupt, copied-to-another-scope, or unknown-history state. Projection cleanup requires an exact scope-bound ownership receipt; DevTools conflicts preserve the handoff for review.
 
 The static `AGENTS.md` projected by Stack does not include Context7; Pi's native bootstrap adds that section after registering the isolated bridge. Pi never writes, owns or removes MCP files. In Claude Code, Codex and OpenCode, a compatible existing Context7 entry is preserved and removed only with explicit canonical Stack ownership. During package installation only, `initialization-diagnostics-v1` permits the exact pending `doctor` envelope described in [the Pi runtime reference](docs/references/pi-runtime.md); it is provisional and does not make Pi healthy. Projection and final `sync` must still complete, and every other unhealthy or malformed result remains blocked.
 
-Pi 0.8.23 also seeds `theme=JorgeX`, `quietStartup=true`, and `hideThinkingBlock=true` only for missing fields during first initialization. User changes and deletions are preserved without reseeding. `hideThinkingBlock` changes presentation only; `defaultThinkingLevel` and reasoning remain unchanged. Pi owns only the fields it creates and records in its lifecycle receipt; pre-existing user settings remain unowned. The JorgeX header preserves builtin and custom commands. `Ctrl+O` remains Pi's native tool presentation, with `NO_COLOR` and `JORGEX_PI_MOTION` behavior unchanged; Stack adds no renderer.
+Pi 0.8.28 also seeds `theme=JorgeX`, `quietStartup=true`, and `hideThinkingBlock=true` only for missing fields during first initialization. User changes and deletions are preserved without reseeding. `hideThinkingBlock` changes presentation only; `defaultThinkingLevel` and reasoning remain unchanged. Pi owns only the fields it creates and records in its lifecycle receipt; pre-existing user settings remain unowned. The JorgeX header preserves builtin and custom commands. `Ctrl+O` remains Pi's native tool presentation, with `NO_COLOR` and `JORGEX_PI_MOTION` behavior unchanged; Stack adds no renderer.
 
 Historically, the published Pi 0.8.0 direct-package snapshot added `work-audit`: the snapshot grew from **17 to 18 skill trees** (96 to 97 files), and the active runtime allowlist grew from **16 to 17 skills**. The historical Pi 0.8.5 snapshot reference records 18 skill trees and 98 files; it does not describe the adopted pin. Reference F2-A is included while the private F1 skills remain preserved. `playwright-cli` remains in the snapshot but inactive because browser automation is a separate opt-in integration.
 
@@ -152,11 +152,11 @@ Claude's official plugin still requires stable Engram 2.0.0 or newer: an existin
 
 ### Integración oficial de Engram
 
-En una instalación real, `install` delega Claude Code, Codex y OpenCode 1.x a `engram setup <runtime>` una vez por runtime durante esa instalación. No ejecuta ese setup durante `sync`, `dry-run`, `--target-dir`, `doctor` ni `uninstall`. Stack respalda los archivos afectados, verifica los artefactos oficiales y revierte el cambio si falla; no modifica `~/.engram`, sus memorias ni reemplaza un binario existente. Los artefactos oficiales se conservan al desinstalar. El `stack/plugins/opencode/engram.ts` legado ya no se despliega y queda retirado por esta integración.
+En una instalación real, `install` delega Claude Code, Codex y OpenCode 1.x a `engram setup <runtime>` una vez por runtime durante esa instalación, y Pi ejecuta `engram setup pi` antes de activar el paquete. El comportamiento del provider oficial permanece sin cambios: Stack no proyecta el protocolo Engram ni filtra sus herramientas. No ejecuta ese setup durante `sync`, `dry-run`, `--target-dir`, `doctor` ni `uninstall`. Stack respalda los archivos afectados, verifica los artefactos oficiales y revierte el cambio si falla; para Pi incluye `settings.json`, `mcp.json` y el árbol `npm`. No modifica `~/.engram`, sus memorias ni reemplaza un binario existente. Los artefactos oficiales se conservan al desinstalar. El `stack/plugins/opencode/engram.ts` legado ya no se despliega y queda retirado por esta integración.
 
 Para Codex, Engram 2.0 ignora `CODEX_HOME` y escribe siempre en `$HOME/.codex`; por eso el setup oficial real requiere ese destino predeterminado. Si `CODEX_HOME` apunta a otro directorio, `install` falla cerrado en el preflight, antes de escribir la configuración de Codex, y recomienda usar `$HOME/.codex`. `sync`, `dry-run` y `--target-dir` no invocan el setup oficial.
 
-La política de complementos distingue estrategias `exact` y `provider-managed`. DevTools MCP y Playwright CLI mantienen pins exactos; las integraciones oficiales de Engram son `provider-managed`/rolling, incluido Codex `main` y `pi-mcp-adapter` sin pin. OpenCode 2 queda fuera de alcance y no bloquea esta integración. La migración de Pi PR04 y `gentle-engram` sigue siendo trabajo futuro; no forma parte de esta entrega.
+La política de complementos distingue estrategias `exact` y `provider-managed`. DevTools MCP y Playwright CLI mantienen pins exactos; las integraciones oficiales de Engram son `provider-managed`/rolling, incluido Codex `main`, `pi-mcp-adapter` y el setup oficial de Pi sin pin en Stack. OpenCode 2 queda fuera de alcance y no bloquea esta integración.
 
 Históricamente, Stack `1.9.7` reconocía el receipt exacto de Pi `npm:jorgex-pi@0.8.4`. Usa versiones exactas, nunca `latest`, y no edites receipts o hashes ni borres `HOME`, Engram o la proyección de otro runtime para forzar confianza. El pin y los comandos actuales de transición y rollback están en [docs/references/pi-runtime.md](docs/references/pi-runtime.md).
 
@@ -206,7 +206,7 @@ Daily operation:
 - `doctor` reports the Playwright CLI state (`disabled`, `healthy`, `missing:package`, `missing:browser`, `unreadable`, `broken`, `outdated`) and, when the opt-in package and browser cache are present, verifies one local headless Chromium launch against `about:blank`; it does not open external sites or repair state. An `unreadable` browser cache includes its exact path and filesystem error code so permissions or another local cause can be investigated. If either preference file is corrupt, doctor prints the exact path and the remedy (`Corrige o borra ese archivo antes de reintentar`) before any other browser check; in that case `install`/`uninstall`/`update`/`update --check` will abort with exit 1 until the file is fixed, so the corruption cannot be reconciled destructively.
 - `update --check` only inspects Playwright CLI when its preference is `enabled` (a binary appearing in `PATH` is not consent). It compares the installed version against the approved pin `0.1.18` — it does not consult npm latest, and a Playwright CLI binary-only update does not require `sync` afterwards.
 - `uninstall` preserves the global `@playwright/cli` package and all browser data by default; `--remove-playwright` removes the package only (never the browser cache, profiles, cookies, storage state, traces, screenshots or videos). If `pnpm remove --global @playwright/cli` exits non-zero, `uninstall` reports the failure instead of a success outro. For DevTools MCP, ownership is released only after the corresponding unmerge is applied; if no unmerge action is written, the ownership marker is preserved for a later retry.
-- `install`/`sync` also inject (and `disable`/`uninstall` remove) managed capability sections in `AGENTS.md` (OpenCode, Codex) or `CLAUDE.md` (Claude Code). File runtimes keep `jorgex:playwright`, `jorgex:chrome-devtools` and `jorgex:context7` independent; Pi 0.8.22 projects the Context7 section after registering its isolated HTTP bridge and keeps the legacy `jorgex:browser` format for migration. User content outside managed markers is preserved. `--target-dir` never reads the real preferences, so by default no section is emitted in target-dir runs — but explicit flags like `--devtools` simulate the MCP entry (and its DevTools block) inside the temp target without touching the real global state, and `install --dry-run --playwright` projects the Playwright section into the plan preview without installing anything. If reconciliation detects a partial or ambiguous system-prompt state, the CLI exits non-zero and recommends repairing it with `sync` or a repeated install; no write is attempted before marker validation. See [docs/references/browser-automation.md](docs/references/browser-automation.md) §2.7 for the full lifecycle.
+- `install`/`sync` also inject (and `disable`/`uninstall` remove) managed capability sections in `AGENTS.md` (OpenCode, Codex) or `CLAUDE.md` (Claude Code). File runtimes keep `jorgex:playwright`, `jorgex:chrome-devtools` and `jorgex:context7` independent; Pi 0.8.28 projects Context7 after registering its isolated HTTP bridge. Stack does not add an Engram protocol section or filter provider tools. User content outside managed markers is preserved. `--target-dir` never reads the real preferences, so by default no section is emitted in target-dir runs — but explicit flags like `--devtools` simulate the MCP entry (and its DevTools block) inside the temp target without touching the real global state, and `install --dry-run --playwright` projects the Playwright section into the plan preview without installing anything. If reconciliation detects a partial or ambiguous system-prompt state, the CLI exits non-zero and recommends repairing it with `sync` or a repeated install; no write is attempted before marker validation. See [docs/references/browser-automation.md](docs/references/browser-automation.md) §2.7 for the full lifecycle.
 
 ### Update: Interactive Flow
 

package/dist/chunk-2CBCBOP7.js

@@ -0,0 +1,245 @@
+#!/usr/bin/env node
+import {
+  registerOfficialSetupVerifier
+} from "./chunk-B76ZJXXD.js";
+import {
+  HOME,
+  samePath
+} from "./chunk-NQZVJFV2.js";
+
+// src/adapters/pi.ts
+import fs from "fs";
+import path from "path";
+function piSystemPromptFile(targetDir) {
+  const configDir = targetDir === void 0 ? process.env.PI_CODING_AGENT_DIR ?? path.join(HOME, ".pi", "agent") : path.join(path.resolve(targetDir), "pi-agent");
+  return path.join(configDir, "AGENTS.md");
+}
+var piAdapter = {
+  id: "pi",
+  paths(configDir) {
+    const piConfigDir = path.dirname(piSystemPromptFile());
+    const agentsHome = samePath(configDir, piConfigDir) ? HOME : path.join(path.dirname(configDir), "home");
+    return {
+      systemPromptFile: path.join(configDir, "AGENTS.md"),
+      agentsDir: path.join(configDir, "agents"),
+      skillsDir: path.join(agentsHome, ".agents", "skills"),
+      commandsDir: path.join(configDir, "prompts"),
+      pluginsDir: null,
+      scriptsDir: path.join(configDir, "scripts"),
+      outputStylesDir: null,
+      profilesDir: null
+    };
+  },
+  renderCommand(file, content) {
+    return { file, content: content.replace(/\{\{input\}\}/g, "$ARGUMENTS") };
+  },
+  // La guía Context7 se habilita al adoptar su registro HTTP en Pi.
+  adaptSystemPromptSections(sections) {
+    const modular = { ...sections };
+    delete modular.context7;
+    return modular;
+  }
+};
+function isRecord(value) {
+  return value !== null && typeof value === "object" && !Array.isArray(value);
+}
+function piPackageSource(entry) {
+  if (typeof entry === "string") return entry;
+  if (!isRecord(entry)) return null;
+  const source = entry["source"];
+  return typeof source === "string" ? source : null;
+}
+function isSafePiVersionSpec(spec) {
+  if (spec === "" || /[\r\n]/.test(spec)) return false;
+  if (spec.includes("/") || spec.includes("\\") || spec.includes(":") || spec.includes("#") || spec.includes("?")) {
+    return false;
+  }
+  if (spec.startsWith(".")) return false;
+  const lower = spec.toLowerCase();
+  if (lower.endsWith(".tar.gz") || lower.endsWith(".tgz") || lower.endsWith(".tar")) return false;
+  return /^[A-Za-z0-9._\-^~><=| +*xXv]+$/.test(spec);
+}
+function claimsProtectedName(source, name) {
+  return source === `npm:${name}` || source.startsWith(`npm:${name}@`);
+}
+function isNamedPiSource(source, name) {
+  if (source === `npm:${name}`) return true;
+  const prefix = `npm:${name}@`;
+  if (!source.startsWith(prefix)) return false;
+  return isSafePiVersionSpec(source.slice(prefix.length));
+}
+function isGentleSource(source) {
+  return isNamedPiSource(source, "gentle-engram");
+}
+function isAdapterSource(source) {
+  return isNamedPiSource(source, "pi-mcp-adapter");
+}
+function isExactPiEngramMcp(value, engramBin) {
+  if (!isRecord(value)) return false;
+  if (typeof engramBin !== "string" || engramBin === "" || !path.isAbsolute(engramBin)) return false;
+  const keys = Object.keys(value).sort();
+  if (keys.length !== 4 || keys[0] !== "args" || keys[1] !== "command" || keys[2] !== "directTools" || keys[3] !== "lifecycle") {
+    return false;
+  }
+  if (value["command"] !== engramBin) return false;
+  if (value["lifecycle"] !== "lazy") return false;
+  if (value["directTools"] !== false) return false;
+  const args = value["args"];
+  if (!Array.isArray(args) || args.length !== 2 || args[0] !== "mcp" || args[1] !== "--tools=agent") {
+    return false;
+  }
+  return true;
+}
+function errnoCode(error) {
+  return error instanceof Error && "code" in error && typeof error.code === "string" ? error.code : "UNKNOWN";
+}
+async function verifyOfficialSetup(args) {
+  void args.homeDir;
+  const passed = [];
+  const missing = [];
+  let duplicates = false;
+  let packagesDetail = null;
+  try {
+    const raw = fs.readFileSync(path.join(args.configDir, "settings.json"), "utf8");
+    let parsed;
+    try {
+      parsed = JSON.parse(raw);
+    } catch {
+      packagesDetail = "packages:invalid";
+      missing.push(packagesDetail);
+      packagesDetail = "singleton inv\xE1lido en settings.json (JSON no parseable)";
+      throw new Error("__invalid__");
+    }
+    if (!isRecord(parsed) || !Array.isArray(parsed["packages"])) {
+      missing.push("packages:missing");
+      packagesDetail = "singleton incompleto en settings.json (falta packages[])";
+    } else {
+      const sources = parsed["packages"].map(piPackageSource);
+      const unsafeClaimed = sources.filter(
+        (source) => source !== null && (claimsProtectedName(source, "gentle-engram") && !isGentleSource(source) || claimsProtectedName(source, "pi-mcp-adapter") && !isAdapterSource(source))
+      );
+      if (unsafeClaimed.length > 0) {
+        missing.push("packages:invalid");
+        packagesDetail = `singleton inv\xE1lido en settings.json (selector inseguro que reclama nombre protegido: ${unsafeClaimed[0]})`;
+      } else {
+        const gentle = sources.filter((source) => source !== null && isGentleSource(source));
+        const adapter = sources.filter((source) => source !== null && isAdapterSource(source));
+        if (gentle.length === 1 && adapter.length === 1) {
+          passed.push("packages");
+          packagesDetail = null;
+        } else {
+          duplicates = gentle.length > 1 || adapter.length > 1;
+          if (duplicates) missing.push("packages:duplicate");
+          else if (gentle.length === 0 || adapter.length === 0) {
+            const absent = [
+              ...gentle.length === 0 ? ["gentle-engram"] : [],
+              ...adapter.length === 0 ? ["pi-mcp-adapter"] : []
+            ].join(" + ");
+            missing.push("packages:missing");
+            void absent;
+          } else {
+            missing.push("packages:missing");
+          }
+          const detail2 = duplicates ? `singleton duplicado en settings.json (gentle-engram x${gentle.length}, pi-mcp-adapter x${adapter.length})` : `singleton incompleto en settings.json (falta ${gentle.length === 0 ? "gentle-engram" : "pi-mcp-adapter"})`;
+          packagesDetail = detail2;
+        }
+      }
+    }
+  } catch (error) {
+    if (error instanceof Error && error.message === "__invalid__") {
+    } else {
+      const code = errnoCode(error);
+      if (code === "ENOENT") {
+        missing.push("packages:missing");
+        packagesDetail = "singleton incompleto en settings.json (ausente)";
+      } else {
+        missing.push("packages:unreadable");
+        packagesDetail = `singleton ilegible en settings.json (unreadable ${code})`;
+      }
+    }
+  }
+  let mcpDetail = null;
+  if (typeof args.engramBin !== "string" || args.engramBin === "") {
+    missing.push("mcp:missing");
+    mcpDetail = "mcp inv\xE1lido en mcp.json (sin engramBin absoluto)";
+  } else {
+    try {
+      const raw = fs.readFileSync(path.join(args.configDir, "mcp.json"), "utf8");
+      let parsed;
+      try {
+        parsed = JSON.parse(raw);
+      } catch {
+        missing.push("mcp:invalid");
+        mcpDetail = "mcp inv\xE1lido en mcp.json (JSON no parseable)";
+        parsed = null;
+        throw new Error("__invalid_mcp__");
+      }
+      if (!isRecord(parsed)) {
+        missing.push("mcp:invalid");
+        mcpDetail = "mcp inv\xE1lido en mcp.json (ra\xEDz no objeto)";
+      } else {
+        const servers = parsed["mcpServers"];
+        if (!isRecord(servers) || servers["engram"] === void 0) {
+          const alt = isRecord(parsed["servers"]) ? parsed["servers"]["engram"] : void 0;
+          if (alt === void 0) {
+            missing.push("mcp:missing");
+            mcpDetail = "mcp ausente en mcp.json (falta mcpServers.engram)";
+          } else if (isExactPiEngramMcp(alt, args.engramBin)) {
+            passed.push("mcp");
+            mcpDetail = null;
+          } else {
+            missing.push("mcp:invalid");
+            mcpDetail = `mcp inv\xE1lido en mcp.json (se exige forma directa can\xF3nica: command === engramBin absoluto, args === ["mcp","--tools=agent"], lifecycle === "lazy", directTools === false)`;
+          }
+        } else if (isExactPiEngramMcp(servers["engram"], args.engramBin)) {
+          const legacy = isRecord(parsed["servers"]) ? parsed["servers"]["engram"] : void 0;
+          if (legacy !== void 0) {
+            missing.push("mcp:conflict");
+            mcpDetail = "mcp en conflicto en mcp.json (servers.engram legacy coexiste con mcpServers.engram can\xF3nico; conflicto fail-closed sin activar Pi)";
+          } else {
+            passed.push("mcp");
+            mcpDetail = null;
+          }
+        } else {
+          const foreign = isRecord(servers["engram"]) && typeof servers["engram"]["command"] === "string" && servers["engram"]["command"] !== args.engramBin && !String(servers["engram"]["command"]).includes("node") && !JSON.stringify(servers["engram"]).includes(args.engramBin);
+          missing.push(foreign ? "mcp:conflict" : "mcp:invalid");
+          mcpDetail = foreign ? `mcp en conflicto en mcp.json (no apunta al binario oficial ${args.engramBin}); se preserva sin reescribir` : `mcp inv\xE1lido en mcp.json (se exige forma directa can\xF3nica: command === engramBin absoluto, args === ["mcp","--tools=agent"], lifecycle === "lazy", directTools === false)`;
+        }
+      }
+    } catch (error) {
+      if (error instanceof Error && error.message === "__invalid_mcp__") {
+      } else {
+        const code = errnoCode(error);
+        if (code === "ENOENT") {
+          if (mcpDetail === null && !missing.some((entry) => entry.startsWith("mcp:"))) {
+            missing.push("mcp:missing");
+            mcpDetail = "mcp ausente en mcp.json (falta mcpServers.engram)";
+          }
+        } else {
+          missing.push("mcp:unreadable");
+          mcpDetail = `mcp ilegible en mcp.json (unreadable ${code}, parcial sin activar Pi)`;
+        }
+      }
+    }
+  }
+  if (missing.length === 0) {
+    return { ok: true, layers: passed, duplicates: false };
+  }
+  const detail = `Pi: setup oficial Engram incompleto (${[
+    ...packagesDetail !== null ? [packagesDetail] : [],
+    ...mcpDetail !== null ? [mcpDetail] : []
+  ].join("; ")}; falta: ${missing.join(", ")}).`;
+  return {
+    ok: false,
+    layers: [...passed, ...missing],
+    duplicates,
+    reason: detail
+  };
+}
+registerOfficialSetupVerifier("pi", verifyOfficialSetup);
+
+export {
+  piSystemPromptFile,
+  piAdapter,
+  verifyOfficialSetup
+};

package/dist/{chunk-NNPFC6QV.js → chunk-4USZMJ3I.js}

@@ -5,14 +5,16 @@ import {
   hasManagedMarkdownSection,
   isCanonicalMcpServerEnabled,
   loadCanonicalDefaults,
-  readTextIfExists,
-  registerOfficialSetupVerifier,
   removeNativeHooks,
   removeSystemPromptSections,
   resolveAgentModel,
   upsertJson,
   upsertNativeHooks
-} from "./chunk-KB5IQEKL.js";
+} from "./chunk-66WVKOU4.js";
+import {
+  readTextIfExists,
+  registerOfficialSetupVerifier
+} from "./chunk-B76ZJXXD.js";
 import {
   stackRoot
 } from "./chunk-NQZVJFV2.js";
@@ -24,13 +26,6 @@ import { isDeepStrictEqual } from "util";
 function yamlString(value) {
   return JSON.stringify(value);
 }
-var memoryTools = (names) => names.flatMap((n) => [`mcp__engram__${n}`, `mcp__plugin_engram_engram__${n}`]);
-var MEMORY_TOOLS = memoryTools(["mem_save", "mem_search", "mem_context"]);
-var ENGRAM_AGENT_TOOLS = [
-  "Read",
-  "Skill",
-  ...memoryTools(["mem_context", "mem_search", "mem_get_observation", "mem_timeline", "mem_current_project"])
-];
 function isRecord(value) {
   return value !== null && typeof value === "object" && !Array.isArray(value);
 }
@@ -88,11 +83,10 @@ function hasClaudeManualApproval(configDir) {
   }
 }
 function toolsFor(agent) {
-  if (agent.name === "engram") return ENGRAM_AGENT_TOOLS.join(", ");
+  if (agent.name === "engram") return null;
   if (!agent.readonly) return null;
   const tools = ["Read", "Grep", "Glob", "Skill"];
   if (agent.bash !== "none") tools.push("Bash");
-  tools.push(...MEMORY_TOOLS);
   return tools.join(", ");
 }
 function hasEngramPlugin(configDir) {
@@ -136,9 +130,6 @@ var claudeCodeAdapter = {
       }] : []
     ]);
   },
-  injectEngramProtocol(ctx) {
-    return !hasEngramPlugin(ctx.configDir);
-  },
   paths(configDir) {
     return {
       systemPromptFile: path.join(configDir, "CLAUDE.md"),