qwen-base 1.0.0 → 1.0.2

package/bin/install.js

@@ -3,8 +3,8 @@
 const fs = require('fs');
 const path = require('path');
 const os = require('os');
+const readline = require('readline');
 
-// Colors
 const green = '\x1b[32m';
 const cyan = '\x1b[36m';
 const yellow = '\x1b[33m';
@@ -14,12 +14,12 @@ const reset = '\x1b[0m';
 const pkg = require('../package.json');
 
 const banner = `
-${green}  ██████╗ ███████╗███████╗██████╗
-  ██╔══██╗██╔════╝██╔════╝██╔══██╗
-  ██████╔╝█████╗  █████╗  ██████╔╝
-  ██╔══██╗██╔══╝  ██╔══╝  ██╔══██╗
-  ██║  ██║███████╗███████╗██║  ██║
-  ╚═╝  ╚═╝╚══════╝╚══════╝╚═╝  ╚═╝${reset}
+${green}  \u2588\u2588\u2588\u2588\u2588\u2557\u2588\u2588\u2588\u2588\u2588\u2588\u2557\u2588\u2588\u2588\u2588\u2588\u2588\u2557\u2588\u2588\u2588\u2588\u2588\u2588\u2557
+  \u2588\u2588\u2554\u2550\u2550\u2588\u2588\u2557\u2588\u2588\u2554\u2550\u2550\u2588\u2588\u2557\u2588\u2588\u2554\u2550\u2550\u2588\u2588\u2557\u2588\u2588\u2554\u2550\u2550\u2588\u2588\u2557
+  \u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2551\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2551\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2551\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2551
+  \u2588\u2588\u2554\u2550\u2550\u2550\u2588\u2588\u2551\u2588\u2588\u2554\u2550\u2550\u2588\u2588\u2551\u2588\u2588\u2554\u2550\u2550\u2588\u2588\u2551\u2588\u2588\u2554\u2550\u2550\u2588\u2588\u2551
+  \u2588\u2588\u2588\u2588\u2588\u2588\u2554\u255d\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2551\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2551\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2551
+  \u255a\u2550\u2550\u2550\u2550\u2550\u255d \u255a\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u255d\u255a\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u255d\u255a\u2550\u2550\u2550\u2550\u2550\u255d${reset}
 
   BASE ${dim}v${pkg.version}${reset}
   Builder's Automated State Engine
@@ -27,8 +27,10 @@ ${green}  ██████╗ ███████╗███████╗
 `;
 
 const args = process.argv.slice(2);
-const hasHelp = args.includes('--help') || args.includes('-h');
+const hasGlobal = args.includes('--global') || args.includes('-g');
 const hasLocal = args.includes('--local') || args.includes('-l');
+const hasHelp = args.includes('--help') || args.includes('-h');
+const skipTools = args.includes('--skip-tools');
 
 function parseConfigDirArg() {
   const idx = args.findIndex(arg => arg === '--config-dir' || arg === '-c');
@@ -41,16 +43,14 @@ function parseConfigDirArg() {
     return nextArg;
   }
   const configDirArg = args.find(arg => arg.startsWith('--config-dir=') || arg.startsWith('-c='));
-  if (configDirArg) {
-    return configDirArg.split('=')[1];
-  }
+  if (configDirArg) return configDirArg.split('=')[1];
   return null;
 }
 
+const explicitConfigDir = parseConfigDirArg();
+
 function expandTilde(filePath) {
-  if (filePath && filePath.startsWith('~/')) {
-    return path.join(os.homedir(), filePath.slice(2));
-  }
+  if (filePath && filePath.startsWith('~/')) return path.join(os.homedir(), filePath.slice(2));
   return filePath;
 }
 
@@ -61,24 +61,17 @@ function copyDir(srcDir, destDir, skipDirs = []) {
     if (skipDirs.includes(entry.name)) continue;
     const srcPath = path.join(srcDir, entry.name);
     const destPath = path.join(destDir, entry.name);
-    if (entry.isDirectory()) {
-      copyDir(srcPath, destPath, skipDirs);
-    } else {
-      fs.copyFileSync(srcPath, destPath);
-    }
+    if (entry.isDirectory()) copyDir(srcPath, destPath, skipDirs);
+    else fs.copyFileSync(srcPath, destPath);
   }
 }
 
-function countFiles(dir, ext) {
+function countFiles(dir) {
   let count = 0;
   const entries = fs.readdirSync(dir, { withFileTypes: true });
   for (const entry of entries) {
-    const fullPath = path.join(dir, entry.name);
-    if (entry.isDirectory()) {
-      count += countFiles(fullPath, ext);
-    } else if (!ext || entry.name.endsWith(ext)) {
-      count++;
-    }
+    if (entry.isDirectory()) count += countFiles(path.join(dir, entry.name));
+    else count++;
   }
   return count;
 }
@@ -89,139 +82,94 @@ if (hasHelp) {
   console.log(`  ${yellow}Usage:${reset} npx qwen-base [options]
 
   ${yellow}Options:${reset}
-    ${cyan}-l, --local${reset}              Install to ./.qwen/commands/ instead of global
-    ${cyan}-c, --config-dir <path>${reset}  Specify custom Qwen config directory
-    ${cyan}-h, --help${reset}               Show this help message
+    ${cyan}-g, --global${reset}              Install globally (to Qwen config directory)
+    ${cyan}-l, --local${reset}               Install locally (to ./.qwen/ in current directory)
+    ${cyan}-c, --config-dir <path>${reset}   Specify custom Qwen config directory
+    ${cyan}--skip-tools${reset}              Skip OSS analysis tool installation
+    ${cyan}-h, --help${reset}                Show this help message
 
   ${yellow}Examples:${reset}
-    ${dim}# Install globally (default)${reset}
-    npx qwen-base
+    ${dim}# Install globally (recommended)${reset}
+    npx qwen-base --global
 
     ${dim}# Install to current project only${reset}
     npx qwen-base --local
 
   ${yellow}What gets installed:${reset}
-    ${cyan}commands/qwen-base/${reset}
-      base.md              Entry point (routing + persona)
-      framework/           Tasks, templates, frameworks (11 commands)
-      commands/            Command definitions
-      hooks/               7 Python hooks for workspace intelligence
-      templates/           operator.json, workspace.json templates
-    ${cyan}.qwen/hooks/${reset}              Python hooks registration
+    ${cyan}commands/qwen-base/${reset}       11 slash commands
+    ${cyan}base/                            Framework (core, transform, domains, schemas, rules, tools)
 `);
   process.exit(0);
 }
 
-const explicitConfigDir = parseConfigDirArg();
-const configDir = expandTilde(explicitConfigDir) || expandTilde(process.env.QWEN_CONFIG_DIR);
-const globalDir = configDir || path.join(os.homedir(), '.qwen');
-const qwenDir = hasLocal ? path.join(process.cwd(), '.qwen') : globalDir;
-const baseDest = path.join(qwenDir, 'commands', 'qwen-base');
-
-const locationLabel = hasLocal
-  ? baseDest.replace(process.cwd(), '.')
-  : baseDest.replace(os.homedir(), '~');
-
-if (fs.existsSync(baseDest)) {
-  console.log(`  ${yellow}Existing installation found at ${locationLabel}${reset}`);
-  console.log(`  Updating...`);
-  fs.rmSync(baseDest, { recursive: true, force: true });
-}
-
-console.log(`  Installing to ${cyan}${locationLabel}${reset}\n`);
-
-const src = path.join(__dirname, '..');
-
-// Copy entry point
-fs.mkdirSync(baseDest, { recursive: true });
-fs.copyFileSync(path.join(src, 'src', 'skill', 'base.md'), path.join(baseDest, 'base.md'));
-console.log(`  ${green}+${reset} base.md ${dim}(entry point)${reset}`);
-
-// Copy framework
-const fwSrc = path.join(src, 'src', 'framework');
-const fwDest = path.join(baseDest, 'framework');
-copyDir(fwSrc, fwDest);
-const fwCount = countFiles(fwSrc);
-console.log(`  ${green}+${reset} framework/ ${dim}(${fwCount} files)${reset}`);
-
-// Copy commands
-const cmdSrc = path.join(src, 'src', 'commands');
-const cmdDest = path.join(baseDest, 'commands');
-copyDir(cmdSrc, cmdDest);
-const cmdCount = countFiles(cmdSrc);
-console.log(`  ${green}+${reset} commands/ ${dim}(${cmdCount} files)${reset}`);
-
-// Copy hooks
-const hooksSrc = path.join(src, 'src', 'hooks');
-const hooksDest = path.join(baseDest, 'hooks');
-copyDir(hooksSrc, hooksDest);
-const hookCount = countFiles(hooksSrc);
-console.log(`  ${green}+${reset} hooks/ ${dim}(${hookCount} Python hooks)${reset}`);
-
-// Copy templates
-const tplSrc = path.join(src, 'src', 'templates');
-const tplDest = path.join(baseDest, 'templates');
-copyDir(tplSrc, tplDest);
-console.log(`  ${green}+${reset} templates/ ${dim}(workspace templates)${reset}`);
-
-// Copy MCP server
-const mcpSrc = path.join(src, 'src', 'packages', 'base-mcp');
-if (fs.existsSync(mcpSrc)) {
-  const mcpDest = path.join(qwenDir, 'base-mcp');
-  copyDir(mcpSrc, mcpDest);
-  console.log(`  ${green}+${reset} base-mcp/ ${dim}(MCP server)${reset}`);
-
-  // Install MCP deps
-  try {
-    require('child_process').execSync('npm install --production --silent', {
-      cwd: mcpDest, stdio: 'pipe'
-    });
-    console.log(`  ${green}+${reset} MCP dependencies installed${reset}`);
-  } catch (e) {
-    console.log(`  ${yellow}!${reset} MCP deps install failed — run cd ${mcpDest} && npm install${reset}`);
+function install(isGlobal) {
+  const src = path.join(__dirname, '..');
+  const configDir = expandTilde(explicitConfigDir) || expandTilde(process.env.QWEN_CONFIG_DIR);
+  const globalDir = configDir || path.join(os.homedir(), '.qwen');
+  const qwenDir = isGlobal ? globalDir : path.join(process.cwd(), '.qwen');
+  const aegisDest = path.join(qwenDir, 'aegis');
+  const cmdsDest = path.join(qwenDir, 'commands', 'qwen-base');
+
+  const locationLabel = isGlobal
+    ? qwenDir.replace(os.homedir(), '~')
+    : qwenDir.replace(process.cwd(), '.');
+
+  if (fs.existsSync(aegisDest) || fs.existsSync(cmdsDest)) {
+    console.log(`  ${yellow}Existing installation found at ${locationLabel}${reset}`);
+    console.log(`  Updating...`);
+    if (fs.existsSync(aegisDest)) fs.rmSync(aegisDest, { recursive: true, force: true });
+    if (fs.existsSync(cmdsDest)) fs.rmSync(cmdsDest, { recursive: true, force: true });
   }
-}
 
-// Wire hooks into .qwen/settings.json
-function wireHooks(qwenDir, hooksDir) {
-  const settingsPath = path.join(qwenDir, 'settings.json');
-  let settings = {};
-  if (fs.existsSync(settingsPath)) {
-    try { settings = JSON.parse(fs.readFileSync(settingsPath, 'utf8')); } catch (e) {}
+  console.log(`  Installing to ${cyan}${locationLabel}${reset}\n`);
+
+  // Copy framework (note: BASE uses 'src/' structure)
+  if (fs.existsSync(path.join(src, 'src'))) {
+    copyDir(path.join(src, 'src'), path.join(qwenDir, 'base'));
+    console.log(`  ${green}+${reset} base/ ${dim}(${countFiles(path.join(qwenDir, 'base'))} framework files)${reset}`);
   }
-  if (!settings.hooks) settings.hooks = {};
-
-  const hookFiles = fs.readdirSync(hooksDir).filter(f => f.endsWith('.py') && !f.startsWith('_'));
-  for (const hookFile of hookFiles) {
-    const hookName = hookFile.replace('.py', '');
-    const hookPath = path.join(hooksDir, hookFile).replace(/\\/g, '/');
-    const hookCommand = `python3 ${hookPath}`;
-
-    // Determine which event
-    let eventName = 'SessionStart';
-    if (hookFile === 'active-hook.py') eventName = 'SessionStart';
-    else if (hookFile === 'psmm-injector.py') eventName = 'SessionStart';
-    else if (hookFile === 'backlog-hook.py') eventName = 'SessionStart';
-    else if (hookFile === 'operator.py') eventName = 'SessionStart';
-    else if (hookFile === 'satellite-detection.py') eventName = 'SessionStart';
-    else if (hookFile === 'apex-insights.py') eventName = 'Stop';
-    else if (hookFile === 'base-pulse-check.py') eventName = 'SessionStart';
-
-    if (!settings.hooks[eventName]) settings.hooks[eventName] = [];
-    const exists = settings.hooks[eventName].some(h =>
-      (h.command && h.command.includes(hookFile)) ||
-      (h.hooks && h.hooks.some(i => i.command && i.command.includes(hookFile)))
-    );
-    if (!exists) {
-      settings.hooks[eventName].push({ hooks: [{ type: 'command', command: hookCommand }] });
-    }
+
+  // Copy commands
+  if (fs.existsSync(path.join(src, 'src', 'commands'))) {
+    fs.mkdirSync(cmdsDest, { recursive: true });
+    copyDir(path.join(src, 'src', 'commands'), cmdsDest);
+    console.log(`  ${green}+${reset} commands/qwen-base/ ${dim}(${countFiles(cmdsDest)} commands)${reset}`);
   }
-  fs.writeFileSync(settingsPath, JSON.stringify(settings, null, 2));
+
+  console.log(`
+  ${green}Done!${reset} Open Qwen Code and type ${cyan}/base${reset} to start.
+`);
 }
 
-wireHooks(qwenDir, hooksDest);
-console.log(`  ${green}+${reset} Hooks wired in settings.json${reset}`);
+function promptLocation() {
+  const rl = readline.createInterface({ input: process.stdin, output: process.stdout });
 
-console.log(`
-  ${green}Done!${reset} Open Qwen Code and type ${cyan}/base${reset} to start.
+  const configDir = expandTilde(explicitConfigDir) || expandTilde(process.env.QWEN_CONFIG_DIR);
+  const globalPath = configDir || path.join(os.homedir(), '.qwen');
+  const globalLabel = globalPath.replace(os.homedir(), '~');
+
+  console.log(`  ${yellow}Where would you like to install?${reset}
+
+  ${cyan}1${reset}) Global ${dim}(${globalLabel})${reset} - available in all projects
+  ${cyan}2${reset}) Local  ${dim}(./.qwen)${reset} - this project only
 `);
+
+  rl.question(`  Choice ${dim}[1]${reset}: `, (answer) => {
+    rl.close();
+    install(answer.trim() !== '2');
+  });
+}
+
+if (hasGlobal && hasLocal) {
+  console.error(`  ${yellow}Cannot specify both --global and --local${reset}`);
+  process.exit(1);
+} else if (explicitConfigDir && hasLocal) {
+  console.error(`  ${yellow}Cannot use --config-dir with --local${reset}`);
+  process.exit(1);
+} else if (hasGlobal) {
+  install(true);
+} else if (hasLocal) {
+  install(false);
+} else {
+  promptLocation();
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "qwen-base",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "Builder's Automated State Engine — workspace lifecycle management for Qwen Code",
   "bin": {
     "qwen-base": "bin/install.js"

package/src/commands/audit-claude-md.md

@@ -1,13 +1,13 @@
 ---
 name: base:audit-claude-md
-description: Audit CLAUDE.md against the CLAUDE.md Strategy and generate a compliant version
+description: Audit QWEN.md against the QWEN.md Strategy and generate a compliant version
 allowed-tools: [Read, Write, Edit, Glob, Grep, Bash]
 ---
 
 <objective>
-Audit the project's CLAUDE.md for strategy compliance, interactively rewrite it section by section, and route operational rules to CARL or an artifact.
+Audit the project's QWEN.md for strategy compliance, interactively rewrite it section by section, and route operational rules to CARL or an artifact.
 
-**When to use:** "audit claude md", "check my claude.md", "rewrite my claude.md", after major workspace changes.
+**When to use:** "audit claude md", "check my QWEN.md", "rewrite my QWEN.md", after major workspace changes.
 </objective>
 
 <execution_context>
@@ -19,18 +19,18 @@ Audit the project's CLAUDE.md for strategy compliance, interactively rewrite it
 <context>
 $ARGUMENTS
 
-@CLAUDE.md
+@QWEN.md
 </context>
 
 <process>
 Follow task: @{~/.qwen/commands/qwen-base/tasks/audit-claude-md.md}
 
 Key gates (do NOT skip):
-1. Load strategy + template BEFORE reading user's CLAUDE.md
+1. Load strategy + template BEFORE reading user's QWEN.md
 2. Present full audit classification — wait for user approval
 3. Detect CARL — wait for user decision on rule routing
 4. Propose each section individually — wait for approval per section
-5. Write to CLAUDE.base.md (never overwrite CLAUDE.md)
+5. Write to CLAUDE.base.md (never overwrite QWEN.md)
 </process>
 
 <success_criteria>
@@ -40,5 +40,5 @@ Key gates (do NOT skip):
 - [ ] CARL detection completed, rule routing decided
 - [ ] Each section approved individually
 - [ ] Final CLAUDE.base.md under 100 lines
-- [ ] Original CLAUDE.md untouched
+- [ ] Original QWEN.md untouched
 </success_criteria>

package/src/commands/audit-claude.md

@@ -11,8 +11,8 @@ Audit all .qwen/ directories in this workspace. Discover sprawl, classify items
 </objective>
 
 <execution_context>
-@base-framework/tasks/audit-claude.md
-@base-framework/frameworks/claude-config-alignment.md
+@{~/.qwen/commands/qwen-base/framework/}tasks/audit-QWEN.md
+@{~/.qwen/commands/qwen-base/framework/}frameworks/qwen-config-alignment.md
 </execution_context>
 
 <context>
@@ -23,7 +23,7 @@ Workspace root config: .qwen/
 </context>
 
 <process>
-Follow task: @base-framework/tasks/audit-claude.md
+Follow task: @{~/.qwen/commands/qwen-base/framework/}tasks/audit-QWEN.md
 
 The framework file defines classification rules, safety protocol, and output format.
 The task file defines the step-by-step process.

package/src/commands/orientation/tasks/task-seeding.md

@@ -15,7 +15,7 @@ As an operator with aligned initiatives and projects, I want to capture the imme
 <steps>
 
 <step name="frame_and_filter" priority="first">
-> Tasks are YOUR accountability items — things that must get done. Not Claude Code todos. Not aspirational ideas. Concrete next actions.
+> Tasks are YOUR accountability items — things that must get done. Not Qwen Code todos. Not aspirational ideas. Concrete next actions.
 >
 > We'll go initiative by initiative, project by project. For each project, I'll show you the current status and ask: "What must get done next?"
 >
@@ -89,5 +89,5 @@ Tasks created in Apex via MCP under their parent projects. Operator's immediate
 - [ ] Tasks created via base_add_project(type="task") with correct parent_id
 - [ ] Operator could skip projects freely
 - [ ] Summary displayed with total counts
-- [ ] NEVER treated tasks as Claude Code internal todos
+- [ ] NEVER treated tasks as Qwen Code internal todos
 </acceptance-criteria>

package/src/framework/context/base-principles.md

@@ -60,7 +60,7 @@ BACKLOG (status=backlog in projects.json)
 BASE scaffold operates in two modes:
 
 - **Standard** (`/base:scaffold`) — Data layer only. Creates `.base/` with workspace.json, `.base/data/state.json`, ROADMAP.md. Scans and tracks what exists. Framework-agnostic.
-- **Full** (`/base:scaffold --full`) — Data layer + projects.json + entities.json. Offers CLAUDE.md audit. The "batteries included" version for AI builders who want the full system.
+- **Full** (`/base:scaffold --full`) — Data layer + projects.json + entities.json. Offers QWEN.md audit. The "batteries included" version for AI builders who want the full system.
 
 Standard mode works for any workspace. Full mode provides Chris's proven operational structure.
 

package/src/framework/frameworks/claude-config-alignment.md

@@ -11,7 +11,7 @@ Designed to be composed into any audit workflow that touches the system layer. T
 - During initial BASE setup on an existing workspace (lots of legacy `.qwen/` dirs)
 - As part of periodic workspace audits
 - After installing a new tool/skill globally and wanting to clean up project-level copies
-- When the user suspects their Claude Code config is fragmented
+- When the user suspects their Qwen Code config is fragmented
 
 ---
 
@@ -125,7 +125,7 @@ An item is PROJECT_SPECIFIC if:
 An item is STALE if:
 - settings.json references MCP servers that aren't in the current `.mcp.json` or global config
 - hooks reference scripts or tools that have been renamed or removed
-- Settings use old configuration patterns that Claude Code no longer supports
+- Settings use old configuration patterns that Qwen Code no longer supports
 - The `.qwen/` directory hasn't been modified in 60+ days AND the project itself shows no recent activity
 
 **Present specific evidence of staleness. Never assume — prove it.**
@@ -168,7 +168,7 @@ Project-level `settings.json` and `settings.local.json` require special handling
 
 ## Remediation Safety Protocol
 
-This is the most important section. `.qwen/` configuration is what makes Claude Code work. A broken config means a broken development environment. Every remediation action must follow these rules:
+This is the most important section. `.qwen/` configuration is what makes Qwen Code work. A broken config means a broken development environment. Every remediation action must follow these rules:
 
 ### Before any change
 1. **Explain what will change and why** — No "cleaning up your config." Say exactly: "Removing `apps/casegate-v2/.qwen/hooks/carl-hook.py` because an identical version runs globally from `~/.qwen/hooks/dynamic-rules-loader.py`. The global hook already fires on every prompt in every project."
@@ -182,7 +182,7 @@ This is the most important section. `.qwen/` configuration is what makes Claude
 
 ### After all changes
 7. **Summary report** — What was changed, what was kept, what needs manual follow-up
-8. **Recommend a test** — "Open Claude Code in {project} and verify hooks fire correctly"
+8. **Recommend a test** — "Open Qwen Code in {project} and verify hooks fire correctly"
 
 ### What this workflow NEVER does
 - Modify `~/.qwen/` (global config) without explicit promotion approval

package/src/framework/frameworks/claudemd-strategy.md

@@ -1,24 +1,24 @@
-# The CLAUDE.md Strategy
+# The QWEN.md Strategy
 
-Composable framework for auditing and writing high-performance CLAUDE.md files. Source of truth for the `/base:audit-claude-md` workflow.
+Composable framework for auditing and writing high-performance QWEN.md files. Source of truth for the `/base:audit-claude-md` workflow.
 
 ---
 
 ## The Structure: What, Why, Who, Where, How
 
-Every CLAUDE.md follows five sections in this exact order. Each section answers one question. Together they give Claude complete operating context without bloat.
+Every QWEN.md follows five sections in this exact order. Each section answers one question. Together they give Claude complete operating context without bloat.
 
 ### What
 What this document is and what this workspace contains.
 
 One line. Sets the contract. Claude knows this is its instruction set.
 
-> "This file provides guidance to Claude Code when working with code in this repository."
+> "This file provides guidance to Qwen Code when working with code in this repository."
 
 ### Why
 The philosophy. Identity context. Why this workspace exists.
 
-This is where you separate identity from operations. CLAUDE.md answers the "who am I working with?" question. Operational details (how to run a specific project, current sprint status) live elsewhere and get referenced with `@` pointers.
+This is where you separate identity from operations. QWEN.md answers the "who am I working with?" question. Operational details (how to run a specific project, current sprint status) live elsewhere and get referenced with `@` pointers.
 
 ### Who
 Business context. Who the user is, what they do, what matters to them.
@@ -81,14 +81,14 @@ It's a binary check. Claude can look at its own output and ask: "Did I do the fo
 
 ## The @ Reference System
 
-CLAUDE.md stays lean by pointing to other files instead of inlining their content.
+QWEN.md stays lean by pointing to other files instead of inlining their content.
 
 ```
 @LINKS.md — Personal branding URLs
 @projects/dashboard-build/PLANNING.md — Active project context
 ```
 
-Claude reads `@`-referenced files on demand. Your CLAUDE.md stays lean while still giving Claude access to deep context.
+Claude reads `@`-referenced files on demand. Your QWEN.md stays lean while still giving Claude access to deep context.
 
 **What to inline vs what to reference:**
 - **Inline:** Identity (who, what, why), workspace structure, rules, quick references
@@ -98,9 +98,9 @@ Claude reads `@`-referenced files on demand. Your CLAUDE.md stays lean while sti
 
 ## What Stays Out
 
-The test: **if it changes every week, it doesn't belong in CLAUDE.md.**
+The test: **if it changes every week, it doesn't belong in QWEN.md.**
 
-CLAUDE.md is the constitution, not the daily newspaper.
+QWEN.md is the constitution, not the daily newspaper.
 
 | Doesn't belong | Where it goes |
 |----------------|---------------|
@@ -116,7 +116,7 @@ CLAUDE.md is the constitution, not the daily newspaper.
 
 Target: **under 100 lines.** This is a routing document, not a knowledge base.
 
-If your CLAUDE.md is over 100 lines, content is being inlined that should be referenced or removed. Common offenders:
+If your QWEN.md is over 100 lines, content is being inlined that should be referenced or removed. Common offenders:
 - Inline system/framework descriptions (replace with a compact table)
 - Redundant location tables when a tree diagram already exists
 - Documentation system descriptions (the tree covers this)
@@ -126,7 +126,7 @@ If your CLAUDE.md is over 100 lines, content is being inlined that should be ref
 
 ## Audit Criteria
 
-When auditing an existing CLAUDE.md, check:
+When auditing an existing QWEN.md, check:
 
 ### Structure
 - [ ] Follows What → Why → Who → Where → How order
@@ -154,5 +154,5 @@ When auditing an existing CLAUDE.md, check:
 
 ### CARL Integration (if present)
 - [ ] Operational rules that belong in domain-specific contexts are flagged for CARL migration
-- [ ] CLAUDE.md rules are constitutional (identity-level), not operational
-- [ ] No duplication between CLAUDE.md rules and CARL domain rules
+- [ ] QWEN.md rules are constitutional (identity-level), not operational
+- [ ] No duplication between QWEN.md rules and CARL domain rules

package/src/framework/frameworks/satellite-registration.md

@@ -2,7 +2,7 @@
 
 ## What Are Satellites
 
-Satellites are projects that live in their own git repos inside the workspace (e.g., `apps/*`). They run their own Claude Code sessions independently. BASE needs visibility into them without owning them.
+Satellites are projects that live in their own git repos inside the workspace (e.g., `apps/*`). They run their own Qwen Code sessions independently. BASE needs visibility into them without owning them.
 
 ## Registration Flow
 

package/src/framework/tasks/audit-claude-md.md

@@ -1,14 +1,14 @@
 <purpose>
-Audit an existing CLAUDE.md against the CLAUDE.md Strategy framework, then interactively rewrite it with user approval at each stage. Detects CARL installation and routes operational rules accordingly.
+Audit an existing QWEN.md against the QWEN.md Strategy framework, then interactively rewrite it with user approval at each stage. Detects CARL installation and routes operational rules accordingly.
 </purpose>
 
 <user-story>
-As an AI builder, I want my CLAUDE.md audited against a proven strategy so I get a compliant, lean configuration file — with operational rules properly routed to CARL or preserved as an artifact for later.
+As an AI builder, I want my QWEN.md audited against a proven strategy so I get a compliant, lean configuration file — with operational rules properly routed to CARL or preserved as an artifact for later.
 </user-story>
 
 <when-to-use>
 - During /base:scaffold (optional step)
-- When user says "audit my claude.md", "improve my claude.md", "rewrite my claude.md"
+- When user says "audit my QWEN.md", "improve my QWEN.md", "rewrite my QWEN.md"
 - Entry point: /base:audit-claude-md
 </when-to-use>
 
@@ -20,7 +20,7 @@ As an AI builder, I want my CLAUDE.md audited against a proven strategy so I get
 <steps>
 
 <step name="load_strategy" priority="first">
-Load the CLAUDE.md Strategy framework and template.
+Load the QWEN.md Strategy framework and template.
 
 1. Read `@{~/.qwen/commands/qwen-base/frameworks/claudemd-strategy.md}` — this is the source of truth
 2. Read `@{~/.qwen/commands/qwen-base/templates/claudemd-template.md}` — this is the structural reference
@@ -30,15 +30,15 @@ You MUST understand the full strategy before reading the user's file. The strate
 </step>
 
 <step name="read_and_catalog">
-Read the user's existing CLAUDE.md and catalog every piece of content.
+Read the user's existing QWEN.md and catalog every piece of content.
 
-1. Read `CLAUDE.md` from workspace root
-2. If no CLAUDE.md exists → skip to `generate_fresh` step
+1. Read `QWEN.md` from workspace root
+2. If no QWEN.md exists → skip to `generate_fresh` step
 3. For every section, paragraph, rule, table, and reference in the file, classify each as:
-   - **KEEP** — belongs in CLAUDE.md per the strategy (identity, structure, constitutional rules)
+   - **KEEP** — belongs in QWEN.md per the strategy (identity, structure, constitutional rules)
    - **REMOVE** — doesn't belong (volatile data, task lists, state references, redundant sections)
    - **RESTRUCTURE** — right content, wrong location or format (e.g., rule using "always" instead of NEVER pattern, operational content in wrong section)
-   - **CARL_CANDIDATE** — operational rule or domain-specific behavior that belongs in a rules engine, not CLAUDE.md
+   - **CARL_CANDIDATE** — operational rule or domain-specific behavior that belongs in a rules engine, not QWEN.md
 
 4. Count total lines. Note if over 100-line budget.
 </step>
@@ -92,7 +92,7 @@ Wait for user decision before proceeding.
 </step>
 
 <step name="propose_rewrite">
-Build the new CLAUDE.md section by section, presenting each for approval.
+Build the new QWEN.md section by section, presenting each for approval.
 
 For EACH section (What, Why, Who, Where, How):
 
@@ -136,36 +136,36 @@ Handle operational rules that were classified as CARL_CANDIDATE.
 </step>
 
 <step name="write_and_finalize">
-Write the approved CLAUDE.md.
+Write the approved QWEN.md.
 
 1. Assemble all approved sections into final document
 2. Verify line count (warn if over 100)
-3. Write to `CLAUDE.base.md` in workspace root (NEVER overwrite CLAUDE.md directly)
+3. Write to `CLAUDE.base.md` in workspace root (NEVER overwrite QWEN.md directly)
 4. Present final diff summary: sections added, removed, restructured, rules routed
 
 Tell user:
-- "Review `CLAUDE.base.md`. To adopt it: `mv CLAUDE.base.md CLAUDE.md`"
-- "Your original CLAUDE.md is untouched."
+- "Review `CLAUDE.base.md`. To adopt it: `mv CLAUDE.base.md QWEN.md`"
+- "Your original QWEN.md is untouched."
 - If CARL candidates were routed: "Operational rules are in {location}."
 </step>
 
 </steps>
 
 <output>
-- `CLAUDE.base.md` — strategy-compliant CLAUDE.md ready for adoption
+- `CLAUDE.base.md` — strategy-compliant QWEN.md ready for adoption
 - CARL domain rules (if CARL installed) or `.base/artifacts/claudemd-audit-rules.md` (if not)
-- Original CLAUDE.md untouched
+- Original QWEN.md untouched
 </output>
 
 <acceptance-criteria>
 - [ ] Strategy framework loaded and understood before audit begins
-- [ ] Every line of existing CLAUDE.md classified (KEEP/REMOVE/RESTRUCTURE/CARL_CANDIDATE)
+- [ ] Every line of existing QWEN.md classified (KEEP/REMOVE/RESTRUCTURE/CARL_CANDIDATE)
 - [ ] Full audit presented to user with approval gate before rewriting
 - [ ] CARL installation detected and rule routing decided with user
 - [ ] Each section proposed individually with user approval
 - [ ] All rules use NEVER pattern
 - [ ] Final output under 100 lines
 - [ ] Operational rules routed to CARL or saved as artifact
-- [ ] Original CLAUDE.md never modified
+- [ ] Original QWEN.md never modified
 - [ ] User informed of how to adopt and next steps
 </acceptance-criteria>

package/src/framework/tasks/audit-claude.md

@@ -3,7 +3,7 @@ Audit all .qwen/ directories across a workspace. Discover sprawl, classify each
 </purpose>
 
 <user-story>
-As an AI builder with multiple projects in my workspace, I want all my .qwen/ directories audited for duplication, staleness, and misplacement, so that my Claude Code configuration is clean, consistent, and I know exactly what's project-specific vs what should be global.
+As an AI builder with multiple projects in my workspace, I want all my .qwen/ directories audited for duplication, staleness, and misplacement, so that my Qwen Code configuration is clean, consistent, and I know exactly what's project-specific vs what should be global.
 </user-story>
 
 <when-to-use>
@@ -15,11 +15,11 @@ As an AI builder with multiple projects in my workspace, I want all my .qwen/ di
 </when-to-use>
 
 <framework>
-@frameworks/claude-config-alignment.md
+@frameworks/qwen-config-alignment.md
 </framework>
 
 <output-rules>
-ALL audit findings MUST be written to a markdown report file at `.base/audits/claude-config-{YYYY-MM-DD}.md`.
+ALL audit findings MUST be written to a markdown report file at `.base/audits/qwen-config-{YYYY-MM-DD}.md`.
 
 Do NOT dump findings into the chat as inline text. The chat is for brief status updates, questions, and confirmations only. The report is where all detail lives.
 
@@ -28,7 +28,7 @@ The report must be:
 - Readable by a human who opens it in any markdown viewer
 - Comprehensive: current state, classifications with evidence, remediation plan with risk levels, items kept and why
 
-After writing the report, tell the operator: "Audit report written to `.base/audits/claude-config-{date}.md`. Review it, then tell me which remediation groups to execute."
+After writing the report, tell the operator: "Audit report written to `.base/audits/qwen-config-{date}.md`. Review it, then tell me which remediation groups to execute."
 
 During remediation execution, update the report with results (append a "Remediation Results" section).
 </output-rules>
@@ -61,7 +61,7 @@ Classify every item in every project-level .qwen/ directory.
 
 **CRITICAL: Git boundary awareness.**
 
-The scanner dataset includes `git_boundary` data for each directory. This tells you what each project actually sees when Claude Code boots there:
+The scanner dataset includes `git_boundary` data for each directory. This tells you what each project actually sees when Qwen Code boots there:
 
 - `has_own_git: true` → This project has its own git root. It does NOT see the workspace root `.qwen/` or workspace `.mcp.json`. It only sees global `~/.qwen/` + its own `.qwen/`.
 - `has_own_git: false` → This project inherits the workspace root. It sees global `~/.qwen/` + workspace root `.qwen/` + its own `.qwen/`.
@@ -102,7 +102,7 @@ For own-git projects, the right framing is:
 <step name="settings_reconciliation">
 Analyze settings.json and settings.local.json files specifically.
 
-These are the most dangerous files because they control Claude Code behavior:
+These are the most dangerous files because they control Qwen Code behavior:
 
 1. For each project-level settings.json:
    a. Parse hook definitions — list every hook command
@@ -162,7 +162,7 @@ If any reclassifications happen in this step, update all downstream plan entries
 </step>
 
 <step name="build_report">
-Write the complete audit report to `.base/audits/claude-config-{YYYY-MM-DD}.md`.
+Write the complete audit report to `.base/audits/qwen-config-{YYYY-MM-DD}.md`.
 
 Report structure:
 1. **MD5 disclaimer** — Always include this at the top, right after the metadata block, as a blockquote:
@@ -183,7 +183,7 @@ Report structure:
 6. **Items Kept (No Action)** — What's staying and exactly why
 7. **Next Steps** — What the operator should do
 
-Tell the operator: "Audit report written to `.base/audits/claude-config-{date}.md`. Review it, then we'll decide how to handle remediation."
+Tell the operator: "Audit report written to `.base/audits/qwen-config-{date}.md`. Review it, then we'll decide how to handle remediation."
 
 **Wait for operator to review the report before proceeding to graduation routing.**
 </step>
@@ -197,7 +197,7 @@ Route remediation into a structured execution path. Present the operator with op
 AUDIT COMPLETE — REMEDIATION ROUTING
 ════════════════════════════════════════
 
-The audit report is ready at .base/audits/claude-config-{date}.md
+The audit report is ready at .base/audits/qwen-config-{date}.md
 
 How would you like to handle remediation?
 
@@ -227,7 +227,7 @@ How would you like to handle remediation?
    2. cd {path}
    3. Run /paul:init
    4. When defining scope, reference the audit report:
-      @.base/audits/claude-config-{date}.md
+      @.base/audits/qwen-config-{date}.md
 
    The audit report's Remediation Plan section maps directly
    to PAUL phases — each remediation group can be a phase.
@@ -255,7 +255,7 @@ How would you like to handle remediation?
    To proceed:
    1. In the selected project, run /paul:milestone
    2. When defining scope, reference the audit report:
-      @.base/audits/claude-config-{date}.md
+      @.base/audits/qwen-config-{date}.md
 
    The audit report's Remediation Plan section provides
    the scope — each remediation group maps to a phase.
@@ -304,9 +304,9 @@ Verify the workspace is healthy after all remediation and update the report.
    - What was executed (by group)
    - What was verified
    - Any issues found during verification
-   - Projects the operator should test by opening Claude Code in them
+   - Projects the operator should test by opening Qwen Code in them
 
-Tell the operator: "Remediation complete. Report updated. Recommend testing Claude Code in: {list of modified projects}."
+Tell the operator: "Remediation complete. Report updated. Recommend testing Qwen Code in: {list of modified projects}."
 </step>
 
 </steps>

package/src/framework/tasks/scaffold.md

@@ -1,5 +1,5 @@
 <purpose>
-Set up BASE in a new or existing workspace. Scan the workspace, ask guided questions, generate the manifest, install hooks, initialize JSON data surfaces, and run operator profile setup. Optional --full mode adds CLAUDE.md audit and guided first groom.
+Set up BASE in a new or existing workspace. Scan the workspace, ask guided questions, generate the manifest, install hooks, initialize JSON data surfaces, and run operator profile setup. Optional --full mode adds QWEN.md audit and guided first groom.
 </purpose>
 
 <user-story>
@@ -10,7 +10,7 @@ As an AI builder setting up my workspace, I want a guided scaffolding process th
 - First-time BASE installation in any workspace
 - When user says "base scaffold", "set up base", "initialize workspace management"
 - Entry point routes here via /base:scaffold
-- Use --full flag for batteries-included mode with CLAUDE.md audit + first groom
+- Use --full flag for batteries-included mode with QWEN.md audit + first groom
 </when-to-use>
 
 <context>
@@ -23,7 +23,7 @@ As an AI builder setting up my workspace, I want a guided scaffolding process th
 Determine scaffold mode.
 
 1. Check if user specified `--full` or mentioned wanting full setup
-2. If `--full`: CLAUDE.md audit + first groom will be offered after data layer setup
+2. If `--full`: QWEN.md audit + first groom will be offered after data layer setup
 3. If standard: data layer + hooks + operator profile
 4. Announce mode: "Running BASE scaffold ({standard|full} mode)."
 </step>
@@ -111,7 +111,7 @@ All hooks live in `.base/hooks/`. Session hooks are registered in `.qwen/setting
 - psmm-injector.py — per-session meta memory injection
 - operator.py — operator identity context injection
 
-**SessionStart hooks** (fire once when Claude Code starts a session):
+**SessionStart hooks** (fire once when Qwen Code starts a session):
 - satellite-detection.py — PAUL project auto-registration and state sync
 
 **On-demand hooks** (invoked by commands, not auto-registered):
@@ -121,7 +121,7 @@ All hooks live in `.base/hooks/`. Session hooks are registered in `.qwen/setting
 
 ### ENVIRONMENT DETECTION (REQUIRED — do this FIRST)
 
-Hooks are shell commands that Claude Code executes. The python path AND file paths must work in the context where Claude Code is running. Detect the environment before wiring anything.
+Hooks are shell commands that Qwen Code executes. The python path AND file paths must work in the context where Qwen Code is running. Detect the environment before wiring anything.
 
 **Step 1: Identify the platform.**
 Run these commands and read the results:
@@ -137,9 +137,9 @@ echo $TERM_PROGRAM  # vscode = VS Code integrated terminal
 |---|---|---|---|
 | **Native Linux** | `uname` = Linux, no WSL in /proc/version | `which python3` → use result | Native paths work |
 | **Native macOS** | `uname` = Darwin | `which python3` → use result (often /opt/homebrew/bin/python3) | Native paths work |
-| **WSL Terminal** (Claude Code CLI in WSL) | Linux + "Microsoft" in /proc/version + NOT in VS Code | `which python3` → use result (typically /usr/bin/python3) | WSL paths work (/home/user/...) |
+| **WSL Terminal** (Qwen Code CLI in WSL) | Linux + "Microsoft" in /proc/version + NOT in VS Code | `which python3` → use result (typically /usr/bin/python3) | WSL paths work (/home/user/...) |
 | **VS Code Extension (WSL Remote)** | Linux + WSL + TERM_PROGRAM=vscode | `which python3` → use result | WSL paths work (VS Code server runs inside WSL) |
-| **VS Code Extension (Windows-native)** | platform: win32 in Claude Code, OR `uname` returns MINGW/MSYS | See troubleshooting below | Windows paths required |
+| **VS Code Extension (Windows-native)** | platform: win32 in Qwen Code, OR `uname` returns MINGW/MSYS | See troubleshooting below | Windows paths required |
 | **Native Windows** | No WSL, Windows paths | `where python` or `py -3` | Windows paths (C:\...) |
 
 **Step 3: Handle the tricky cases.**
@@ -158,7 +158,7 @@ This is the hardest case. The VS Code extension runs on the Windows side but can
    - This runs the VS Code server inside WSL — all hooks fire natively
    - All WSL paths and python work correctly
 
-2. **Use Claude Code CLI in WSL terminal instead of VS Code extension:**
+2. **Use Qwen Code CLI in WSL terminal instead of VS Code extension:**
    - Open a WSL terminal, `cd` to workspace, run `claude`
    - All hooks fire natively in WSL context
    - Use VS Code separately for editing if needed
@@ -178,7 +178,7 @@ This is the hardest case. The VS Code extension runs on the Windows side but can
    ```
    This is fragile and NOT recommended for most users.
 
-**IMPORTANT: Ask the user which environment they use Claude Code in before proceeding.**
+**IMPORTANT: Ask the user which environment they use Qwen Code in before proceeding.**
 If they use multiple environments (e.g., CLI in WSL + VS Code extension), explain the constraints and recommend option 1 (VS Code Remote WSL).
 
 ---
@@ -199,7 +199,7 @@ For each auto-fire hook:
 
 Hook registration format in settings.json:
 
-**CRITICAL: Each event type array contains objects with a `hooks` array inside — NOT flat command objects.** This is the Claude Code settings.json schema. Getting this wrong means hooks silently fail.
+**CRITICAL: Each event type array contains objects with a `hooks` array inside — NOT flat command objects.** This is the Qwen Code settings.json schema. Getting this wrong means hooks silently fail.
 
 ```json
 {
@@ -236,16 +236,16 @@ If hooks aren't firing after setup, diagnose with these checks:
 
 **Symptom: "operation blocked by hook" or "No such file"**
 - Python path is wrong for the current environment
-- Fix: re-detect python path for the environment Claude Code is running in
+- Fix: re-detect python path for the environment Qwen Code is running in
 
 **Symptom: Zero hooks fire (no CARL, no pulse, no calendar, nothing)**
 - Likely a platform mismatch (Windows paths vs WSL paths)
 - Check: `echo $PATH | tr ':' '\n' | grep python` — does python3 resolve?
-- Check: Can Claude Code's shell access the hook file? Run `cat {hook_path}` to verify
+- Check: Can Qwen Code's shell access the hook file? Run `cat {hook_path}` to verify
 
 **Symptom: Hooks fire in terminal but not in VS Code (or vice versa)**
-- Different Claude Code instances run in different contexts
-- VS Code extension (Windows-native) ≠ Claude Code CLI (WSL)
+- Different Qwen Code instances run in different contexts
+- VS Code extension (Windows-native) ≠ Qwen Code CLI (WSL)
 - Fix: Use VS Code Remote WSL extension so both contexts are WSL
 
 **Symptom: "python3: command not found"**
@@ -306,11 +306,11 @@ The MCP server package lives globally at `~/.qwen/base-framework/packages/base-m
 <step name="full_mode_extras">
 **Full mode only.**
 
-**CLAUDE.md audit:**
-1. Check if CLAUDE.md exists
-2. If exists: "Want me to audit your CLAUDE.md against the CLAUDE.md Strategy?"
+**QWEN.md audit:**
+1. Check if QWEN.md exists
+2. If exists: "Want me to audit your QWEN.md against the QWEN.md Strategy?"
    - If yes: route to `/base:audit-claude-md` (interactive, strategy-driven audit with CARL detection)
-3. If doesn't exist: "Want me to generate a CLAUDE.md from the strategy template?"
+3. If doesn't exist: "Want me to generate a QWEN.md from the strategy template?"
    - If yes: use `@{~/.qwen/commands/qwen-base/templates/claudemd-template.md}` as starting point, fill from detected workspace structure
 
 **First groom:**
@@ -347,8 +347,8 @@ Quick review and cleanup. Catches artifacts from path detection bugs, stale file
    - Check `node_modules/` exists in `.base/base-mcp/`
    - If broken: fix it (copy from global, npm install, re-register)
 
-5. **Structure alignment** — Verify workspace matches CLAUDE.md's Where section:
-   - Read CLAUDE.md (if it exists) and extract the Where section
+5. **Structure alignment** — Verify workspace matches QWEN.md's Where section:
+   - Read QWEN.md (if it exists) and extract the Where section
    - Compare declared directories against what actually exists
    - Flag any mismatches (declared but not created, or created but not declared)
    - Don't auto-fix — just report for user awareness
@@ -369,7 +369,7 @@ If everything is clean: "Workspace is clean. No artifacts, all paths valid, stru
 </steps>
 
 <output>
-Fully configured BASE installation. Standard mode: data layer with JSON surfaces, hooks wired, operator profile setup, MCP registered, post-scaffold cleanup verified. Full mode: adds CLAUDE.md audit and guided first groom.
+Fully configured BASE installation. Standard mode: data layer with JSON surfaces, hooks wired, operator profile setup, MCP registered, post-scaffold cleanup verified. Full mode: adds QWEN.md audit and guided first groom.
 </output>
 
 <acceptance-criteria>
@@ -383,7 +383,7 @@ Fully configured BASE installation. Standard mode: data layer with JSON surfaces
 - [ ] All auto-fire hooks installed and registered in settings.json (UserPromptSubmit + SessionStart)
 - [ ] BASE MCP server wired in .mcp.json
 - [ ] Post-scaffold cleanup passed (no artifacts, valid paths, structure aligned)
-- [ ] (Full mode) CLAUDE.md audit offered
+- [ ] (Full mode) QWEN.md audit offered
 - [ ] (Full mode) First groom offered
 - [ ] Operator informed of next groom date
 </acceptance-criteria>

package/src/framework/tasks/surface-convert.md

@@ -124,8 +124,8 @@ If any items couldn't be auto-mapped, present them for manual resolution.
 <step name="cleanup">
 ## Step 6: Clean Up
 
-1. Check if the original file is @-referenced in CLAUDE.md
-2. If found, offer: "Remove @{file} from CLAUDE.md? The surface hook replaces it."
+1. Check if the original file is @-referenced in QWEN.md
+2. If found, offer: "Remove @{file} from QWEN.md? The surface hook replaces it."
 3. Suggest: "Original file preserved at {path} for reference."
 
 Do NOT delete the original markdown file — the user decides its fate.

package/src/framework/templates/claudemd-template.md

@@ -1,15 +1,15 @@
-# CLAUDE.md Template
+# QWEN.md Template
 
-Reference template for generating strategy-compliant CLAUDE.md files. Placeholders use `{PLACEHOLDER}` format. Comments use `<!-- -->` and must be removed in final output.
+Reference template for generating strategy-compliant QWEN.md files. Placeholders use `{PLACEHOLDER}` format. Comments use `<!-- -->` and must be removed in final output.
 
 ***
 
 ```Markdown
-# CLAUDE.md
+# QWEN.md
 
 ## What
 
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+This file provides guidance to Qwen Code (claude.ai/code) when working with code in this repository.
 
 ---
 
@@ -97,6 +97,6 @@ NEVER {WRONG_ACTION} — {RIGHT_ACTION}
 * Remove all `<!-- -->` comments before finalizing
 * Remove placeholder sections that don't apply (not every workspace needs Git Strategy or Systems)
 * The Where tree should reflect the ACTUAL filesystem, verified by scanning
-* Rules should be workspace-identity-level, not operational. If a rule only applies during specific work (e.g., "when writing tests..."), it belongs in a domain-specific rule system, not CLAUDE.md
+* Rules should be workspace-identity-level, not operational. If a rule only applies during specific work (e.g., "when writing tests..."), it belongs in a domain-specific rule system, not QWEN.md
 * `@` references point Claude to files it should read on demand — use for anything volatile or detailed
 

package/src/framework/utils/scan-claude-dirs.py

@@ -270,16 +270,16 @@ def find_git_root(directory):
 
 
 def detect_git_boundary(claude_dir, workspace_root):
-    """Determine which config layers are visible when Claude Code boots in this directory.
+    """Determine which config layers are visible when Qwen Code boots in this directory.
 
-    Claude Code resolves the project root from the nearest .git boundary.
+    Qwen Code resolves the project root from the nearest .git boundary.
     - Global ~/.qwen/ is always visible
     - Workspace root .qwen/ is only visible if the project's git root IS the workspace root
     - The project's own .qwen/ is visible if it's at or under the git root
 
     Returns a dict describing the visibility context.
     """
-    # The .claude dir's parent is where Claude Code would boot
+    # The .claude dir's parent is where Qwen Code would boot
     parent_dir = os.path.dirname(claude_dir)
     git_root = find_git_root(parent_dir)
 

package/src/hooks/_template.py

@@ -70,7 +70,7 @@ For details on any item, use base_get_item("{SURFACE_NAME}", id)."""
 
 
 def main():
-    # --- Read hook input from stdin (Claude Code provides session context) ---
+    # --- Read hook input from stdin (Qwen Code provides session context) ---
     try:
         input_data = json.loads(sys.stdin.read())
         session_id = input_data.get("session_id", "")

package/src/hooks/psmm-injector.py

@@ -5,7 +5,7 @@ Purpose: Per-Session Meta Memory — inject ephemeral session observations
          into every prompt so they stay hot in long sessions (1M window).
 
          Uses a single psmm.json file with session-keyed entries.
-         Each session gets its own array keyed by Claude Code session UUID.
+         Each session gets its own array keyed by Qwen Code session UUID.
          Stale sessions are NOT auto-cleaned — that's the operator's job
          via CARL hygiene / BASE drift detection.
 

package/src/hooks/satellite-detection.py

@@ -4,7 +4,7 @@ Hook: satellite-detection.py
 Purpose: Scans the workspace recursively for .paul/paul.json files,
          auto-registers new satellites, and syncs paul.json state to
          workspace.json and projects.json.
-Triggers: SessionStart — runs once when Claude Code starts a session.
+Triggers: SessionStart — runs once when Qwen Code starts a session.
 Output: <base-satellites> block if new satellites registered, silent otherwise.
 
 Sync flow (paul.json → workspace.json → projects.json):

package/src/skill/base.md

@@ -3,14 +3,14 @@ name: base
 type: suite
 version: 0.1.0
 category: workspace-orchestration
-description: "Builder's Automated State Engine — workspace lifecycle management for Claude Code. Scaffold, audit, groom, and maintain AI builder workspaces. Manage data surfaces for structured context injection. Use when user mentions workspace setup, cleanup, organization, maintenance, grooming, auditing workspace health, surfaces, or BASE."
+description: "Builder's Automated State Engine — workspace lifecycle management for Qwen Code. Scaffold, audit, groom, and maintain AI builder workspaces. Manage data surfaces for structured context injection. Use when user mentions workspace setup, cleanup, organization, maintenance, grooming, auditing workspace health, surfaces, or BASE."
 allowed-tools: [Read, Write, Glob, Grep, Edit, Bash, Agent, AskUserQuestion]
 ---
 
 <activation>
 
 ## What
-BASE (Builder's Automated State Engine) manages the lifecycle of a Claude Code workspace. It scaffolds new workspaces, audits existing ones, runs structured grooming cycles, and maintains workspace health through automated drift detection.
+BASE (Builder's Automated State Engine) manages the lifecycle of a Qwen Code workspace. It scaffolds new workspaces, audits existing ones, runs structured grooming cycles, and maintains workspace health through automated drift detection.
 
 ## When to Use
 - User says "base", "workspace", "cleanup", "organize", "audit my workspace", "groom", "surface", "create a surface"
@@ -45,7 +45,7 @@ Workspace operations engineer. Knows the territory, tracks what's drifting, enfo
 - Context document lifecycle (projects.json, state.json, entities.json)
 - Tool and configuration management
 - Drift detection and prevention patterns
-- Claude Code ecosystem (PAUL, CARL, AEGIS, Skillsmith integration)
+- Qwen Code ecosystem (PAUL, CARL, AEGIS, Skillsmith integration)
 
 </persona>
 
@@ -59,7 +59,7 @@ Workspace operations engineer. Knows the territory, tracks what's drifting, enfo
 | `/base:scaffold` | Set up BASE in a new workspace | `@{~/.qwen/commands/qwen-base/tasks/scaffold.md}` |
 | `/base:status` | Quick health check (one-liner) | `@{~/.qwen/commands/qwen-base/tasks/status.md}` |
 | `/base:history` | Workspace evolution timeline | `@{~/.qwen/commands/qwen-base/tasks/history.md}` |
-| `/base:audit-claude-md` | Audit CLAUDE.md, generate recommended version | `@{~/.qwen/commands/qwen-base/tasks/audit-claude-md.md}` |
+| `/base:audit-claude-md` | Audit QWEN.md, generate recommended version | `@{~/.qwen/commands/qwen-base/tasks/audit-claude-md.md}` |
 | `/base:carl-hygiene` | CARL domain maintenance and rule review | `@{~/.qwen/commands/qwen-base/tasks/carl-hygiene.md}` |
 | `/base:surface create` | Create a new data surface (guided) | `@{~/.qwen/commands/qwen-base/tasks/surface-create.md}` |
 | `/base:surface convert` | Convert markdown file to data surface | `@{~/.qwen/commands/qwen-base/tasks/surface-convert.md}` |

package/src/templates/workspace.json

@@ -49,7 +49,7 @@
     },
     "system-layer": {
       "type": "system-layer",
-      "description": "Claude Code commands, hooks, skills, CARL domains",
+      "description": "Qwen Code commands, hooks, skills, CARL domains",
       "paths": [
         ".qwen/commands/",
         ".qwen/hooks/",