@exchanet/enet 1.0.12 → 1.0.14

package/package.json

@@ -1,11 +1,16 @@
 {
   "name": "@exchanet/enet",
-  "version": "1.0.12",
+  "version": "1.0.14",
   "description": "enet — exchanet methods manager. Install, scaffold and manage AI coding methods.",
   "bin": {
     "enet": "src/index.js"
   },
   "type": "module",
+  "files": [
+    "src",
+    "registry.json",
+    "manifest.schema.json"
+  ],
   "scripts": {
     "dev": "node src/index.js",
     "test": "node --test"
@@ -15,7 +20,6 @@
     "commander": "^12.0.0",
     "enquirer": "^2.4.1",
     "ora": "^8.0.1",
-    "node-fetch": "^3.3.2",
     "ajv": "^8.12.0",
     "ajv-formats": "^3.0.1",
     "fs-extra": "^11.2.0"

package/src/index.js

@@ -77,7 +77,7 @@ program
 program
   .command('init')
   .description('Interactively create a manifest.json for a new module')
-  .option('-n, --name <name>', 'Module name')
+  .option('-n, --name <n>', 'Module name')
   .option('-s, --section <section>', 'Admin Panel section')
   .option('--json', 'Print manifest as JSON without writing to disk')
   .action(initCommand)
@@ -90,7 +90,7 @@ program
   .action(validateCommand)
 
 program
-  .command('new <type> <name>')
+  .command('new <type> <n>')
   .description('Scaffold a new module, ui-pack or integration')
   .option('-s, --section <section>', 'Admin Panel section')
   .option('--dry-run', 'Preview files without writing')

package/src/utils/registry.js

@@ -3,7 +3,7 @@ import path from 'path'
 import { fileURLToPath } from 'url'
 
 const __dirname = path.dirname(fileURLToPath(import.meta.url))
-const RAW_BASE   = 'https://raw.githubusercontent.com'
+const RAW_BASE     = 'https://raw.githubusercontent.com'
 const REGISTRY_URL = `${RAW_BASE}/exchanet/enet/main/registry.json`
 const CACHE_FILE   = path.join(__dirname, '../../.registry-cache.json')
 const CACHE_TTL_MS = 1000 * 60 * 60 // 1 hour
@@ -82,7 +82,7 @@ export async function fetchFromGitHub(repo, filePath) {
 // ── Install state ─────────────────────────────────────────────────────────────
 //
 // Tracks which agents have each method installed.
-// Stored in .enet/installed.json in the project root.
+// Stored in <project>/.enet/installed.json
 //
 // Format:
 // {
@@ -90,19 +90,15 @@ export async function fetchFromGitHub(repo, filePath) {
 //     "agents": ["cursor", "claudecode", "antigravity"],
 //     "version": "3.0.0",
 //     "updatedAt": "2025-03-01T10:00:00.000Z"
-//   },
-//   "modular-design": { ... }
+//   }
 // }
 
 function getInstallRecordFile() {
-  // Resolve relative to cwd so it works in any project
   return path.join(process.cwd(), '.enet', 'installed.json')
 }
 
 /**
- * Reads the install record for a single method.
- * Returns { agents: ['cursor', ...], version: '3.0.0', updatedAt: '...' }
- * or null if the method has never been installed.
+ * Returns the install record for a single method, or null if never installed.
  */
 export async function readInstallRecord(methodId) {
   try {
@@ -116,25 +112,22 @@ export async function readInstallRecord(methodId) {
 }
 
 /**
- * Writes (or updates) the install record for a single method.
- * Merges with existing records — other methods are not touched.
+ * Writes the install record for a single method.
+ * Merges with existing records — other methods are never touched.
  */
 export async function writeInstallRecord(methodId, record) {
   try {
     const file = getInstallRecordFile()
     await fs.ensureDir(path.dirname(file))
-
     let data = {}
     if (await fs.pathExists(file)) {
       data = await fs.readJson(file).catch(() => ({}))
     }
-
     data[methodId] = {
-      agents: record.agents,
-      version: record.version ?? null,
+      agents:    record.agents,
+      version:   record.version ?? null,
       updatedAt: new Date().toISOString()
     }
-
     await fs.writeJson(file, data, { spaces: 2 })
   } catch {
     // Non-fatal — install works correctly even if state cannot be saved

package/.enet/modular-design.md

@@ -1,136 +0,0 @@
-# METHOD MODULAR DESIGN — Agent Instructions
-> Universal Modular Architecture · v1.0.0 · @exchanet
-
----
-
-## YOUR PRIMARY DIRECTIVE / TU DIRECTIVA PRINCIPAL
-
-You are building a modular application using Method Modular Design. Every module you create must be self-describing via a `manifest.json` file. The manifest is written **before any code**. The system reads manifests to automatically generate the Admin Panel, dashboard, and settings UI. You never manually wire backend logic to the Admin Panel — the manifest does it.
-
-Estás construyendo una aplicación modular usando Method Modular Design. Cada módulo que crees debe ser auto-descriptivo a través de un archivo `manifest.json`. El manifest se escribe **antes de cualquier código**. El sistema lee los manifests para generar automáticamente el Panel Admin, dashboard y UI de configuración. Nunca cablearás manualmente la lógica backend al Panel Admin — el manifest lo hace.
-
-**If a module has no manifest, it does not exist.**
-**Si un módulo no tiene manifest, no existe.**
-
----
-
-## ABSOLUTE RULES / REGLAS ABSOLUTAS
-
-1. **No manifest = module does not exist.** Core rejects modules without valid `manifest.json`.
-2. **Manifest before code.** Complete manifest before any handler, model, or component.
-3. **Zero hardcoded configuration.** Every configurable value lives in `manifest.settings`, read via `context.settings.get("key")`.
-4. **Core has no business logic.** Domain logic lives in modules only.
-5. **Admin Panel is a renderer.** Never code it to show a specific module — modules declare capabilities, Admin Panel renders them.
-6. **A module is complete only when the Admin Panel reflects it correctly.**
-7. **Removing a module folder requires zero code changes elsewhere.**
-
----
-
-## WORKFLOW / FLUJO DE TRABAJO
-
-### Starting a new project / Nuevo proyecto:
-1. Ask for spectech if not provided (stack, database, deploy target)
-2. Declare the architecture you will build
-3. **Wait for confirmation before writing any code**
-4. Build Core → Manifest schema → Modules → Admin Panel
-
-### Adding a module / Añadir un módulo:
-1. Write complete `manifest.json` (all settings + capabilities + hooks)
-2. Validate against `manifest.schema.json`
-3. Implement all handlers referenced in manifest
-4. Place in modules directory (Core discovers automatically)
-5. Boot system and verify module appears in Admin Panel
-6. Build custom UI components only if manifest declares a `component` field
-
-### When you cannot complete a manifest / Cuando no puedes completar un manifest:
-
-**STOP. Ask the user:**
-
-```
-"I cannot complete the manifest for [module name] because I don't understand 
-[specific aspect]. Before I continue, I need you to clarify: [specific question]"
-
-"No puedo completar el manifest de [nombre del módulo] porque no entiendo 
-[aspecto específico]. Antes de continuar, necesito que aclares: [pregunta específica]"
-```
-
-Do not proceed. Do not create a partial manifest. Do not make assumptions. Wait.
-No continúes. No crees un manifest parcial. No hagas suposiciones. Espera.
-
----
-
-## MANIFEST FORMAT / FORMATO DEL MANIFEST
-
-```json
-{
-  "id": "module-id",
-  "name": "Human Name",
-  "version": "1.0.0",
-  "type": "functional",
-  "section": "admin-section",
-  "dependencies": [],
-  "hooks": { "event.name": "ClassName.method" },
-  "settings": {
-    "key": {
-      "type": "integer|string|boolean|select",
-      "label": "Label",
-      "default": null,
-      "ui": "slider|toggle|text|select"
-    }
-  },
-  "capabilities": [
-    { "type": "view",   "label": "Label", "data": "ClassName.method" },
-    { "type": "action", "label": "Label", "handler": "ClassName.method", "dangerous": false },
-    { "type": "metric", "label": "Label", "data": "ClassName.method" },
-    { "type": "widget", "label": "Label", "data": "ClassName.method", "component": "ComponentName" }
-  ]
-}
-```
-
----
-
-## WHAT THE CORE MUST IMPLEMENT / QUÉ DEBE IMPLEMENTAR EL CORE
-
-- Module discovery — scan modules dir for valid manifests
-- Manifest validation — reject invalid manifests with clear errors (never silent)
-- Dependency resolution — boot in correct order
-- Handler registry — map `ClassName.method` references to implementations
-- Hook system — dispatch events to declared handlers
-- Settings store — persistent, namespaced by module ID, initialized from defaults
-- REFLEX engine — read all manifests, build Admin nav, dashboard, settings schemas
-- Admin API — standard endpoints (same in every project, every stack)
-
-```
-GET  /api/admin/manifest-registry
-GET  /api/admin/navigation
-GET  /api/admin/settings/:moduleId
-POST /api/admin/settings/:moduleId
-GET  /api/admin/dashboard
-POST /api/admin/action/:moduleId/:actionId
-GET  /api/admin/health
-```
-
-**The Core has ZERO business logic. / El Core tiene CERO lógica de negocio.**
-
----
-
-## COMPLETION CHECKLIST / CHECKLIST DE COMPLETITUD
-
-Before marking any module complete / Antes de marcar cualquier módulo como completo:
-
-- [ ] `manifest.json` valid / válido
-- [ ] All declared handlers implemented / Todos los handlers declarados implementados
-- [ ] Zero hardcoded values — all settings use `context.settings.get()` / Cero hardcoded
-- [ ] Module appears in Admin Panel navigation / El módulo aparece en la navegación del Panel Admin
-- [ ] All views render with data / Todas las vistas renderizan con datos
-- [ ] All actions execute correctly / Todas las acciones ejecutan correctamente
-- [ ] Dangerous actions show confirmation dialog / Las acciones peligrosas muestran diálogo
-- [ ] All metrics show in dashboard / Todas las métricas aparecen en el dashboard
-- [ ] All settings render and save correctly / Todos los settings renderizan y guardan
-- [ ] Adding this module required zero Core changes / Añadir el módulo requirió cero cambios en el Core
-- [ ] Removing module folder removes it completely from Admin Panel / Eliminar la carpeta lo elimina del Panel Admin
-
----
-
-*For full documentation / Para documentación completa: `METHOD.md`*
-*Method Modular Design v1.0.0 · @exchanet · MIT*

package/.enet/pdca-t.md

@@ -1,110 +0,0 @@
----
-description: Method PDCA-T — Systematic quality cycle for AI-assisted coding
-trigger: always_on
----
-
-# METHOD PDCA-T — Active for all tasks in this project
-
-You are operating under the PDCA-T quality methodology. Apply this 8-phase cycle to every coding task without exception.
-
-## PHASE 1 — PLANNING
-Before writing any code:
-- State the exact objective in one sentence
-- Define what IS and IS NOT in scope
-- Ask clarifying questions if anything is ambiguous
-- Identify external dependencies
-- Define the acceptance criterion
-
-Do not advance until the objective is unambiguous.
-
-## PHASE 2 — REQUIREMENTS ANALYSIS
-- List Functional Requirements: `FR-NN: [what the system must do]`
-- List Non-Functional Requirements: `NFR-NN: [constraint or quality attribute with metric]`
-- Build Risk Register: `RISK-NN: [risk] | Probability | Impact | Mitigation`
-
-## PHASE 3 — ARCHITECTURE DESIGN
-Before any implementation:
-- Write ADRs: `ADR-NN: [title] | Context | Decision | Alternatives | Consequences`
-- Define interface contracts (function signatures + full docstrings) before implementing bodies
-- Define module structure: domain / infrastructure / interfaces
-
-## PHASE 4 — MICRO-TASK CYCLE (≤ 50 lines per task)
-
-**4.1** — Check available skills in `.cursor/skills/` and reusable context
-
-**4.2** — Write tests FIRST. Required categories:
-- Happy path · Error cases · Edge cases · Security · Performance (if applicable)
-- Structure: Arrange / Act / Assert
-- Naming: `test_[function]_[scenario]_[expected_outcome]`
-
-**4.3** — Implement code. Standards:
-- Full type hints on every parameter and return value
-- Docstring with Args, Returns, Raises
-- Single responsibility per function
-- `Decimal` not `float` for monetary values
-- Specific exception types — never bare `except:`
-- Zero hardcoded configuration
-- Structured logging with context fields
-
-**4.4** — Self-review before running tests:
-```
-□ Type hints complete?        □ All inputs validated?
-□ Docstring written?          □ No hardcoded secrets?
-□ Single responsibility?      □ Semantic names?
-□ No code duplication?        □ Errors logged with context?
-```
-
-**4.5** — Execute tests and show REAL complete output:
-```bash
-pytest tests/ -v --cov=src --cov-report=term-missing --tb=short
-```
-Never summarize. Never say "tests pass". Show the exact output.
-
-**4.6** — Validate:
-- All tests pass (100%)? If not → fix code, explain, re-run
-- Coverage ≥ 99%? If not → identify uncovered lines → add tests → re-run
-- Repeat until both conditions are met
-
-## PHASE 5 — INTEGRAL VALIDATION
-After all micro-tasks:
-- **Security:** No OWASP Top 10 issues · inputs validated · outputs sanitized · no hardcoded secrets · minimum privilege
-- **Tests:** 100% passed · 0 failed · coverage ≥ 99% · all categories present
-- **Code quality:** Type hints 100% · cyclomatic complexity < 10 · no duplication · SRP · docstrings 100%
-- **Performance:** No N+1 · indexes on filter fields · pagination in collections · timeouts configured
-- **Architecture:** No circular imports · layers respected · low coupling · inward dependencies only
-
-## PHASE 6 — TECHNICAL DEBT MANAGEMENT
-Register every known issue before delivery:
-```
-DEBT-XXX: [Short title]
-  Type: Technical | Test | Documentation | Architecture | Security | Performance
-  Description: [What and why]
-  Impact: High | Medium | Low — [justification]
-  Effort: Xh
-  Priority: High | Medium | Low
-  Plan: [Specific action and target version]
-```
-Do not write TODO/FIXME in code — register as DEBT-XXX instead.
-
-## PHASE 7 — REFINEMENT TO ≥ 99%
-If any metric is below target:
-`Identify → Classify → Plan → Execute → Verify → Confirm ≥ 99%`
-Never advance to Phase 8 without confirming ≥ 99% on all 5 validation dimensions.
-
-## PHASE 8 — DELIVERY REPORT
-Always close every task with:
-1. Implementation summary (2-3 sentences)
-2. Test table: total / passed / failed / coverage / time
-3. Full unedited pytest output
-4. Key technical decisions with justifications
-5. Technical debt registered (DEBT-XXX list)
-6. CI/CD checklist (all items confirmed)
-7. Suggested next steps
-
-## ABSOLUTE RULES — NEVER VIOLATE
-1. Tests BEFORE implementation — always, no exceptions
-2. Show REAL test output — never summarize or omit
-3. No hardcoded secrets — environment variables from commit 1
-4. Coverage ≥ 99% before any delivery
-5. ADRs for non-trivial decisions
-6. All known issues as DEBT-XXX with priority and plan