@cleocode/cleo 2026.3.7 → 2026.3.11

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cleocode/cleo",
-  "version": "2026.3.7",
+  "version": "2026.3.11",
   "description": "CLEO V2 - TypeScript task management CLI for AI coding agents",
   "mcpName": "io.github.kryptobaseddev/cleo-mcp-server",
   "type": "module",
@@ -30,10 +30,13 @@
     "lint": "tsc --noEmit",
     "prepare": "npm run build",
     "prepack": "npm run build",
+    "postinstall": "node bin/postinstall.js",
     "migrate:todos": "node dist/scripts/migrate-todo-to-tasks.js",
     "cleo:update-status": "node dist/scripts/update-task-status.js",
     "adr:validate": "tsx dev/validate-adrs.ts",
-    "adr:manifest": "tsx dev/generate-adr-manifest.ts"
+    "adr:manifest": "tsx dev/generate-adr-manifest.ts",
+    "features:generate": "tsx dev/generate-features.ts",
+    "version:sync": "tsx dev/version-sync.ts"
   },
   "engines": {
     "node": ">=24.13.1"
@@ -58,10 +61,11 @@
     "templates",
     "packages/ct-skills/skills",
     "completions",
-    "server.json"
+    "server.json",
+    "bin"
   ],
   "dependencies": {
-    "@cleocode/caamp": "^1.1.3",
+    "@cleocode/caamp": "^1.5.2",
     "@cleocode/lafs-protocol": "^1.6.0",
     "@modelcontextprotocol/sdk": "^1.26.0",
     "ajv": "^8.18.0",
@@ -72,6 +76,7 @@
     "pino-roll": "^4.0.0",
     "proper-lockfile": "^4.1.2",
     "sql.js": "^1.14.0",
+    "sqlite-vec": "^0.1.7-alpha.2",
     "write-file-atomic": "^6.0.0",
     "yaml": "^2.8.2"
   },

package/packages/ct-skills/profiles/core.json

@@ -1,7 +1,7 @@
 {
   "name": "core",
-  "description": "Orchestration and pipeline awareness",
+  "description": "Orchestration and LOOM (RCASD-IVTR+C) pipeline awareness",
   "extends": "minimal",
-  "skills": ["ct-orchestrator"],
+  "skills": ["ct-orchestrator", "loom"],
   "includeProtocols": ["agent-protocol"]
 }

package/packages/ct-skills/profiles/recommended.json

@@ -1,7 +1,7 @@
 {
   "name": "recommended",
-  "description": "Full RCASD pipeline skills for epic-driven development",
+  "description": "Full LOOM (RCASD-IVTR+C pipeline) skills for epic-driven development",
   "extends": "core",
-  "skills": ["ct-epic-architect", "ct-research-agent", "ct-spec-writer", "ct-validator"],
+  "skills": ["ct-epic-architect", "ct-research-agent", "ct-spec-writer", "ct-validator", "loom"],
   "includeProtocols": ["research", "consensus", "specification", "decomposition", "validation", "adr"]
 }

package/packages/ct-skills/skills/_shared/subagent-protocol-base.md

@@ -93,7 +93,9 @@ See the reference above for:
 
 ---
 
-## Task Lifecycle Integration
+## Task Lifecycle Integration (LOOM)
+
+All work follows the **LOOM** (Logical Order of Operations Methodology) framework through the RCASD-IVTR+C pipeline stages. See `docs/concepts/vision.md` for the complete LOOM framework, neural hierarchy model, and brain metaphor mapping.
 
 Reference: @skills/_shared/task-system-integration.md
 

package/packages/ct-skills/skills/ct-cleo/SKILL.md

@@ -35,7 +35,7 @@ MCP is the **primary** entry point. Use `cleo_query` for reads and `cleo_mutate`
 | `orchestrate` | `next` | Next task suggestion (`params: { epicId }`) |
 | `research` | `list` | Research manifest entries |
 | `research` | `show` | Research entry details (`params: { entryId }`) |
-| `validate` | `report` | Validate task data integrity |
+| `check` | `schema` | Validate task data schema integrity |
 | `system` | `dash` | Project overview dashboard |
 | `system` | `context` | Context window usage |
 | `skills` | `list` | Available skills |
@@ -180,9 +180,11 @@ After EVERY command:
 | 11 | `E_DEPTH_EXCEEDED` | Max depth 3 (epic->task->subtask) |
 | 12 | `E_SIBLING_LIMIT` | Max 7 siblings per parent |
 
-## RCSD-IVTR Lifecycle
+## RCSD-IVTR Lifecycle (LOOM)
 
-**Lifecycle**: See CLEO-INJECTION.md standard tier for full RCASD-IVTR+C pipeline details, or `references/rcsd-lifecycle.md` for gate enforcement and subagent architecture.
+**LOOM** (Logical Order of Operations Methodology) is the systematic framework for how CLEO processes project threads through the RCASD-IVTR+C pipeline. See `docs/concepts/vision.md` for the complete LOOM framework, neural hierarchy model, and brain metaphor mapping.
+
+**Lifecycle**: See CLEO-INJECTION.md standard tier for full RCASD-IVTR+C pipeline details, or `references/loom-lifecycle.md` for gate enforcement and subagent architecture.
 
 ## Pipeline Awareness
 
@@ -212,5 +214,5 @@ Epics follow the RCASD-IVTR+C lifecycle managed through pipeline stages. Use `pi
 For detailed guidance on specific topics, see:
 
 - **Session Protocol**: `references/session-protocol.md`
-- **RCSD Lifecycle**: `references/rcsd-lifecycle.md`
+- **LOOM Lifecycle**: `references/loom-lifecycle.md`
 - **Anti-Patterns**: `references/anti-patterns.md`

package/packages/ct-skills/skills/ct-cleo/references/{rcsd-lifecycle.md → loom-lifecycle.md}

@@ -1,16 +1,23 @@
-# RCSD-IVTR Lifecycle (Detailed)
+# LOOM Lifecycle (Detailed)
 
-Projects follow a structured lifecycle with gate enforcement.
+**LOOM** (Logical Order of Operations Methodology) is the systematic framework for how CLEO processes project threads through the RCASD-IVTR+C pipeline. This document details the lifecycle stages and gate enforcement.
+
+See `docs/concepts/vision.md` for the complete LOOM framework, neural hierarchy model, and brain metaphor mapping.
 
 ## Pipeline Stages
 
 ```
-RCSD PIPELINE (setup phase):
-  Research -> Consensus -> Specification -> Decomposition
-                              |
-                              v
-EXECUTION (core/polish):
-  Implementation -> Contribution -> Release
+LOOM (RCASD-IVTR+C) PIPELINE:
+
+RCASD (Planning Phase):
+  Research -> Consensus -> Architecture Decision -> Specification -> Decomposition
+                                                              |
+                                                              v
+IVTR (Execution Phase):
+  Implementation -> Validation -> Testing -> Release
+
++C (Cross-Cutting):
+  Contribution (applies across all stages)
 ```
 
 Each stage has a **lifecycle gate**. Entering a later stage requires prior stages to be `completed` or `skipped`. Gate enforcement mode is configured in `.cleo/config.json` (`strict` | `advisory` | `off`).
@@ -31,14 +38,16 @@ Each stage has a **lifecycle gate**. Entering a later stage requires prior stage
 
 ## Lifecycle Gate Enforcement
 
-CLEO enforces RCSD-IVTR lifecycle progression through automatic gate checks at spawn time.
+CLEO enforces LOOM (RCASD-IVTR+C) lifecycle progression through automatic gate checks at spawn time.
 
 ```
-research --+---> consensus --+---> specification --+---> decomposition
-           |                 |                     |
-           | GATE            | GATE                | GATE
-           |                 |                     |
-           +-----------------+---------------------+---> implementation ---> release
+research --+---> consensus --+---> architecture_decision --+---> specification --+---> decomposition
+           |                 |                              |                    |
+           | GATE            | GATE                         | GATE               | GATE
+           |                 |                              |                    |
+           +-----------------+------------------------------+--------------------+---> implementation --+---> release
+                                                                                                         |
+                                                                                                    validation/testing
 ```
 
 | Enforcement Mode | On Gate Failure | Default |

package/packages/ct-skills/skills/ct-orchestrator/SKILL.md

@@ -55,11 +55,13 @@ You are the **Orchestrator** - a conductor, not a musician. Coordinate complex w
 | ORC-008 | Zero architectural decisions | "Architecture MUST be pre-decided by HITL" |
 | ORC-009 | MUST NEVER write code | "Every line of code is written by a subagent" |
 
-## RCASD Pipeline Management
+## RCASD Pipeline Management (LOOM)
 
-The orchestrator manages epic-level pipeline progression through the RCASD-IVTR+C lifecycle.
+The orchestrator manages epic-level pipeline progression through the **LOOM** (Logical Order of Operations Methodology) framework — the systematic approach for processing project threads through the RCASD-IVTR+C lifecycle.
 
-**RCASD Pipeline Flow**: Research -> Consensus -> Architecture Decision -> Specification -> Decomposition -> Implementation -> Validation -> Testing -> Release -> Contribution
+**LOOM Pipeline Flow**: Research -> Consensus -> Architecture Decision -> Specification -> Decomposition -> Implementation -> Validation -> Testing -> Release -> Contribution
+
+See `docs/concepts/vision.md` for the complete LOOM framework, neural hierarchy model, and brain metaphor mapping.
 
 ### Pipeline Decision Matrix
 
@@ -118,7 +120,7 @@ This separation means the orchestrator protocol works identically regardless of
 ### Quick Start — MCP (Recommended)
 
 ```
-cleo_query({ domain: "orchestrate", operation: "start", params: { epicId: "T1575" }})
+cleo_mutate({ domain: "orchestrate", operation: "start", params: { epicId: "T1575" }})
 ```
 
 **Returns**: Session state, context budget, next task, pipeline stage, and recommended action in one call.
@@ -230,7 +232,7 @@ The spawn prompt combines the **Base Protocol** (`agents/cleo-subagent/AGENT.md`
 ### Phase 1: Discovery
 
 ```
-cleo_query({ domain: "orchestrate", operation: "start", params: { epicId: "T1575" }})
+cleo_mutate({ domain: "orchestrate", operation: "start", params: { epicId: "T1575" }})
 cleo_query({ domain: "research", operation: "pending" })
 cleo_query({ domain: "pipeline", operation: "stage.status", params: { epicId: "T1575" }})
 ```
@@ -322,7 +324,7 @@ Content flows between subagents via **manifest-mediated handoffs**, not through
 | Handling Manifest Followups | Subagent left TODOs | `research.pending`, `tasks.add` |
 | Parallel Execution | Independent tasks in same wave | `orchestrate.analyze`, `orchestrate.ready` |
 | Pipeline-Aware Orchestration | Multi-stage epics | `pipeline.stage.status`, `pipeline.stage.validate`, `pipeline.stage.gate.pass` |
-| Quality Gates | Verification required | `validate.report`, `pipeline.stage.validate` |
+| Quality Gates | Verification required | `check.schema`, `pipeline.stage.validate` |
 | Release | Ship a version | `release.create`, `release.ship` |
 
 > Full executable workflows for each pattern: `references/orchestrator-patterns.md`

package/packages/ct-skills/skills/manifest.json

@@ -54,7 +54,7 @@
       "status": "active",
       "tier": 0,
       "token_budget": 6000,
-      "references": ["skills/ct-cleo/references/session-protocol.md", "skills/ct-cleo/references/rcsd-lifecycle.md", "skills/ct-cleo/references/anti-patterns.md"],
+      "references": ["skills/ct-cleo/references/session-protocol.md", "skills/ct-cleo/references/loom-lifecycle.md", "skills/ct-cleo/references/anti-patterns.md"],
       "capabilities": {
         "inputs": ["TASK_ID", "SESSION_ID"],
         "outputs": ["session-state", "task-state"],

package/packages/ct-skills/skills.json

@@ -7,7 +7,7 @@
       "description": "CLEO task management protocol - core guidance for session, task, and workflow operations. Provides MCP-first workflow, CLI fallback, session protocol, task discovery patterns, RCSD lifecycle overview, and error handling. Load this skill for detailed CLEO protocol guidance.",
       "version": "2.0.0",
       "path": "skills/ct-cleo/SKILL.md",
-      "references": ["skills/ct-cleo/references/session-protocol.md", "skills/ct-cleo/references/rcsd-lifecycle.md", "skills/ct-cleo/references/anti-patterns.md"],
+      "references": ["skills/ct-cleo/references/session-protocol.md", "skills/ct-cleo/references/loom-lifecycle.md", "skills/ct-cleo/references/anti-patterns.md"],
       "core": true,
       "category": "core",
       "tier": 0,
@@ -241,6 +241,25 @@
       "compatibility": ["claude-code", "cursor", "windsurf", "gemini-cli"],
       "license": "MIT",
       "metadata": {}
+    },
+    {
+      "name": "loom",
+      "description": "LOOM (Logical Order of Operations Methodology) - the systematic framework for how CLEO processes project threads through the RCASD-IVTR+C pipeline. LOOM encompasses the full lifecycle methodology that transforms raw ideas into delivered artifacts, from Research through Release with the Contribution protocol (+C) running across all stages. References docs/concepts/vision.md for the complete LOOM framework, neural hierarchy model, and brain metaphor mapping.",
+      "version": "1.0.0",
+      "path": "docs/concepts/vision.md",
+      "references": [".cleo/adrs/ADR-007-domain-consolidation.md", ".cleo/adrs/ADR-009-BRAIN-cognitive-architecture.md"],
+      "core": false,
+      "category": "core",
+      "tier": 0,
+      "protocol": null,
+      "dependencies": [],
+      "sharedResources": [],
+      "compatibility": ["claude-code", "cursor", "windsurf", "gemini-cli"],
+      "license": "MIT",
+      "metadata": {
+        "concepts": ["LOOM", "RCASD-IVTR+C", "lifecycle pipeline", "neural hierarchy", "brain metaphor"],
+        "domains": ["tasks", "session", "memory", "check", "pipeline", "orchestrate", "tools", "admin", "nexus", "sharing"]
+      }
     }
   ]
 }