qualia-framework 5.9.1 → 6.2.7

package/skills/qualia-hook-gen/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: qualia-hook-gen
-description: "Take a project's CLAUDE.md or rules/*.md instruction and convert it deterministically into a Claude Code pre-tool-use hook. Generates block-{cmd}.sh + the settings.json patch + activation steps. Lets users actually shrink their CLAUDE.md instead of just hearing the instruction-budget advice. Trigger on 'qualia-hook-gen', 'turn this rule into a hook', 'enforce this deterministically', 'block npm', 'force pnpm', 'convert claude.md to hooks', 'shrink my instruction budget'. v5.3 from Matt Pocock's enforce-deterministically-not-instructionally pattern."
+description: "Take a project's CLAUDE.md or rules/*.md instruction and convert it deterministically into a Claude Code pre-tool-use hook. Generates block-{cmd}.sh + the settings.json patch + activation steps. Lets users actually shrink their CLAUDE.md instead of just hearing the instruction-budget advice. Trigger on 'qualia-hook-gen', 'turn this rule into a hook', 'enforce this deterministically', 'block npm', 'force pnpm', 'convert claude.md to hooks', 'shrink my instruction budget'."
 allowed-tools:
   - Bash
   - Read

package/skills/qualia-learn/SKILL.md

@@ -7,6 +7,7 @@ allowed-tools:
   - Edit
   - Glob
   - Grep
+  - Bash
 ---
 
 # /qualia-learn — Save Knowledge

package/skills/qualia-map/SKILL.md

@@ -8,6 +8,7 @@ allowed-tools:
   - Grep
   - Glob
   - Agent
+  - AskUserQuestion
 ---
 
 # /qualia-map — Codebase Mapping (Brownfield)
@@ -162,7 +163,7 @@ Read `.planning/codebase/onboarding.md`. Per detected dimension:
 - Domain docs at non-default path → `.planning/agents/domain.md`
 - CLAUDE.md/AGENTS.md found → APPEND `## Qualia substrate` (never overwrite)
 
-"none" → skip silently, defaults apply.
+"none" → report that no preference was provided; defaults apply.
 
 ### 6. Commit
 

package/skills/qualia-milestone/SKILL.md

@@ -38,7 +38,7 @@ node ~/.claude/bin/state.js check
 
 If either fires (without `--force`), stop and show the error. The user must verify remaining phases first (or add `--force` for explicit bypass on a preview/demo milestone).
 
-### 1b. Demo-Extension Branch (v5.6)
+### 1b. Demo-Extension Branch
 
 Detect if this is a demo project closing its only milestone:
 
@@ -276,6 +276,6 @@ node ~/.claude/bin/qualia-ui.js end "M{N} CLOSED · M{N+1} OPEN" "/qualia-plan 1
 2. **JOURNEY.md is the source of truth for next milestone.** Don't ask the user to name it unless JOURNEY.md is missing (legacy project).
 3. **Archive, don't delete.** Old phase work stays accessible via `.planning/archive/`.
 4. **New milestone = fresh phase numbering.** First phase of the new milestone is Phase 1, not Phase {N+1}.
-5. **ERP sync aware.** tracking.json milestones[] gets a summary entry on close — the ERP reads this to render the tree.
+5. **Report aware.** `tracking.json.milestones[]` gets a summary entry on close so local status and `/qualia-report` have milestone context.
 6. **Handoff is the final milestone (full projects).** If the current milestone IS Handoff, there is no "next" — route to `/qualia-report` and the project is done.
 7. **Demo closes via the demo-extension branch (Step 1b).** A demo's single milestone closing triggers the "client signed?" question. The framework never silently auto-extends a demo without asking — the conversion is a real business decision.

package/skills/qualia-new/SKILL.md

@@ -153,7 +153,7 @@ git add .planning/PROJECT.md
 git commit -m "docs: initialize project"
 ```
 
-### Step 8a. Seed CONTEXT.md and decisions/ (v5.0 — REQUIRED)
+### Step 8a. Seed CONTEXT.md and decisions/ (REQUIRED)
 
 The domain glossary is the single highest-leverage piece of substrate — every road agent loads it BEFORE PROJECT.md/DESIGN.md. Misalignment is the #1 failure mode in AI coding; CONTEXT.md kills it.
 
@@ -166,7 +166,7 @@ mkdir -p .planning/decisions
 cp ~/.claude/qualia-templates/decisions/ADR-template.md .planning/decisions/_template.md
 ```
 
-Then **seed the glossary from the questioning answers**. For each domain term that came up during Step 1 (Deep Questioning) — entities, actions, statuses, key nouns the user repeatedly said — add an entry to `.planning/CONTEXT.md` under `## Language` with:
+Then **seed the glossary from the questioning answers**. For each domain term that came up during the Step 4 `/qualia-discuss` interview — entities, actions, statuses, key nouns the user repeatedly said — add an entry to `.planning/CONTEXT.md` under `## Language` with:
 - the term
 - a one-sentence definition
 - an `Avoid:` line listing rejected synonyms (terms the team should NOT use for this concept)
@@ -182,7 +182,7 @@ git commit -m "docs: seed CONTEXT.md domain glossary + decisions/ folder"
 
 The glossary stays terse — one sentence per entry. It's loaded into every agent spawn; bloat costs tokens. `/qualia-discuss` will grow it inline as decisions crystallize during phase planning.
 
-### Step 8b. Write PRODUCT.md (v4.5.0 — REQUIRED)
+### Step 8b. Write PRODUCT.md (REQUIRED)
 
 `PRODUCT.md` is the "who and why" every road agent reads before designing or building. It is **required** — the planner, builder, and verifier all load it as substrate.
 
@@ -216,9 +216,9 @@ git commit -m "docs: PRODUCT.md — register, users, voice, anti-references"
 }
 ```
 
-**Note:** `workflow.research` is ALWAYS `true` for v4. It exists for telemetry but is no longer read as a gate.
+**Note:** `workflow.research` is always `true`. It exists for telemetry but is no longer read as a gate.
 
-### Step 10. Create DESIGN.md (frontend projects — v4.5.0 OKLCH-first)
+### Step 10. Create DESIGN.md (frontend projects — OKLCH-first)
 
 If frontend work is involved, generate `.planning/DESIGN.md` from `templates/DESIGN.md`. The generation MUST commit to four things upfront (these go in §1 of DESIGN.md):
 
@@ -419,7 +419,7 @@ Do NOT use `--quick` for: client projects, anything with compliance stakes, anyt
 1. **Project type is the first question, period.** Step 1 (Demo / Full / Quick) is the literal first interaction with the user — even before "what are you building". Every downstream step branches on the answer. Don't skip it, don't infer it, don't ask anything before it.
 2. **AskUserQuestion for every discrete-choice question.** Project type, brownfield gate, design vibe, client type, approval gate, auto-chain — all use the interactive UI. The ONLY free-text question in the kickoff flow is the Step 3 one-line pitch. No plain-text prompts for anything that has a closed set of answers.
 3. **No ad-hoc clarification questioning.** After Step 3 (one-line pitch), the next tool call is `/qualia-discuss`. No "let me ask a few quick things first", no "that's too broad, can you clarify". Depth is the discuss skill's job — not yours.
-4. **Discovery interview is mandatory (v5.6).** Step 4 always invokes `/qualia-discuss` in PROJECT MODE. No free-form questioning loop, no "I'll just sketch PROJECT.md from the user's first message." The interview is 8 questions for demo, 14 for full project.
+4. **Discovery interview is mandatory.** Step 4 always invokes `/qualia-discuss` in PROJECT MODE. No free-form questioning loop, no "I'll just sketch PROJECT.md from the user's first message." The interview is 8 questions for demo, 14 for full project.
 5. **Research runs automatically.** No permission ask. Only `--quick` skips it. Demo path uses `<scope>quick</scope>` (3-call budget per researcher); full project uses standard 8-call budget.
 6. **Demo design philosophy is non-negotiable.** Real backend always (Supabase, real auth), DESIGN.md mandatory, slop-detect hard-block, 1 milestone, focus on real agent/platform functionality + design quality. No mock data, no lorem ipsum, no broken flows. Speed comes from skipping multi-milestone planning, never from skipping design quality, mocking the backend, or cutting corners on the core flow. A demo that uses mock data is not a Qualia demo.
 7. **Demos are 1 milestone, full projects are 2-5.** Demo journeys have no "Handoff" — the demo IS the artifact. Full projects always end in Handoff (fixed 4 phases). The journey-tree adapts to both shapes.

package/skills/qualia-optimize/SKILL.md

@@ -41,7 +41,7 @@ Modes: `full`, `perf`, `ui`, `backend`, `alignment`, `deepen`, `fix`.
 
 ### Step 2: Load Planning Context (MANDATORY)
 
-Read all (skip silently if missing):
+Read all (use the shown NO_* marker when missing):
 
 ```bash
 cat .planning/PROJECT.md 2>/dev/null || echo "NO_PROJECT"

package/skills/qualia-plan/SKILL.md

@@ -212,7 +212,7 @@ With `--gaps`, planner enters gap-closure mode:
 ## Rules
 
 1. **Plan-checker mandatory by default.** Skip only with `--skip-check`.
-2. **Max 3 revision cycles.** 3 fails → escalate; scope probably wrong.
+2. **Max 2 revision cycles.** 2 fails → escalate; scope probably wrong.
 3. **Honor locked decisions.** phase-{N}-context.md locked decisions non-negotiable.
 4. **One plan file per phase.** No phase-1-plan-v2.md. Edit in place.
 5. **Revision is surgical.** Fix only what checker flagged; no scope creep.

package/skills/qualia-polish/REFERENCE.md

@@ -256,10 +256,12 @@ Per the spec's hard constraint (§5g `prefers-reduced-motion` and §5c mobile-on
 
 This is intentional. Most visual regressions Fawzi has documented in `/insights` (hero videos cropped wrong on mobile, touch targets < 44px on mobile, navigation collapse misbehaving) only show up below 768. Scoring on desktop alone is how we got "looks great in dev" → "looks broken on the user's phone."
 
-## What the loop does NOT do (deferred to v5.2)
+## What the loop does NOT do
 
-- Cross-browser rendering checks (Firefox / WebKit) — Chromium-only, per `qualia-polish` Stage 4 precedent
-- Accessibility audits beyond what the rubric scores — use `/qualia-polish` Stage 3 (Lighthouse + axe) for that
-- Performance regressions — use `/qualia-polish --loop` only after Lighthouse score passes
-- Reference-image-only mode (compare to a target screenshot without a brief) — currently the brief is required; reference is supplemental
-- Multi-page sweeps — one URL per invocation; chain `/qualia-polish --loop` per route for site-wide passes
+- Cross-browser rendering checks (Firefox / WebKit) — Chromium-only, per `qualia-polish` Stage 4 precedent.
+- Accessibility audits beyond what the rubric scores — use `/qualia-polish` Stage 3 (Lighthouse + axe) for that.
+- Performance regressions — use `/qualia-polish --loop` only after Lighthouse score passes.
+- Reference-image-only mode (compare to a target screenshot without a brief) — the brief is required; reference is supplemental.
+- Aesthetic pivots — if the issue is "the whole vibe is wrong", `/qualia-vibe` swaps the aesthetic in minutes instead of grinding the loop against a vibe that doesn't fit.
+
+Implemented as of v5.2: `--routes a,b,c` for multi-route sweeps, `--reduced-motion` for `prefers-reduced-motion: reduce` capture.

package/skills/qualia-polish/SKILL.md

@@ -36,7 +36,7 @@ Other flags: `--register=brand|product` overrides register inference. Loop-speci
 
 When `--loop` is the first flag, the polish run is fully autonomous: screenshot a live URL at three viewports, score 8 design dimensions of `qualia-design/design-rubric.md` against the brief using vision, fix top issues in the codebase, re-screenshot, repeat until every dimension scores ≥ 3 or the kill-switch fires (regression, budget cap, max iterations).
 
-This is the surface formerly known as `/qualia-polish-loop` (consolidated into a flag in v5.8.0). The scripts ship at `skills/qualia-polish/scripts/{loop,playwright-capture,score}.mjs`; vision evaluator is `agents/visual-evaluator.md`; full loop spec lives in this skill's `REFERENCE.md`.
+Scripts ship at `skills/qualia-polish/scripts/{loop,playwright-capture,score}.mjs`; the vision evaluator is `agents/visual-evaluator.md`; the full loop spec lives in this skill's `REFERENCE.md`.
 
 When `--loop` is detected on entry, route to the loop process documented in `REFERENCE.md` and stop executing the standard stages below. The two paths share Stage 0 substrate gates and the rubric, but diverge from Stage 1 onward.
 
@@ -72,15 +72,17 @@ Read PRODUCT.md and DESIGN.md. Identify the **register** — Brand (marketing/la
 2. `register:` field in PRODUCT.md
 3. `--register` flag override
 
-For App / Redesign scope, write the brief BEFORE any code (use `ultrathink`):
+For App / Redesign scope, write the brief BEFORE any code (use `ultrathink`). Per `rules/one-opinion.md` — **propose one direction, do NOT list a menu of aesthetic options to the user.** Infer the one direction from `PRODUCT.md` register + anti-references + scene sentence, then commit to it in writing:
 
 ```
-Aesthetic direction:  {editorial · brutalist · luxury · maximalist · retro-futuristic · organic · terminal-native · ...}
-Color strategy:       {Restrained · Committed · Full palette · Drenched}
+Aesthetic direction:  {ONE concrete direction — e.g. "editorial broadsheet, ivory ground, deep navy ink, italic accents"}
+Color strategy:       {ONE choice — Restrained / Committed / Full palette / Drenched — with one-line justification}
 Scene sentence:       {who uses this, where, ambient light, mood — concrete}
 Differentiation:      {what someone remembers 24 hours later}
 ```
 
+If the user pushes back on the proposed direction, that is a `/qualia-vibe` trigger — switch surfaces, do not start enumerating alternatives in the brief.
+
 For Component / Section / Quick scope, the brief is implicit (loaded from DESIGN.md). Skip the ultrathink step but cite the relevant DESIGN.md tokens you'll touch.
 
 For Critique scope, no commit needed — you're scoring, not editing.
@@ -95,7 +97,7 @@ node bin/slop-detect.mjs {target_paths}
 npx tsc --noEmit 2>&1 | head -20
 
 # Token enforcement (if Stylelint configured)
-npx stylelint "src/**/*.css" 2>&1 | head -20  # optional, skip silently if not configured
+npx stylelint "src/**/*.css" 2>&1 | head -20  # optional, report if not configured
 ```
 
 ANY critical-severity slop hit = mandatory fix before proceeding. Don't stage anything until critical findings are zero.
@@ -148,19 +150,19 @@ npx lhci autorun \
 npx @axe-core/cli http://localhost:3000{route} --exit 2>&1 | tail -30
 ```
 
-If Lighthouse/axe not installed, skip silently and note in the report. Don't fail the polish over missing tooling.
+If Lighthouse/axe are not installed, continue but note the missing tooling in the report. Don't fail the polish over optional local tooling, and don't hide the skipped gate.
 
 If a11y < 90 OR axe critical/serious violations: **fix programmatically** (these are deterministic — no vision needed). Re-run to confirm.
 
 ### Stage 4 — Vision loop (Redesign scope only — max 2 iterations)
 
-Use Anthropic's `webapp-testing` skill (Playwright). Capture screenshots at 3 viewports: 375 / 768 / 1280. Single browser (Chromium) is fine in 2026 — cross-browser CSS rendering differences are vanishingly rare.
+Use `skills/qualia-polish/scripts/playwright-capture.mjs` (Playwright backend, with Chrome-binary fallback). Capture screenshots at 3 viewports: 375 / 768 / 1440 — these match what `agents/visual-evaluator.md` expects, and what the `--loop` mode captures. Single browser (Chromium) is fine in 2026 — cross-browser CSS rendering differences are vanishingly rare.
 
 ```
 viewports: [
   { width: 375,  height: 812,  name: 'mobile' },
   { width: 768,  height: 1024, name: 'tablet' },
-  { width: 1280, height: 800,  name: 'desktop' }
+  { width: 1440, height: 900,  name: 'desktop' }
 ]
 ```
 
@@ -261,7 +263,7 @@ node ~/.claude/bin/qualia-ui.js end "POLISHED" "{next command — depends on con
 | Symptom | Likely cause | Action |
 |---|---|---|
 | `bin/slop-detect.mjs not found` | Framework not installed in project | Run `npx qualia install` or pull script from framework repo |
-| `PRODUCT.md missing` | Pre-v4.5.0 project | Run setup (ask 5 questions, generate). For Component scope, can proceed with nudge. |
+| `PRODUCT.md missing` | Project predates the PRODUCT.md substrate | Run setup (ask 5 questions, generate). For Component scope, can proceed with nudge. |
 | `Lighthouse not installed` | Optional tool | Skip Stage 3 numeric gates, note in report. Don't fail. |
 | `webapp-testing skill not present` | Optional Anthropic skill | Skip Stage 4 vision loop on Redesign scope. Note in report. Recommend installing. |
 | Vision loop oscillates between iterations | Rubric not anchored properly | Verify rubric prompt instructs "default to 3, only 1-2 = fix". Hard cap at 2 iterations. |

package/skills/qualia-polish/scripts/loop.mjs

@@ -29,7 +29,7 @@
  */
 
 import { readFileSync, writeFileSync, existsSync, mkdirSync } from "node:fs";
-import { dirname } from "node:path";
+import path, { dirname } from "node:path";
 import { argv, exit } from "node:process";
 import { spawnSync } from "node:child_process";
 
@@ -202,10 +202,17 @@ function cmdCommitFix() {
   if (!statePath || !file) { console.error("--state and --file required"); exit(2); }
   const state = loadState(statePath);
 
-  // slop-detect gate — block on critical findings
+  // slop-detect gate — block on critical findings. Resolve the script path with
+  // a search order so installs that put slop-detect in non-default locations
+  // still gate. Silent skip is reserved for genuinely missing installs.
   const slopBin = process.env.SLOP_DETECT_BIN || "node";
-  const slopScript = process.env.SLOP_DETECT_SCRIPT || `${process.env.HOME}/.claude/bin/slop-detect.mjs`;
-  if (existsSync(slopScript)) {
+  const slopCandidates = [
+    process.env.SLOP_DETECT_SCRIPT,
+    `${process.env.HOME}/.claude/bin/slop-detect.mjs`,
+    path.join(path.dirname(new URL(import.meta.url).pathname), "..", "..", "..", "bin", "slop-detect.mjs"),
+  ].filter(Boolean);
+  const slopScript = slopCandidates.find((p) => existsSync(p));
+  if (slopScript) {
     const r = spawnSync(slopBin, [slopScript, file], { encoding: "utf8" });
     if (r.status === 1) {
       console.log(JSON.stringify({ ok: false, gate: "slop-detect", file, output: r.stdout }, null, 2));
@@ -213,12 +220,17 @@ function cmdCommitFix() {
     }
   }
 
-  // Stage + commit
+  // Stage + commit. Set a bot identity inline so the commit works on fresh
+  // clones where git user.name / user.email aren't configured yet.
   const safeSlug = String(slug).toLowerCase().replace(/[^a-z0-9-]+/g, "-").slice(0, 48);
   const msg = `qpl-${state.iteration}: ${safeSlug}`;
   const add = spawnSync("git", ["add", file], { encoding: "utf8" });
   if (add.status !== 0) { console.error(add.stderr); exit(2); }
-  const commit = spawnSync("git", ["commit", "-m", msg], { encoding: "utf8" });
+  const commit = spawnSync("git", [
+    "-c", "user.name=Qualia Polish Loop",
+    "-c", "user.email=polish-loop@qualia.solutions",
+    "commit", "-m", msg,
+  ], { encoding: "utf8" });
   if (commit.status !== 0) {
     // empty diff → nothing to commit; not fatal
     if (/nothing to commit/i.test(commit.stdout + commit.stderr)) {

package/skills/qualia-postmortem/SKILL.md

@@ -95,7 +95,7 @@ matches the failure. Use this lookup:
 | Wave 2 task ran before wave 1 committed | `agents/planner.md` (dependency graph) |
 | Build passed locally, broke in CI | `rules/deployment.md` or a missing pre-deploy-gate scan |
 | RLS missing on new table | `rules/security.md` + `agents/builder.md` (security persona handling) |
-| Design regression — fonts off, contrast fail | `qualia-design/frontend.md` + `skills/qualia-design/SKILL.md` |
+| Design regression — fonts off, contrast fail | `qualia-design/frontend.md` + `qualia-design/design-laws.md` + `skills/qualia-polish/SKILL.md` |
 | Migration unsafe (DROP without IF EXISTS, etc.) | `hooks/migration-guard.js` |
 | Verifier missed it | `agents/verifier.md` — most embarrassing case, address with extra care |
 

package/skills/qualia-report/SKILL.md

@@ -126,7 +126,7 @@ fi
 ### Step 6 — Upload to ERP
 
 The full payload-builder + 3-attempt-retry logic lives unchanged from v4 — see the **ERP Upload** section below for the canonical implementation. Behavior summary:
-- ERP disabled in config → skip silently, note local commit
+- ERP disabled in config → skip upload with an info line, note local commit
 - API key missing → warn with self-service fix instructions, skip upload
 - 401/422 → permanent failure, no retry, tell employee to ask Fawzi
 - Transient (timeout/5xx) → 3 attempts with 1s/3s/9s backoff
@@ -149,7 +149,7 @@ node ~/.claude/bin/qualia-ui.js info "Shift report submitted. You can clock out
 | Symptom | Likely cause | Self-service fix |
 |---|---|---|
 | "Could not allocate report ID" | tracking.json missing/corrupt | `cat .planning/tracking.json` to inspect, or restore from `git checkout HEAD -- .planning/tracking.json` |
-| "ERP API key missing" | `~/.claude/.erp-api-key` empty | `qualia-framework set-erp-key <key>` (ask Fawzi for the key) |
+| "ERP API key missing" | `~/.claude/.erp-api-key` empty | `printf '%s' "$QUALIA_ERP_KEY" \| qualia-framework set-erp-key` (ask Fawzi for the key) |
 | "ERP auth failed (401)" | Key revoked or wrong | Ask Fawzi for a fresh key |
 | "ERP upload failed after 3 attempts" | ERP down or network issue | Local commit is safe. Re-run `/qualia-report` later. |
 | "git push failed" | Auth or network or upstream issue | `git push` manually, see the error, fix, re-run |
@@ -181,52 +181,16 @@ IDEMPOTENCY_KEY=$(node -e "
 
 # Guard: API key required for upload (otherwise curl posts an empty bearer)
 if [ "$ERP_ENABLED" = "true" ] && [ -z "$API_KEY" ] && [ "$DRY_RUN" != "true" ]; then
-  node ~/.claude/bin/qualia-ui.js warn "ERP API key missing (~/.claude/.erp-api-key). Run: qualia-framework set-erp-key <key>"
+  node ~/.claude/bin/qualia-ui.js warn "ERP API key missing (~/.claude/.erp-api-key). Run: printf '%s' \"\$QUALIA_ERP_KEY\" | qualia-framework set-erp-key"
   ERP_ENABLED="false"
 fi
 
-# Build payload (env-var-passed user values to dodge shell escaping)
+# Build payload (env-var-passed user values to dodge shell escaping).
+# `report-payload.js` is the canonical, tested Framework -> ERP payload builder.
 PAYLOAD=$(
   SUBMITTED_BY="$SUBMITTED_BY" SUBMITTED_AT="$SUBMITTED_AT" \
   CLIENT_REPORT_ID="$CLIENT_REPORT_ID" REPORT_FILE="$REPORT_FILE" \
-  node -e "
-    const fs=require('fs'),path=require('path'),os=require('os');
-    const {spawnSync}=require('child_process');
-    const git=(a)=>{const r=spawnSync('git',a,{encoding:'utf8',timeout:3000});return r.status===0?r.stdout.trim():'';};
-    const repoSlug=(r)=>(r||'').replace(/^git@github\\.com:/,'github.com/').replace(/^https?:\\/\\//,'').replace(/\\.git$/,'').split('/').filter(Boolean).pop();
-    let config={};try{config=JSON.parse(fs.readFileSync(path.join(os.homedir(),'.claude/.qualia-config.json'),'utf8'));}catch{}
-    const t=JSON.parse(fs.readFileSync('.planning/tracking.json','utf8'));
-    const notes=fs.readFileSync(process.env.REPORT_FILE,'utf8').substring(0,60000);
-    const commits=[];try{const r=spawnSync('git',['log','--oneline','--since=8 hours ago','--format=%h'],{encoding:'utf8',timeout:3000});if(r.stdout)commits.push(...r.stdout.trim().split('\n').filter(Boolean));}catch{}
-    const gitRemote=t.git_remote||git(['config','--get','remote.origin.url']);
-    const projectKey=t.project_id||repoSlug(gitRemote)||require('path').basename(process.cwd());
-    // Session duration: minutes from session_started_at to submitted_at. The ERP's
-    // example payload (docs/erp-contract.md:93) includes this; without it the ERP
-    // can't compute shift-length analytics without parsing notes.
-    let sessionDurationMinutes=0;
-    if(t.session_started_at){
-      const startMs=Date.parse(t.session_started_at);
-      const endMs=Date.parse(process.env.SUBMITTED_AT)||Date.now();
-      if(!Number.isNaN(startMs)&&endMs>startMs){
-        sessionDurationMinutes=Math.round((endMs-startMs)/60000);
-      }
-    }
-    console.log(JSON.stringify({
-      project:t.project||require('path').basename(process.cwd()),
-      project_id:projectKey,team_id:t.team_id||'qualia-solutions',git_remote:gitRemote,
-      client:t.client||'',client_report_id:process.env.CLIENT_REPORT_ID,
-      framework_version:config.version||'',milestone:t.milestone||1,
-      milestone_name:t.milestone_name||'',milestones:Array.isArray(t.milestones)?t.milestones:[],
-      phase:t.phase,phase_name:t.phase_name,total_phases:t.total_phases,status:t.status,
-      tasks_done:t.tasks_done||0,tasks_total:t.tasks_total||0,verification:t.verification||'pending',
-      gap_cycles:(t.gap_cycles||{})[String(t.phase)]||0,build_count:t.build_count||0,
-      deploy_count:t.deploy_count||0,deployed_url:t.deployed_url||'',
-      session_started_at:t.session_started_at||'',last_pushed_at:t.last_pushed_at||'',
-      session_duration_minutes:sessionDurationMinutes,
-      lifetime:t.lifetime||{},commits:commits,notes:notes,
-      submitted_by:process.env.SUBMITTED_BY||'unknown',submitted_at:process.env.SUBMITTED_AT
-    }));
-  "
+  node ~/.claude/bin/report-payload.js
 )
 
 # --dry-run: print and stop

package/skills/qualia-road/SKILL.md

@@ -32,7 +32,7 @@ Final milestone = Handoff:
 Done.
 ```
 
-## Design as a thread (v4.5.0+)
+## Design as a thread
 Every road agent loads `PRODUCT.md + DESIGN.md + design-laws.md` substrate. Builders run `slop-detect` on every frontend commit. Verifiers score 8 design dimensions per phase.
 
 ## /qualia-polish is scope-adaptive
@@ -45,7 +45,19 @@ Every road agent loads `PRODUCT.md + DESIGN.md + design-laws.md` substrate. Buil
 /qualia-polish --quick                       ~1m  gates only
 ```
 
-## /qualia-polish --loop -- autonomous visual QA (v5.1+, consolidated into /qualia-polish in v5.8)
+## Design pivots — /qualia-vibe (v6.1+)
+```
+/qualia-vibe                              fast aesthetic pivot: ONE proposed direction, swap tokens, keep layout (~3 min)
+/qualia-vibe brutalist                    explicit pivot to named direction
+/qualia-vibe --variants 3                 opt-in menu (uses AskUserQuestion; default flow is one-opinion)
+/qualia-vibe --extract https://stripe.com reverse-engineer DESIGN.md from a reference URL
+/qualia-vibe --extract ./inspo.png        same, from a local screenshot
+/qualia-vibe --sync                       show drift between code (CSS vars, Tailwind config) and DESIGN.md
+/qualia-vibe --sync --write               patch DESIGN.md to match code, commit
+```
+`/qualia-vibe` is for the WHOLE-SITE aesthetic. For surgical component-level fixes use `/qualia-polish` (component or section scope). For ground-up structural redesign use `/qualia-polish --redesign`.
+
+## /qualia-polish --loop — autonomous visual QA
 ```
 /qualia-polish --loop http://localhost:3000               screenshot + eval + fix loop
 /qualia-polish --loop {url} --max 4                       cap iterations
@@ -55,14 +67,14 @@ Every road agent loads `PRODUCT.md + DESIGN.md + design-laws.md` substrate. Buil
 ```
 Screenshots at 3 viewports (375/768/1440), scores 8 design dimensions using vision, fixes issues, re-screenshots, loops until all dims >= 3 or kill-switch triggers. Per-iteration git commits for clean revert.
 
-## v5.3+ skills
+## Deterministic-enforcement skills
 ```
 /qualia-hook-gen       convert a CLAUDE.md/rules instruction into a deterministic pre-tool-use hook
 /qualia-optimize --deepen   spawns 3 parallel interface-design variants per candidate (Step 5b)
 ```
 `/qualia-hook-gen` reduces lifetime token cost (each migrated rule frees ~50-200 tokens per request). `/qualia-optimize --deepen` produces dramatically better refactor RFCs because 3 radically-different interfaces are surfaced and the human picks/hybridizes.
 
-## Alignment substrate (v5.0+)
+## Alignment substrate
 Before high-stakes phases, run alignment skills against `.planning/CONTEXT.md` (domain glossary) and `.planning/decisions/` (ADRs):
 
 ```
@@ -105,7 +117,7 @@ No accumulated garbage. No context rot.
 - **Intent verification** — Confirm before modifying 3+ files (OWNER role: just do it)
 
 ## Tracking
-`.planning/tracking.json` is updated on every push. The ERP reads it via git.
+`.planning/tracking.json` is updated locally on every push. It feeds statusline, stop-session-log, and `/qualia-report`; the ERP receives explicit report uploads and does not read this file from git.
 Never edit tracking.json manually — hooks update it from STATE.md.
 
 ## Compaction — ALWAYS preserve

package/skills/qualia-verify/SKILL.md

@@ -19,7 +19,7 @@ Spawn verifier to check phase goal. Does NOT trust build summaries; greps codeba
 `/qualia-verify` — verify current built phase
 `/qualia-verify {N}` — verify specific phase
 `/qualia-verify {N} --auto` — verify + auto-chain: PASS → next phase/milestone; FAIL → gap closure; gap limit → halt
-`/qualia-verify {N} --adversarial` — second verifier in fresh context with adversarial prompt. Union findings. Recommended for high-stakes phases (Handoff, payment/auth/migration). v4.3.0+.
+`/qualia-verify {N} --adversarial` — second verifier in fresh context with adversarial prompt. Union findings. Recommended for high-stakes phases (Handoff, payment/auth/migration).
 
 ## Process
 
@@ -106,7 +106,7 @@ Findings merge into main report. Union PASS/FAIL: either pass found CRITICAL/HIG
 
 ### 2d. INSUFFICIENT EVIDENCE downgrade (mandatory)
 
-The verifier marks criteria it could not check (budget exhaustion, missing context) as `INSUFFICIENT EVIDENCE`. The orchestrator treats those as silent PASS unless explicitly downgraded — that's the #1 false-pass vector. Grep the verification file before declaring PASS:
+The verifier marks criteria it could not check (budget exhaustion, missing context) as `INSUFFICIENT EVIDENCE`. The orchestrator must treat those as FAIL before declaring PASS. Grep the verification file and downgrade immediately:
 
 ```bash
 IE_COUNT=$(grep -c "INSUFFICIENT EVIDENCE" .planning/phase-{N}-verification.md 2>/dev/null || echo 0)
@@ -142,7 +142,7 @@ Per gap:
 node ~/.claude/bin/qualia-ui.js fail "{gap description}"
 ```
 
-**Self-healing (v4.3.0+):** before re-planning gaps, run postmortem so framework learns from miss. Writes `.planning/phase-{N}-postmortem.md`. Does NOT auto-apply deltas unless user runs `/qualia-postmortem --apply`.
+**Self-healing:** before re-planning gaps, run postmortem so the framework learns from the miss. Writes `.planning/phase-{N}-postmortem.md`. Does NOT auto-apply deltas unless user runs `/qualia-postmortem --apply`.
 
 ```
 /qualia-postmortem --phase {N}