multimodel-dev-os 2.0.0 → 2.6.0

package/docs/templates-guide.md

@@ -55,13 +55,13 @@ To view and list templates directly from your shell:
 
 ```bash
 # List all templates
-node bin/multimodel-dev-os.js templates
+npx multimodel-dev-os templates
 
 # Inspect nextjs-saas layout details
-node bin/multimodel-dev-os.js show-template nextjs-saas
+npx multimodel-dev-os show-template nextjs-saas
 
 # Bootstrap target using a template
-node bin/multimodel-dev-os.js init --target ../my-new-app --template nextjs-saas
+npx multimodel-dev-os init --target ../my-new-app --template nextjs-saas
 ```
 
 ---
@@ -69,3 +69,14 @@ node bin/multimodel-dev-os.js init --target ../my-new-app --template nextjs-saas
 ## Template Quality Assurance
 
 To ensure all contributed templates meet our rigorous quality standards before packaging, refer to our [Template Quality Assurance Blueprint](/template-qa).
+
+## Template Recommendations for Existing Repos
+
+If you are onboarding an existing repository and unsure which template profile to use, the recommendation engine can automatically analyze your project files:
+
+```bash
+# Analyze framework and package signals, then output recommendation
+npx multimodel-dev-os onboard recommend --target .
+```
+
+For detailed heuristics and confidence weights, refer to the [Template Recommendation Engine docs](/template-recommendation).

package/docs/tool-registry.md

@@ -0,0 +1,21 @@
+# Tool & Protocol Registry
+
+The **Tool Registry** governs connection protocols, interfaces, and file associations for developer environments and AI agents.
+
+---
+
+## 1. Tool Mappings
+
+Tools configured in `.ai/registries/tools.yaml` are mapped by:
+*   **Interface Type**: `editor` (IDE plugins), `terminal` (CLI clients), or `assistant` (chat helpers).
+*   **Protocols**: Connection formats such as `stdin-stdout`, `mcp-jsonrpc` (Model Context Protocol), or custom config parameters.
+*   **Registry Keys**: Associated configuration files (e.g. `.cursorrules` for Cursor, `CLAUDE.md` for Claude Code).
+
+---
+
+## 2. Model Context Protocol (MCP) Integration
+
+MultiModel Dev OS leverages MCP to expose local resources to models:
+1.  **Server Bindings**: Developers declare local MCP servers (e.g. gcloud SDK MCP, Chrome DevTools MCP) under the tools registry.
+2.  **Capability Matching**: The Capability Registry checks if the selected model has `mcp-compliance: 1.0` before attempting native bindings.
+3.  **Unified Tool Access**: Exposes filesystem, browser automation, and deployment commands directly to agent execution loops securely.

package/docs/v2-release-checklist.md

@@ -4,7 +4,7 @@ Use this checklist to verify compliance before publishing `multimodel-dev-os` to
 
 ## Pre-Flight Requirements
 
-- [x] Ensure version string in `package.json` is set to `2.0.0`.
+- [x] Ensure version string in `package.json` is set to `2.0.1`.
 - [x] Verify version strings in documentation and install scripts (`scripts/install.sh`, `scripts/install.ps1`) align with the release.
 - [x] Run full release verification:
   ```bash

package/docs/v2-roadmap.md

@@ -9,7 +9,7 @@ This document outlines the development path, stabilization targets, and migratio
 The primary goal of the **v2.0.0 release** is to promote the experimental features introduced in `v1.2.0` (Template Galaxy, Model Compatibility Layer, and Android Expo template) into officially frozen, production-grade core components, and resume stable package publication to the public npm registry.
 
 > [!IMPORTANT]
-> **v2.0.0 is the active stable release.** NPM publishing is resumed, consolidating the Template Galaxy and Model registries.
+> **v2.0.1 is the active stable release.** NPM publishing is resumed, consolidating the Template Galaxy and Model registries.
 
 ---
 
@@ -93,3 +93,23 @@ The `v2.0.0` release requires:
 1. 100% pass rate on all automated linter and verifier checks.
 2. Complete documentation updates across all guides and discovery indices.
 3. Explicit maintainer sign-off on local testing of the Android Expo template.
+
+---
+
+## 6. Future Stages: v2.1.0 to v3.0.0
+
+*   **v2.1.0 — Intelligence Core & Registries Foundation**
+    *   Design and document schemas (`memory.schema.json`, `feedback.schema.json`).
+    *   Introduce `.ai/registries/` configuration databases.
+    *   Implement CLI routing helper `mmdo capability route` and `mmdo memory build/refresh`.
+*   **v2.2.0 — Feedback Loops & Tool Integrations**
+    *   Add `mmdo learn` capability to append feedback metrics.
+    *   Define `.ai/registries/tools.yaml` with MCP protocol interfaces.
+*   **v2.3.0 — Proposal Engine & Safety Controls**
+    *   Deploy proposal structures under `.ai/proposals/`.
+    *   Implement CLI pipeline `mmdo improve propose/review/apply`.
+*   **v2.4.0 — Local/Offline Operations**
+    *   Integrate local model scoring (Llama.cpp, Ollama) and offline schema checks.
+*   **v3.0.0 — Unified Autonomous Co-Pilot Ecosystem**
+    *   Full multi-agent orchestration workflows with dynamic task handoffs.
+    *   Distributed registry syncing and cryptographically signed self-improvement proposals.

package/docs/workflow-orchestration.md

@@ -0,0 +1,59 @@
+# Workflow Orchestration
+
+MultiModel Dev OS `v2.5.0` features a built-in **Workflow Runner** designed to orchestrate codebase diagnostic pipelines safely.
+
+---
+
+## 1. CLI Commands
+
+Workflows are registered in [.ai/registries/workflows.yaml](file:///.ai/registries/workflows.yaml) and can be executed via the following subcommands:
+
+### List Registered Workflows
+Prints name, risk, and summary of all active workflows:
+```bash
+npx multimodel-dev-os workflow list
+```
+
+### Show Workflow Specifications
+Displays details, memory write permissions, code modification permissions, and individual logical steps:
+```bash
+npx multimodel-dev-os workflow show repo-health
+```
+
+### Plan Workflow Execution (Dry-Run)
+Prints the execution sequence, command lists, and expected outputs without executing any logic:
+```bash
+npx multimodel-dev-os workflow plan repo-health
+```
+
+### Run Workflow
+Executes the workflow steps sequentially:
+```bash
+npx multimodel-dev-os workflow run repo-health
+```
+
+---
+
+## 2. Standard Built-in Workflows
+
+MultiModel Dev OS defines 5 baseline workflows:
+
+1.  **`repo-health`** (Low Risk): Scans framework signals, performs advisory doctor audits, and verifies file structures.
+2.  **`memory-refresh`** (Medium Risk): Assesses memory differences and incremental refreshes.
+3.  **`feedback-review`** (Low Risk): Lists active developer logs and compiles rules to `learning-rules.md`.
+4.  **`proposal-review`** (Low Risk): Inspects codebase proposals, checks status counts, and displays audit apply logs.
+5.  **`release-check`** (Low Risk): Verifies codebase structures, executes release doctors, and runs package pack checks.
+
+---
+
+## 3. Strict Safety Gates
+
+The workflow engine enforces strict safety boundaries:
+
+*   **No File Modifications**: Allowed workflows only execute read-only checkups and incremental metadata updates (memory file compilation, feedback summaries).
+*   **No Shell Execution**: Shell command execution from `workflows.yaml` is prohibited. Steps map directly to internal Javascript CLI functions.
+*   **No Autonomy**: Any step requiring code changes (e.g. applying proposals) stops and outputs manual next-step instructions for the developer.
+
+## 4. Bundled Registry Fallback
+
+If the repository does not have a local `.ai/registries/workflows.yaml` registry file initialized yet, the workflow runner will automatically fall back to the bundled registry package templates and output a notice. This allows running read-only diagnostics prior to full project onboarding.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "multimodel-dev-os",
-  "version": "2.0.0",
+  "version": "2.6.0",
   "bin": {
     "multimodel-dev-os": "bin/multimodel-dev-os.js"
   },

package/scripts/install.ps1

@@ -11,7 +11,7 @@ param(
   [switch]$Help
 )
 
-$Version = "2.0.0"
+$Version = "2.6.0"
 $RepoUrl = "https://raw.githubusercontent.com/rizvee/multimodel-dev-os/main"
 
 if ($Help) {

package/scripts/install.sh

@@ -7,7 +7,7 @@ set -euo pipefail
 #        --all      (install all adapters)
 #        --dry-run  (show what would be created without creating)
 
-VERSION="2.0.0"
+VERSION="2.6.0"
 REPO_URL="https://raw.githubusercontent.com/rizvee/multimodel-dev-os/main"
 CAVEMAN=false
 DRY_RUN=false

package/scripts/prepublish-guard.js

@@ -2,7 +2,7 @@
 
 /**
  * MultiModel Dev OS - Prepublish Guard
- * Blocks accidental npm publications until v2.0.0.
+ * Blocks accidental npm publications.
  */
 
 import { readFileSync, existsSync } from 'fs';
@@ -15,8 +15,8 @@ const projectRoot = join(__dirname, '..');
 
 // 1. Check environment variable override
 if (process.env.MMDO_ALLOW_PUBLISH !== 'true') {
-  console.error('\n\x1b[31m[ABORT] NPM publishing is paused until v2.0.0.\x1b[0m');
-  console.error('To override this guard during the approved v2 release, set the environment variable:');
+  console.error('\n\x1b[31m[ABORT] Publishing requires explicit release approval. Set MMDO_ALLOW_PUBLISH=true only during an approved npm publish.\x1b[0m');
+  console.error('To override this guard during the approved release, set the environment variable:');
   console.log('  \x1b[33mMMDO_ALLOW_PUBLISH=true\x1b[0m\n');
   process.exit(1);
 }

package/scripts/verify.js

@@ -231,6 +231,21 @@ checkFile('docs/v2-migration.md');
 checkFile('docs/v2-release-checklist.md');
 checkFile('docs/package-safety.md');
 
+// --- v2.1.0 Intelligence Layer Documentation ---
+console.log('\nIntelligence Layer Documentation:');
+checkFile('docs/future-proof-architecture.md');
+checkFile('docs/self-improving-codebase.md');
+checkFile('docs/feedback-learning.md');
+checkFile('docs/hash-compressed-memory.md');
+checkFile('docs/capability-registry.md');
+checkFile('docs/tool-registry.md');
+checkFile('docs/improvement-proposals.md');
+checkFile('docs/learning-rules.md');
+checkFile('docs/approved-proposal-apply.md');
+checkFile('docs/repository-command-center.md');
+checkFile('docs/workflow-orchestration.md');
+checkFile('docs/agent-handoff.md');
+
 // --- Model & Adapter Registries ---
 console.log('\nModel & Adapter Registries:');
 checkFile('.ai/models/registry.yaml');
@@ -250,6 +265,28 @@ checkFile('.ai/schema/config.schema.json');
 checkFile('.ai/schema/template.schema.json');
 checkFile('.ai/schema/adapter.schema.json');
 
+// --- v2.1.0 Intelligence Layer (Schemas, Policies, Registries) ---
+console.log('\nIntelligence Layer Schemas:');
+checkFile('.ai/intelligence/memory.schema.json');
+checkFile('.ai/intelligence/feedback.schema.json');
+checkFile('.ai/intelligence/README.md');
+checkFile('.ai/intelligence/feedback-log.example.jsonl');
+checkFile('.ai/intelligence/learning-rules.example.md');
+checkFile('.ai/intelligence/improvement-proposal.schema.json');
+checkFile('.ai/intelligence/apply-log.schema.json');
+checkFile('.ai/proposals/README.md');
+checkFile('.ai/proposals/apply-operation.example.json');
+
+console.log('\nIntelligence Layer Policies:');
+checkFile('.ai/policies/self-improvement-policy.md');
+checkFile('.ai/policies/memory-policy.md');
+checkFile('.ai/policies/approval-gates.md');
+
+console.log('\nIntelligence Layer Registries:');
+checkFile('.ai/registries/capabilities.yaml');
+checkFile('.ai/registries/tools.yaml');
+checkFile('.ai/registries/workflows.yaml');
+
 // --- Test Blueprints ---
 console.log('\nTest Manuals:');
 checkFile('tests/README.md');
@@ -377,6 +414,9 @@ verifyRegistryParsed('.ai/models/routing-presets.yaml', 'presets');
 verifyRegistryParsed('.ai/models/local-models.yaml', 'local_engines');
 verifyRegistryParsed('.ai/adapters/registry.yaml', 'adapters');
 verifyRegistryParsed('.ai/templates/registry.yaml', 'templates');
+verifyRegistryParsed('.ai/registries/capabilities.yaml', 'capabilities');
+verifyRegistryParsed('.ai/registries/tools.yaml', 'tools');
+verifyRegistryParsed('.ai/registries/workflows.yaml', 'workflows');
 
 // --- CLI & Packaging Pre-Flight Tests ---
 console.log('\nRunning CLI & Packaging Pre-Flight Tests...');
@@ -408,11 +448,70 @@ try {
     console.log(`  ${GREEN}✓${NC} CLI help displays v${expectedVersion}`);
     pass++;
   }
+  
+  if (helpOutput.includes('scan') && helpOutput.includes('memory') && helpOutput.includes('status') && helpOutput.includes('workflow') && helpOutput.includes('handoff')) {
+    console.log(`  ${GREEN}✓${NC} CLI help includes scan, memory, status, workflow, and handoff commands`);
+    pass++;
+  } else {
+    console.error(`  ${RED}✗${NC} CLI help is missing scan, memory, status, workflow, or handoff commands`);
+    fail++;
+  }
 } catch (e) {
   console.error(`  ${RED}✗${NC} node bin/multimodel-dev-os.js --help failed: ${e.message}`);
   fail++;
 }
 
+// Verify docs mention memory build
+try {
+  const mdContent = readFileSync(join(projectRoot, 'docs', 'hash-compressed-memory.md'), 'utf8');
+  if (mdContent.includes('memory build')) {
+    console.log(`  ${GREEN}✓${NC} docs/hash-compressed-memory.md mentions 'memory build'`);
+    pass++;
+  } else {
+    console.error(`  ${RED}✗${NC} docs/hash-compressed-memory.md does not mention 'memory build'`);
+    fail++;
+  }
+} catch (e) {
+  console.error(`  ${RED}✗${NC} docs check failed: ${e.message}`);
+  fail++;
+}
+
+// Verify no generated memory or feedback logs or proposals are committed/tracked in git root/intelligence folder
+try {
+  const checkUntracked = (relPath) => {
+    if (existsSync(join(projectRoot, relPath))) {
+      console.error(`  ${RED}✗${NC} ${relPath} should not be tracked/committed!`);
+      fail++;
+    } else {
+      console.log(`  ${GREEN}✓${NC} ${relPath} is not tracked/committed`);
+      pass++;
+    }
+  };
+  checkUntracked('.ai/intelligence/memory.hash.json');
+  checkUntracked('.ai/intelligence/memory.summary.md');
+  checkUntracked('.ai/intelligence/feedback-log.jsonl');
+  checkUntracked('.ai/intelligence/learning-rules.md');
+  checkUntracked('.ai/intelligence/handoff.md');
+  checkUntracked('.ai/proposals/apply-log.jsonl');
+  
+  // also check if any proposal-*.md file exists directly in projectRoot/proposals (since it shouldn't be tracked)
+  const proposalsDir = join(projectRoot, '.ai', 'proposals');
+  if (existsSync(proposalsDir)) {
+    const files = readdirSync(proposalsDir);
+    const hasRuntimeProposals = files.some(f => f.startsWith('proposal-') && f !== 'proposal-template.md' && f.endsWith('.md'));
+    if (hasRuntimeProposals) {
+      console.error(`  ${RED}✗${NC} Runtime proposals should not be committed/tracked!`);
+      fail++;
+    } else {
+      console.log(`  ${GREEN}✓${NC} No runtime proposals committed`);
+      pass++;
+    }
+  }
+} catch (e) {
+  console.error(`  ${RED}✗${NC} Tracking verification of generated files failed: ${e.message}`);
+  fail++;
+}
+
 // Verify npm pack dry-run shows current version dynamically
 try {
   const packOutput = execSync('npm pack --dry-run', { cwd: projectRoot, encoding: 'utf8', stdio: ['ignore', 'pipe', 'pipe'] });
@@ -447,12 +546,17 @@ try {
 
 // --- Package Safety & Hygiene Checks ---
 console.log('\nPackage Safety & Hygiene Checks:');
-if (existsSync(join(projectRoot, '.npmrc'))) {
+if (existsSync(join(projectRoot, '.npmrc')) && process.env.MMDO_ALLOW_PUBLISH !== 'true') {
   console.error(`  ${RED}✗ .npmrc file exists in package root (security risk)${NC}`);
   fail++;
 } else {
-  console.log(`  ${GREEN}✓${NC} No .npmrc file present in package root`);
-  pass++;
+  if (existsSync(join(projectRoot, '.npmrc'))) {
+    console.log(`  ${YELLOW}!${NC} .npmrc file present in package root (allowed via MMDO_ALLOW_PUBLISH)`);
+    warn++;
+  } else {
+    console.log(`  ${GREEN}✓${NC} No .npmrc file present in package root`);
+    pass++;
+  }
 }
 
 const checkExamplesHygiene = (dir) => {