multimodel-dev-os 2.0.0 → 2.0.1

package/README.md

@@ -127,23 +127,23 @@ Cuts prompt rules overhead down by **~79%** using highly optimized short-hand de
 npx multimodel-dev-os@latest init --caveman
 ```
 
-### 4. Registry & Model Commands (Unreleased v1.2.x/v1.3.x - Local Source Only)
-To run registries and the Android Expo template, clone the source and run locally:
+### 4. Registry & Model Commands (v2.0.0 Stable Release)
+Run model capabilities registries, adapter registers, and scaffold mobile templates directly:
 ```bash
 # List model or adapter registries
-node bin/multimodel-dev-os.js models
-node bin/multimodel-dev-os.js adapters
+npx multimodel-dev-os@latest models
+npx multimodel-dev-os@latest adapters
 
 # Scaffold the Android Expo template
-node bin/multimodel-dev-os.js init --template expo-react-native-android
+npx multimodel-dev-os@latest init --template expo-react-native-android
 ```
 
-For more details on when these features will package stably, read the [v2.0.0 Roadmap](https://rizvee.github.io/multimodel-dev-os/v2-roadmap).
+For more details, see the [Model Capabilities Registry Guide](https://rizvee.github.io/multimodel-dev-os/model-compatibility).
 
 ### 5. Quality Gates
 Run assertions and diagnostic checkups:
-- **`validate`** (Strict schema checkup): `node bin/multimodel-dev-os.js validate`
-- **`doctor`** (Advisory compatibility warning): `node bin/multimodel-dev-os.js doctor`
+- **`validate`** (Strict schema checkup): `npx multimodel-dev-os@latest validate`
+- **`doctor`** (Advisory compatibility warning): `npx multimodel-dev-os@latest doctor`
 
 ---
 
@@ -184,8 +184,8 @@ Discover how engineering teams deploy MultiModel Dev OS:
 
 ## Stable Protocol Specification & Roadmap
 
-MultiModel Dev OS version `v1.1.0` officially freezes the Layer 1, Layer 2, and Layer 3 specifications. Active development on registries and template extensions (`v1.2.x` and `v1.3.x`) is source-only.
-- 🗺️ [v2.0.0 Roadmap](/docs/v2-roadmap.md) (Stabilization targets & publishing runbook)
+MultiModel Dev OS v2.x packages the stable Layer 1, Layer 2, and Layer 3 specifications alongside the Model Compatibility and Template Galaxy registries.
+- 🏁 [v2 Release Checklist](/docs/v2-release-checklist.md) (Release quality checklist)
 - 🛡️ [Stable Protocol Specification](https://rizvee.github.io/multimodel-dev-os/stable-protocol)
 - 🔌 [Multi-Agent Compatibility Guides](https://rizvee.github.io/multimodel-dev-os/compatibility)
 - 📈 [Upgrade & Migration Guide](https://rizvee.github.io/multimodel-dev-os/migration-guide)

package/bin/multimodel-dev-os.js

@@ -13,7 +13,7 @@ const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
 const sourceRoot = resolve(__dirname, '..');
 
-let version = '2.0.0';
+let version = '2.0.1';
 try {
   const pkgData = JSON.parse(readFileSync(resolve(sourceRoot, 'package.json'), 'utf8'));
   version = pkgData.version;
@@ -316,8 +316,9 @@ function handleInit(options) {
   // Check if requested template is planned
   const tInfo = TEMPLATES[options.template];
   if (tInfo && tInfo.status === 'planned') {
-    console.warn(`  \x1b[33m[WARNING] Template '${options.template}' is a PLANNED template in the roadmap.\x1b[0m`);
-    console.warn(`  It is not fully scaffolded yet and will fall back to bootstrapping the 'general-app' profile.\n`);
+    console.warn(`  \x1b[33m[WARNING] Template '${options.template}' is planned for a future release and is not yet available.\x1b[0m`);
+    console.warn(`  To view available templates, run: \x1b[36mnpx multimodel-dev-os templates\x1b[0m`);
+    console.warn(`  Falling back to the stable \x1b[32m'general-app'\x1b[0m profile...\n`);
     options.template = 'general-app';
   }
 
@@ -331,7 +332,9 @@ function handleInit(options) {
   // Source path mapping for core files
   let templateDir = join(sourceRoot, 'examples', options.template);
   if (!existsSync(templateDir)) {
-    console.warn(`  \x1b[33m[WARNING] Template '${options.template}' not found. Falling back to 'general-app' profile.\x1b[0m`);
+    console.warn(`  \x1b[33m[WARNING] Template '${options.template}' source files could not be found.\x1b[0m`);
+    console.warn(`  To view available templates, run: \x1b[36mnpx multimodel-dev-os templates\x1b[0m`);
+    console.warn(`  Falling back to the stable \x1b[32m'general-app'\x1b[0m profile...\n`);
     templateDir = join(sourceRoot, 'examples', 'general-app');
   }
 
@@ -501,6 +504,27 @@ function handleInit(options) {
   }
 
   console.log(`\n\x1b[32m✔ Project initialized successfully! [Total Operations: ${operations.length}]\x1b[0m\n`);
+  console.log(`\x1b[36mNext Steps to Complete Integration:\x1b[0m`);
+  console.log(`  1. \x1b[1mEdit AGENTS.md\x1b[0m in your project root to document your stack context.`);
+  console.log(`  2. \x1b[1mEdit .ai/config.yaml\x1b[0m to configure active model routing presets.`);
+  if (options.adapters.length > 0) {
+    console.log(`  3. \x1b[1mActivate IDE / Agent Rules:\x1b[0m`);
+    console.log(`     Ensure adapter configuration files are copied or linked to the root of your workspace:`);
+    options.adapters.forEach(adapter => {
+      const a = ADAPTERS[adapter];
+      if (a && a.rules_file) {
+        console.log(`     - For \x1b[32m${a.name || adapter}\x1b[0m: Check the root-level \x1b[33m${a.rules_file}\x1b[0m file`);
+      }
+    });
+  } else {
+    console.log(`  3. \x1b[1mSelect IDE / Tool Adapters:\x1b[0m`);
+    console.log(`     To generate rules for Cursor, Claude Code, etc., run:`);
+    console.log(`     \x1b[36mnpx multimodel-dev-os init --adapter cursor --adapter claude\x1b[0m`);
+  }
+  console.log(`  4. \x1b[1mRun Diagnostics:\x1b[0m`);
+  console.log(`     Verify your workspace structural compliance:`);
+  console.log(`     \x1b[36mnpx multimodel-dev-os validate\x1b[0m`);
+  console.log(`     \x1b[36mnpx multimodel-dev-os doctor\x1b[0m\n`);
 }
 
 function handleVerify(options) {

package/docs/.vitepress/config.js

@@ -32,7 +32,7 @@ export default {
         'license': 'https://opensource.org/licenses/MIT',
         'url': 'https://github.com/rizvee/multimodel-dev-os',
         'downloadUrl': 'https://www.npmjs.com/package/multimodel-dev-os',
-        'softwareVersion': '2.0.0',
+        'softwareVersion': '2.0.1',
         'description': 'Portable, vendor-neutral AI Developer OS for multi-agent coding workflows.'
       })
     ]

package/docs/cli-roadmap.md

@@ -1,6 +1,6 @@
 # CLI Roadmap
 
-> The zero-dependency CLI utility is fully integrated with `npm` and `npx` in v0.3.0!
+> The zero-dependency CLI utility is fully integrated with `npm` and `npx` in v2.0.0!
 
 ## Current CLI Usage
 
@@ -23,7 +23,7 @@ npx multimodel-dev-os@latest init --force
 npx multimodel-dev-os@latest verify
 ```
 
-Alternatively, you can run the CLI locally within a cloned workspace:
+Alternatively, you can run the CLI directly from cloned source during development:
 ```bash
 node bin/multimodel-dev-os.js init
 node bin/multimodel-dev-os.js verify
@@ -37,25 +37,17 @@ node bin/multimodel-dev-os.js verify
 | `show-template` | Inspect stack specifications of a template | v0.5.0 | ✅ Completed |
 | `doctor` | Advisory checkup of workspace compatibility | v0.5.0 | ✅ Completed |
 | `validate` | Strict directory schema compliance checks | v0.5.0 | ✅ Completed |
-| `sync` | Regenerate adapter files from root AGENTS.md | v0.6.0 | 📋 Planned |
-| `add-adapter` | Add a new adapter to the project | v0.6.0 | 📋 Planned |
-| `models` | List configured model registry entries | v1.2.0 | Source Only |
-| `show-model` | Inspect settings for a model registry entry | v1.2.0 | Source Only |
-| `providers` | List configured model registry providers | v1.2.0 | Source Only |
-| `route-model`| Route a target prompt based on presets | v1.2.0 | Source Only |
-| `adapters` | List configured adapter registry entries | v1.2.0 | Source Only |
-| `show-adapter`| Inspect settings for an adapter registry entry | v1.2.0 | Source Only |
-| `skills` | List configured skill registry entries | v1.2.0 | Source Only |
-| `show-skill` | Inspect settings for a skill registry entry | v1.2.0 | Source Only |
-
-> [!NOTE]
-> All new `v1.2.0` subcommands listed as **Source Only** are fully implemented in the source code but are unreleased on the npm package registry. To run them, execute from a clone of the GitHub repository. They will be packaged officially in the `v2.0.0` stable release.
-
-## CLI v2.0.0 Stabilization Goal
-
-Ahead of the `v2.0.0` release, we will run a comprehensive compatibility pass:
-* **Backward Compatibility**: Ensure that all new registries configurations and subcommand syntax do not break the stable `v1.0.0` and `v1.1.0` CLI behaviors.
-* **Unified Quality Gates**: Integrate model registry and adapter configuration validation parameters directly into the standard `validate` and `doctor` command pipelines.
-* **Cross-Platform Hardening**: Audit all commands on Windows (PowerShell/CMD), macOS, and Linux bash environments before resuming npm package publishing.
+| `models` | List configured model registry entries | v2.0.0 | ✅ Completed |
+| `show-model` | Inspect settings for a model registry entry | v2.0.0 | ✅ Completed |
+| `providers` | List configured model registry providers | v2.0.0 | ✅ Completed |
+| `route-model`| Route a target prompt based on presets | v2.0.0 | ✅ Completed |
+| `adapters` | List configured adapter registry entries | v2.0.0 | ✅ Completed |
+| `show-adapter`| Inspect settings for an adapter registry entry | v2.0.0 | ✅ Completed |
+| `skills` | List configured skill registry entries | v2.0.0 | ✅ Completed |
+| `show-skill` | Inspect settings for a skill registry entry | v2.0.0 | ✅ Completed |
+
+## CLI v2.0.0 Stabilization & Beyond
+
+The `v2.0.0` stabilization milestone was completed successfully, hardening registries configurations, custom skill checking tools, and token size overrides. Any future subcommands or adapter sync mechanisms will follow SemVer guidelines to ensure full backward compatibility.
 
 

package/docs/faq.md

@@ -62,6 +62,6 @@ Yes, for tools that auto-detect specific files:
 ## Protocol & Migration
 
 **Is the MultiModel Dev OS protocol stable?**
-Yes. As of version `v1.1.0`, the core specifications are officially frozen and backward-compatible. This ensures that any codebase prepared using `v1.1.0` will operate seamlessly inside future `1.x` ecosystems.
+Yes. As of version `v1.1.0`, the core specifications are officially frozen and backward-compatible. This ensures that codebases prepared using `v1.1.0` or later operate seamlessly inside all `1.x` and `2.x` ecosystems.
 
 Explore our [Stable Protocol Specification](/stable-protocol) or [Upgrade & Migration Guide](/migration-guide) for details.

package/docs/index.md

@@ -16,8 +16,8 @@ hero:
       text: Stable Protocol Specs
       link: /stable-protocol
     - theme: alt
-      text: v1.0 Readiness
-      link: /v1-readiness
+      text: v2 Release Checklist
+      link: /v2-release-checklist
     - theme: alt
       text: View Case Studies
       link: /case-studies/
@@ -141,9 +141,9 @@ MultiModel Dev OS maps repository context directly to all major developer tools
     <div class="card-title">📈 Migration Playbook</div>
     <div class="card-desc">Upgrade older workspaces to v1.1.0 standards cleanly.</div>
   </a>
-  <a href="/v1-checklist" class="card-item">
-    <div class="card-title">🏁 Release Checklist</div>
-    <div class="card-desc">Audit repository compliance with the strict release quality gates.</div>
+  <a href="/v2-release-checklist" class="card-item">
+    <div class="card-title">🏁 v2 Release Checklist</div>
+    <div class="card-desc">Audit repository compliance with the strict v2 release quality gates.</div>
   </a>
   <a href="/llms.txt" class="card-item" target="_blank">
     <div class="card-title">🤖 AI Discovery (llms.txt)</div>

package/docs/npm-publishing.md

@@ -12,13 +12,13 @@ Before publishing, always test the built package locally by compiling a compress
    ```bash
    npm pack
    ```
-   This creates a file named like `multimodel-dev-os-0.3.0.tgz` in your directory root.
+   This creates a file named like `multimodel-dev-os-2.0.1.tgz` in your directory root.
 
 2. **Verify bundle contents:**
    Create an empty temporary workspace, extract the tarball, and confirm that only required scaffold folders are included (no `.github/`, test configurations, or local system files):
    ```bash
    mkdir -p /tmp/package-test && cd /tmp/package-test
-   tar -xzf /path/to/multimodel-dev-os-0.3.0.tgz
+   tar -xzf /path/to/multimodel-dev-os-2.0.1.tgz
    ls -la package/
    ```
 
@@ -61,34 +61,34 @@ Execute these validation actions strictly in sequence before triggering a releas
 ## 3. Versioning & Rollback Strategy
 
 * **Semantic Versioning (SemVer) Discipline:**
-  * **Patch Release (e.g. 0.3.1):** Backward-compatible bug fixes or documentation updates.
-  * **Minor Release (e.g. 0.4.0):** Backward-compatible new features (like new adapter sync mechanisms).
-  * **Major Release (e.g. 1.0.0):** Breaking changes to core specification files.
+   * **Patch Release (e.g. 2.0.1):** Backward-compatible bug fixes or documentation updates.
+   * **Minor Release (e.g. 2.1.0):** Backward-compatible new features (like new adapter sync mechanisms).
+   * **Major Release (e.g. 3.0.0):** Breaking changes to core specification files.
 
 * **Rollback & Deprecation Guidelines:**
-  * Since published versions cannot be republished or overwritten, **never unpublish** unless absolutely necessary.
-  * If a critical bug is discovered, immediately publish a new patch version (e.g. `v0.3.1`).
-  * If a version is broken, flag it as deprecated to inform downstream installers:
-    ```bash
-    npm deprecate multimodel-dev-os@0.3.0 "Critical bug found, please use v0.3.1 instead."
-    ```
+   * Since published versions cannot be republished or overwritten, **never unpublish** unless absolutely necessary.
+   * If a critical bug is discovered, immediately publish a new patch version (e.g. `v2.0.1`).
+   * If a version is broken, flag it as deprecated to inform downstream installers:
+     ```bash
+     npm deprecate multimodel-dev-os@2.0.0 "Critical bug found, please use v2.0.1 instead."
+     ```
 
 ---
 
-## 4. Prepublish Safety Guard (v2.0.0 Stable)
+## 4. Prepublish Safety Guard (v2.0.1 Stable)
 
 > [!IMPORTANT]
-> **v2.0.0 is the active stable release.** NPM publishing is no longer paused.
+> **v2.0.1 is the active stable release.** NPM publishing is no longer paused.
 
 ### Source vs. Registry Strategy
-* **GitHub main branch (Source)**: Contains the current stable `v2.0.0` codebase.
+* **GitHub main branch (Source)**: Contains the current stable `v2.0.1` codebase.
 * **npm latest (Registry)**: Pulled and installed globally or via npx.
 
 ### Prepublish Safety Guard
 To prevent accidental `npm publish` executions on developer environments, a local validation script has been added to package hooks. If you run `npm publish`, it is blocked by default.
 
-To bypass this check during the approved `v2.0.0` release window:
-1. Ensure the version in `package.json` starts with `2.` (e.g. `2.0.0`).
+To bypass this check during approved release windows:
+1. Ensure the version in `package.json` starts with `2.` (e.g. `2.0.1`).
 2. Run publication with the override env variable:
    ```powershell
    # PowerShell

package/docs/public/llms-full.txt

@@ -1,4 +1,4 @@
-# MultiModel Dev OS — Comprehensive AI Assistant Discoverability Guide (v2.0.0 Stable Release)
+# MultiModel Dev OS — Comprehensive AI Assistant Discoverability Guide (v2.0.1 Stable Release)
 
 MultiModel Dev OS is a repository-level porting specification designed to align context and instructions across diverse developer tools and AI models.
 

package/docs/public/llms.txt

@@ -1,4 +1,4 @@
-# MultiModel Dev OS (v2.0.0 Stable Release)
+# MultiModel Dev OS (v2.0.1 Stable Release)
 
 Portable, vendor-neutral workspace configuration standard for multi-agent AI pair-programming workflows.
 

package/docs/public/sitemap.xml

@@ -61,8 +61,58 @@
     <priority>0.6</priority>
   </url>
   <url>
-    <loc>https://rizvee.github.io/multimodel-dev-os/v1-checklist</loc>
+    <loc>https://rizvee.github.io/multimodel-dev-os/v2-release-checklist</loc>
     <changefreq>weekly</changefreq>
     <priority>0.6</priority>
   </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/model-routing</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/local-models</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/provider-strategy</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/agent-compatibility</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/adapter-authoring</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/template-authoring</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/skill-authoring</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/v2-migration</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/package-safety</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/registry-contribution</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
 </urlset>

package/docs/quickstart.md

@@ -8,7 +8,7 @@ Get the MultiModel Dev OS integrated into your codebase in under 2 minutes to sy
 
 ## Option A: NPX Scaffolding (Stable Packages)
 
-Initialize any project instantly using our public npm registry. Note that this pulls the latest stable npm-published release (`v2.0.0`):
+Initialize any project instantly using our public npm registry. Note that this pulls the latest stable npm-published release (`v2.0.1`):
 
 ```bash
 # Standard interactive initialization in the current directory
@@ -49,18 +49,13 @@ curl -fsSL https://raw.githubusercontent.com/rizvee/multimodel-dev-os/main/scrip
 
 ---
 
-## Option D: Node.js Local Scaffolding CLI (Direct Run)
+## Option D: Scaffold Target Directory (NPX Direct)
 
-If you prefer to run directly from cloned source without global installation:
+If you prefer to initialize a target project path directly:
 
-1. Clone this repository locally:
-   ```bash
-   git clone https://github.com/rizvee/multimodel-dev-os.git
-   ```
-2. Run the CLI directly from the cloned repository source:
-   ```bash
-   node bin/multimodel-dev-os.js init --target /path/to/your-project --template nextjs-saas --adapter cursor
-   ```
+```bash
+npx multimodel-dev-os@latest init --target /path/to/your-project --template nextjs-saas --adapter cursor
+```
 
 ---
 
@@ -82,13 +77,10 @@ You can run our strict validation check or advisory doctor checkup to validate s
 
 ```bash
 # Strict directory schema validation
-node bin/multimodel-dev-os.js validate
+npx multimodel-dev-os validate
 
 # Advisory doctor workspace compatibility audit
-node bin/multimodel-dev-os.js doctor
-
-# Verify repository structure checks
-npm run verify
+npx multimodel-dev-os doctor
 ```
 
 Explore our canonical [Stable Protocol Specification](/stable-protocol) or [Upgrade & Migration Guide](/migration-guide) for details.

package/docs/release-policy.md

@@ -34,26 +34,9 @@ No package shall be merged or released without:
 
 ---
 
-## 4. NPM Publishing Pause & Roadmap Development
-
-To ensure high stability and thorough testing of the Template Galaxy and Model Compatibility Layers, package publishing to the public npm registry is paused during all `v1.2.x` minor releases:
-* **GitHub Repository (Source)**: Serve as the primary, active source branch containing unreleased v1.2+ features (such as template extensions, model registries, and CLI expansions).
-* **NPM Registry (Latest)**: Remains on the last approved stable version.
-* **v2.0.0 (Next Target)**: Will serve as the next stable release published to the npm registry, packaging the hardened registries and Template Galaxy features.
-
-### Local Source & Verification Procedures
-
-Contributors and developers must verify and test unreleased `v1.2.x` features locally rather than running publication steps:
-1. **Execute commands from the source binary:**
-   ```bash
-   node bin/multimodel-dev-os.js init
-   node bin/multimodel-dev-os.js verify
-   ```
-2. **Compile and test the package bundle locally:**
-   ```bash
-   npm pack
-   ```
-   This generates a local `.tgz` archive. Install it in a target test project to run validations.
-
-Never execute `npm publish` in the main workspace unless actively packaging the approved `v2.0.0` release.
+## 4. Release Channel & Staging Controls
 
+MultiModel Dev OS releases new versions directly to the public NPM registry:
+*   **Stable Releases (`npx multimodel-dev-os`)**: Published to the public registry under semantic version categories (e.g. `2.0.0`, `2.0.1`).
+*   **Release Candidates**: Built and validated locally via the automated verification script (`scripts/verify.js`) before tags or packaging runs.
+*   **Staging Verification**: To test new configurations prior to publishing, package the bundle locally (`npm pack`) and run CLI checkups in clean test directories.

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
 ```
 
 ---

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.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "multimodel-dev-os",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "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.0.1"
 $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.0.1"
 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);
 }