multimodel-dev-os 2.0.0 → 2.6.0

package/docs/improvement-proposals.md

@@ -0,0 +1,70 @@
+# Codebase Improvement Proposals
+
+MultiModel Dev OS supports structured codebase optimization and refactoring proposals via a secure, proposal-based self-improvement pipeline.
+
+---
+
+## 1. Safety Principles
+
+To guarantee repository integrity and prevent unintended changes, all self-improvement operations adhere to three core rules:
+1.  **Write-Protection**: The CLI binary, security guards, workflows, and core policies are read-only and cannot be modified by model proposals.
+2.  **Human-in-the-Loop (HITL)**: Models cannot write code directly to the workspace without explicit user verification.
+3.  **Proposal-Only Modifications**: The proposal engine compiles ideas without applying edits directly.
+
+---
+
+## 2. Proposal-Review Cycle
+
+The workflow follows these stages:
+
+### Stage A: Proposal Generation
+Run the following command to check codebase context and write a proposal:
+```bash
+npx multimodel-dev-os improve propose --title "Fix unignored config files"
+```
+This generates a markdown file under `.ai/proposals/proposal-YYYYMMDD-HHMMSS.md` containing Frontmatter metadata and markdown explanation.
+
+### Stage B: Human Review
+The developer runs the review command to inspect active proposals:
+```bash
+npx multimodel-dev-os improve review
+```
+This prints a summary table of pending, approved, and rejected proposals.
+
+To see aggregates of proposal statuses:
+```bash
+npx multimodel-dev-os improve status
+```
+
+## 3. Proposal Execution
+
+Once a proposal is reviewed, you can execute it in one of two ways:
+
+### A. Automated Application (Recommended)
+Starting in v2.4.1, approved proposals with machine-applicable operation blocks can be executed automatically:
+1. Edit the frontmatter metadata block to set `approval_status` to `approved`.
+2. Validate the proposal and its safety boundaries:
+   ```bash
+   npx multimodel-dev-os improve validate .ai/proposals/proposal-xxxx.md
+   ```
+3. Preview planned changes using the dry-run diff command:
+   ```bash
+   npx multimodel-dev-os improve diff .ai/proposals/proposal-xxxx.md
+   ```
+4. Deterministically apply changes to the repository:
+   ```bash
+   npx multimodel-dev-os improve apply .ai/proposals/proposal-xxxx.md --approved
+   ```
+
+For detailed specifications on safety gates, allowed operations, and audit logs, see the [Approved Proposal Application Guide](/approved-proposal-apply).
+
+### B. Manual Implementation
+For proposals containing vague instructions or complex edits without structured operation blocks:
+1. Manually implement and verify the code edits within your workspace.
+2. Edit the frontmatter metadata block to set `approval_status` to `approved` to archive.
+
+---
+
+## Command Center Integration
+
+The [Repository Command Center](repository-command-center.md) displays active proposal counts (pending, approved, and rejected) and provides a recommended command if pending proposals are waiting for review. You can run `mmdo status` to get a quick overview of your self-improvement status.

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/learning-rules.md

@@ -0,0 +1,36 @@
+# Learning Rules and Feedback Loop
+
+MultiModel Dev OS captures developer corrections and instruction overrides to compile reusable system rules that refine subsequent agent proposal generations.
+
+---
+
+## 1. Feedback Loop Commands
+
+### 1. Log Feedback
+To log a design preference or instruction override, run:
+```bash
+npx multimodel-dev-os feedback add "Prefer vanilla CSS or CSS Modules in legacy components" --type preference --tags styling --files "src/components/legacy/*"
+```
+This logs a structured JSON entry to `.ai/intelligence/feedback-log.jsonl`.
+
+### 2. List Logged Feedback
+To view all feedback entries in a formatted list:
+```bash
+npx multimodel-dev-os feedback list
+```
+
+### 3. Summarize Feedback
+To compile the raw feedback log into instructions that agents read:
+```bash
+npx multimodel-dev-os feedback summarize
+```
+This aggregates the logs by type and writes `.ai/intelligence/learning-rules.md`.
+
+---
+
+## 2. Context Ingestion by Agents
+
+Prior to generating proposals or refactoring components:
+1. Model agents read `.ai/intelligence/learning-rules.md` as context.
+2. The rules act as prompt constraints matching specific file target patterns.
+3. This prevents agents from repeating previously corrected mistakes.

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.6.0 Stable Release)
 
 MultiModel Dev OS is a repository-level porting specification designed to align context and instructions across diverse developer tools and AI models.
 
@@ -38,13 +38,43 @@ The protocol decouples the centralized workspace context from the individual too
 
 All compliant MultiModel Dev OS CLIs strictly enforce the following command contracts:
 - **`init`**: Scaffolds the standard `.ai/` context configuration directories. Supports `--template`, `--caveman`, `--adapter`, and dynamic registries mapping.
+- **`status`**: Displays a compact project intelligence dashboard summarizing package details, frameworks, memory freshness, feedback logs, improvement proposals, and audit execution metrics.
+- **`scan`**: Performs a read-only codebase scan to detect frameworks, package managers, MultiModel Dev OS configurations, and potential context-bloat or security risks.
+- **`onboard`**: Safely integrates MultiModel Dev OS into existing repositories. Subcommands:
+  - `analyze`: Scans repository structure, frameworks, languages, and risk markers. Read-only.
+  - `recommend`: Runs scanner diagnostics and recommendations for templates and adapters. Read-only.
+  - `plan`: Generates onboarding plan `.ai/intelligence/onboarding.plan.json` and report `.ai/intelligence/onboarding.report.md`. Read-only.
+  - `apply`: Copies configuration templates to target directory. Overwrites require `--force` and automatically generate backups.
+  - `status`: Show progress and completeness percentage dashboard.
+- **`adapter`**: Manage and sync rule/settings files for IDE adapters. Subcommands:
+  - `status`: Show rules files status and enable/disable states from config.
+  - `diff <adapter>`: Show rules diff between bundled template and target root file.
+  - `sync <adapter|all>`: Synchronizes rule files (requires `--approved`). Overwrites require `--force` and automatically generate backups.
+- **`memory`**: Compiles or reviews codebase hash-compressed memory. Subcommands:
+  - `build`: Scans target codebase and writes memory metadata to `.ai/intelligence/memory.hash.json` and `.ai/intelligence/memory.summary.md`.
+  - `refresh`: Incremental update comparing changed file hashes to update the memory files.
+  - `diff`: Prints added, removed, or changed files compared to `memory.hash.json` without executing writes.
+- **`feedback`**: Manage developer feedback loops. Subcommands:
+  - `add`: Logs raw developer feedback to `feedback-log.jsonl`.
+  - `list`: Lists logged feedback entries.
+  - `summarize`: Compiles feedback entries into `learning-rules.md`.
+- **`improve`**: Manage codebase self-improvement proposals. Subcommands:
+  - `propose`: Scans context and writes a proposal file under `.ai/proposals/`.
+  - `review`: Lists proposals and their active statuses.
+  - `status`: Shows aggregates of proposal statuses.
+  - `validate`: Validate proposal safety gates and operations block.
+  - `diff`: Preview proposed changes in unified diff format without modifying files.
+  - `apply`: Deterministically apply approved operations to the target codebase (requires `--approved`).
+  - `log`: Display Applied Proposals Audit Log execution history.
+- **`workflow`**: Orchestrate read-only development workflows (list, show, plan, run). Steps are restricted to safe, non-destructive CLI functions.
+- **`handoff`**: Compile token-compressed session context (build, show) at `.ai/intelligence/handoff.md` to transfer state to a new agent or model session.
 - **`verify`**: Automated release script that checks structure integrity.
 - **`templates`**: Lists built-in template profiles (supports overrides via `--registry <path>`).
 - **`validate`**: Strict Quality Gate checking the layout rules on disk (supports `--all-registries`).
 - **`validate-template`**: Scans a template registry entry and source directory structure for completeness.
 - **`validate-adapter`**: Audits an adapter config file and directory setup compliance.
 - **`validate-skill`**: Checks a custom skill file against standard Markdown headers.
-- **`doctor`**: Advisory checkup auditing ignored folders and token footprint (supports `--tokens` and `--release`).
+- **`doctor`**: Advisory checkup auditing ignored folders and token footprint (supports `--tokens`, `--release`, `--intelligence`, and `--onboarding`).
 
 ---
 

package/docs/public/llms.txt

@@ -1,10 +1,51 @@
-# MultiModel Dev OS (v2.0.0 Stable Release)
+# MultiModel Dev OS (v2.6.0 Stable Release)
 
 Portable, vendor-neutral workspace configuration standard for multi-agent AI pair-programming workflows.
 
-## Fast Setup (Stable npm @latest)
+## Fast Setup & Commands (Stable npm @latest)
 ```bash
+# Initialize workspace
 npx multimodel-dev-os@latest init
+
+# Scan codebase signals & check status
+npx multimodel-dev-os@latest scan
+npx multimodel-dev-os@latest status
+
+# Onboard existing repositories safely
+npx multimodel-dev-os@latest onboard analyze
+npx multimodel-dev-os@latest onboard recommend
+npx multimodel-dev-os@latest onboard plan
+npx multimodel-dev-os@latest onboard apply --approved
+npx multimodel-dev-os@latest onboard status
+
+# Manage and sync IDE adapter configuration files
+npx multimodel-dev-os@latest adapter status
+npx multimodel-dev-os@latest adapter diff cursor
+npx multimodel-dev-os@latest adapter sync cursor --approved
+
+# Build/refresh memory index
+npx multimodel-dev-os@latest memory build
+npx multimodel-dev-os@latest memory refresh
+
+# Run automated workflow cycles
+npx multimodel-dev-os@latest workflow run repo-health
+npx multimodel-dev-os@latest workflow list
+
+# Compile session handoff spec
+npx multimodel-dev-os@latest handoff build
+npx multimodel-dev-os@latest handoff show
+
+# Manage developer feedback loop
+npx multimodel-dev-os@latest feedback add "Avoid Tailwind CSS" --type preference
+npx multimodel-dev-os@latest feedback summarize
+
+# Draft, review, validate, and apply codebase improvement proposals
+npx multimodel-dev-os@latest improve propose --title "Fix config issues"
+npx multimodel-dev-os@latest improve review
+npx multimodel-dev-os@latest improve validate .ai/proposals/proposal-xxxx.md
+npx multimodel-dev-os@latest improve diff .ai/proposals/proposal-xxxx.md
+npx multimodel-dev-os@latest improve apply .ai/proposals/proposal-xxxx.md --approved
+npx multimodel-dev-os@latest improve log
 ```
 
 ## Supported Tools

package/docs/public/sitemap.xml

@@ -61,8 +61,88 @@
     <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>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/future-proof-architecture</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/self-improving-codebase</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/hash-compressed-memory</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/feedback-learning</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/capability-registry</loc>
+    <changefreq>weekly</changefreq>
+    <priority>0.7</priority>
+  </url>
+  <url>
+    <loc>https://rizvee.github.io/multimodel-dev-os/tool-registry</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
+```
 
 ---
 
@@ -78,17 +73,20 @@ If you prefer to run directly from cloned source without global installation:
 
 ## Verify & Diagnose
 
-You can run our strict validation check or advisory doctor checkup to validate structural health:
+Validate structural health, run codebase scans, and build hash-compressed memory:
 
 ```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
+npx multimodel-dev-os doctor
+
+# Advisory codebase scanner
+npx multimodel-dev-os scan
 
-# Verify repository structure checks
-npm run verify
+# Build codebase memory index
+npx multimodel-dev-os memory build
 ```
 
 Explore our canonical [Stable Protocol Specification](/stable-protocol) or [Upgrade & Migration Guide](/migration-guide) for details.

package/docs/real-repo-onboarding.md

@@ -0,0 +1,27 @@
+# Onboarding Existing Repositories
+
+MultiModel Dev OS provides a safe, step-by-step onboarding protocol to configure coding agents in any existing codebase without modifying application source files.
+
+## Onboarding Commands
+
+To onboard an existing repository, run the following commands:
+
+```bash
+# 1. Analyze the project structure, language, framework, and security signals
+npx multimodel-dev-os onboard analyze --target .
+
+# 2. Output template recommendations and suggested next steps
+npx multimodel-dev-os onboard recommend --target .
+
+# 3. Generate a structured onboarding plan and markdown report
+npx multimodel-dev-os onboard plan --target .
+
+# 4. Safely apply the onboarding plan to generate AI Dev OS scaffolding
+npx multimodel-dev-os onboard apply --target . --approved
+```
+
+## Security & Safety Guarantees
+
+* **Read-only Commands**: `analyze`, `recommend`, and `plan` are read-only and make no modifications.
+* **No Source Code Mutation**: `apply` only creates/updates MultiModel Dev OS configuration files (`.ai/`, `AGENTS.md`, `MEMORY.md`, etc.). It never touches your application source code.
+* **Backup Support**: If a file already exists, the onboard engine skips it. To overwrite, use `--force`, which creates a `.bak` backup file first.

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/repository-command-center.md

@@ -0,0 +1,52 @@
+# Repository Command Center Guide
+
+The **Repository Command Center** introduced in `v2.5.0` provides a unified, read-only operational dashboard summarizing the entire repository intelligence status of a MultiModel Dev OS workspace.
+
+---
+
+## 1. Using the `status` Command
+
+The `status` command allows developers and AI agents to instantly check project health and progress.
+
+```bash
+npx multimodel-dev-os status
+```
+
+Or target a specific subdirectory:
+
+```bash
+npx multimodel-dev-os status --target ./some-subproject
+```
+
+### Dashboard View
+
+Running `status` prints a formatted, color-coded status summary:
+
+1.  **Project Info**: Displays the package name and package version from the root `package.json`.
+2.  **Framework & Dependency Signals**: Summarizes detected languages, framework engines (e.g. Next.js, Express, React), and package lockfiles (e.g. `package-lock.json`).
+3.  **Memory State**:
+    *   `CURRENT` (Green): Memory index is fully built and matches the filesystem.
+    *   `STALE` (Yellow): Modifications have been made. Lists number of added, removed, or modified files.
+    *   `MISSING` (Red): No memory files have been built yet.
+4.  **Feedback Loop & Rules**: Displays total count of developer feedback entries and whether compiled learning rules are active.
+5.  **Improvement Proposals**: Lists total optimization proposals, categorized by approval status (`pending`, `approved`, `rejected`).
+6.  **Apply Audit Log**: Counts applied proposal runs.
+7.  **Next Recommended Command**: Offers dynamic advice on what to execute next (e.g., refreshing memory, review proposals, running health checks).
+
+---
+
+## 2. Benefits for Multi-Agent Workflows
+
+*   **Context Discovery**: Instantly summarizes active templates, environment structures, and boundaries.
+*   **Zero-Dependency Parsing**: Fast initialization checks that don't load external libraries.
+*   **Actionable Next Steps**: Guides developers and AI models to the correct command sequence, preventing execution drift.
+
+## 3. Onboarding Status
+
+For uninitialized repositories, you can inspect the onboarding status directly:
+
+```bash
+npx multimodel-dev-os onboard status
+```
+
+This prints a checklist of crucial MultiModel Dev OS files and an overall completeness percentage score.

package/docs/self-improving-codebase.md

@@ -0,0 +1,46 @@
+# Self-Improving Codebase Operations
+
+MultiModel Dev OS supports codebase refactoring, styling, and structural optimizations through a secure, proposal-based self-improvement pipeline.
+
+---
+
+## 1. Safety Principles
+
+To guarantee repository integrity and prevent unintended changes, all self-improvement operations adhere to three core rules:
+1.  **Write-Protection**: The CLI binary, security guards, workflows, and core policies are read-only and cannot be modified by model proposals.
+2.  **Human-in-the-Loop (HITL)**: Models cannot write code directly to the workspace without explicit user verification.
+3.  **Diff-Validated Execution**: Every modification must pass local verification tests, with manual commit approval.
+
+---
+
+## 2. Proposal-Review Cycle
+
+The execution path follows two stages:
+
+### Stage A: Proposal Generation
+Before compiling a proposal, the agent scans the codebase using `mmdo scan` and builds the hash-compressed memory index via `mmdo memory build` to ensure the proposal is context-aware and token-efficient. The agent then identifies an optimization and saves a structured document under `.ai/proposals/proposal-YYYYMMDD-HHMMSS.md`. The proposal specifies the rationale, affected files list, risk level, test command, and rollback steps.
+
+### Stage B: Human Review
+The developer runs the review CLI command:
+```bash
+npx multimodel-dev-os improve review
+```
+This shows the proposed changes, affected files, risk levels, and verify commands.
+
+To view status:
+```bash
+npx multimodel-dev-os improve status
+```
+
+*Note: Starting in v2.4.1, automated proposal application is supported via the `improve apply` command, provided that a valid operations JSON block exists in the proposal file and the developer passes the `--approved` flag. Vague proposals or those targeting protected files/paths must still be executed manually.*
+
+For complete automated application details, please refer to the [Approved Proposal Application Guide](/approved-proposal-apply).
+
+---
+
+## Command Center Integration
+
+The [Repository Command Center](repository-command-center.md) serves as the unified dashboard for the self-improvement loop. Running `mmdo status` displays the counts of pending/approved/rejected proposals, memory state, and feedback logs. Developers can orchestrate the review cycle safely by executing the `proposal-review` workflow:
+```bash
+npx multimodel-dev-os workflow run proposal-review
+```

package/docs/template-recommendation.md

@@ -0,0 +1,22 @@
+# Template Recommendation Engine
+
+The recommendation engine matches existing codebases to the best-fit template profile.
+
+## Heuristics & Confidence Scores
+
+The engine assigns weights to file signatures and package dependencies:
+
+* **Next.js SaaS (`nextjs-saas`)**: Matches if `next.config.js` or `next.config.ts` is present (Weight: +0.6) or `package.json` contains `next` dependency (Weight: +0.4).
+* **Android Expo Mobile (`expo-react-native-android`)**: Matches if `app.json` or `eas.json` is present (Weight: +0.8).
+* **WordPress Theme/Plugin (`wordpress-theme-plugin`)**: Matches if `wp-content` directory or header-decorated PHP style files are found (Weight: +0.8).
+* **E-Commerce Store (`ecommerce-store`)**: Matches if Stripe, Shopify, or checkout-related dependencies are present (Weight: +0.4).
+* **SEO Landing Page (`seo-landing-page`)**: Matches if raw HTML files + Tailwind configs exist without framework elements (Weight: +0.5).
+* **General App (`general-app`)**: Serves as the fallback profile if no other template achieves a confidence score greater than 0.4.
+
+## Command
+
+To check template recommendations for your project:
+
+```bash
+npx multimodel-dev-os onboard recommend --target .
+```