codymaster 4.8.0 → 5.2.0

package/scripts/postinstall.js

@@ -13,7 +13,7 @@ const fs = require('fs');
 const path = require('path');
 const { execSync, execFileSync } = require('child_process');
 
-let skillCount = 60;
+let skillCount = 68;
 try {
   const skillsDir = path.join(__dirname, '..', 'skills');
   if (fs.existsSync(skillsDir)) {
@@ -214,7 +214,6 @@ const showSkillGuide = (choice) => {
   }
 
   console.log('');
-  console.log(`${W}${BOLD}${isVi ? 'Nhấn ENTER để quay lại...' : 'Press ENTER to go back...'}${NC}`);
 };
 
 const printMenu = () => {
@@ -244,20 +243,11 @@ const printMenu = () => {
     console.log(`  ${C}⚙️ Operations${NC}    : Triển khai an toàn & Quản lý CI/CD`);
     console.log(`  ${C}📈 Growth${NC}        : Tối ưu chuyển đổi (CRO) & Tracking`);
     console.log('');
-    console.log(`    ${W}${BOLD}💡 Nhập số (1-12) để xem hướng dẫn & ví dụ:${NC}`);
+    console.log(`    ${W}${BOLD}🌟 Lệnh phổ biến:${NC}`);
     console.log('');
-    console.log(`   1. ${Y}Cách CodyMaster vận hành    ${NC} → cm-how-it-work`);
-    console.log(`   2. ${Y}Vibe coding (Zero code)     ${NC} → cm-start`);
-    console.log(`   3. ${Y}Tham gia dự án có sẵn       ${NC} → cm-brainstorm-idea`);
-    console.log(`   4. ${Y}Code giao diện từ URL/Ảnh   ${NC} → cm-ux-master`);
-    console.log(`   5. ${Y}Lập trình TDD & Pair code   ${NC} → cm-tdd`);
-    console.log(`   6. ${Y}Dọn dẹp & Tái cấu trúc      ${NC} → cm-clean-code`);
-    console.log(`   7. ${Y}Quét & Sửa lỗi bảo mật      ${NC} → cm-security-gate`);
-    console.log(`   8. ${Y}Viết tài liệu Docs & API    ${NC} → cm-dockit`);
-    console.log(`   9. ${Y}Tạo Landing Page "WOW"      ${NC} → cm-cro-methodology`);
-    console.log(`  10. ${Y}Bảng theo dõi tiến độ       ${NC} → cm dashboard`);
-    console.log(`  11. ${Y}Xem Demo tự động            ${NC} → /cm:demo`);
-    console.log(`  12. ${Y}Trợ giúp & Cú pháp lệnh      ${NC} → cm help`);
+    console.log(`   🔸 ${Y}Bảng tiến độ (Dashboard)    ${NC} → cm dashboard`);
+    console.log(`   🔸 ${Y}Cần trợ giúp / Tìm kỹ năng    ${NC} → cm help`);
+    console.log(`   🔸 ${Y}Cách CodyMaster hoạt động  ${NC} → cm-how-it-work`);
   } else {
     console.log(`  ${C}🎯 Orchestration${NC} : Task Planning & Agent Synergy`);
     console.log(`  ${C}🎨 Product${NC}       : UX/UI Mastery & User Psychology`);
@@ -266,20 +256,11 @@ const printMenu = () => {
     console.log(`  ${C}⚙️ Operations${NC}    : Safe Deployments & CI/CD Excellence`);
     console.log(`  ${C}📈 Growth${NC}        : Conversion Tracking & Hacks`);
     console.log('');
-    console.log(`    ${W}${BOLD}💡 Type a number (1-12) for guide & examples:${NC}`);
+    console.log(`    ${W}${BOLD}🌟 Popular Commands:${NC}`);
     console.log('');
-    console.log(`   1. ${Y}The ultimate guide          ${NC} → cm-how-it-work`);
-    console.log(`   2. ${Y}Vibe coding (Zero code)     ${NC} → cm-start`);
-    console.log(`   3. ${Y}Code an existing project    ${NC} → cm-brainstorm-idea`);
-    console.log(`   4. ${Y}Generate UX/UI designs      ${NC} → cm-ux-master`);
-    console.log(`   5. ${Y}Code TDD & Pair coding      ${NC} → cm-tdd`);
-    console.log(`   6. ${Y}Clean & Refactor codebase   ${NC} → cm-clean-code`);
-    console.log(`   7. ${Y}Scan for vulnerabilities    ${NC} → cm-security-gate`);
-    console.log(`   8. ${Y}Write docs & generate APIs  ${NC} → cm-dockit`);
-    console.log(`   9. ${Y}Release WOW landing page    ${NC} → cm-cro-methodology`);
-    console.log(`  10. ${Y}Open progress dashboard     ${NC} → cm dashboard`);
-    console.log(`  11. ${Y}See an interactive demo     ${NC} → /cm:demo`);
-    console.log(`  12. ${Y}Help & Command list         ${NC} → cm help`);
+    console.log(`   🔸 ${Y}Open progress dashboard    ${NC} → cm dashboard`);
+    console.log(`   🔸 ${Y}Help & Command list        ${NC} → cm help`);
+    console.log(`   🔸 ${Y}The ultimate guide         ${NC} → cm-how-it-work`);
   }
   
   console.log('');
@@ -287,25 +268,6 @@ const printMenu = () => {
   console.log('');
 };
 
-const installOpenViking = () => {
-  console.log('');
-  console.log(`${G}${BOLD}OpenViking — Installing Core Feature${NC}`);
-  try {
-    console.log(`  ${W}Running: pip install openviking${NC}`);
-    execSync('pip install openviking', { stdio: 'inherit' });
-    console.log(`  ${G}✅ OpenViking installed.${NC}`);
-  } catch (e) {
-    try {
-      console.log(`  ${W}Running: pip3 install openviking${NC}`);
-      execSync('pip3 install openviking', { stdio: 'inherit' });
-      console.log(`  ${G}✅ OpenViking installed.${NC}`);
-    } catch (err) {
-      console.log(`  ${O}⚠️  Could not install OpenViking automatically. Please run 'pip install openviking' manually.${NC}`);
-    }
-  }
-  console.log('');
-};
-
 const isInstalledAsNpmDependency = () => {
   const root = path.resolve(__dirname, '..').replace(/\\/g, '/');
   return /[/\\]node_modules[/\\]codymaster$/i.test(root);
@@ -325,21 +287,10 @@ const activateCli = () => {
     return;
   }
 
-  if (fs.existsSync(path.join(pkgRoot, 'package.json'))) {
-    try {
-      const pkg = require(path.join(pkgRoot, 'package.json'));
-      if (pkg.name === 'codymaster') {
-        console.log(`  ${W}Linking ${C}cm${W} for local repo development (npm link)...${NC}`);
-        execFileSync(npmCmd(), ['link'], { stdio: 'inherit', cwd: pkgRoot });
-      }
-    } catch (e) {
-      // Ignore if npm link fails
-    }
-  }
+
 };
 
 const main = () => {
-  installOpenViking();
   activateCli();
   printMenu();
 };

package/skills/CLAUDE.md

@@ -129,11 +129,6 @@ The YAML frontmatter `description` field is critical for skill discovery: includ
 /plugin install systems-architecture@wondelai-skills # DDIA, System Design, Clean Architecture, Release It!, High Performance Browser Networking
 ```
 
-### Via skills.sh
-```bash
-npx skills add wondelai/skills              # All skills
-npx skills add wondelai/skills/{skill-name} # Individual skill
-```
 
 ## Versioning Policy
 

package/skills/_shared/helpers.md

@@ -35,11 +35,6 @@ Read .cm/skeleton-index.md    (~500 tokens) — modules, entry points, config fi
 Query: cm_query(scope="learnings", query="{current module or error type}", limit=5)
    OR read .cm/memory/learnings.json filtered to scope == "global" | "module:X"
 
-# OpenViking backend (if storage.backend: viking in .cm/config.yaml):
-Query: cm_query(query="{current module or error type}", limit=5)
-→ OpenViking uses VECTOR SEMANTIC SEARCH — no need for exact keyword match.
-   "i18n locale update" will also match "translation missing" and "locale fallback"
-
 Rules:
   NEVER  load status = "invalidated"   (proven wrong)
   CAUTION status = "corrected"         (verify before applying)
@@ -64,9 +59,8 @@ cm continuity budget  (or: loadBudget + checkBudget in code)
 > L0 indexes + context bus + scope filter make this possible.
 > Only escalate to L2 when L0/L1 explicitly flag the need.
 >
-> **Viking bonus:** With OpenViking backend, L0/L1 indexes are auto-generated by the engine —
-> no manual `cm continuity index` needed. Vector search also improves Step 3 recall by ~40%.
-> Switch: set `storage.backend: viking` in `.cm/config.yaml`.
+> **Legacy note:** Some older projects may still keep `storage.backend: viking` in config.
+> CodyMaster now routes that back to SQLite, so do not design workflows around a separate Viking backend.
 
 ---
 

package/skills/cm-browse/SKILL.md

@@ -1,5 +1,11 @@
+---
+name: cm-browse
+description: "Use when you need visual QA, screenshots, or post-deploy smoke testing through a real browser with Playwright."
+---
 # cm-browse — local Playwright daemon
 
+> **Full runbook:** [docs/browse-daemon.md](../../docs/browse-daemon.md) (install Chromium, token, troubleshooting).
+
 ## When to use
 
 - Visual QA, screenshots, post-deploy smoke through a **real browser** (not only Stitch/Pencil).

package/skills/cm-conductor-worktrees/SKILL.md

@@ -1,3 +1,7 @@
+---
+name: cm-conductor-worktrees
+description: "Use when you need to manage parallel git worktrees for isolated feature development."
+---
 # cm-conductor-worktrees — parallel worktrees
 
 ## CLI

package/skills/cm-content-factory/landing/docs/content/changelog.md

@@ -2,16 +2,16 @@
 
 Welcome to the **"Neural Spine"** era! Version 5 is a massive milestone that transitions CodyMaster from a specialized "Content Factory" tool into a full-fledged **Senior AI-Native Engineering Workspace**. 
 
-We achieved this paradigm shift by deeply studying and integrating the architectural breakthroughs from two external frameworks: **OpenViking** and **OpenSpace**.
+We achieved this paradigm shift by refining CodyMaster into a local-first Smart Spine architecture paired with **OpenSpace** execution.
 
 ---
 
 ## 🚀 Key Architectural Shifts
 
-### 1. Replaced "Dumb" RAG with OpenViking (Semantic Memory)
+### 1. Replaced "Dumb" RAG with Layered Smart Spine Memory
 **The Problem in v4**: AI agents suffered from "code amnesia." Standard Retrieval-Augmented Generation (RAG) relied on chunking text indiscriminately. Agents hallucinated imports and forgot how system components linked together.
 **The v5 Upgrade**:
-By adopting OpenViking concepts, CodyMaster v5 introduces an **AST (Abstract Syntax Tree)** and **Vector-based Memory Engine**. 
+By adopting layered retrieval concepts, CodyMaster v5 introduces a structured memory engine built around indexes, SQLite search, and progressive loading. 
 - It creates a **L0 Skeleton Index** of your entire system's structure instantly.
 - It provides a **L1 Symbol Index** to grasp function signatures perfectly without bogging down the LLM context window with implementation details.
 - Your AI agent now acts like a senior dev who inherently "knows" your monolith's entire structure before typing a single line.
@@ -33,4 +33,4 @@ We introduced **OpenSpace**—a secure sandbox and execution container.
 * **Completely Self-Evolving Skills**: The Skill Chain Engine analyzes repeated commands in your workflow and dynamically builds *new* automation skills specifically tailored to your unique codebase.
 
 > [!TIP]
-> **To Experience It Directly:** Try assigning a task requiring multi-file context tracking, such as *"Migrate our authentication endpoints across the monolith to use the new JWT standard."* and watch OpenViking automatically pull the precise 7 files needed.
+> **To Experience It Directly:** Try assigning a task requiring multi-file context tracking, such as *"Migrate our authentication endpoints across the monolith to use the new JWT standard."* and watch Smart Spine pull the precise files needed without bloating the context window.

package/skills/cm-content-factory/landing/docs/content/deployment.md

@@ -7,7 +7,7 @@ Setting up CodyMaster v5 for your engineering team is straightforward. Follow th
 Ensure your environment meets the following requirements:
 - Node.js v18.0.0 or higher
 - Git
-- SQLite (for local OpenViking memory limits, pre-packaged)
+- SQLite-compatible local environment for CodyMaster's default memory stack
 
 ## 2. Installation
 
@@ -28,7 +28,7 @@ cm init
 
 This will automatically:
 1. Generate the `.agent/` folder structure to house specialized skills.
-2. Spin up the **OpenViking** indexer, which will immediately begin mapping your project's Abstract Syntax Trees (AST) and caching semantic vectors.
+2. Prepare CodyMaster's local memory and index surfaces so Smart Spine can retrieve project context efficiently.
 
 ## 4. Bootstrapping Agents
 
@@ -38,7 +38,7 @@ You can dispatch your first agent task utilizing the full memory and execution l
 cm do "Refactor the user dashboard to utilize Tailwind CSS dark mode variants, ensuring all current unit tests still pass."
 ```
 
-- Watch the terminal to see OpenViking extract relevant context without filling the token window with unnecessary `.json` configs.
+- Watch the terminal to see Smart Spine pull relevant context without filling the token window with unnecessary `.json` configs.
 - Watch OpenSpace dynamically spin up `npm run test` immediately after the code generation completes, self-correcting any errors before offering a Git commit.
 
 ## Continuous CI/CD (Founders Edition)

package/skills/cm-content-factory/landing/docs/content/execution-flow.md

@@ -6,17 +6,17 @@ When you dispatch a command to the system, it doesn't just blindly pass your tex
 
 ## The High-Level Flow
 
-Here is a visual breakdown of how the OpenViking and OpenSpace integrations handle an incoming task:
+Here is a visual breakdown of how Smart Spine memory and OpenSpace handle an incoming task:
 
 ```mermaid
 graph TD
     User([User Prompt: "Refactor Authentication"]) ==> Router
     
     subgraph "Phase 1: Knowledge Gathering"
-        Router[Task Router] --> OViking{OpenViking Engine}
-        OViking --> L0[L0: Skeleton Directory Map]
-        OViking --> L1[L1: Symbol Headers]
-        OViking --> L2[L2: Semantic Vectors]
+        Router[Task Router] --> Memory{Smart Spine Memory}
+        Memory --> L0[L0: Skeleton Directory Map]
+        Memory --> L1[L1: Symbol Headers]
+        Memory --> L2[L2: Indexed Project Context]
         L0 --> Compiler[Context Builder]
         L1 --> Compiler
         L2 --> Compiler
@@ -37,7 +37,7 @@ graph TD
     
     style User fill:#3b82f6,stroke:#fff,stroke-width:2px,color:#fff
     style Ship fill:#10b981,stroke:#fff,stroke-width:2px,color:#fff
-    style OViking fill:#8b5cf6,stroke:#fff,stroke-width:2px,color:#fff
+    style Memory fill:#8b5cf6,stroke:#fff,stroke-width:2px,color:#fff
     style Sandbox fill:#f59e0b,stroke:#fff,stroke-width:2px,color:#111
 ```
 
@@ -46,8 +46,8 @@ graph TD
 ## Step-by-Step Walkthrough
 
 ### 1. Task Routing & Context Building
-The moment you hit enter, your command is sent to the **Task Router**. Before connecting to an external AI model (like Claude 3.5 or GPT-4o), the router queries **OpenViking**. 
-- OpenViking executes a rapid vector search over the local SQLite cache to find all functionally related files. 
+The moment you hit enter, your command is sent to the **Task Router**. Before connecting to an external AI model (like Claude 3.5 or GPT-4o), the router queries **Smart Spine memory**. 
+- Smart Spine uses project indexes and local memory search to find all functionally related files. 
 - It bundles the `L0` (Project Structure), `L1` (Function Interfaces), and `L2` (Implementation Logic) to create a highly compressed, precisely targeted knowledge package.
 
 ### 2. Autonomous Execution

package/skills/cm-content-factory/landing/docs/content/memory-system.md

@@ -0,0 +1,38 @@
+# Layered Memory System
+
+**CodyMaster's Smart Spine memory** is built to keep context retrieval practical, local-first, and honest about what ships today.
+
+## Why this matters
+
+Standard AI workflows often over-rely on blunt keyword search or huge prompt dumps. That creates three predictable problems:
+- agents miss architectural relationships between files
+- token windows fill with low-signal context
+- teams start depending on extra services before the core workflow is even stable
+
+## The CodyMaster approach
+
+CodyMaster uses a layered memory model that combines:
+
+1. **L0 indexes** for fast structural awareness
+2. **SQLite + FTS5** for durable searchable learnings and decisions
+3. **L1/L2 progressive loading** so agents only load richer context when the task actually needs it
+4. **Context Bus** for passing task outputs between skill steps without re-deriving state from chat
+
+## What you get in practice
+
+- Local-first memory with no extra semantic service required
+- Better context targeting than raw grep-only workflows
+- Lower token usage through progressive loading
+- A supportable default setup that works across real projects today
+
+## Recommended setup
+
+The supported CodyMaster path is:
+
+```bash
+npm install
+npm run build
+npm run test:gate:kit
+```
+
+From there, CodyMaster builds and queries context through the shipped Smart Spine stack without requiring a separate semantic service.

package/skills/cm-content-factory/landing/docs/content/openspace.md

@@ -19,7 +19,7 @@ OpenSpace surrounds the agent with a secure execution container (sandbox) tightl
 ## Anatomy of a Session
 
 When an agent is initialized in OpenSpace, it acts as a headless developer:
-1. It pulls semantic context from **[OpenViking](#openviking)**.
+1. It pulls focused context from the **[Layered Memory System](#memory-system)**.
 2. It drafts a solution to isolated branch files.
 3. It spawns an OpenSpace terminal subprocess to run Linters and Unit Tests.
 4. If a test fails, it captures the `stderr` output within OpenSpace and self-heals the code until all checks pass.

package/skills/cm-content-factory/landing/docs/content/use-cases.md

@@ -7,7 +7,7 @@ Here are the optimal scenarios where the Founders Edition architecture outperfor
 ## 1. Full-Stack Monolithic Refactoring
 *The Challenge*: Changing an authentication provider or modifying deeply nested CSS logic across a massive 500,000-line React/Node.js monolith usually incites dozens of cascading regressions.
 *The Spine Solution*:
-- **OpenViking** maps exactly where the legacy authentication logic touches every API router.
+- **Smart Spine memory** maps where the legacy authentication logic touches every API router through indexes and searchable project memory.
 - **OpenSpace** attempts the refactor in an isolated branch and continuously runs the test suite.
 - The outcome is a tightly controlled refactoring PR that didn't miss a single edge case.
 
@@ -22,5 +22,5 @@ Here are the optimal scenarios where the Founders Edition architecture outperfor
 *The Challenge*: Teams accrue dead code, unused imports, and unoptimized queries over years of product pivots.
 *The Spine Solution*:
 - An agent equipped with the `cm-clean-code` skill natively runs over the codebase at midnight via cron job.
-- OpenSpace runs AST (Abstract Syntax Tree) evaluations against OpenViking indexing to guarantee no unused code is actually being referenced dynamically.
+- OpenSpace runs AST-aware checks against CodyMaster's indexed project context to guarantee no unused code is actually being referenced dynamically.
 - The agent creates a PR each morning with a detailed breakdown of the removed complexity and the token savings achieved.

package/skills/cm-content-factory/landing/docs/content/v5-intro.md

@@ -8,13 +8,13 @@ While standard AI coding assistants excel at generating functions and isolated s
 
 A spine connects the brain to the nervous system, passing critical signals instantly and maintaining the structure of the body. In CodyMaster v5, the **Neural Spine** represents the underlying infrastructure that connects your AI agents to the real world:
 
-- **Memory (OpenViking)**: Deep semantic retrieval and code comprehension spanning thousands of files.
+- **Memory (Smart Spine)**: Layered local-first retrieval using SQLite, indexes, and progressive loading.
 - **Execution (OpenSpace)**: A sandboxed, secure environment for agents to run bash commands, databases, and testing suites.
 - **State (Context Bus)**: A fluid mechanism to exchange parameters between specialized subagents without overflowing token limits.
 
 ## Core Capabilities
 
-1. **Eliminating Context Drift**: Your agents no longer guess your architecture. They retrieve the exact semantic structure directly from OpenViking.
+1. **Eliminating Context Drift**: Your agents no longer guess your architecture. They retrieve the exact structural context through Smart Spine indexes and focused memory queries.
 2. **Zero-Regression Shipping**: OpenSpace guarantees that AI-generated code is thoroughly tested (TDD-first) via automated gates before reaching production.
 3. **Multi-Agent Orchestration**: Outsource frontend, backend, and security audits to specialized subagents running in parallel.
 
@@ -22,7 +22,7 @@ A spine connects the brain to the nervous system, passing critical signals insta
 
 Explore the backbone technologies driving this paradigm shift:
 
-- [Explore OpenViking Memory](#openviking)
+- [Explore Layered Memory](#memory-system)
 - [Understand OpenSpace Containers](#openspace)
 - [Real-world Use Cases](#use-cases)
 - [Deploy the Framework](#deployment)

package/skills/cm-content-factory/landing/docs/index.html

@@ -169,7 +169,7 @@
                 <a href="#v5-intro" class="nav-link active" onclick="loadDoc('v5-intro')">The Neural Spine</a>
                 <a href="#changelog" class="nav-link" onclick="loadDoc('changelog')">What's New in v5</a>
                 <a href="#execution-flow" class="nav-link" onclick="loadDoc('execution-flow')">Execution Flow</a>
-                <a href="#openviking" class="nav-link" onclick="loadDoc('openviking')">OpenViking Memory</a>
+                <a href="#memory-system" class="nav-link" onclick="loadDoc('memory-system')">Layered Memory</a>
                 <a href="#openspace" class="nav-link" onclick="loadDoc('openspace')">OpenSpace Workspace</a>
             </div>
 

package/skills/cm-content-factory/landing/index.html

@@ -6,9 +6,9 @@
   <meta name="viewport" content="width=device-width, initial-scale=1.0" />
   <title>CodyMaster v5 — The Neural Spine for AI-Native Engineering</title>
   <meta name="description"
-    content="The high-performance autonomous backbone for AI agents. Featuring OpenViking semantic memory, context bus orchestration, and OpenSpace workspace isolation. Build real products with context-aware intelligence." />
+    content="The high-performance autonomous backbone for AI agents. Featuring Smart Spine memory, context bus orchestration, and OpenSpace workspace isolation. Build real products with context-aware intelligence." />
   <meta name="keywords"
-    content="CodyMaster v5, AI agent backbone, OpenViking, OpenSpace, semantic memory, context bus, AI-native engineering" />
+    content="CodyMaster v5, AI agent backbone, Smart Spine, OpenSpace, semantic memory, context bus, AI-native engineering" />
 
   <!-- Open Graph -->
   <meta property="og:title" content="CodyMaster v5 — The Neural Spine for AI Agents" />
@@ -677,4 +677,4 @@
   <script src="script.js"></script>
 </body>
 
-</html>
+</html>