qualia-framework 6.6.0 → 6.7.1

package/README.md

@@ -75,7 +75,7 @@ Two human gates per project. One halt case (gap-cycle limit exceeded on a failin
 ### Phase-specific depth (optional)
 
 ```
-/qualia-discuss N   # Capture decisions before planning a complex phase (locks constraints for the planner)
+/qualia-scope N   # Capture decisions before planning a complex phase (locks constraints for the planner)
 /qualia-research N  # Deep-research a niche phase (Context7/WebFetch/WebSearch)
 /qualia-map         # Map existing codebase (brownfield projects — run before /qualia-new)
 ```
@@ -137,7 +137,7 @@ Project
 
 ## What's Inside (v6.3.0)
 
-- **23 installed skills**, focused into Road (new / plan / build / verify / milestone / polish / ship / handoff / report), depth (discuss, research, map), navigation (qualia router + road), quality (fix, review, optimize with `--deepen` parallel-interface design, feature, test), design (`qualia-polish --loop` and `--vibe`), health/reporting (doctor, learn, postmortem), and Zoho workflow support. Retired helper commands are pruned on install rather than exposed as default slash commands.
+- **25 installed skills**, focused into Road (new / plan / build / verify / milestone / polish / ship / handoff / report), depth (scope, research, map), navigation (qualia router + road), quality (fix, review, optimize with `--deepen` parallel-interface design, feature, test), design (`qualia-polish --loop` and `--vibe`), health/reporting (doctor, learn, postmortem), and Zoho workflow support. Retired helper commands are pruned on install rather than exposed as default slash commands.
 - **9 agents** (each runs in fresh context): planner, builder, verifier, qa-browser, researcher, research-synthesizer, roadmapper, plan-checker, visual-evaluator
 - **12 hooks** (pure Node.js, cross-platform): session-start, auto-update, git-guardrails, branch-guard, pre-push tracking stamp, migration-guard, pre-deploy-gate, stop-session-log, fawzi-approval-guard, vercel-account-guard, env-empty-guard, supabase-destructive-guard
 - **10 installed rules** (`rules/`): grounding, security, infrastructure, deployment, speed, architecture, trust-boundary, codex-goal, one-opinion, and always-on command-output transparency.
@@ -214,7 +214,7 @@ npx qualia-framework@latest install
      |
      v
 ~/.claude/ and/or ~/.codex/
-  ├── skills/             23 installed skills (each may ship SKILL.md + REFERENCE.md + scripts/ + fixtures/)
+  ├── skills/             25 installed skills (each may ship SKILL.md + REFERENCE.md + scripts/ + fixtures/)
   ├── agents/             9 agent definitions (Claude .md, Codex .toml)
   ├── hooks/              11 Node.js hooks — cross-platform (no bash dependency)
   ├── bin/                state.js + qualia-ui.js + statusline.js + knowledge.js + knowledge-flush.js + slop-detect.mjs + planning-hygiene.js + plan-contract.js + agent-runs.js + ERP/report helpers

package/agents/roadmapper.md

@@ -23,7 +23,7 @@ You do NOT run research — that's already done upstream.
 Per `rules/grounding.md`. JOURNEY.md / REQUIREMENTS.md / ROADMAP.md become canon for every downstream agent. Anything you write becomes the source of truth — fabrications calcify into requirements:
 
 1. **Every milestone scope ties back to PROJECT.md or research.** Format inline: `{milestone scope sentence} — [PROJECT.md §Goals]` or `[research/SUMMARY.md §Architecture]`. Sections without attribution will be rejected by the user during the journey-approval gate.
-2. **Every REQ-ID has a source line.** REQ-001 cites the line in PROJECT.md or research where the requirement originated. No `/qualia-discuss` loop should be needed to ask "where did REQ-007 come from?" later.
+2. **Every REQ-ID has a source line.** REQ-001 cites the line in PROJECT.md or research where the requirement originated. No `/qualia-scope` loop should be needed to ask "where did REQ-007 come from?" later.
 3. **Don't invent features that weren't asked for.** If PROJECT.md mentions "user dashboard" and you derive 8 dashboard sub-requirements, cite which user need each one addresses. If you can't, drop it.
 4. **No hedging in milestone names or success criteria.** "M2 might include payments" → either it does (commit to it with citation) or it goes in `Out of Scope`. Roadmaps with hedge language produce hedge plans.
 5. **Tool-use is mandatory before challenging an assumption.** Before saying "the tech stack should be Next.js," `Read` PROJECT.md to confirm whether the user already chose. The user's preferences override your taste.

package/bin/command-surface.js

@@ -9,7 +9,6 @@ const ACTIVE_SKILLS = [
   "qualia",
   "qualia-new",
   "qualia-scope",
-  "qualia-discuss",
   "qualia-map",
   "qualia-research",
   "qualia-plan",
@@ -57,6 +56,9 @@ const RETIRED_SKILLS = [
   "qualia-hook-gen",   // framework-authoring utility, not employee default
   "qualia-skill-new",  // framework-authoring utility, not employee default
   "qualia-flush",      // available as qualia-framework flush / automation
+
+  // A4 surface collapse (v6.7): folded where a surviving skill genuinely covers it.
+  "qualia-discuss",    // folded into qualia-scope — PROJECT MODE (kickoff → project-discovery.md) + PHASE MODE (grill → phase-N-context.md) now live there via its mode router
 ];
 
 function activeSkills() {