cclaw-cli 0.51.29 → 0.51.30

package/dist/cli.d.ts

@@ -1,6 +1,7 @@
 #!/usr/bin/env node
 import type { FlowTrack, HarnessId } from "./types.js";
 import type { ArchiveDisposition } from "./runs.js";
+export { parseHarnessSelectionAnswer } from "./harness-selection.js";
 type CommandName = "init" | "sync" | "doctor" | "upgrade" | "uninstall" | "archive" | "internal";
 interface ParsedArgs {
     command?: CommandName;
@@ -27,17 +28,5 @@ export declare function usage(): string;
 declare function parseHarnesses(raw: string): HarnessId[];
 declare function parseTrack(raw: string): FlowTrack;
 declare function parseArchiveDisposition(raw: string): ArchiveDisposition;
-export type HarnessSelectionAnswer = {
-    kind: "accept";
-} | {
-    kind: "all";
-} | {
-    kind: "toggle";
-    indexes: number[];
-} | {
-    kind: "invalid";
-    message: string;
-};
-export declare function parseHarnessSelectionAnswer(raw: string): HarnessSelectionAnswer;
 declare function parseArgs(argv: string[]): ParsedArgs;
 export { parseArgs, parseArchiveDisposition, parseHarnesses, parseTrack };

package/dist/cli.js

@@ -13,6 +13,8 @@ import { CCLAW_VERSION, RUNTIME_ROOT } from "./constants.js";
 import { createDefaultConfig, readConfig } from "./config.js";
 import { detectHarnesses } from "./init-detect.js";
 import { HARNESS_ADAPTERS } from "./harness-adapters.js";
+import { promptHarnessSelectionChecklist } from "./harness-selection.js";
+export { parseHarnessSelectionAnswer } from "./harness-selection.js";
 import { classifyCodexHooksFlag, codexConfigPath, patchCodexHooksFlag, readCodexConfig, writeCodexConfig } from "./codex-feature-flag.js";
 import { runInternalCommand } from "./internal/advance-stage.js";
 const INSTALLER_COMMANDS = [
@@ -67,8 +69,8 @@ Examples:
   npx cclaw-cli archive --disposition=cancelled --reason="deprioritized"
   npx cclaw-cli upgrade
 
-Happy-path work happens inside your harness via /cc, /cc-next,
-/cc-ideate, /cc-view, /cc-finish, and /cc-cancel. Doctor is an operator/support surface:
+Happy-path work happens inside your harness via /cc, /cc-ideate,
+and /cc-cancel. Doctor is an operator/support surface:
 it verifies install/runtime wiring, but a real harness smoke test is
 still needed to prove provider auth and model execution.
 
@@ -171,93 +173,8 @@ function buildInitSurfacePreview(harnesses) {
     }
     return lines;
 }
-function harnessLabel(harness) {
-    const adapter = HARNESS_ADAPTERS[harness];
-    const tier = adapter ? `${adapter.reality.declaredSupport}, ${adapter.capabilities.hookSurface} hooks` : "supported";
-    return `${harness} (${tier})`;
-}
-function selectedHarnessPreview(harnesses) {
-    return harnesses.length > 0 ? harnesses.join(", ") : "none";
-}
-export function parseHarnessSelectionAnswer(raw) {
-    const answer = raw.trim().toLowerCase();
-    if (answer.length === 0)
-        return { kind: "accept" };
-    if (answer === "all")
-        return { kind: "all" };
-    if (answer === "none") {
-        return { kind: "invalid", message: "Zero harnesses is not supported. Select at least one harness." };
-    }
-    const parts = answer.split(",").map((part) => part.trim()).filter(Boolean);
-    const indexes = parts.map((part) => Number.parseInt(part, 10));
-    if (indexes.some((value) => !Number.isInteger(value) || value < 1 || value > HARNESS_IDS.length)) {
-        return { kind: "invalid", message: `Invalid selection. Use numbers 1-${HARNESS_IDS.length}, comma-separated.` };
-    }
-    return { kind: "toggle", indexes };
-}
-async function promptHarnessSelection(defaults, ctx, label = "Harness selection") {
-    const rl = createInterface({
-        input: process.stdin,
-        output: ctx.stdout
-    });
-    const defaultSet = new Set(defaults.harnesses);
-    const selected = new Set(defaults.harnesses.length > 0 ? defaults.harnesses : HARNESS_IDS);
-    const detected = new Set(defaults.detectedHarnesses ?? []);
-    const current = new Set(defaults.currentHarnesses ?? []);
-    const printMenu = () => {
-        ctx.stdout.write(`\n${label}\n`);
-        ctx.stdout.write(`Detected: ${selectedHarnessPreview(defaults.detectedHarnesses ?? [])}\n`);
-        ctx.stdout.write(`Current: ${selectedHarnessPreview(defaults.currentHarnesses ?? [])}\n`);
-        ctx.stdout.write(`Supported harnesses and target paths:\n`);
-        HARNESS_IDS.forEach((harness, index) => {
-            const adapter = HARNESS_ADAPTERS[harness];
-            const markers = [
-                detected.has(harness) ? "detected" : "",
-                current.has(harness) ? "current" : "",
-                defaultSet.has(harness) ? "default" : ""
-            ].filter(Boolean).join(", ");
-            const checked = selected.has(harness) ? "x" : " ";
-            ctx.stdout.write(`  ${index + 1}. [${checked}] ${harnessLabel(harness)} -> ${adapter.commandDir}${markers ? ` (${markers})` : ""}\n`);
-        });
-        ctx.stdout.write("Enter numbers to toggle (for example 1,3), 'all', or press Enter to accept.\n");
-    };
-    try {
-        while (true) {
-            printMenu();
-            const answer = await rl.question(`Selected [${[...selected].join(",") || "select at least one"}]: `);
-            const parsedAnswer = parseHarnessSelectionAnswer(answer);
-            if (parsedAnswer.kind === "accept") {
-                if (selected.size === 0) {
-                    ctx.stdout.write("Select at least one harness.\n");
-                    continue;
-                }
-                return HARNESS_IDS.filter((harness) => selected.has(harness));
-            }
-            if (parsedAnswer.kind === "all") {
-                HARNESS_IDS.forEach((harness) => selected.add(harness));
-                continue;
-            }
-            if (parsedAnswer.kind === "invalid") {
-                ctx.stdout.write(`${parsedAnswer.message}\n`);
-                continue;
-            }
-            for (const index of parsedAnswer.indexes) {
-                const harness = HARNESS_IDS[index - 1];
-                if (!harness)
-                    continue;
-                if (selected.has(harness))
-                    selected.delete(harness);
-                else
-                    selected.add(harness);
-            }
-        }
-    }
-    finally {
-        rl.close();
-    }
-}
 async function promptInitConfig(defaults, ctx) {
-    const harnesses = await promptHarnessSelection(defaults, ctx, "Initial cclaw harnesses");
+    const harnesses = await promptHarnessSelectionChecklist(defaults, ctx, "Initial cclaw harnesses");
     return { harnesses };
 }
 /**
@@ -392,7 +309,7 @@ async function resolveSyncInputs(parsed, ctx) {
     const detectedHarnesses = await detectHarnesses(ctx.cwd);
     const defaults = detectedHarnesses.length > 0 ? detectedHarnesses : currentHarnesses.length > 0 ? currentHarnesses : HARNESS_IDS.slice();
     return {
-        harnesses: await promptHarnessSelection({
+        harnesses: await promptHarnessSelectionChecklist({
             harnesses: defaults,
             detectedHarnesses,
             currentHarnesses

package/dist/content/closeout-guidance.js

@@ -13,7 +13,7 @@ export function closeoutSubstateInline() {
     return `\`${CLOSEOUT_SUBSTATE_KEY}\``;
 }
 export function closeoutNextCommandGuidance() {
-    return `After ship completes, the closeout chain ${closeoutChainInline()} runs automatically, driven by ${closeoutSubstateInline()}. Continue through \`/cc-next\`; do not branch into \`ce:compound\`, a separate operations router, or a one-off closeout command. Ralph Loop may be mentioned only as tdd carry-forward context when it explains the next \`/cc-next\` move; it is not part of compound/archive routing.`;
+    return `After ship completes, the closeout chain ${closeoutChainInline()} runs automatically, driven by ${closeoutSubstateInline()}. Continue through \`/cc\`; do not branch into \`ce:compound\`, a separate operations router, or a one-off closeout command. Ralph Loop may be mentioned only as tdd carry-forward context when it explains the next \`/cc\` move; it is not part of compound/archive routing.`;
 }
 export function closeoutSubstateProtocolBullets() {
     return `When \`currentStage === "ship"\`, route by **${closeoutSubstateInline()}**:
@@ -35,8 +35,8 @@ export function closeoutSubstateProtocolBullets() {
   - \`"archived"\` (transient) -> report "run archived" and stop.`;
 }
 export function closeoutFlowMapSentence() {
-    return `The first stage names are the critical path. \`retro\`, \`compound\`, and \`archive\` are post-ship closeout substates under ${closeoutSubstateInline()}, not separate stage schemas or commands. Continue them with \`/cc-next\`; do not route compound closeout through \`ce:compound\`.`;
+    return `The first stage names are the critical path. \`retro\`, \`compound\`, and \`archive\` are post-ship closeout substates under ${closeoutSubstateInline()}, not separate stage schemas or commands. Continue them with \`/cc\`; do not route compound closeout through \`ce:compound\`.`;
 }
 export function closeoutProtocolBehaviorSentence() {
-    return `Keep decision, completion, and preamble discipline inline: ask only decision-changing questions, verify gates before advancing, and keep context compact. After \`ship\`, keep using \`/cc-next\` through ${closeoutChainInline()}; do not route normal closeout through \`ce:compound\` or a separate operations command. In compound closeout, assess overlap before appending knowledge: refresh recurring bug-track learnings as actionable rules/tests, keep knowledge-track learnings as durable process/project guidance, and mark outdated entries with lightweight \`supersedes\` / \`superseded_by\` fields instead of building a new doc system.`;
+    return `Keep decision, completion, and preamble discipline inline: ask only decision-changing questions, verify gates before advancing, and keep context compact. After \`ship\`, keep using \`/cc\` through ${closeoutChainInline()}; do not route normal closeout through \`ce:compound\` or a separate operations command. In compound closeout, assess overlap before appending knowledge: refresh recurring bug-track learnings as actionable rules/tests, keep knowledge-track learnings as durable process/project guidance, and mark outdated entries with lightweight \`supersedes\` / \`superseded_by\` fields instead of building a new doc system.`;
 }

package/dist/content/core-agents.js

@@ -498,11 +498,11 @@ export function agentRoutingTable() {
     return `| Stage Entry | Primary Agent(s) | Supporting guidance |
 |---|---|---|
 | Brainstorm (start with \`/cc <idea>\`) | ${brainstormPrimary} | Run in-thread research playbooks: \`research/repo-scan.md\`, \`research/learnings-lookup.md\` |
-| Scope / Design / Plan (via \`/cc-next\`) | ${scopeDesignPlanPrimary} | Use \`research/git-history.md\` (scope) and \`research/framework-docs-lookup.md\` + \`research/best-practices-lookup.md\` (design) as needed |
-| Spec (via \`/cc-next\`) | ${specPrimary} | planner (if ambiguity or conflicts remain) |
-| TDD (via \`/cc-next\`) | ${tddPrimary} | doc-updater on public behavior/config changes |
-| Review (via \`/cc-next\`) | ${reviewPrimary} | conditional second reviewer for high blast-radius diffs |
-| Ship (via \`/cc-next\`) | ${shipPrimary} | security-reviewer when release risk is elevated |
+| Scope / Design / Plan (via \`/cc\`) | ${scopeDesignPlanPrimary} | Use \`research/git-history.md\` (scope) and \`research/framework-docs-lookup.md\` + \`research/best-practices-lookup.md\` (design) as needed |
+| Spec (via \`/cc\`) | ${specPrimary} | planner (if ambiguity or conflicts remain) |
+| TDD (via \`/cc\`) | ${tddPrimary} | doc-updater on public behavior/config changes |
+| Review (via \`/cc\`) | ${reviewPrimary} | conditional second reviewer for high blast-radius diffs |
+| Ship (via \`/cc\`) | ${shipPrimary} | security-reviewer when release risk is elevated |
 `;
 }
 /**

package/dist/content/meta-skill.js

@@ -13,7 +13,7 @@ function generatedHelperSkillList() {
 export function usingCclawSkillMarkdown() {
     return `---
 name: using-cclaw
-description: "Routing brain for cclaw. Decide whether to start/resume a stage, answer directly, or use visible commands like /cc, /cc-next, /cc-ideate, and /cc-view."
+description: "Routing brain for cclaw. Decide whether to start/resume a stage, answer directly, or use visible commands like /cc, /cc-ideate, and /cc-cancel."
 ---
 
 # Using Cclaw
@@ -65,11 +65,10 @@ Task arrives
   ├─ Pure question / non-software ask? -> answer directly (no stage)
   ├─ New software work? -> /cc <idea>
   ├─ Repo-improvement discovery? -> /cc-ideate
-  ├─ Resume existing flow? -> /cc or /cc-next
+  ├─ Resume existing flow? -> /cc
   ├─ Knowledge operation? -> load the learnings skill
-  ├─ Read-only workspace view? -> /cc-view [status|tree|diff]
-  ├─ Normal post-ship closeout? -> /cc-next drives ${closeoutChainInline()}
-  └─ Explicit early archival/reset? -> npx cclaw-cli archive [--name=<slug>]
+  ├─ Normal post-ship closeout? -> /cc drives ${closeoutChainInline()}
+  └─ Explicit early cancellation/abandonment? -> /cc-cancel
 \`\`\`
 
 ## Task classification
@@ -87,7 +86,7 @@ Task arrives
 Before stage work:
 
 1. Read \`.cclaw/state/flow-state.json\`.
-2. If active stage exists, continue with \`/cc\` or \`/cc-next\`.
+2. If active stage exists, continue with \`/cc\`.
 3. Do not jump directly to stage-specific commands.
 
 ## Platform reliability notes
@@ -98,13 +97,12 @@ Before stage work:
 
 ## Stage quick map
 
-Use \`/cc <idea>\` for new work, \`/cc-next\` for progression and closeout, \`/cc-view\` for read-only state, and \`/cc-ideate\` for backlog discovery.
+Use \`/cc <idea>\` for new work, \`/cc\` for progression and closeout, \`/cc-ideate\` for backlog discovery, and \`/cc-cancel\` for cancellation/abandonment.
 
 ## Main vs Operator Surfaces
 
-- **Main workflow:** \`/cc\`, \`/cc-next\`, \`/cc-ideate\`, \`/cc-view status\`, and \`node .cclaw/hooks/stage-complete.mjs <stage>\` inside the installed harness runtime.
+- **Main workflow:** \`/cc\`, \`/cc-ideate\`, and \`/cc-cancel\` inside the installed harness runtime.
 - **Installer/support surface:** \`npx cclaw-cli init\`, \`npx cclaw-cli sync\`, \`npx cclaw-cli upgrade\`, \`npx cclaw-cli doctor\`, and explicit support/archive actions. Do not ask users to install or run a \`cclaw\` binary during normal stage flow.
-- **Read-only support:** \`/cc-view tree\` and \`/cc-view diff\`.
 - Use operator/support surfaces only for install/runtime diagnosis, explicit archival, or deeper inspection. Do not make them part of the happy path.
 
 ## Whole flow map

package/dist/content/next-command.d.ts

@@ -10,8 +10,8 @@
 export declare const RALPH_LOOP_CONTRACT_MARKER = "ralph-loop-contract:v1";
 export declare function ralphLoopContractSnippet(): string;
 /**
- * Command contract for /cc-next — the primary progression command.
- * Reads flow-state, starts the current stage if unfinished, or advances if all gates pass.
+ * Internal compatibility contract for /cc-next.
+ * /cc is the promoted public progression command; this remains as an internal/legacy alias.
  */
 export declare function nextCommandContract(): string;
 /**

package/dist/content/next-command.js

@@ -44,8 +44,8 @@ Ralph Loop fields never gate-check on their own.
 <!-- ${RALPH_LOOP_CONTRACT_MARKER} -->`;
 }
 /**
- * Command contract for /cc-next — the primary progression command.
- * Reads flow-state, starts the current stage if unfinished, or advances if all gates pass.
+ * Internal compatibility contract for /cc-next.
+ * /cc is the promoted public progression command; this remains as an internal/legacy alias.
  */
 export function nextCommandContract() {
     const flowPath = flowStatePath();
@@ -56,14 +56,14 @@ export function nextCommandContract() {
 
 ## Purpose
 
-**The primary progression command.** Read flow state, determine what to do:
+**Internal compatibility progression command.** \`/cc\` is the promoted public start/resume/continue command. This contract remains for legacy shims and internal references; read flow state, determine what to do:
 
 - **Current stage not started / in progress** → load its skill and execute it.
 - **Current stage complete (all gates passed)** → advance \`currentStage\` and load the next skill.
-- **Ship complete** → continue the resumable ${closeoutChainInline()} closeout via \`/cc-next\`.
+- **Ship complete** → continue the resumable ${closeoutChainInline()} closeout. Public habit: use \`/cc\`.
 - **Flow complete** → report done after closeout has archived the run.
 
-This is the only progression command the user needs to drive the entire flow. Stage command contracts are internal implementation details loaded by \`/cc-next\`.
+The public habit is \`/cc\`; this command is a compatibility/internal route for the same progression behavior. Stage command contracts are internal implementation details.
 
 ## HARD-GATE
 
@@ -116,13 +116,13 @@ ${ralphLoopContractSnippet()}
 
 ## Resume Semantics
 
-\`/cc-next\` in a **new session** = resume from where you left off:
+\`/cc\` in a **new session** resumes from where you left off; \`/cc-next\` is a compatibility alias:
 - Flow-state records \`currentStage\` and which gates have passed.
 - The stage skill reads upstream artifacts and picks up context.
 - ${closeoutSubstateInline()} carries the post-ship substate, so a crashed
   session during retro/compound/archive resumes at the exact step without
   regenerating the retro draft.
-- No special resume command needed — \`/cc-next\` IS the resume command.
+- No special resume command needed — \`/cc\` is the public resume/progression command.
 
 ## Headless mode
 
@@ -171,14 +171,14 @@ export function nextCommandSkillMarkdown() {
         .join("\n");
     return `---
 name: ${NEXT_SKILL_NAME}
-description: "The primary progression command. Reads flow state, starts/resumes the current stage or advances to the next one."
+description: "Internal compatibility progression command. Prefer /cc for start, resume, continue, and closeout."
 ---
 
-# /cc-next — Flow Progression
+# /cc-next — Flow Progression Compatibility
 
 ## Overview
 
-\`/cc-next\` is **the only command you need** to drive the entire cclaw flow.
+\`/cc\` is the public command to drive the cclaw flow. \`/cc-next\` remains as an internal/compatibility alias for progression.
 
 ## Operator Output Contract
 
@@ -192,7 +192,7 @@ Gates: <passed>/<required> passed, <blocked> blocked
 Delegations: <done>/<mandatory> done
 Blocked by: <none | gate/delegation/reconciliation/stale/TDD/review/closeout ids>
 Blocker category: <sync-recovery | user-decision | stage-work | delegation-proof | review-rework | closeout>
-Next: <exact next action, usually /cc-next or one named remediation>
+Next: <exact next action, usually /cc or one named remediation>
 Evidence needed: <artifact/test/review/delegation evidence required to unblock>
 \`\`\`
 
@@ -207,7 +207,7 @@ would unblock it. Do not dump full artifacts in progression output.
 3. If **not** → loads the stage skill and starts/resumes execution
 4. If **yes** → advances to the next stage and loads its skill
 
-**Resume:** \`/cc-next\` in a new session picks up from where \`flow-state.json\` says you are.
+**Resume:** \`/cc\` in a new session picks up from where \`flow-state.json\` says you are.
 
 ## HARD-GATE
 
@@ -267,7 +267,7 @@ by inspecting ${closeoutSubstateInline()}:
 | \`ready_to_archive\`    | Run \`npx cclaw-cli archive\`; reset flow-state on success |
 | \`archived\`            | Report "run archived"; stop                         |
 
-Each step owns its own state transition. \`/cc-next\` keeps retro and compound
+Each step owns its own state transition. \`/cc\` keeps retro and compound
 in-session, then uses the archive runtime only at \`ready_to_archive\`.
 
 Otherwise report **"Flow complete. All stages finished."** and stop.
@@ -276,7 +276,7 @@ Otherwise (non-terminal \`next\`): load the next stage skill and begin execution
 
 ## Stage order
 
-This table is the track-aware critical path. It must match \`flow-state.json.track\`; do not follow the natural schema edge when the active track skips a stage. Quick skips ceremony, not safety: spec approval, RED/GREEN/REFACTOR evidence, review, and ship gates still apply. After \`ship\`, \`/cc-next\` continues closeout via ${closeoutSubstateInline()}: ${closeoutChainInline()}.
+This table is the track-aware critical path. It must match \`flow-state.json.track\`; do not follow the natural schema edge when the active track skips a stage. Quick skips ceremony, not safety: spec approval, RED/GREEN/REFACTOR evidence, review, and ship gates still apply. After \`ship\`, \`/cc\` continues closeout via ${closeoutSubstateInline()}: ${closeoutChainInline()}.
 
 | Stage | Standard next | Medium next | Quick next | Skill path |
 |---|---|---|---|---|
@@ -293,6 +293,6 @@ ${naturalStageRows}
 - Advancing when \`blocked\` is non-empty for the current stage.
 - Treating \`passed\` as trusted when artifact evidence contradicts it.
 - Skipping **review** or **ship** because "the code looks fine".
-- Loading a stage skill directly instead of using \`/cc-next\` for progression.
+- Loading a stage skill directly instead of using \`/cc\` for progression.
 `;
 }

package/dist/content/node-hooks.js

@@ -938,7 +938,7 @@ async function handleSessionStart(runtime) {
   );
   const knowledge = await buildKnowledgeDigest(runtime.root, state.currentStage, knowledgeRaw);
 
-  // Refresh Ralph Loop status each session-start so /cc-next and the model
+  // Refresh Ralph Loop status each session-start so /cc and the model
   // both read a consistent "iter=N, acClosed=[...]" snapshot. Runs only when
   // we are in tdd — other stages skip the write to keep the file stable.
   let ralphLoopLine = "";
@@ -1137,7 +1137,7 @@ async function handleStopHandoff(runtime) {
   const shipSubstate = typeof closeoutObj.shipSubstate === "string" ? closeoutObj.shipSubstate : "idle";
   const closeoutContext =
     state.currentStage === "ship" || shipSubstate !== "idle"
-      ? " closeout.shipSubstate=" + shipSubstate + "; closeout chain=retro -> compound -> archive; continue closeout with /cc-next."
+      ? " closeout.shipSubstate=" + shipSubstate + "; closeout chain=retro -> compound -> archive; continue closeout with /cc."
       : "";
 
   const message =

package/dist/content/session-hooks.js

@@ -36,7 +36,7 @@ When a new session begins in any harness:
 \`\`\`
 Cclaw flow state: [current stage] ([N] of 8 stages completed)
 Knowledge highlights: [rule/pattern 1], [rule/pattern 2], [rule/pattern 3]
-Next action: /cc-next to continue, /cc to start new work, or describe what you'd like to do.
+Next action: /cc to continue or start work, /cc-cancel to cancel, or describe what you'd like to do.
 \`\`\`
 
 ## Session Stop Protocol

package/dist/content/stage-command.js

@@ -10,7 +10,7 @@ Load and follow the authoritative stage skill:
 
 - \`${skillPath}\`
 
-Normal stage resume and advancement uses \`/cc-next\`. Use \`/cc-next\` to read
+Normal stage resume and advancement uses \`/cc\`. Use \`/cc\` to read
 \`.cclaw/state/flow-state.json\`, select the active stage, and advance only after
 that stage's gates pass. Do not duplicate the stage protocol here.
 `;

package/dist/content/stage-common-guidance.js

@@ -11,7 +11,7 @@ ${conversationLanguagePolicyMarkdown()}
 - Stage-specific skills expose **Completion Parameters** plus the gates that
   matter for that stage.
 - Generic execution stays inline: verify required gates, update the artifact,
-  harvest learnings, then use \`/cc-next\` for progression.
+  harvest learnings, then use \`/cc\` for progression.
 - Do not create separate protocol files.
 
 ## Context readiness
@@ -30,11 +30,11 @@ ${conversationLanguagePolicyMarkdown()}
 
 Use this same closeout menu for every stage:
 
-- **A) Advance** — run \`/cc-next\` and continue the critical path; after \`ship\`, the same command drives \`retro -> compound -> archive\`.
+- **A) Advance** — run \`/cc\` and continue the critical path; after \`ship\`, the same command drives \`retro -> compound -> archive\`.
 - **B) Revise this stage** — stay on current stage and apply feedback.
-- **C) Pause / park** — run \`/cc-view status\`, then stop and resume later.
+- **C) Pause / park** — stop after summarizing current stage, blockers, and next \`/cc\` action.
 - **D) Rewind** — run \`npx cclaw-cli internal rewind <target-stage> "<reason>"\` as the managed support/runtime repair action; after redoing the target stage, run \`npx cclaw-cli internal rewind --ack <target-stage>\` to clear the stale marker.
-- **E) Abandon** — only when the user explicitly wants to end a non-ship active run early, archive with \`npx cclaw-cli archive --skip-retro --retro-reason="<reason>"\`. Once in post-ship closeout, continue \`/cc-next\` through retro/compound/archive instead.
+- **E) Abandon** — only when the user explicitly wants to end a non-ship active run early, archive with \`npx cclaw-cli archive --skip-retro --retro-reason="<reason>"\`. Once in post-ship closeout, continue \`/cc\` through retro/compound/archive instead.
 
 Recommendation defaults:
 

package/dist/content/stages/plan.js

@@ -50,7 +50,7 @@ export const PLAN = {
             "Run anti-placeholder + anti-scope-reduction scans — block `TODO/TBD/...` and phrasing like `v1`, `for now`, `later` for locked boundaries.",
             "Define validation points — mark where progress must be checked before continuing, with concrete command and expected evidence.",
             "Define execution posture — record whether execution should be sequential, dependency-batched, parallel-safe, or blocked; include risk triggers and RED/GREEN/REFACTOR checkpoint/commit expectations when the repo workflow supports them. This fulfills the `plan_execution_posture_recorded` gate.",
-            "WAIT_FOR_CONFIRM — write plan artifact and explicitly pause. **STOP.** Do NOT proceed until user confirms. Then close the stage with `node .cclaw/hooks/stage-complete.mjs plan` and tell user to run `/cc-next`."
+            "WAIT_FOR_CONFIRM — write plan artifact and explicitly pause. **STOP.** Do NOT proceed until user confirms. Then close the stage with `node .cclaw/hooks/stage-complete.mjs plan` and tell user to run `/cc`."
         ],
         interactionProtocol: [
             "Plan in read-only mode relative to implementation.",
@@ -61,7 +61,7 @@ export const PLAN = {
             "Preserve locked scope boundaries: no silent scope reduction language in task rows.",
             "Enforce WAIT_FOR_CONFIRM: present the plan summary with options (A) Approve / (B) Revise / (C) Reject.",
             "**STOP.** Do NOT proceed until user explicitly approves.",
-            "**STOP BEFORE ADVANCE.** Mandatory delegation `planner` must be marked completed or explicitly waived in `.cclaw/state/delegation-log.json`. Then close the stage via `node .cclaw/hooks/stage-complete.mjs plan` and tell the user to run `/cc-next`."
+            "**STOP BEFORE ADVANCE.** Mandatory delegation `planner` must be marked completed or explicitly waived in `.cclaw/state/delegation-log.json`. Then close the stage via `node .cclaw/hooks/stage-complete.mjs plan` and tell the user to run `/cc`."
         ],
         process: [
             "Build dependency graph and ordered slices.",

package/dist/content/stages/review.js

@@ -47,7 +47,7 @@ export const REVIEW = {
             "Classify findings — Critical (blocks ship), Important (should fix), Suggestion (optional improvement).",
             "Victory Detector — before verdict, confirm Layer 1, Layer 2, security sweep, structured findings, trace evidence, and unresolved-critical status are complete; otherwise iterate findings or route back to TDD.",
             "Produce verdict — APPROVED, APPROVED_WITH_CONCERNS, or BLOCKED.",
-            "If verdict is BLOCKED, emit remediation route token `ROUTE_BACK_TO_TDD`, include the managed command `cclaw internal rewind tdd \"review_blocked_by_critical <finding-ids>\"`, list the critical finding IDs and required TDD evidence to repair, and satisfy the special transition guard `review_verdict_blocked` instead of `review_criticals_resolved`. After TDD rework, clear the stale marker with `cclaw internal rewind --ack tdd` before `/cc-next`."
+            "If verdict is BLOCKED, emit remediation route token `ROUTE_BACK_TO_TDD`, include the managed command `cclaw internal rewind tdd \"review_blocked_by_critical <finding-ids>\"`, list the critical finding IDs and required TDD evidence to repair, and satisfy the special transition guard `review_verdict_blocked` instead of `review_criticals_resolved`. After TDD rework, clear the stale marker with `cclaw internal rewind --ack tdd` before `/cc`."
         ],
         interactionProtocol: [
             "Run Layer 1 (spec compliance) completely before starting Layer 2.",

package/dist/content/start-command.d.ts

@@ -1,7 +1,7 @@
 /**
  * Command contract for /cc — the unified entry point.
- * No args → reads existing flow state and behaves like /cc-next only when a
- * tracked flow already exists; missing state/fresh placeholder state blocks with
+ * No args → reads existing flow state and progresses it when a tracked flow
+ * already exists; missing state/fresh placeholder state blocks with
  * init/start guidance. With prompt → classifies the idea, selects a track, and
  * starts the first stage of that track (brainstorm for medium/standard, spec for quick).
  */

package/dist/content/start-command.js

@@ -7,8 +7,8 @@ function flowStatePath() {
 }
 /**
  * Command contract for /cc — the unified entry point.
- * No args → reads existing flow state and behaves like /cc-next only when a
- * tracked flow already exists; missing state/fresh placeholder state blocks with
+ * No args → reads existing flow state and progresses it when a tracked flow
+ * already exists; missing state/fresh placeholder state blocks with
  * init/start guidance. With prompt → classifies the idea, selects a track, and
  * starts the first stage of that track (brainstorm for medium/standard, spec for quick).
  */
@@ -20,10 +20,10 @@ export function startCommandContract() {
 
 **The unified entry point for the cclaw flow.**
 
-- \`/cc\` (no arguments) → reads existing flow state and resumes/progresses it through \`/cc-next\`. If flow state is missing or still a fresh init placeholder, stop and guide the user to run \`/cc <prompt>\` or \`cclaw init\`; do not silently create a brainstorm run.
+- \`/cc\` (no arguments) → reads existing flow state and resumes/progresses the active flow. If flow state is missing or still a fresh init placeholder, stop and guide the user to run \`/cc <prompt>\` or \`cclaw init\`; do not silently create a brainstorm run.
 - \`/cc <prompt>\` (with an idea/description) → saves the prompt as idea context and starts the first stage of the resolved track.
 
-This is the **recommended way to start** working with cclaw. Use \`/cc-next\` for subsequent stage progression.
+This is the **recommended way to start, resume, and continue** working with cclaw.
 
 ## HARD-GATE
 
@@ -81,7 +81,7 @@ ${conversationLanguagePolicyMarkdown()}
    - **standard** (full 8 stages — default fallback) — anything that introduces a new capability with architecture uncertainty, touches many modules, or has unclear scope.
      Triggers: \`new feature\`, \`refactor\`, \`migration\`, \`platform\`, \`architecture\`, \`schema\`, \`integrate\`, \`workflow\`, \`onboarding\`, or any prompt that does not match quick/medium confidently.
    - When triggers conflict, prefer **standard** over **medium**, and **medium** over **quick**.
-   - Report **track selection confidence** as high/medium/low with the matched trigger or fallback reason, plus one sentence explaining what the selected track skips and what safety gates remain. Be explicit that this recommendation is advisory until the user accepts and the managed helper writes state; after that, \`/cc-next\` follows the configured track.
+   - Report **track selection confidence** as high/medium/low with the matched trigger or fallback reason, plus one sentence explaining what the selected track skips and what safety gates remain. Be explicit that this recommendation is advisory until the user accepts and the managed helper writes state; after that, \`/cc\` follows the configured track.
 8. Present one compact **Start framing** summary: class, recommended track, track selection confidence, stack, origin docs, seed recalls, and the recommended next action. Ask a single confirmation question only when there is a destructive reset, a real contradiction, or ambiguous software/non-software classification.
 9. Present the recommendation as a single decision with explicit options:
    > \`Recommended track: <quick|medium|standard>\` because \`<one-line reason citing matched triggers>\`.
@@ -112,7 +112,7 @@ If during any stage the agent discovers evidence that contradicts the initial Ph
 1. Read \`${flowPath}\`.
 2. If flow state is missing → guide the user to run \`cclaw init\` and stop.
 3. If flow state is only a fresh init placeholder (\`completedStages: []\`, all \`passed\` arrays empty, and no \`00-idea.md\`) → stop and ask for \`/cc <prompt>\` to start a tracked run. Do not create a brainstorm state implicitly.
-4. Otherwise behave exactly like \`/cc-next\`: check current stage gates, resume if incomplete, advance if complete.
+4. Otherwise check current stage gates, resume if incomplete, and advance if complete.
 
 ## Headless mode
 
@@ -151,7 +151,7 @@ description: "Unified entry point for the cclaw flow. No args = resume/next. Wit
 
 \`/cc\` is the **starting command** for cclaw. It intelligently routes:
 
-- **No arguments** → acts as \`/cc-next\` only for an existing tracked flow; missing/fresh placeholder state blocks with start guidance
+- **No arguments** → resumes or progresses an existing tracked flow; missing/fresh placeholder state blocks with start guidance
 - **With a prompt** → classifies the task, picks a track (quick/medium/standard), and starts the **first stage of that track** (not always brainstorm — e.g. the \`quick\` track starts at \`spec\`)
 
 ## HARD-GATE
@@ -185,7 +185,7 @@ ${conversationLanguagePolicyMarkdown()}
    | \`standard\` | \`new feature\`, \`refactor\`, \`migration\`, \`platform\`, \`architecture\`, \`schema\`, \`integrate\`, \`workflow\`, \`onboarding\` (or no confident quick/medium match) | New or uncertain multi-module work |
 
    - On conflict, prefer \`standard\` over \`medium\`, and \`medium\` over \`quick\`.
-   - Always state the recommendation as a one-line reason citing matched triggers and a high/medium/low track selection confidence. Clarify that the heuristic is advisory until the managed helper writes state; after that, \`/cc-next\` follows the selected track. Include override guidance: switch to standard when architecture, schema, migration, security, or unclear scope appears; switch to medium when product framing is needed but architecture is known.
+   - Always state the recommendation as a one-line reason citing matched triggers and a high/medium/low track selection confidence. Clarify that the heuristic is advisory until the managed helper writes state; after that, \`/cc\` follows the selected track. Include override guidance: switch to standard when architecture, schema, migration, security, or unclear scope appears; switch to medium when product framing is needed but architecture is known.
 8. Run the managed start helper: \`node .cclaw/hooks/start-flow.mjs --track=<quick|medium|standard> --class=<class> --prompt=<prompt> --stack=<stack> --reason=<matched heuristic>\`. The helper writes \`${flowPath}\`, computes \`skippedStages\`, resets the gate catalog, and writes \`${RUNTIME_ROOT}/artifacts/00-idea.md\`. If it fails, STOP and report the exact command/output; do not manually edit flow state.
 9. Load and execute the **first stage skill of the chosen track** (\`brainstorming\` for medium/standard, \`specification-authoring\` for quick) plus its matching command file.
 
@@ -195,7 +195,7 @@ If mid-stage evidence contradicts the initial Class/Track decision (the "trivial
 
 ### Path B: \`/cc\` (no arguments)
 
-Delegate to \`/cc-next\` behavior only when a tracked flow exists:
+Progress the tracked flow only when one exists:
 
 1. Read \`${flowPath}\`.
 2. If missing, guide the user to run \`cclaw init\` and stop.
@@ -205,15 +205,17 @@ Delegate to \`/cc-next\` behavior only when a tracked flow exists:
 6. If complete → advance to next stage and execute.
 7. If flow is done → report completion.
 
-## When to use \`/cc\` vs \`/cc-next\`
+## Public flow habit
+
+Use \`/cc\` for the happy path:
 
 | Scenario | Command |
 |---|---|
 | Starting work for the first time | \`/cc\` or \`/cc <idea>\` |
 | Resuming in a new session | \`/cc\` |
-| Progressing after completing a stage | \`/cc-next\` |
+| Progressing after completing a stage | \`/cc\` |
 | Starting with a specific idea | \`/cc <idea>\` |
 
-Both commands read the same \`flow-state.json\`. The difference is that \`/cc <prompt>\` resolves class + track and starts that track's first stage, while \`/cc\` and \`/cc-next\` follow the current state.
+\`/cc <prompt>\` resolves class + track and starts that track's first stage; \`/cc\` without a prompt follows the current \`flow-state.json\`.
 `;
 }

package/dist/content/status-command.js

@@ -78,17 +78,17 @@ a read-only command.
     - harness row
     - stale stage row
 11. Suggest the next action:
-    - If current stage has unmet gates -> \`/cc-next\` to resume.
+    - If current stage has unmet gates -> \`/cc\` to resume.
     - If a mandatory delegation is missing evidence -> dispatch the worker/reviewer or waive with rationale; do not advance silently.
     - If a TDD blocker taxonomy code is present (\`NO_SOURCE_CONTEXT\`, \`NO_TEST_SURFACE\`, \`NO_IMPLEMENTABLE_SLICE\`, \`RED_NOT_EXPRESSIBLE\`, \`NO_VCS_MODE\`) -> name the blocker and the rewind/config route.
     - If review is blocked by critical findings -> show \`cclaw internal rewind tdd "review_blocked_by_critical <finding-ids>"\` plus the later \`cclaw internal rewind --ack tdd\`.
-    - If closeout substate is non-idle -> \`/cc-next\` to continue the chain.
-    - If current stage is complete -> \`/cc-next\` to advance (or report "Flow complete" if terminal).
+    - If closeout substate is non-idle -> \`/cc\` to continue the chain.
+    - If current stage is complete -> \`/cc\` to advance (or report "Flow complete" if terminal).
 
 ## Output Guidelines
 
 - Keep output compact (≤ 40 lines) — status, not narrative.
-- Start with the same operator rows as \`/cc-next\` when possible:
+- Start with the same operator rows as \`/cc\` when possible:
   \`Current\`, \`Stage\`, \`Progress\`, \`Gates\`, \`Delegations\`, \`Risks\`, \`Blocked by\`, \`Next\`, \`Evidence needed\`. Use labels like \`gate: tdd_green_full_suite\`, \`delegation proof: reviewer evidenceRefs\`, and \`closeout: compound_review\` instead of raw JSON tone.
 - When blocked, include a plain-English action block:
   \`Current: <stage or closeout substate>\`; \`Blocked by: <gate/delegation/blocker code>\`; \`Next: <exact command or managed remediation>\`; \`Evidence needed: <artifact/test/review/delegation evidence>\`.
@@ -103,7 +103,7 @@ a read-only command.
 - Collapsing \`◎ missing-evidence\` into \`✓ completed\` — role-switch gaps must stay
   visible so the stage cannot advance silently.
 - Omitting the closeout row when \`shipSubstate !== "idle"\`; it is the only signal
-  that tells the user why \`/cc-next\` is about to run retro/compound/archive.
+  that tells the user why \`/cc\` is about to run retro/compound/archive.
 - Mutating state to "clean up" during a status check.
 `;
 }

package/dist/content/subagents.js

@@ -445,7 +445,7 @@ Implementation that touches shared source trees must remain **sequential** unles
   - **3–4:** appendix / “worth tracking” section (not merge-blocking alone)
   - **1–2:** suppress from primary narrative unless paired with stronger evidence
 
-### Review Army Artifact Contract (required in review stage via /cc-next)
+### Review Army Artifact Contract (required in review stage via /cc)
 
 Write a structured reconciliation artifact at \`.cclaw/artifacts/07-review-army.json\` using this schema:
 

package/dist/content/templates.d.ts

@@ -1,4 +1,4 @@
 export declare const ARTIFACT_TEMPLATES: Record<string, string>;
 export declare const RULEBOOK_MARKDOWN = "# Cclaw Rulebook\n\n## MUST_ALWAYS\n- Follow flow order: brainstorm -> scope -> design -> spec -> plan -> tdd -> review -> ship\n- Require explicit user confirmation after plan before TDD\n- Keep evidence artifacts in `.cclaw/artifacts/`\n- Enforce RED before GREEN in TDD\n- Run two-layer review (spec_compliance and code_quality) before ship\n- Validate all inputs before processing \u2014 never trust external data without sanitization\n- Prefer immutable data patterns and pure functions where the language supports them\n- Follow existing repo conventions, patterns, and directory structure \u2014 match the codebase\n- Verify claims with fresh evidence: \"tests pass\" requires running tests in this message\n- Use conventional commits: `type(scope): description` (feat, fix, refactor, test, docs, chore)\n\n## MUST_NEVER\n- Skip RED phase and jump directly to GREEN in TDD\n- Ship with critical review findings\n- Start implementation during /brainstorm\n- Modify generated cclaw files manually when CLI can regenerate them\n- Commit `.cclaw/` or generated shim files\n- Expose secrets, tokens, API keys, or absolute system paths in agent output\n- Duplicate existing functionality without explicit justification \u2014 search before building\n- Bypass security checks, linting hooks, or type checking to \"move faster\"\n- Claim success (\"Done,\" \"All good,\" \"Tests pass\") without running verification in this message\n- Make changes outside the blast radius of the current task without user consent\n\n## DELEGATION\nWhen a task requires specialist knowledge (security audit, performance profiling, database review),\ndelegate to a specialized agent or skill if the harness supports it. The primary agent should:\n1. Identify the specialist domain\n2. Provide focused context (relevant files, the specific concern)\n3. Evaluate the specialist output before acting on it \u2014 do not blindly apply recommendations\n";
-export declare const CURSOR_WORKFLOW_RULE_MDC = "---\ndescription: cclaw workflow guardrails for Cursor agent sessions\nglobs:\n  - \"**/*\"\nalwaysApply: true\n---\n\n<!-- cclaw-managed-cursor-workflow-rule -->\n\n# Cclaw Workflow Guardrails\n\n## Activation Rule\n\nBefore responding to coding work:\n1. Read `.cclaw/state/flow-state.json`.\n2. Start with `/cc` or continue with `/cc-next`.\n3. If no software-stage flow applies, respond normally.\n\n## Stage Order\n\n`brainstorm -> scope -> design -> spec -> plan -> tdd -> review -> ship`\n\nTrack-specific skips are allowed only when `flow-state.track` + `skippedStages` explicitly say so.\n\n## Task Classification\n\n| Class | Route |\n|---|---|\n| non-trivial software work | `/cc <idea>` |\n| trivial software fix | `/cc <idea>` (quick track) |\n| bugfix with repro | `/cc <idea>` and enforce RED-first in tdd |\n| pure question / non-software | direct answer (no stage flow) |\n\n## Command Surface\n\n- `/cc` = entry and resume.\n- `/cc-next` = only progression path.\n- Knowledge capture and recall use the `learnings` skill when requested.\n\n## Verification Discipline\n\n- No completion claim without fresh command evidence in this turn.\n- Do not mark gates passed from memory.\n- Keep evidence in `.cclaw/artifacts/`; archive via `npx cclaw-cli archive`.\n\n## Delegation And Approvals\n\n- Machine-only checks in design/plan/tdd/review/ship should auto-dispatch when tooling supports it.\n- Ask for user input only at explicit approval gates (scope mode, plan approval, challenge resolution, ship finalization).\n- If harness capabilities are partial, record waiver reasons in delegation logs.\n\n## Routing Source Of Truth\n\n- Primary router: `.cclaw/skills/using-cclaw/SKILL.md`.\n- Stage behavior: current stage skill plus `.cclaw/state/flow-state.json`.\n- Preamble budget: keep role/status announcements brief and avoid repeating\n  them unless the stage or role changes.\n";
+export declare const CURSOR_WORKFLOW_RULE_MDC = "---\ndescription: cclaw workflow guardrails for Cursor agent sessions\nglobs:\n  - \"**/*\"\nalwaysApply: true\n---\n\n<!-- cclaw-managed-cursor-workflow-rule -->\n\n# Cclaw Workflow Guardrails\n\n## Activation Rule\n\nBefore responding to coding work:\n1. Read `.cclaw/state/flow-state.json`.\n2. Start with `/cc` or continue with `/cc`.\n3. If no software-stage flow applies, respond normally.\n\n## Stage Order\n\n`brainstorm -> scope -> design -> spec -> plan -> tdd -> review -> ship`\n\nTrack-specific skips are allowed only when `flow-state.track` + `skippedStages` explicitly say so.\n\n## Task Classification\n\n| Class | Route |\n|---|---|\n| non-trivial software work | `/cc <idea>` |\n| trivial software fix | `/cc <idea>` (quick track) |\n| bugfix with repro | `/cc <idea>` and enforce RED-first in tdd |\n| pure question / non-software | direct answer (no stage flow) |\n\n## Command Surface\n\n- `/cc` = entry and resume.\n- `/cc` = only progression path.\n- Knowledge capture and recall use the `learnings` skill when requested.\n\n## Verification Discipline\n\n- No completion claim without fresh command evidence in this turn.\n- Do not mark gates passed from memory.\n- Keep evidence in `.cclaw/artifacts/`; archive via `npx cclaw-cli archive`.\n\n## Delegation And Approvals\n\n- Machine-only checks in design/plan/tdd/review/ship should auto-dispatch when tooling supports it.\n- Ask for user input only at explicit approval gates (scope mode, plan approval, challenge resolution, ship finalization).\n- If harness capabilities are partial, record waiver reasons in delegation logs.\n\n## Routing Source Of Truth\n\n- Primary router: `.cclaw/skills/using-cclaw/SKILL.md`.\n- Stage behavior: current stage skill plus `.cclaw/state/flow-state.json`.\n- Preamble budget: keep role/status announcements brief and avoid repeating\n  them unless the stage or role changes.\n";
 export declare function buildRulesJson(): Record<string, unknown>;