cclaw-cli 0.14.0 → 0.15.0

package/dist/content/archive-command.js

@@ -11,14 +11,14 @@ function activeArtifactsPath() {
     return `${RUNTIME_ROOT}/artifacts`;
 }
 export function archiveCommandContract() {
-    return `# /cc-archive
+    return `# /cc-ops archive
 
 ## Purpose
 
 Archive the active cclaw run from inside the harness flow (agent-first finish).
 
 This command removes the user-facing CLI gap: users can stay in \`/cc-*\` flow and
-finish with \`/cc-archive\` after ship + retro are complete.
+finish with \`/cc-ops archive\` after ship + retro are complete.
 
 ## HARD-GATE
 
@@ -28,13 +28,13 @@ finish with \`/cc-archive\` after ship + retro are complete.
 
 ## Inputs
 
-\`/cc-archive [--name=<slug>] [--skip-retro --retro-reason=<text>]\`
+\`/cc-ops archive [--name=<slug>] [--skip-retro --retro-reason=<text>]\`
 
 ## Algorithm
 
 1. Read \`${flowStatePath()}\`.
 2. If ship is complete and \`retro.completedAt\` is absent:
-   - block with explicit instruction: run \`/cc-retro\` first.
+   - block with explicit instruction: run \`/cc-ops retro\` first.
 3. Build archive command:
    - base: \`npx cclaw archive\`
    - optional: \`--name=<slug>\`
@@ -66,7 +66,7 @@ name: ${ARCHIVE_SKILL_NAME}
 description: "Archive the active cclaw run from harness flow and reset runtime safely."
 ---
 
-# /cc-archive
+# /cc-ops archive
 
 ## HARD-GATE
 
@@ -78,7 +78,7 @@ runtime command so state snapshots and manifest generation stay atomic.
 1. Read \`${flowStatePath()}\`:
    - confirm whether ship is completed,
    - check \`retro.completedAt\` for post-ship runs.
-2. If ship complete and retro incomplete -> stop and direct user to \`/cc-retro\`.
+2. If ship complete and retro incomplete -> stop and direct user to \`/cc-ops retro\`.
 3. Build shell command:
    - \`npx cclaw archive\`
    - append \`--name=<slug>\` when provided

package/dist/content/contracts.js

@@ -36,7 +36,7 @@ ${schema.hardGate}
 ${hydrationLines}
 4. Stream \`.cclaw/knowledge.jsonl\` and apply relevant JSON-line entries (strict schema: type, trigger, action, confidence, domain, stage, created, project).
 5. Write stage output to ${writeStepPaths}.
-6. Do NOT copy artifacts into \`.cclaw/runs/\`; archival is handled by \`/cc-archive\` (agent-facing wrapper over archive runtime).
+6. Do NOT copy artifacts into \`.cclaw/runs/\`; archival is handled by \`/cc-ops archive\` (agent-facing wrapper over archive runtime).
 
 ## Gates
 ${gateIds}

package/dist/content/diff-command.js

@@ -8,7 +8,7 @@ function snapshotPath() {
     return `${RUNTIME_ROOT}/state/flow-state.snapshot.json`;
 }
 export function diffCommandContract() {
-    return `# /cc-diff
+    return `# /cc-view diff
 
 ## Purpose
 
@@ -54,7 +54,7 @@ name: ${DIFF_SKILL_NAME}
 description: "Compare current flow-state against saved snapshot and render gate/stage deltas."
 ---
 
-# /cc-diff
+# /cc-view diff
 
 ## HARD-GATE
 

package/dist/content/feature-command.js

@@ -14,7 +14,7 @@ function runtimeStatePath() {
     return `${RUNTIME_ROOT}/state`;
 }
 export function featureCommandContract() {
-    return `# /cc-feature
+    return `# /cc-ops feature
 
 ## Purpose
 
@@ -34,19 +34,19 @@ Feature snapshots live under \`${featuresRoot()}/<feature-id>/\`.
 
 ## Subcommands
 
-### \`/cc-feature status\`
+### \`/cc-ops feature status\`
 Show active feature id and snapshot location.
 
-### \`/cc-feature list\`
+### \`/cc-ops feature list\`
 List all feature ids in \`${featuresRoot()}/\` (directory names).
 
-### \`/cc-feature new <feature-id>\`
+### \`/cc-ops feature new <feature-id>\`
 Create \`${featuresRoot()}/<feature-id>/artifacts\` and \`${featuresRoot()}/<feature-id>/state\`.
 
 Optional flag:
 - \`--clone-active\`: clone current active runtime into the new feature snapshot.
 
-### \`/cc-feature switch <feature-id>\`
+### \`/cc-ops feature switch <feature-id>\`
 1. Snapshot current active runtime into \`${featuresRoot()}/<active>/\`.
 2. Restore target snapshot from \`${featuresRoot()}/<feature-id>/\` into active runtime:
    - \`${runtimeArtifactsPath()}\`
@@ -73,7 +73,7 @@ name: ${FEATURE_SKILL_NAME}
 description: "Manage cclaw multi-feature workspaces (status/list/new/switch) while preserving active flow runtime."
 ---
 
-# /cc-feature — Feature Workspace Manager
+# /cc-ops feature — Feature Workspace Manager
 
 ## HARD-GATE
 
@@ -113,7 +113,7 @@ Do not switch feature by editing only \`active-feature.json\`. A valid switch mu
 
 ## Safety checks
 
-- If target feature does not exist: block and suggest \`/cc-feature new <id>\`.
+- If target feature does not exist: block and suggest \`/cc-ops feature new <id>\`.
 - If snapshot copy fails: abort switch, keep current active feature unchanged.
 - Preserve global pointer file \`active-feature.json\` when restoring state.
 `;

package/dist/content/harnesses-doc.js

@@ -67,16 +67,20 @@ All harnesses receive the same utility commands:
 - \`/cc-next\` - stage progression
 - \`/cc-view\` - read-only router for status/tree/diff
 - \`/cc-learn\` - knowledge capture/lookup
-- \`/cc-status\` - read-only visual flow snapshot
-- \`/cc-tree\` - deep flow tree (stages, artifacts, stale markers)
-- \`/cc-diff\` - before/after flow-state diff map
 - \`/cc-ops\` - operations router for feature/tdd-log/retro/archive/rewind
-- \`/cc-feature\` - multi-feature workspace management
-- \`/cc-tdd-log\` - explicit RED/GREEN/REFACTOR evidence log
-- \`/cc-retro\` - mandatory retrospective gate before archive
-- \`/cc-archive\` - archive active run from harness flow
-- \`/cc-rewind\` - rewind flow and invalidate downstream stages
-- \`/cc-rewind-ack\` - clear stale stage markers after redo
+
+Read-only subcommands:
+- \`/cc-view status\` - visual flow snapshot
+- \`/cc-view tree\` - deep flow tree (stages, artifacts, stale markers)
+- \`/cc-view diff\` - before/after flow-state diff map
+
+Operations subcommands:
+- \`/cc-ops feature ...\` - multi-feature workspace management
+- \`/cc-ops tdd-log ...\` - explicit RED/GREEN/REFACTOR evidence log
+- \`/cc-ops retro\` - mandatory retrospective gate before archive
+- \`/cc-ops archive\` - archive active run from harness flow
+- \`/cc-ops rewind ...\` - rewind flow and invalidate downstream stages
+- \`/cc-ops rewind-ack ...\` - clear stale stage markers after redo
 
 Stage order remains canonical:
 \`brainstorm -> scope -> design -> spec -> plan -> tdd -> review -> ship\`

package/dist/content/hooks.js

@@ -496,7 +496,7 @@ To disable suggestions persistently set ${RUNTIME_ROOT}/state/suggestion-memory.
 fi
 if [ -n "$STALE_STAGES" ]; then
   CTX="$CTX
-Stale stages pending acknowledgement: $STALE_STAGES (use /cc-rewind-ack <stage> after redo)."
+Stale stages pending acknowledgement: $STALE_STAGES (use /cc-ops rewind-ack <stage> after redo)."
 fi
 if [ -n "$KNOWLEDGE_DIGEST" ]; then
   CTX="$CTX
@@ -742,7 +742,7 @@ if [ "$CHECKPOINT_WRITTEN" -eq 0 ]; then
   CHECKPOINT_NOTE="Checkpoint update failed. Review ${RUNTIME_ROOT}/state/checkpoint.json manually."
 fi
 
-RUN_SYNC_NOTE="Run metadata sync removed; active artifacts stay in ${RUNTIME_ROOT}/artifacts until /cc-archive (or cclaw archive runtime)."
+RUN_SYNC_NOTE="Run metadata sync removed; active artifacts stay in ${RUNTIME_ROOT}/artifacts until /cc-ops archive (or cclaw archive runtime)."
 
 # --- Escape for JSON ---
 ${ESCAPE_FN}

package/dist/content/learnings.d.ts

@@ -5,4 +5,3 @@
 export declare const KNOWLEDGE_JSONL_FIELDS: readonly ["type", "trigger", "action", "confidence", "domain", "stage", "created", "project"];
 export declare function learnSkillMarkdown(): string;
 export declare function learnCommandContract(): string;
-export declare function selfImprovementBlock(stageName: string): string;

package/dist/content/learnings.js

@@ -134,12 +134,3 @@ Do not edit source code from this command. Only operate on \`${KNOWLEDGE_PATH}\`
 | \`curate\` | — | Hand off to the **knowledge-curation** skill: read-only audit + soft-archive plan when the file exceeds the curation threshold. |
 `;
 }
-export function selfImprovementBlock(stageName) {
-    return `## Operational Self-Improvement
-
-Before closeout, capture 1-3 reusable insights in \`${KNOWLEDGE_PATH}\` whenever
-the stage produced non-obvious decisions, patterns, or lessons.
-Prefer \`type=rule|pattern|lesson\` (\`compound\` stays retro-only) and set
-\`stage: "${stageName}"\` unless the insight is explicitly cross-stage.
-`;
-}

package/dist/content/next-command.js

@@ -33,13 +33,13 @@ This is the only progression command the user needs to drive the entire flow. St
 
 - **Do not** invent gate completion: use only \`${flowPath}\` plus observable evidence in repo artifacts.
 - **Do not** skip stages: advance only from \`currentStage\` to its configured successor.
-- If the flow reaches terminal ship completion, route closeout in order: **/cc-retro -> /cc-archive**.
+- If the flow reaches terminal ship completion, route closeout in order: **/cc-ops retro -> /cc-ops archive**.
 
 ## Algorithm (mandatory)
 
 1. Read **\`${flowPath}\`**. If missing → **BLOCKED** (state missing).
 2. Parse JSON. Capture \`currentStage\` and \`stageGateCatalog[currentStage]\`.
-3. If \`staleStages[currentStage]\` exists, do not advance automatically. Re-run the stage artifact work, then clear the marker with \`/cc-rewind-ack <currentStage>\`.
+3. If \`staleStages[currentStage]\` exists, do not advance automatically. Re-run the stage artifact work, then clear the marker with \`/cc-ops rewind-ack <currentStage>\`.
 4. Let \`G\` = \`requiredGates\` for **\`currentStage\`** from the stage schema.
 5. Let \`catalog\` = \`stageGateCatalog[currentStage]\` from flow state.
 6. **Satisfied** for gate id \`g\`: \`g\` in \`catalog.passed\` and \`g\` not in \`catalog.blocked\`.
@@ -55,8 +55,8 @@ This is the only progression command the user needs to drive the entire flow. St
 ### Path B: Current stage IS complete (all gates passed, all delegations satisfied)
 
 → If current stage's \`next\` is **\`done\`**:
-  - if \`currentStage === "ship"\` and \`retro.completedAt\` is missing -> route to \`/cc-retro\`,
-  - if \`currentStage === "ship"\` and \`retro.completedAt\` is present -> route to \`/cc-archive\`,
+  - if \`currentStage === "ship"\` and \`retro.completedAt\` is missing -> route to \`/cc-ops retro\`,
+  - if \`currentStage === "ship"\` and \`retro.completedAt\` is present -> route to \`/cc-ops archive\`,
   - otherwise report **"Flow complete. All stages finished."** and stop.
 → Otherwise: load **\`${RUNTIME_ROOT}/skills/<skillFolder>/SKILL.md\`** and **\`${RUNTIME_ROOT}/commands/<nextStage>.md\`** for the successor stage. Execute that stage's protocol.
 
@@ -124,7 +124,7 @@ Do **not** mark gates satisfied from memory alone. Cite **artifact evidence** (p
 
 1. Open **\`${flowPath}\`**.
 2. Record \`currentStage\` and \`stageGateCatalog[currentStage]\`.
-3. If \`staleStages[currentStage]\` exists, re-run the stage and clear marker via \`/cc-rewind-ack <currentStage>\` before advancing.
+3. If \`staleStages[currentStage]\` exists, re-run the stage and clear marker via \`/cc-ops rewind-ack <currentStage>\` before advancing.
 4. If the file is missing or invalid JSON → **BLOCKED** (report and stop).
 
 ### Step 2: Evaluate gates
@@ -149,8 +149,8 @@ Execute the stage protocol. The stage skill handles interaction, STOP points, ga
 
 If \`next\` is \`done\`:
 
-- If \`currentStage\` is \`ship\` and \`retro.completedAt\` is missing -> route to \`/cc-retro\`.
-- If \`currentStage\` is \`ship\` and \`retro.completedAt\` exists -> route to \`/cc-archive\`.
+- If \`currentStage\` is \`ship\` and \`retro.completedAt\` is missing -> route to \`/cc-ops retro\`.
+- If \`currentStage\` is \`ship\` and \`retro.completedAt\` exists -> route to \`/cc-ops archive\`.
 - Otherwise report **"Flow complete. All stages finished."** and stop.
 
 Otherwise load the next stage's skill and command contract, begin execution.

package/dist/content/ops-command.js

@@ -9,12 +9,12 @@ export function opsCommandContract() {
 Unified operational command surface for non-stage flow actions.
 
 Subcommands:
-- \`feature\` -> \`/cc-feature\`
-- \`tdd-log\` -> \`/cc-tdd-log\`
-- \`retro\` -> \`/cc-retro\`
-- \`archive\` -> \`/cc-archive\`
-- \`rewind\` -> \`/cc-rewind\`
-- \`rewind-ack\` -> \`/cc-rewind-ack\`
+- \`feature\` -> \`/cc-ops feature\`
+- \`tdd-log\` -> \`/cc-ops tdd-log\`
+- \`retro\` -> \`/cc-ops retro\`
+- \`archive\` -> \`/cc-ops archive\`
+- \`rewind\` -> \`/cc-ops rewind\`
+- \`rewind-ack\` -> \`/cc-ops rewind-ack\`
 
 ## HARD-GATE
 

package/dist/content/retro-command.js

@@ -11,7 +11,7 @@ function knowledgePath() {
     return `${RUNTIME_ROOT}/knowledge.jsonl`;
 }
 export function retroCommandContract() {
-    return `# /cc-retro
+    return `# /cc-ops retro
 
 ## Purpose
 
@@ -36,7 +36,7 @@ Mandatory retrospective gate before archive once ship is complete.
    - \`required: true\`
    - \`completedAt: <ISO>\`
    - \`compoundEntries: <count>\`
-5. Report completion summary and remind user that \`/cc-archive\` is now unblocked.
+5. Report completion summary and remind user that \`/cc-ops archive\` is now unblocked.
 
 ## Primary skill
 
@@ -49,7 +49,7 @@ name: ${RETRO_SKILL_NAME}
 description: "Run mandatory retrospective and record compound knowledge before archive."
 ---
 
-# /cc-retro
+# /cc-ops retro
 
 ## HARD-GATE
 

package/dist/content/rewind-command.js

@@ -11,7 +11,7 @@ function rewindLogPath() {
     return `${RUNTIME_ROOT}/state/rewind-log.jsonl`;
 }
 export function rewindCommandContract() {
-    return `# /cc-rewind
+    return `# /cc-ops rewind
 
 ## Purpose
 
@@ -25,7 +25,7 @@ Rewind active flow to an earlier stage and atomically invalidate downstream work
 
 ## Inputs
 
-\`/cc-rewind <target-stage> [reason]\`
+\`/cc-ops rewind <target-stage> [reason]\`
 
 ## Algorithm
 
@@ -55,7 +55,7 @@ Rewind active flow to an earlier stage and atomically invalidate downstream work
 `;
 }
 export function rewindAcknowledgeCommandContract() {
-    return `# /cc-rewind-ack
+    return `# /cc-ops rewind-ack
 
 ## Purpose
 
@@ -63,7 +63,7 @@ Acknowledge and clear stale-stage markers after downstream work is intentionally
 
 ## Input
 
-\`/cc-rewind-ack <stage>\`
+\`/cc-ops rewind-ack <stage>\`
 
 ## HARD-GATE
 
@@ -89,7 +89,7 @@ name: ${REWIND_SKILL_NAME}
 description: "Rewind active flow stage safely and acknowledge stale invalidations."
 ---
 
-# /cc-rewind + /cc-rewind-ack
+# /cc-ops rewind + /cc-ops rewind-ack
 
 ## HARD-GATE
 

package/dist/content/skills.js

@@ -1,6 +1,5 @@
 import { RUNTIME_ROOT } from "../constants.js";
 import { STAGE_EXAMPLES_REFERENCE_DIR, stageDomainExamples, stageExamples, stageGoodBadExamples } from "./examples.js";
-import { selfImprovementBlock } from "./learnings.js";
 import { STAGE_COMMON_GUIDANCE_REL_PATH } from "./stage-common-guidance.js";
 import { stageAutoSubagentDispatch, stageSchema } from "./stage-schema.js";
 const VERIFICATION_STAGES = ["tdd", "review", "ship"];
@@ -378,7 +377,6 @@ ${mergedAntiPatterns(schema)}
 ## Verification
 ${schema.exitCriteria.map((item) => `- [ ] ${item}`).join("\n")}
 
-${selfImprovementBlock(schema.stage)}
 ${completionParametersBlock(schema)}
 ## Shared Stage Guidance
 See:

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

@@ -24,9 +24,9 @@ Use this same closeout menu for every stage:
 
 - **A) Advance** — run \`/cc-next\` and continue.
 - **B) Revise this stage** — stay on current stage and apply feedback.
-- **C) Pause / park** — stop now and resume later.
-- **D) Rewind** — move to a prior stage explicitly chosen by the user.
-- **E) Abandon** — cancel this flow; artifacts remain on disk.
+- **C) Pause / park** — run \`/cc-view status\`, then stop and resume later.
+- **D) Rewind** — run \`/cc-ops rewind <target-stage>\`.
+- **E) Abandon** — archive with \`/cc-ops archive --skip-retro --retro-reason="<reason>"\` when user explicitly wants to end the run.
 
 Recommendation defaults:
 
@@ -58,9 +58,17 @@ Rollback / fallback: <if decision proves wrong>
 
 ## Self-improvement reminder
 
-If a reusable lesson appears during the stage, append one strict-schema JSONL
-entry (manually via \`/cc-learn add\` or directly in stage closeout protocol).
-Do not keep operational lessons only in chat.
+Before closeout, capture 1-3 reusable insights in \`.cclaw/knowledge.jsonl\`
+whenever the stage produced non-obvious decisions, patterns, or lessons.
+Prefer \`type=rule|pattern|lesson\` (\`compound\` stays retro-focused).
+
+Track policy:
+- \`standard\` / \`medium\`: required for \`design\`, \`tdd\`, and \`review\`;
+  recommended for other stages.
+- \`quick\`: recommended only.
+
+"No learning captured" is acceptable only with an explicit reason
+(for example, purely mechanical edits with no new decisions).
 
 ## Progressive disclosure baseline
 

package/dist/content/stage-schema.d.ts

@@ -6,14 +6,6 @@ export interface StageGate {
     /** Used when tier=conditional. Predicate syntax mirrors conditional delegation rules. */
     condition?: string;
 }
-export interface StageRationalization {
-    claim: string;
-    reality: string;
-}
-export interface CognitivePattern {
-    name: string;
-    description: string;
-}
 export interface ReviewSection {
     title: string;
     evaluationPoints: string[];
@@ -54,10 +46,6 @@ export interface StageAutoSubagentDispatch {
     /** Optional skill folder the dispatched agent should load as additional context. */
     skill?: string;
 }
-export interface NamedAntiPattern {
-    title: string;
-    description: string;
-}
 export interface StageSchema {
     stage: FlowStage;
     skillFolder: string;
@@ -87,19 +75,15 @@ export interface StageSchema {
     blockers: string[];
     exitCriteria: string[];
     antiPatterns: string[];
-    rationalizations: StageRationalization[];
     redFlags: string[];
     policyNeedles: string[];
     artifactFile: string;
     next: FlowStage | "done";
     checklist: string[];
-    cognitivePatterns: CognitivePattern[];
     reviewSections: ReviewSection[];
     completionStatus: string[];
     crossStageTrace: CrossStageTrace;
     artifactValidation: ArtifactValidation[];
-    namedAntiPattern?: NamedAntiPattern;
-    decisionRecordFormat?: string;
     /** When true, stage skill includes wave auto-execute guidance (tdd). */
     waveExecutionAllowed?: boolean;
     /** Sections that remain required even when the trivial-change escape hatch is active (design only). */