qualia-framework 2.4.5 → 2.4.9

package/framework/qualia-framework/workflows/settings.md

@@ -12,8 +12,8 @@ Read all files referenced by the invoking prompt's execution_context before star
 Ensure config exists and load current state:
 
 ```bash
-node /home/qualia/.claude/qualia-engine/bin/qualia-tools.js config-ensure-section
-INIT=$(node /home/qualia/.claude/qualia-engine/bin/qualia-tools.js state load)
+node /home/qualia/.claude/qualia-framework/bin/qualia-tools.js config-ensure-section
+INIT=$(node /home/qualia/.claude/qualia-framework/bin/qualia-tools.js state load)
 ```
 
 Creates `.planning/config.json` with defaults if missing and loads current config values.

package/framework/qualia-framework/workflows/update.md

@@ -13,11 +13,11 @@ Detect whether Qualia is installed locally or globally by checking both location
 
 ```bash
 # Check local first (takes priority)
-if [ -f "./.claude/qualia-engine/VERSION" ]; then
-  cat "./.claude/qualia-engine/VERSION"
+if [ -f "./.claude/qualia-framework/VERSION" ]; then
+  cat "./.claude/qualia-framework/VERSION"
   echo "LOCAL"
-elif [ -f /home/qualia/.claude/qualia-engine/VERSION ]; then
-  cat /home/qualia/.claude/qualia-engine/VERSION
+elif [ -f /home/qualia/.claude/qualia-framework/VERSION ]; then
+  cat /home/qualia/.claude/qualia-framework/VERSION
   echo "GLOBAL"
 else
   echo "UNKNOWN"
@@ -47,14 +47,14 @@ Proceed to install step (treat as version 0.0.0 for comparison).
 Check npm for latest version:
 
 ```bash
-npm view qualia-engine-cc version 2>/dev/null
+npm view qualia-framework-cc version 2>/dev/null
 ```
 
 **If npm check fails:**
 ```
 Couldn't check for updates (offline or npm unavailable).
 
-To update manually: `npx qualia-engine-cc --global`
+To update manually: `npx qualia-framework-cc --global`
 ```
 
 Exit.
@@ -118,7 +118,7 @@ Exit.
 
 ⚠️  **Note:** The installer performs a clean install of Qualia folders:
 - `skills/qualia/` will be wiped and replaced
-- `qualia-engine/` will be wiped and replaced
+- `qualia-framework/` will be wiped and replaced
 - `agents/qualia-*` files will be replaced
 
 (Paths are relative to your install location: `/home/qualia/.claude/` for global, `./.claude/` for local)
@@ -146,12 +146,12 @@ Run the update using the install type detected in step 1:
 
 **If LOCAL install:**
 ```bash
-npx qualia-engine-cc --local
+npx qualia-framework-cc --local
 ```
 
 **If GLOBAL install (or unknown):**
 ```bash
-npx qualia-engine-cc --global
+npx qualia-framework-cc --global
 ```
 
 Capture output. If install fails, show error and exit.
@@ -179,7 +179,7 @@ Format completion message (changelog was already shown in confirmation step):
 
 ⚠️  Restart Claude Code to pick up the new commands.
 
-[View full changelog](https://github.com/glittercowboy/qualia-engine/blob/main/CHANGELOG.md)
+[View full changelog](https://github.com/glittercowboy/qualia-framework/blob/main/CHANGELOG.md)
 ```
 </step>
 

package/framework/qualia-framework/workflows/verify-phase.md

@@ -18,8 +18,8 @@ Then verify each level against the actual codebase.
 </core_principle>
 
 <required_reading>
-@/home/qualia/.claude/qualia-engine/references/verification-patterns.md
-@/home/qualia/.claude/qualia-engine/templates/verification-report.md
+@/home/qualia/.claude/qualia-framework/references/verification-patterns.md
+@/home/qualia/.claude/qualia-framework/templates/verification-report.md
 </required_reading>
 
 <process>
@@ -28,14 +28,14 @@ Then verify each level against the actual codebase.
 Load phase operation context:
 
 ```bash
-INIT=$(node /home/qualia/.claude/qualia-engine/bin/qualia-tools.js init phase-op "${PHASE_ARG}")
+INIT=$(node /home/qualia/.claude/qualia-framework/bin/qualia-tools.js init phase-op "${PHASE_ARG}")
 ```
 
 Extract from init JSON: `phase_dir`, `phase_number`, `phase_name`, `has_plans`, `plan_count`.
 
 Then load phase details and list plans/summaries:
 ```bash
-node /home/qualia/.claude/qualia-engine/bin/qualia-tools.js roadmap get-phase "${phase_number}"
+node /home/qualia/.claude/qualia-framework/bin/qualia-tools.js roadmap get-phase "${phase_number}"
 grep -E "^| ${phase_number}" .planning/REQUIREMENTS.md 2>/dev/null
 ls "$phase_dir"/*-SUMMARY.md "$phase_dir"/*-PLAN.md 2>/dev/null
 ```
@@ -166,7 +166,7 @@ REPORT_PATH="$PHASE_DIR/${PHASE_NUM}-VERIFICATION.md"
 
 Fill template sections: frontmatter (phase/timestamp/status/score), goal achievement, artifact table, wiring table, requirements coverage, anti-patterns, human verification, gaps summary, fix plans (if gaps_found), metadata.
 
-See /home/qualia/.claude/qualia-engine/templates/verification-report.md for complete template.
+See /home/qualia/.claude/qualia-framework/templates/verification-report.md for complete template.
 </step>
 
 <step name="return_to_orchestrator">

package/framework/qualia-framework/workflows/verify-work.md

@@ -15,7 +15,7 @@ No Pass/Fail buttons. No severity questions. Just: "Here's what should happen. D
 </philosophy>
 
 <template>
-@/home/qualia/.claude/qualia-engine/templates/UAT.md
+@/home/qualia/.claude/qualia-framework/templates/UAT.md
 </template>
 
 <process>
@@ -24,7 +24,7 @@ No Pass/Fail buttons. No severity questions. Just: "Here's what should happen. D
 If $ARGUMENTS contains a phase number, load context:
 
 ```bash
-INIT=$(node /home/qualia/.claude/qualia-engine/bin/qualia-tools.js init verify-work "${PHASE_ARG}")
+INIT=$(node /home/qualia/.claude/qualia-framework/bin/qualia-tools.js init verify-work "${PHASE_ARG}")
 ```
 
 Parse JSON for: `planner_model`, `checker_model`, `commit_docs`, `phase_found`, `phase_dir`, `phase_number`, `phase_name`, `has_verification`.
@@ -321,7 +321,7 @@ Clear Current Test section:
 
 Commit the UAT file:
 ```bash
-node /home/qualia/.claude/qualia-engine/bin/qualia-tools.js commit "test({phase}): complete UAT - {passed} passed, {issues} issues" --files ".planning/phases/XX-name/{phase}-UAT.md"
+node /home/qualia/.claude/qualia-framework/bin/qualia-tools.js commit "test({phase}): complete UAT - {passed} passed, {issues} issues" --files ".planning/phases/XX-name/{phase}-UAT.md"
 ```
 
 Present summary:
@@ -389,7 +389,7 @@ Spawning parallel debug agents to investigate each issue.
 ```
 
 - Load diagnose-issues workflow
-- Follow @/home/qualia/.claude/qualia-engine/workflows/diagnose-issues.md
+- Follow @/home/qualia/.claude/qualia-framework/workflows/diagnose-issues.md
 - Spawn parallel debug agents for each issue
 - Collect root causes
 - Update UAT.md with root causes

package/framework/rules/context7.md

@@ -2,10 +2,13 @@
 alwaysApply: true
 ---
 
-When working with libraries, frameworks, or APIs — fetch current documentation instead of relying on training data. This includes setup questions, code generation, API references, and anything involving specific packages.
+Use Context7 MCP to fetch current documentation whenever the user asks about a library, framework, SDK, API, CLI tool, or cloud service -- even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. This includes API syntax, configuration, version migration, library-specific debugging, setup instructions, and CLI tool usage. Use even when you think you know the answer -- your training data may not reflect recent changes. Prefer this over web search for library docs.
+
+Do not use for: refactoring, writing scripts from scratch, debugging business logic, code review, or general programming concepts.
 
 ## Steps
 
-1. If Context7 MCP is available, use `resolve-library-id` + `query-docs`
-2. Otherwise, use WebFetch or WebSearch to find current docs
-3. Answer using the fetched docs — include code examples and cite the version
+1. Always start with `resolve-library-id` using the library name and the user's question, unless the user provides an exact library ID in `/org/project` format
+2. Pick the best match (ID format: `/org/project`) by: exact name match, description relevance, code snippet count, source reputation (High/Medium preferred), and benchmark score (higher is better). If results don't look right, try alternate names or queries (e.g., "next.js" not "nextjs", or rephrase the question). Use version-specific IDs when the user mentions a version
+3. `query-docs` with the selected library ID and the user's full question (not single words)
+4. Answer using the fetched docs

package/framework/rules/speed.md

@@ -17,8 +17,7 @@ alwaysApply: true
 **Use shortcuts:**
 - `/ship` — Full deploy pipeline (quality gates → commit → deploy → verify)
 - `/status` — Quick project health check
-- `/audit` — Deep security + quality audit
-- `/switch <project>` — Switch project context
+- `/qualia-review` — Deep security + quality audit
 - `/memory` — View/manage persistent rules
 - `/learn` — Save a lesson from a mistake
-- `/handoff` — Save context before /clear
+- `/qualia-pause-work` — Save context before /clear

package/framework/scripts/sync-to-framework.sh

@@ -22,7 +22,7 @@ COMPONENTS=(
     "hooks"
     "rules"
     "knowledge"
-    "qualia-engine"
+    "qualia-framework"
     "scripts"
 )
 

package/framework/skills/animate/SKILL.md

@@ -30,8 +30,8 @@ You cannot do a great job without having necessary context, such as target audie
 
 Attempt to gather these from the current thread or codebase.
 
-1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and call the AskUserQuestionTool to clarify. whether you got it right.
-2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and call the AskUserQuestionTool to clarify. clarifying questions first to complete your context.
+1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and ask the user directly to clarify. whether you got it right.
+2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and ask the user directly to clarify. clarifying questions first to complete your context.
 
 Do NOT proceed until you have answers. Guessing leads to inappropriate or excessive animation.
 
@@ -58,7 +58,7 @@ Analyze where motion would improve the experience:
    - Who's the audience? (Motion-sensitive users? Power users who want speed?)
    - What matters most? (One hero animation vs many micro-interactions?)
 
-If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify.
+If any of these are unclear from the codebase, STOP and ask the user directly to clarify.
 
 **CRITICAL**: Respect `prefers-reduced-motion`. Always provide non-animated alternatives for users who need them.
 

package/framework/skills/bolder/SKILL.md

@@ -30,8 +30,8 @@ You cannot do a great job without having necessary context, such as target audie
 
 Attempt to gather these from the current thread or codebase.
 
-1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and call the AskUserQuestionTool to clarify. whether you got it right.
-2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and call the AskUserQuestionTool to clarify. clarifying questions first to complete your context.
+1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and ask the user directly to clarify. whether you got it right.
+2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and ask the user directly to clarify. clarifying questions first to complete your context.
 
 Do NOT proceed until you have answers. Guessing leads to generic AI slop.
 
@@ -59,7 +59,7 @@ Analyze what makes the design feel too safe or boring:
    - Who's the audience? (What will resonate?)
    - What are the constraints? (Brand guidelines, accessibility, performance)
 
-If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify.
+If any of these are unclear from the codebase, STOP and ask the user directly to clarify.
 
 **CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos.
 

package/framework/skills/colorize/SKILL.md

@@ -30,8 +30,8 @@ You cannot do a great job without having necessary context, such as target audie
 
 Attempt to gather these from the current thread or codebase.
 
-1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and call the AskUserQuestionTool to clarify. whether you got it right.
-2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and call the AskUserQuestionTool to clarify. clarifying questions first to complete your context.
+1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and ask the user directly to clarify. whether you got it right.
+2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and ask the user directly to clarify. clarifying questions first to complete your context.
 
 Do NOT proceed until you have answers. Guessing leads to generic AI slop colors.
 
@@ -59,7 +59,7 @@ Analyze the current state and identify opportunities:
    - **Wayfinding**: Helping users navigate and understand structure
    - **Delight**: Moments of visual interest and personality
 
-If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify.
+If any of these are unclear from the codebase, STOP and ask the user directly to clarify.
 
 **CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose.
 

package/framework/skills/delight/SKILL.md

@@ -30,8 +30,8 @@ You cannot do a great job without having necessary context, such as target audie
 
 Attempt to gather these from the current thread or codebase.
 
-1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and call the AskUserQuestionTool to clarify. whether you got it right.
-2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and call the AskUserQuestionTool to clarify. clarifying questions first to complete your context.
+1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and ask the user directly to clarify. whether you got it right.
+2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and ask the user directly to clarify. clarifying questions first to complete your context.
 
 Do NOT proceed until you have answers. Delight that's wrong for the context is worse than no delight at all.
 
@@ -66,7 +66,7 @@ Identify where delight would enhance (not distract from) the experience:
    - **Helpful surprises**: Anticipating needs before users ask (productivity tools)
    - **Sensory richness**: Satisfying sounds, smooth animations (creative tools)
 
-If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify.
+If any of these are unclear from the codebase, STOP and ask the user directly to clarify.
 
 **CRITICAL**: Delight should enhance usability, never obscure it. If users notice the delight more than accomplishing their goal, you've gone too far.
 

package/framework/skills/design-quieter/SKILL.md

@@ -30,8 +30,8 @@ You cannot do a great job without having necessary context, such as target audie
 
 Attempt to gather these from the current thread or codebase.
 
-1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and call the AskUserQuestionTool to clarify. whether you got it right.
-2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and call the AskUserQuestionTool to clarify. clarifying questions first to complete your context.
+1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and ask the user directly to clarify. whether you got it right.
+2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and ask the user directly to clarify. clarifying questions first to complete your context.
 
 Do NOT proceed until you have answers. Guessing leads to generic design.
 
@@ -59,7 +59,7 @@ Analyze what makes the design feel too intense:
    - What's working? (Don't throw away good ideas)
    - What's the core message? (Preserve what matters)
 
-If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify.
+If any of these are unclear from the codebase, STOP and ask the user directly to clarify.
 
 **CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness.
 

package/framework/skills/distill/SKILL.md

@@ -30,8 +30,8 @@ You cannot do a great job without having necessary context, such as target audie
 
 Attempt to gather these from the current thread or codebase.
 
-1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and call the AskUserQuestionTool to clarify. whether you got it right.
-2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and call the AskUserQuestionTool to clarify. clarifying questions first to complete your context.
+1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and STOP and ask the user directly to clarify. whether you got it right.
+2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and ask the user directly to clarify. clarifying questions first to complete your context.
 
 Do NOT proceed until you have answers. Simplifying the wrong things destroys usability.
 
@@ -59,7 +59,7 @@ Analyze what makes the design feel complex or cluttered:
    - What can be removed, hidden, or combined?
    - What's the 20% that delivers 80% of value?
 
-If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify.
+If any of these are unclear from the codebase, STOP and ask the user directly to clarify.
 
 **CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence.
 

package/framework/skills/qualia-add-todo/SKILL.md

@@ -21,7 +21,7 @@ Ensure the todos directory exists:
 mkdir -p .planning/todos
 ```
 
-Reference: `~/.claude/qualia-engine/workflows/add-todo.md`
+Reference: `~/.claude/qualia-framework/workflows/add-todo.md`
 
 ### 2. Extract Content
 

package/framework/skills/qualia-check-todos/SKILL.md

@@ -21,7 +21,7 @@ Read all files in `.planning/todos/`. Parse frontmatter for status, area, priori
 
 Also read `.planning/STATE.md` and `.planning/ROADMAP.md` for project context.
 
-Reference: `~/.claude/qualia-engine/workflows/check-todos.md`
+Reference: `~/.claude/qualia-framework/workflows/check-todos.md`
 
 ### 2. Display List
 

package/framework/skills/qualia-debug/SKILL.md

@@ -20,7 +20,7 @@ Systematic debugging with four modes: interactive symptom-based debugging, deep
 
 Load state with `qualia-tools.js`:
 ```bash
-node ~/.claude/qualia-engine/bin/qualia-tools.js phase-op current
+node ~/.claude/qualia-framework/bin/qualia-tools.js phase-op current
 ```
 
 Check for existing debug sessions in `.planning/debug/`.
@@ -59,7 +59,7 @@ Reference: `~/.claude/agents/qualia-debugger.md`
 
 Model resolution:
 ```bash
-node ~/.claude/qualia-engine/bin/qualia-tools.js resolve-model qualia-debugger
+node ~/.claude/qualia-framework/bin/qualia-tools.js resolve-model qualia-debugger
 ```
 
 The debugger follows a systematic approach:

package/framework/skills/qualia-discuss-phase/SKILL.md

@@ -22,7 +22,7 @@ The phase boundary is FIXED — discussion clarifies HOW to implement, not WHETH
 
 Read the phase description from ROADMAP.md and any existing research.
 
-Reference: `~/.claude/qualia-engine/workflows/discuss-phase.md`
+Reference: `~/.claude/qualia-framework/workflows/discuss-phase.md`
 
 ### 2. Identify Domain Gray Areas
 
@@ -65,7 +65,7 @@ Write decisions to `.planning/phases/{phase}-{slug}/{phase}-CONTEXT.md`:
 - Specific preferences expressed
 ```
 
-Template: `~/.claude/qualia-engine/templates/context.md`
+Template: `~/.claude/qualia-framework/templates/context.md`
 
 ### 5. Handoff
 

package/framework/skills/qualia-framework-audit/SKILL.md

@@ -486,7 +486,7 @@ Output as direct text (NOT via Bash):
 
   Date         {date}
   Scope        {full / specific dimension}
-  Framework    v{qualia-engine VERSION}
+  Framework    v{qualia-framework VERSION}
 
   INVENTORY
   Agents       {N}     Teams     {N}

package/framework/skills/qualia-list-phase-assumptions/SKILL.md

@@ -22,7 +22,7 @@ Read:
 - `.planning/REQUIREMENTS.md` — Related requirements
 - Phase RESEARCH.md if it exists
 
-Reference: `~/.claude/qualia-engine/workflows/list-phase-assumptions.md`
+Reference: `~/.claude/qualia-framework/workflows/list-phase-assumptions.md`
 
 ### 2. Analyze 5 Areas
 

package/framework/skills/qualia-new-milestone/SKILL.md

@@ -25,11 +25,11 @@ Read:
 - `.planning/milestones/` — Previous milestone archives (if any)
 - `.planning/STATE.md` — Current state
 
-Reference: `~/.claude/qualia-engine/workflows/new-milestone.md`
+Reference: `~/.claude/qualia-framework/workflows/new-milestone.md`
 
 ### 2. Questioning Phase
 
-Reference: `~/.claude/qualia-engine/references/questioning.md`
+Reference: `~/.claude/qualia-framework/references/questioning.md`
 
 Ask targeted questions building on existing project knowledge:
 - What's the goal of this milestone?
@@ -50,7 +50,7 @@ Add new milestone section to existing PROJECT.md (don't overwrite).
 
 #### Create REQUIREMENTS.md
 Fresh requirements for this milestone:
-Template: `~/.claude/qualia-engine/templates/requirements.md`
+Template: `~/.claude/qualia-framework/templates/requirements.md`
 - Milestone definition (v{next_version})
 - Functional requirements
 - Non-functional requirements
@@ -65,7 +65,7 @@ Reset phase tracking for the new milestone while preserving project-level info.
 #### Research (if conducted)
 Save to `.planning/research/` directory.
 
-UI/brand reference: `~/.claude/qualia-engine/references/ui-brand.md`
+UI/brand reference: `~/.claude/qualia-framework/references/ui-brand.md`
 
 ### 5. Next Step
 

package/framework/skills/qualia-optimize/SKILL.md

@@ -83,7 +83,7 @@ Classify project type: `web` | `voice` | `mobile` | `agent` | `edge-functions` |
 
 ### Step 4: Spawn Wave 1 Agents (parallel)
 
-Based on mode, spawn agents in a **single message** with multiple Task() calls.
+Based on mode, spawn agents in a **single message** with multiple Agent() calls.
 
 | Mode | Agents |
 |------|--------|
@@ -93,12 +93,12 @@ Based on mode, spawn agents in a **single message** with multiple Task() calls.
 | `backend` | backend-agent only |
 | `alignment` | general-purpose with alignment prompt |
 
-**CRITICAL**: Inline ALL planning context into each agent prompt. `@` references don't work across Task() boundaries.
+**CRITICAL**: Inline ALL planning context into each agent prompt. `@` references don't work across Agent() boundaries.
 
 #### Frontend Agent Prompt
 
 ```
-Task(
+Agent(
   prompt="You are optimizing a project's frontend. Read the planning docs and codebase rules below, then analyze the actual code.
 
 <planning>
@@ -148,7 +148,7 @@ For EVERY finding, output in this exact format:
 #### Backend Agent Prompt
 
 ```
-Task(
+Agent(
   prompt="You are optimizing a project's backend. Read the planning docs and security rules below, then analyze the actual code.
 
 <planning>
@@ -201,7 +201,7 @@ For EVERY finding, output:
 #### Performance Oracle Prompt
 
 ```
-Task(
+Agent(
   prompt="You are analyzing cross-cutting performance issues. Read the project context, then analyze the codebase.
 
 <planning>
@@ -250,7 +250,7 @@ For EVERY finding, output:
 After all Wave 1 agents return, spawn the architecture strategist with their combined findings:
 
 ```
-Task(
+Agent(
   prompt="You are synthesizing optimization findings from 3 specialist agents. Look for cross-cutting architectural issues.
 
 <wave1_findings>
@@ -367,7 +367,7 @@ status: {clean|needs_attention|critical_issues}
 
 Commit:
 ```bash
-node ~/.claude/qualia-engine/bin/qualia-tools.js commit "docs: optimization report ({mode} mode, {critical} critical)" --files .planning/OPTIMIZE.md
+node ~/.claude/qualia-framework/bin/qualia-tools.js commit "docs: optimization report ({mode} mode, {critical} critical)" --files .planning/OPTIMIZE.md
 ```
 
 **Present results:**

package/framework/skills/qualia-pause-work/SKILL.md

@@ -18,7 +18,7 @@ Save current session context so the next session can pick up exactly where you l
 
 Load `.planning/STATE.md` and check current phase status.
 
-Reference: `~/.claude/qualia-engine/workflows/pause-work.md`
+Reference: `~/.claude/qualia-framework/workflows/pause-work.md`
 
 ### 2. Create `.continue-here.md`
 

package/framework/skills/qualia-plan-milestone-gaps/SKILL.md

@@ -21,7 +21,7 @@ ls -t .planning/v*-MILESTONE-AUDIT.md | head -1
 
 Read the most recent `v*-MILESTONE-AUDIT.md` file.
 
-Reference: `~/.claude/qualia-engine/workflows/plan-milestone-gaps.md`
+Reference: `~/.claude/qualia-framework/workflows/plan-milestone-gaps.md`
 
 ### 2. Load Project Context