mcp-efficiency-engine 0.1.6 → 0.1.7

package/FINAL_USAGE_GUIDE.md

@@ -95,6 +95,14 @@ npm install mcp-efficiency-engine
 
 Si el entorno bloquea scripts de npm (`allow-scripts`), ejecutar manualmente:
 
+```powershell
+npm install mcp-efficiency-engine
+npm approve-scripts mcp-efficiency-engine
+npm rebuild mcp-efficiency-engine
+```
+
+Alternativa manual equivalente:
+
 ```powershell
 npx mcp-efficiency-engine install
 npx mcp-efficiency-engine validate -PortableMode

package/README.md

@@ -190,13 +190,21 @@ Comportamiento esperado:
 
 - copia al proyecto host los artefactos canonicos del engine (`scripts`, `.github`, `.vscode`, `repo-intake`, `orchestrator`, `policies`, `observability`, `autodocs/schema`, `memory`, etc.)
 - instala motores y herramientas via bootstrap portable
-- si no existe `repo-registry/repos.yml`, pregunta por owner/prefix y si quieres registrar un repo inicial para intake
-- si no añades repos en ese momento, deja el registry plantilla listo para añadirlos despues y rerun de intake
+- si no existe `repo-registry/repos.yml`, en modo interactivo pregunta por owner/prefix y repo inicial para intake
+- si la instalacion corre en modo no interactivo (comun en lifecycle scripts de npm), crea automaticamente un repo inicial por defecto: dominio `dev`, location `.`
 
 Nota npm (entornos con politicas de scripts):
 
-- si `npm` bloquea `install`/`postinstall` (por ejemplo con `allow-scripts`), el scaffold/bootstrapping puede no ejecutarse automaticamente
-- en ese caso, aprueba scripts (`npm approve-scripts`) o ejecuta manualmente:
+- si `npm` bloquea `install`/`postinstall` (por ejemplo con `allow-scripts`), el scaffold/bootstrapping no se ejecuta automaticamente
+- flujo recomendado en dos pasos:
+
+```powershell
+npm install mcp-efficiency-engine
+npm approve-scripts mcp-efficiency-engine
+npm rebuild mcp-efficiency-engine
+```
+
+- alternativa manual equivalente:
 
 ```powershell
 npx mcp-efficiency-engine install
@@ -217,6 +225,33 @@ npm install -g mcp-efficiency-engine
 mcpee install
 ```
 
+### Cuando se conectan boosts/repos auxiliares
+
+Resumen rapido:
+
+- `npm install` + `rebuild` instala/configura el engine.
+- La conexion real de boosts/repos ocurre al ejecutar intake.
+- Si no configuras repos adicionales, se usa el repo inicial por defecto.
+
+Pasos recomendados despues de instalar:
+
+```powershell
+# 1) (Opcional) editar repos auxiliares/boosts
+notepad .\repo-registry\repos.yml
+
+# 2) materializar capacidades de todos los repos del registry
+.\scripts\intake\run-repo-intake.cmd
+
+# 3) validar que el router ya los ve
+.\scripts\ops\hi.ps1
+```
+
+Si quieres que te pregunte por owner/prefix/repo inicial en modo asistido, ejecuta:
+
+```powershell
+npx mcp-efficiency-engine install
+```
+
 ### 2) Validación mínima
 
 ```powershell

package/bin/install-host.js

@@ -238,6 +238,15 @@ function deriveRepoPrefix(targetRoot, options) {
   return `${path.basename(targetRoot).replace(/[^a-zA-Z0-9_-]/g, "-").toLowerCase()}_`;
 }
 
+function deriveDefaultRepoName(targetRoot, options) {
+  if (options.initialRepoName) {
+    return options.initialRepoName;
+  }
+
+  const safeBaseName = path.basename(targetRoot).replace(/[^a-zA-Z0-9_-]/g, "-").toLowerCase();
+  return `${deriveRepoPrefix(targetRoot, options)}${safeBaseName}`;
+}
+
 function initializeTemplateRegistry(targetRoot, options) {
   const registryPath = path.join(targetRoot, "repo-registry", "repos.yml");
   if (fs.existsSync(registryPath)) {
@@ -245,14 +254,28 @@ function initializeTemplateRegistry(targetRoot, options) {
   }
 
   const initScript = path.join(targetRoot, "scripts", "intake", "init-template-registry.ps1");
+  const resolvedPrefix = deriveRepoPrefix(targetRoot, options);
   const args = [
     "-Owner",
     options.owner || "your-team",
     "-RepoNamePrefix",
-    deriveRepoPrefix(targetRoot, options),
-    "-SkipInitialRepo",
+    resolvedPrefix,
   ];
 
+  if (options.skipInitialRepo) {
+    args.push("-SkipInitialRepo");
+  }
+  else {
+    args.push(
+      "-InitialRepoName",
+      deriveDefaultRepoName(targetRoot, options),
+      "-InitialRepoDomain",
+      options.initialRepoDomain || "dev",
+      "-InitialRepoLocation",
+      options.initialRepoLocation || ".",
+    );
+  }
+
   return runPowerShell(initScript, args, targetRoot);
 }
 
@@ -314,7 +337,8 @@ function runHostInstall(rawOptions) {
       return hookStatus;
     }
 
-    process.stdout.write("[mcpee] Modo no interactivo detectado. Se inicializo el registry plantilla y se omitio bootstrap interactivo.\n");
+    process.stdout.write("[mcpee] Modo no interactivo detectado. Se inicializo repos.yml con un repo inicial por defecto y se omitio bootstrap interactivo.\n");
+    process.stdout.write("[mcpee] Si npm bloqueo scripts, ejecuta: npm approve-scripts mcp-efficiency-engine ; npm rebuild mcp-efficiency-engine\n");
     return 0;
   }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-efficiency-engine",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "description": "Motor de orquestacion para agentes MCP con routing por dominio y bootstrap portable.",
   "license": "MIT",
   "type": "commonjs",

package/scripts/setup/setup-prerequisites.ps1

@@ -143,6 +143,27 @@ function Ensure-PythonModuleInstalled {
     }
 }
 
+function Sync-GraphifyArtifactsFromScripts {
+    $scriptsGraphPath = 'scripts/graphify-out/graph.json'
+    $contextGraphDir = 'context/graphify-out'
+    $contextGraphPath = Join-Path $contextGraphDir 'graph.json'
+
+    if (-not (Test-Path $scriptsGraphPath)) {
+        return $false
+    }
+
+    New-Item -ItemType Directory -Path $contextGraphDir -Force | Out-Null
+    Copy-Item -Path $scriptsGraphPath -Destination $contextGraphPath -Force
+
+    $scriptsManifestPath = 'scripts/graphify-out/manifest.json'
+    $contextManifestPath = Join-Path $contextGraphDir 'manifest.json'
+    if (Test-Path $scriptsManifestPath) {
+        Copy-Item -Path $scriptsManifestPath -Destination $contextManifestPath -Force
+    }
+
+    return $true
+}
+
 Write-Host '== MCP platform prerequisites setup =='
 
 $toolingManifest = Get-ToolingManifest -Path $toolingManifestPath
@@ -212,8 +233,15 @@ if (-not $SkipGraphify) {
     }
 
     if (-not (Test-Path 'context/graphify-out/graph.json')) {
-        Write-Host '[setup] graphify extract scripts --no-cluster --out context'
-        & $pyCmd @pyArgs -m graphify extract scripts --no-cluster --out context
+        Write-Host '[setup] graphify update scripts --no-cluster'
+        & $pyCmd @pyArgs -m graphify update scripts --no-cluster
+        if ($LASTEXITCODE -ne 0) {
+            throw "graphify update failed with exit code $LASTEXITCODE"
+        }
+
+        if (Sync-GraphifyArtifactsFromScripts) {
+            Write-Host '[ok] graphify output synced from scripts/graphify-out to context/graphify-out'
+        }
     }
     else {
         Write-Host '[ok] context/graphify-out/graph.json already exists'

package/scripts/setup/validate-context.ps1

@@ -69,6 +69,24 @@ function Write-SetupValidationReport {
   $Report | ConvertTo-Json -Depth 20 | Set-Content -Path $Path -Encoding utf8
 }
 
+function Sync-GraphifyArtifactsIfNeeded {
+  $contextGraphDir = Join-Path $repoRoot 'context/graphify-out'
+  $contextGraphPath = Join-Path $contextGraphDir 'graph.json'
+  $scriptsGraphDir = Join-Path $repoRoot 'scripts/graphify-out'
+  $scriptsGraphPath = Join-Path $scriptsGraphDir 'graph.json'
+
+  if ((-not (Test-Path $contextGraphPath)) -and (Test-Path $scriptsGraphPath)) {
+    New-Item -ItemType Directory -Path $contextGraphDir -Force | Out-Null
+    Copy-Item -Path $scriptsGraphPath -Destination $contextGraphPath -Force
+
+    $scriptsManifestPath = Join-Path $scriptsGraphDir 'manifest.json'
+    $contextManifestPath = Join-Path $contextGraphDir 'manifest.json'
+    if ((-not (Test-Path $contextManifestPath)) -and (Test-Path $scriptsManifestPath)) {
+      Copy-Item -Path $scriptsManifestPath -Destination $contextManifestPath -Force
+    }
+  }
+}
+
 # Ensure report directory exists
 $reportDir = Split-Path -Parent $setupValidationReportPath
 if (-not (Test-Path $reportDir)) {
@@ -192,8 +210,9 @@ if ($toolingManifest -and ($toolingManifest.PSObject.Properties.Name -contains '
 
 try {
   $mcpRaw = Get-Content -Raw -Path '.vscode/mcp.json' | ConvertFrom-Json -Depth 20
-  if ($mcpRaw.servers.gitnexus.command -ne 'gitnexus') {
-    $errors += 'MCP gitnexus command should be local `gitnexus` (avoid npx startup latency).'
+  $gitnexusCommand = [string]$mcpRaw.servers.gitnexus.command
+  if ($gitnexusCommand -eq 'npx') {
+    $errors += 'MCP gitnexus command should avoid `npx` (startup latency). Use local `gitnexus` or local wrapper script.'
   }
   $scanLimit = 0
   $gitnexusHasEnv = ($mcpRaw.servers.gitnexus.PSObject.Properties.Name -contains 'env')
@@ -215,6 +234,8 @@ catch {
   $errors += "Unable to parse .vscode/mcp.json: $($_.Exception.Message)"
 }
 
+Sync-GraphifyArtifactsIfNeeded
+
 $specFiles = @(
   "specs/architecture.spec.md",
   "specs/azure-rag.spec.md",
@@ -332,9 +353,9 @@ else {
   }
 }
 
-if (-not (Test-Path "context/graphify-out/graph.json")) {
+if ((-not (Test-Path "context/graphify-out/graph.json")) -and (-not (Test-Path "scripts/graphify-out/graph.json"))) {
   if (-not ($CIMode)) {
-    $errors += "Missing context/graphify-out/graph.json. Run: py -3.14 -m graphify extract scripts --no-cluster --out context"
+    $errors += "Missing graphify graph output. Run: py -3.14 -m graphify update scripts --no-cluster"
   }
 }