multimodel-dev-os 1.0.0 → 2.0.0

package/docs/.vitepress/config.js

@@ -3,6 +3,40 @@ export default {
   title: 'MultiModel Dev OS',
   description: 'Portable, vendor-neutral AI Developer OS for multi-agent coding workflows.',
   ignoreDeadLinks: true,
+  head: [
+    ['link', { rel: 'icon', href: '/multimodel-dev-os/favicon.png', type: 'image/png' }],
+    ['link', { rel: 'canonical', href: 'https://rizvee.github.io/multimodel-dev-os/' }],
+    ['meta', { name: 'theme-color', content: '#6366f1' }],
+    ['meta', { name: 'robots', content: 'index, follow' }],
+    ['meta', { name: 'application-name', content: 'MultiModel Dev OS' }],
+    ['meta', { name: 'apple-mobile-web-app-title', content: 'MultiModel Dev OS' }],
+    ['meta', { property: 'og:title', content: 'MultiModel Dev OS' }],
+    ['meta', { property: 'og:description', content: 'Portable AI Dev OS for Codex, Antigravity, Cursor, Claude, Gemini, VS Code, and multimodel coding workflows.' }],
+    ['meta', { property: 'og:image', content: 'https://rizvee.github.io/multimodel-dev-os/assets/social-preview.svg' }],
+    ['meta', { property: 'og:url', content: 'https://rizvee.github.io/multimodel-dev-os/' }],
+    ['meta', { property: 'og:type', content: 'website' }],
+    ['meta', { name: 'twitter:card', content: 'summary_large_image' }],
+    ['meta', { name: 'twitter:title', content: 'MultiModel Dev OS' }],
+    ['meta', { name: 'twitter:description', content: 'Portable AI Dev OS for Codex, Antigravity, Cursor, Claude, Gemini, VS Code, and multimodel coding workflows.' }],
+    ['meta', { name: 'twitter:image', content: 'https://rizvee.github.io/multimodel-dev-os/assets/social-preview.svg' }],
+    [
+      'script',
+      { type: 'application/ld+json' },
+      JSON.stringify({
+        '@context': 'https://schema.org',
+        '@type': 'SoftwareApplication',
+        'name': 'MultiModel Dev OS',
+        'applicationCategory': 'DeveloperApplication',
+        'operatingSystem': 'Windows, macOS, Linux',
+        'programmingLanguage': 'JavaScript',
+        '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',
+        'description': 'Portable, vendor-neutral AI Developer OS for multi-agent coding workflows.'
+      })
+    ]
+  ],
   themeConfig: {
     logo: '/logo.png',
     nav: [
@@ -28,10 +62,44 @@ export default {
           { text: 'Stable Protocol Specification', link: '/stable-protocol' },
           { text: 'Adapter Compatibility', link: '/compatibility' },
           { text: 'Upgrades & Migration', link: '/migration-guide' },
+          { text: 'v2 Migration Guide', link: '/v2-migration' },
+          { text: 'v2 Release Checklist', link: '/v2-release-checklist' },
+          { text: 'Package Safety', link: '/package-safety' },
           { text: 'Templates QA Blueprint', link: '/template-qa' },
           { text: 'v1.0.0 Readiness Checklist', link: '/v1-readiness' }
         ]
       },
+      {
+        text: 'Model Compatibility Layer',
+        items: [
+          { text: 'Model Capabilities Registry', link: '/model-compatibility' },
+          { text: 'Model Routing & Presets', link: '/model-routing' },
+          { text: 'Local & Offline Models', link: '/local-models' },
+          { text: 'API Provider Strategy', link: '/provider-strategy' }
+        ]
+      },
+      {
+        text: 'Agent & IDE Extensions',
+        items: [
+          { text: 'Agent Compatibility Mappings', link: '/agent-compatibility' },
+          { text: 'Custom Adapters Guide', link: '/adapter-authoring' },
+          { text: 'Template Authoring Guide', link: '/template-authoring' },
+          { text: 'Skill Authoring Guide', link: '/skill-authoring' },
+          { text: 'Registry Contribution Guide', link: '/registry-contribution' }
+        ]
+      },
+      {
+        text: 'Mobile Integration & Delivery',
+        items: [
+          { text: 'Expo Android Delivery', link: '/mobile-android' }
+        ]
+      },
+      {
+        text: 'Token Cost Optimization',
+        items: [
+          { text: 'Token Budgets & Optimization', link: '/token-optimization' }
+        ]
+      },
       {
         text: 'Case Studies & Playbooks',
         items: [
@@ -74,6 +142,7 @@ export default {
           { text: 'Public Launch Checklist', link: '/launch-checklist' },
           { text: 'Release Playbook Template', link: '/release-template' },
           { text: 'CLI Roadmap', link: '/cli-roadmap' },
+          { text: 'v2.0.0 Roadmap', link: '/v2-roadmap' },
           { text: 'NPM Publishing Runbook', link: '/npm-publishing' },
           { text: 'Pre-flight Release Testing', link: '/testing-v0.2' },
           { text: 'Release Policy', link: '/release-policy' },

package/docs/adapter-authoring.md

@@ -0,0 +1,46 @@
+# Custom IDE Adapter Authoring Guide
+
+MultiModel Dev OS is fully extensible. Developers and teams can build custom adapters to route protocol directives to new IDE interfaces, command-line coding agents, or company-proprietary AI environments.
+
+---
+
+## Authoring Workflow
+
+To construct a new adapter:
+
+### 1. Register the Adapter Metadata
+Open [.ai/adapters/registry.yaml](file:///F:/multimodel-dev-os/.ai/adapters/registry.yaml) and declare the adapter properties:
+```yaml
+adapters:
+  my-custom-agent:
+    name: "My Custom Agent"
+    config_file: ".mycustomrules"
+    type: "coding-agent"
+    docs: "docs/adapters/my-custom-agent.md"
+```
+
+### 2. Scaffold the Adapter Assets
+Create the adapter assets directory under `adapters/my-custom-agent/`:
+* **`adapters/my-custom-agent/setup.md`**: Guide for developers enabling this adapter.
+* **`adapters/my-custom-agent/.mycustomrules`**: Rule boilerplate template which contains variables (e.g. system prompts or build scripts references) to be copied to project root during CLI initialization.
+
+### 3. Register in CLI
+Open `bin/multimodel-dev-os.js` and extend the `handleInit` mapping:
+```javascript
+} else if (adapter === 'my-custom-agent') {
+  const srcFile = join(sourceRoot, 'adapters/my-custom-agent/.mycustomrules');
+  const destFile = join(options.target, '.mycustomrules');
+  if (existsSync(srcFile)) {
+    writeFileSync(destFile, readFileSync(srcFile));
+  }
+}
+```
+
+### 4. Verify Compliance
+Extend `scripts/verify.js` to ensure the new files are verified:
+```javascript
+checkFile('adapters/my-custom-agent/setup.md');
+checkFile('adapters/my-custom-agent/.mycustomrules');
+```
+
+Run `npm run verify` to confirm all assertions pass cleanly.

package/docs/agent-compatibility.md

@@ -0,0 +1,51 @@
+# Coding Agent & IDE Adapter Compatibility
+
+MultiModel Dev OS acts as an interoperability layer across modern developer agents, terminal assistants, and IDE extensions.
+
+---
+
+## Agent Registry Mapping
+Compatible configurations and destination files are detailed in [.ai/adapters/registry.yaml](file:///F:/multimodel-dev-os/.ai/adapters/registry.yaml):
+
+```yaml
+adapters:
+  continue:
+    name: "Continue"
+    config_file: ".continue/config.json"
+    type: "editor-extension"
+    docs: "docs/adapters.md"
+  cline:
+    name: "Cline"
+    config_file: ".clinerules"
+    type: "coding-agent"
+    docs: "docs/agent-compatibility.md"
+  roo-code:
+    name: "Roo Code"
+    config_file: ".clinerules"
+    type: "coding-agent"
+    docs: "docs/agent-compatibility.md"
+```
+
+---
+
+## Supported Agent Configurations
+
+### 1. Continue
+* **File Target**: `.continue/config.json`
+* **Workflow**: Integrates custom system prompts and routing matrices into the VS Code / JetBrains sidebar panel.
+
+### 2. Cline / Roo Code
+* **File Target**: `.clinerules`
+* **Workflow**: Feeds strict directory layout schemas and role assignments directly to agent context loops during project scans.
+
+### 3. Aider
+* **File Target**: `.aider.conf.yml`
+* **Workflow**: Centralizes exclude filters, auto-commit actions, and CLI test verification shortcuts.
+
+### 4. Windsurf
+* **File Target**: `.windsurfrules`
+* **Workflow**: Injects development constraints and build commands into the IDE context window.
+
+### 5. OpenHands / Terminal Agents
+* **File Target**: `CLAUDE.md` / `adapters/codex/AGENTS.md`
+* **Workflow**: Standardize shell execution targets and error-handling steps for autonomous agents.

package/docs/case-studies/index.md

@@ -1,6 +1,8 @@
-# Real-World Case Studies
+# Real-World Case Studies: AI Dev OS Integrations
 
-Explore how engineering teams and developers leverage `multimodel-dev-os` to prevent instruction drift, secure workspace boundaries, and save significant LLM token context budgets.
+Explore how engineering teams and developers leverage MultiModel Dev OS to prevent instruction drift, secure workspace boundaries, and save significant LLM token context budgets.
+
+> **Use when**: Designing a workflow for a specific tech stack (like Next.js SaaS schema synchronization, WordPress themes, headless checkout loops, or multi-model handoffs).
 
 ---
 
@@ -9,16 +11,18 @@ Explore how engineering teams and developers leverage `multimodel-dev-os` to pre
 Select a case study to see specific problems, setups, commands, outcomes, and reusable design patterns:
 
 ### 1. [Full-Stack Next.js SaaS](nextjs-saas.md)
-*Solving schema sync and inline autocompletion shifts across full-stack applications.*
+*Solving schema sync and inline autocompletion shifts across full-stack applications (Nextjs SaaS template / database schema synchronization).*
 
 ### 2. [WordPress Theme & Plugin Development](wordpress-site.md)
-*Securing PHP coding style conventions and folder overrides during local scaffolding.*
+*Securing PHP coding style conventions and folder overrides during local scaffolding (WordPress theme folder boundaries).*
 
 ### 3. [E-Commerce Webhooks & State Tracking](ecommerce-store.md)
-*Keeping payment routes and database event states strictly aligned between terminal-based models and editors.*
+*Keeping payment routes and database event states strictly aligned between terminal-based models and editors (e-commerce state webhooks).*
 
 ### 4. [SEO Landing Page Audits](seo-landing-page.md)
-*Managing multiple automated performance linter audits and SEO checkups.*
+*Managing multiple automated performance linter audits and SEO checkups (SEO landing page performance Core Web Vitals).*
 
 ### 5. [Multi-Model Handoff Protocols](multimodel-handoff.md)
-*Structuring sequential session logs to pass context between Claude Code and Gemini with zero token drops.*
+*Structuring sequential session logs to pass context between Claude Code and Gemini with zero token drops (Claude Gemini handoff logs).*
+
+Explore our [Stable Protocol Specification](/stable-protocol) or [Upgrade & Migration Guide](/migration-guide) for details.

package/docs/cli-roadmap.md

@@ -39,26 +39,23 @@ node bin/multimodel-dev-os.js verify
 | `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 |
 
-## Requirements Completed in v0.5.0
+> [!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.
 
-- [x] Implemented strict `validate` CLI command for structural directory validation.
-- [x] Implemented advisory `doctor` command for project compatibility warnings.
-- [x] Implemented `templates` and `show-template` commands for built-in profiles inspection.
-- [x] Upgraded all 5 built-in template profiles with practical real-world contents.
-- [x] Implemented dynamic context budgetary constraints and skills validation.
-- [x] Preserved zero-dependency pure Node CLI implementations.
+## CLI v2.0.0 Stabilization Goal
 
-## Future Releases (v0.6.0+)
+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.
 
-* **Adapter Autoregeneration (`sync`):** Parse custom override boundaries inside adapters and automatically synchronize them with updates in the root markdown source of truth.
-* **Interactive Mode:** Provide step-by-step CLI options if run without arguments.
-
-## Protocol Stabilization & v1.0.0 Freeze (v0.9.0)
-
-In version **v0.9.0**, we pivot the roadmap to focus on **stabilization and hardening** ahead of the official `v1.0.0` freeze:
-- **API Freeze:** The CLI syntax, standard command names (`init`, `verify`, `validate`, `doctor`, `templates`), and dynamic flags are frozen to ensure zero breaking changes in future minor patches.
-- **Robust JSON Schemas:** Added standard validators inside `.ai/schema/` to define config and template formats.
-- **Continuous Integration Gates:** Transitioning `validate` to serve as a strict build blocker for pulling and publishing code.
-- **Enhanced Warning Paths:** Hardened CLI error messaging when directory write conflicts occur, mapping absolute paths cleanly.
 

package/docs/compatibility.md

@@ -1,6 +1,8 @@
 # Compatibility & Customization Guide
 
-This document maps how `multimodel-dev-os` integrates across diverse IDEs and terminal utilities, detailing what parameters developers can customize without breaking the protocol.
+This document maps how MultiModel Dev OS integrates across diverse IDEs and terminal utilities, detailing what parameters developers can customize without breaking the protocol.
+
+> **Use when**: Setting up tool configurations (like Cursor project rules or Claude Code project instructions) or configuring the active adapter mappings in `.ai/config.yaml`.
 
 ---
 
@@ -37,6 +39,8 @@ To guarantee validation compliance:
 
 ---
 
-## 4. v1.0.0 Compatibility Guarantee
+## 4. v1.1.0 Compatibility Guarantee
+
+The supported tool matrix and custom specifications listed here represent the officially frozen contracts of MultiModel Dev OS `v1.1.0`. Any backward-compatible extensions introduced in subsequent `1.x` releases will build on top of these mappings without breaking current project integrations.
 
-The supported tool matrix and custom specifications listed here represent the officially frozen contracts of MultiModel Dev OS `v1.0.0`. Any backward-compatible extensions introduced in subsequent `1.x` releases will build on top of these mappings without breaking current project integrations.
+Explore our [Stable Protocol Specification](/stable-protocol) or [Upgrade & Migration Guide](/migration-guide) for details.

package/docs/cost-optimization.md

@@ -1,6 +1,8 @@
-# LLM Cost & Context Optimization Playbook
+# LLM Cost & Context Optimization Playbook (v1.1.0)
 
-Maximizing developer velocity while minimizing LLM prompt overhead and API billing budgets is a critical priority for engineering teams. This playbook maps 12 industry cost-reduction techniques directly to native `multimodel-dev-os` features.
+Maximizing developer velocity while minimizing LLM prompt overhead and API billing budgets is a critical priority for engineering teams. This playbook maps 12 industry cost-reduction techniques directly to native MultiModel Dev OS features.
+
+> **Use when**: Optimizing API token usage, configuring Caveman Mode settings, or designing modular prompt caching strategies.
 
 ---
 
@@ -59,3 +61,5 @@ Below is how the 12 core context optimization strategies are implemented inside
 ### 12. Embedding Hygiene
 - **The Strategy:** Ensure semantic search indexes only relevant source files instead of temporary distributions.
 - **Dev OS Implementation:** Strict routing specifications mapped inside `context-routing.md` and pre-configured `.gitignore` definitions protect search databases from index pollution.
+
+Explore our [Stable Protocol Specification](/stable-protocol) or [Upgrade & Migration Guide](/migration-guide) for details.

package/docs/faq.md

@@ -1,91 +1,67 @@
-# FAQ
+# FAQ: MultiModel Dev OS Questions & Answers
+
+Frequently asked questions regarding MultiModel Dev OS, AI coding agents compatibility, and prompt context optimization.
+
+> **Use when**: Resolving setup ambiguities, understanding comparative advantages over simple rules files, or auditing CLI validations.
+
+---
 
 ## General
 
-**What is multimodel-dev-os?**
-A set of markdown files and conventions that let multiple AI coding tools
-(Codex, Cursor, Claude, Gemini, Antigravity, VS Code) share the same
-project context. Not a runtime. Not an AI agent. Think `.editorconfig`
-but for AI tools.
+**What is MultiModel Dev OS?**
+A set of markdown templates and directory structures that allow multiple AI coding tools (Codex, Cursor, Claude Code, Gemini, Antigravity, VS Code) to share a single portable AI project context. It acts like `.editorconfig` but for AI assistants.
 
-**Is this an operating system?**
-No. "Dev OS" is a metaphor for the shared operating layer between tools.
-It's just markdown files in your repo.
+**Is this a runtime operating system?**
+No. It is a metaphorical "OS" providing standard files (`AGENTS.md`, `MEMORY.md`, `TASKS.md`, `RUNBOOK.md`) to coordinate multiple tools.
 
 **What does "multimodel" mean?**
-Multiple AI models/tools working on the same project.
-Not "multimodal" (multiple input types like text + image).
+Multiple distinct AI coding models/agents (such as Codex, Antigravity, Cursor, and Claude Code) operating sequentially on the exact same workspace branch.
+
+---
 
 ## Setup
 
 **Do I need Node.js?**
 It depends on your installation path:
-* **Yes:** If you run the primary, recommended `npx multimodel-dev-os@latest init` workflow, Node.js is required.
-* **No:** If you run the fallback automated shell installer scripts (`install.sh` or `install.ps1`), they run purely on native bash or PowerShell and download resources directly.
+* **Yes:** If you run the primary, recommended `npx multimodel-dev-os@latest init` workflow.
+* **No:** If you run the fallback bash (`install.sh`) or PowerShell (`install.ps1`) one-liners.
 
 **Why not just write a single manual AGENTS.md myself?**
-While you can write a raw markdown instruction file manually, `multimodel-dev-os` offers a standardized development environment:
-1. **Automated Bridging:** Rather than copying and pasting rules into `.cursorrules`, `CLAUDE.md`, `.vscode/settings.json`, and `.gemini/settings.json`, our adapters dynamically references your root source of truth.
-2. **Standardized Context Segregation:** Separates concerns cleanly (`MEMORY.md` for architectural context, `TASKS.md` for task state tracking, `RUNBOOK.md` for incident response, and `.ai/` for skills and prompts).
-3. **Structured Verification:** Pre-packaged CLI and verification scripts test and assert the structural completeness of your rules.
-4. **Token Savings:** Seamlessly switches into Caveman Mode to slash token footprints by **~79%** for smaller models.
-
-**Can I use just one AI tool?**
-Yes. Use a single adapter. The multi-agent features are optional.
+While you can write a raw markdown file, MultiModel Dev OS offers:
+1. **Automated Bridging:** Adapters dynamically map your root source to Cursor, Claude, and Gemini native rules.
+2. **Context Budgets:** Toggle **Caveman Mode** to slash prompt rules overhead by **~79%**.
+3. **Structured Verification:** Built-in CLI commands validate workspace specifications instantly.
 
-**Which files are required?**
-At minimum: `AGENTS.md`. Everything else is optional.
-The installer creates the full structure, but you can delete what you don't need.
+---
 
 ## Adapters
 
 **Do I copy adapter files to my project root?**
 Yes, for tools that auto-detect specific files:
-- Cursor → copy `.cursorrules` to root
-- Claude → copy `CLAUDE.md` to root
-- VS Code → copy `.vscode/` to root
+- Cursor → `.cursorrules`
+- Claude Code → `CLAUDE.md`
+- VS Code → `.vscode/settings.json`
 
-**My tool isn't listed. Can I add one?**
-Yes. See [docs/adapters.md](adapters.md) for the guide. PRs welcome.
-
-**Will adapters break if a tool changes its config format?**
-Possibly. Adapters are community-maintained. File an issue if you
-notice an adapter is outdated.
+---
 
 ## Caveman Mode
 
 **When should I use Caveman Mode?**
-When your context window is tight, your model is small, or you're
-optimizing for API cost. It cuts ~79% of tokens.
-
-**Can I mix standard and caveman files?**
-Yes. Each file is independent. You could have a standard `AGENTS.md`
-and a caveman `TASKS.md`.
-
-## Orchestrator
+**Best for**: Context optimization for AI coding when you are using compact context budget windows, smaller models, or want to save money on API bill parameters.
 
-**Does the orchestrator run agents automatically?**
-No, not in v0.1. It's a protocol spec — conventions for how agents
-should coordinate. Runtime orchestration is planned for v0.2+.
-
-**Do I need the orchestrator for single-agent workflows?**
-No. The orchestrator is only relevant when multiple agents work
-on the same codebase.
+---
 
 ## Diagnostics & Validation
 
 **What is the difference between `validate` and `doctor`?**
-* **`validate`** is strict and verifies that your workspace strictly complies with the multimodel-dev-os directory schema. It checks for the existence of core files/directories and ensures enabled adapter rule references are not broken. If any checks fail, it exits with an error status (exit code 1).
-* **`doctor`** is advisory. It inspects compatibility constraints, warning you about potential context bloat (e.g. missing `.gitignore` files or non-ignored build directories) or active rules missing matching files. It reports warnings without blocking execution.
+* **`validate`** is strict and verifies compliance with the directory schema.
+* **`doctor`** is advisory and warns you about large unignored directories or empty placeholders.
 
-**How do I view available scaffolding templates?**
-You can use `node bin/multimodel-dev-os.js templates` (or `list-templates`) to view all available tech stacks and detailed blueprints, or `show-template <name>` to inspect a specific template's specifications.
+---
 
 ## Protocol & Migration
 
 **Is the MultiModel Dev OS protocol stable?**
-Yes. As of version `v1.0.0`, the core specifications (Root Contracts Layer, `.ai/` settings configurations, and adapter file targets) are officially frozen and backward-compatible. This ensures that any codebase prepared using `v1.0.0` will operate seamlessly inside future `1.x` ecosystems.
-
-**How do I migrate my repository to v1.0.0?**
-Upgrading is straightforward. Refer to our [Upgrades & Migration Guide](migration-guide.md) to inspect directory shifts, execute strict validation checks (`npx multimodel-dev-os validate`), and audit compatibility issues.
+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.
 
+Explore our [Stable Protocol Specification](/stable-protocol) or [Upgrade & Migration Guide](/migration-guide) for details.

package/docs/final-launch.md

@@ -1,13 +1,16 @@
-# Final Launch Guidelines
+# Final Launch Guidelines (v2.0.0 Target)
 
-This document details the final launch guidelines and distribution routines for the public `v1.0.0` release of MultiModel Dev OS.
+This document details the final launch guidelines and distribution routines for the public releases of MultiModel Dev OS.
+
+> [!IMPORTANT]
+> **v2.0.0 is the active stable release.** NPM publishing is no longer paused. All Template Galaxy and Model Compatibility features are now available on the public registry.
 
 ---
 
 ## 1. Local Pre-flight Verification
 
-Prior to pushing files to the remote repository, ensure that:
-- The exact target version `1.0.0` is configured in `package.json`.
+Prior to pushing files or preparing a release, ensure that:
+- The exact target version starts with `2.` (e.g. `2.0.0`) in `package.json` for publishing, or remains at `1.2.0` for local development.
 - The cross-platform verify script completes cleanly:
   ```bash
   npm run verify
@@ -25,5 +28,8 @@ When publishing the stable release, communicate the key advantages clearly:
 - **Portability**: Write-once configurations working seamlessly across Cursor, Claude, Gemini, Antigravity, and VS Code.
 - **Context Economy**: Up to 79% reduction in prompt tokens through Caveman Mode configurations.
 - **Zero Dependencies**: A completely self-contained CLI for lightning-fast setups.
+- **AI Discoverability**: Ready-to-ingest discoverability guides (`llms.txt` / `llms-full.txt`) for LLM agents.
 
 Refer to `docs/launch-kit.md` for specific copy blocks ready for distribution on Twitter/X, LinkedIn, Hacker News, and Reddit.
+
+Explore our [Stable Protocol Specification](/stable-protocol) or [Upgrade & Migration Guide](/migration-guide) for details.

package/docs/index.md

@@ -71,6 +71,22 @@ features:
   font-size: 0.9rem;
   color: var(--vp-c-text-2);
 }
+.works-with-grid {
+  display: grid;
+  grid-template-columns: repeat(auto-fit, minmax(140px, 1fr));
+  gap: 1rem;
+  margin-top: 1.5rem;
+  margin-bottom: 2.5rem;
+}
+.works-with-item {
+  border: 1px solid var(--vp-c-bg-mute);
+  background-color: var(--vp-c-bg-soft);
+  border-radius: 6px;
+  padding: 1rem;
+  text-align: center;
+  font-weight: 500;
+  font-size: 0.95rem;
+}
 </style>
 
 ## Quick Start Setup
@@ -83,6 +99,21 @@ npx multimodel-dev-os@latest init
 
 ---
 
+## Works With
+
+MultiModel Dev OS maps repository context directly to all major developer tools and coding agents:
+
+<div class="works-with-grid">
+  <div class="works-with-item">🤖 Codex</div>
+  <div class="works-with-item">🪐 Antigravity</div>
+  <div class="works-with-item">🎯 Cursor</div>
+  <div class="works-with-item">⚡ Claude Code</div>
+  <div class="works-with-item">🧠 Gemini</div>
+  <div class="works-with-item">💻 VS Code</div>
+</div>
+
+---
+
 ## Core Specifications & Playbooks
 
 <div class="grid-container">
@@ -108,16 +139,28 @@ npx multimodel-dev-os@latest init
   </a>
   <a href="/migration-guide" class="card-item">
     <div class="card-title">📈 Migration Playbook</div>
-    <div class="card-desc">Upgrade older workspaces to v1.0.0 standards cleanly.</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>
+  <a href="/llms.txt" class="card-item" target="_blank">
+    <div class="card-title">🤖 AI Discovery (llms.txt)</div>
+    <div class="card-desc">A highly concise, structured overview formatted specifically for AI context ingestion.</div>
+  </a>
 </div>
 
 ---
 
+## For AI Assistants and Coding Agents
+
+To support modern AI search, GEO discovery, and developer agents:
+- We provide [llms.txt](/llms.txt) and [llms-full.txt](/llms-full.txt) at the root of the hosted documentation to allow Large Language Models and AEO utilities to read full workspace specs in single, token-optimized files.
+- The officially frozen protocol guarantees that agents can read and write workspace rules without manual supervision or instruction drift.
+
+---
+
 ## Cost & Context Optimization
 
 Minimize prompt overhead and API billing by mapping key context-reduction techniques to MultiModel Dev OS features:

package/docs/local-models.md

@@ -0,0 +1,48 @@
+# Local & Open-Weight Offline Models Guide
+
+MultiModel Dev OS supports offline development workflows utilizing open-weight models running on local developer hardware (via Ollama, Llama.cpp, or vLLM).
+
+---
+
+## Local Models Configuration
+Local model bindings are defined in [.ai/models/local-models.yaml](file:///F:/multimodel-dev-os/.ai/models/local-models.yaml):
+
+```yaml
+local_engines:
+  ollama:
+    base_url: "http://localhost:11434/v1"
+    models:
+      - alias: local-coder-model
+        official_id: qwen2.5-coder:7b
+      - alias: open-weight-reasoner
+        official_id: deepseek-r1:8b
+```
+
+---
+
+## Local Setup Instructions
+
+### 1. Using Ollama
+To spin up a local model runner and pull target coding weights:
+```bash
+# Install Ollama and run server
+ollama run qwen2.5-coder:7b
+
+# In another terminal tab, run MultiModel Dev OS verify
+node bin/multimodel-dev-os.js verify
+```
+
+### 2. Local fallback routing
+To configure local fallback when remote APIs are unavailable, set your primary model map to point to the local coder model:
+```yaml
+# .ai/context/model-map.md
+Planning: open-weight-reasoner
+Execution: local-coder-model
+```
+
+---
+
+## Benefits & Optimization
+* **Zero API Cost**: Local model queries carry no token charges.
+* **Privacy Compliance**: No code snippets or workspace context files leave the local host machine.
+* **Offline-Ready**: Develop and build applications on flights or remote zones with zero internet dependencies.