cclaw-cli 0.49.0 → 0.51.1

package/dist/content/track-render-context.js

@@ -0,0 +1,44 @@
+function artifactFileName(path) {
+    return path.split("/").pop() ?? path;
+}
+export function trackRenderContext(track) {
+    if (track === "quick") {
+        return {
+            track,
+            usesPlanTerminology: false,
+            traceabilitySourceNoun: "acceptance criterion",
+            traceabilityIdNoun: "acceptance criterion ID",
+            traceabilitySliceNoun: "acceptance slice",
+            upstreamArtifactLabel: "spec artifact",
+            upstreamArtifactPath: ".cclaw/artifacts/04-spec.md"
+        };
+    }
+    return {
+        track,
+        usesPlanTerminology: true,
+        traceabilitySourceNoun: "plan task",
+        traceabilityIdNoun: "plan task ID",
+        traceabilitySliceNoun: "plan slice",
+        upstreamArtifactLabel: "plan artifact",
+        upstreamArtifactPath: ".cclaw/artifacts/05-plan.md"
+    };
+}
+/**
+ * Render track-aware terminology for text that defaults to standard-track plan
+ * wording. Keep this centralized so quick-track rewrites do not drift across
+ * stage content generators.
+ */
+export function renderTrackTerminology(value, context) {
+    if (context.usesPlanTerminology) {
+        return value;
+    }
+    return value
+        .replace(/\btask from the plan\b/giu, `${context.traceabilitySourceNoun} from the spec`)
+        .replace(/\bplan task ID\b/giu, context.traceabilityIdNoun)
+        .replace(/\bplan task\b/giu, context.traceabilitySourceNoun)
+        .replace(/\bplan row\b/giu, "acceptance row")
+        .replace(/\btraceable to plan slice\b/giu, `traceable to ${context.traceabilitySliceNoun}`)
+        .replace(/\bplan slice\b/giu, context.traceabilitySliceNoun)
+        .replace(/\bplan artifact\b/giu, context.upstreamArtifactLabel)
+        .replace(/05-plan\.md/gu, artifactFileName(context.upstreamArtifactPath));
+}

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

@@ -1,2 +1 @@
-export declare function treeCommandContract(): string;
-export declare function treeCommandSkillMarkdown(): string;
+export declare function treeSubcommandMarkdown(): string;

package/dist/content/tree-command.js

@@ -1,6 +1,4 @@
 import { RUNTIME_ROOT } from "../constants.js";
-const TREE_SKILL_FOLDER = "flow-tree";
-const TREE_SKILL_NAME = "flow-tree";
 function flowStatePath() {
     return `${RUNTIME_ROOT}/state/flow-state.json`;
 }
@@ -13,90 +11,9 @@ function artifactsPath() {
 function rewindLogPath() {
     return `${RUNTIME_ROOT}/state/rewind-log.jsonl`;
 }
-function harnessPlaybooksDir() {
-    return `${RUNTIME_ROOT}/references/harnesses`;
-}
-export function treeCommandContract() {
+export function treeSubcommandMarkdown() {
     return `# /cc-view tree
 
-## Purpose
-
-Render a visual flow tree for quick orientation across stages, gates, delegations
-(with fulfillmentMode), ship closeout substate, stale markers, artifact presence,
-and per-harness playbook availability.
-
-## HARD-GATE
-
-- \`/cc-view tree\` is read-only. Do not mutate flow-state or artifacts.
-- Use values from \`${flowStatePath()}\` and \`${delegationLogPath()}\`; never infer missing evidence.
-
-## Algorithm
-
-1. Read \`${flowStatePath()}\`.
-2. Read \`${delegationLogPath()}\` (if missing, treat current-stage delegations as pending).
-3. Detect artifact files in \`${artifactsPath()}\` (\`01-brainstorm.md\` …
-   \`08-ship.md\` plus \`09-retro.md\`).
-4. Read rewind records from \`${rewindLogPath()}\` when present for stale-stage context.
-5. Inspect \`${harnessPlaybooksDir()}\` to confirm per-harness playbooks exist
-   for the installed harness set.
-6. Render the tree using stage order from active track:
-   - stage node marker: passed/current/pending/skipped/stale
-   - gate summary: \`passed/required\`
-   - delegation summary for current stage (each agent carries its
-     \`fulfillmentMode\` label)
-   - artifact marker per stage (exists / stale copy / missing)
-7. When \`currentStage === "ship"\` or \`closeout.shipSubstate !== "idle"\`,
-   append a closeout sub-tree under ship with substate and retro/compound flags.
-8. Append a final \`harnesses\` branch summarising tier + fallback +
-   playbook-present for each installed harness.
-
-## Tree Format
-
-\`\`\`
-cclaw flow tree (track=<track>, run=<runId>)
-├─ [✓] brainstorm  gates 6/6   artifact 01-brainstorm.md
-├─ [✓] scope       gates 5/5   artifact 02-scope.md
-├─ [▶] design      gates 2/7   artifact 03-design.md
-│  ├─ delegations:
-│  │   ├─ planner   ✓ completed  mode=isolated
-│  │   └─ reviewer  ○ pending
-│  └─ stale: none
-├─ [○] spec        gates -     artifact missing
-└─ [○] plan        gates -     artifact missing
-
-closeout (shipSubstate=retro_review):
-  ├─ retro:    drafted 09-retro.md · awaiting accept/edit/skip
-  ├─ compound: —
-  └─ archive:  pending
-
-harnesses:
-  ├─ claude    tier=tier1 fallback=native           playbook ✓
-  ├─ cursor    tier=tier2 fallback=generic-dispatch playbook ✓
-  ├─ opencode  tier=tier2 fallback=role-switch      playbook ✓
-  └─ codex     tier=tier2 fallback=role-switch      playbook ✓
-\`\`\`
-
-- Closeout sub-tree is **omitted** when \`currentStage !== "ship"\` and
-  \`shipSubstate === "idle"\`.
-- Delegations sub-branch is omitted when the stage has no mandatory agents.
-- Playbook marker is \`✗ missing\` when the file under
-  \`${harnessPlaybooksDir()}/<harness>-playbook.md\` is absent.
-
-Use UTF markers by default, ASCII fallback when terminal cannot render UTF.
-
-## Primary skill
-
-**${RUNTIME_ROOT}/skills/${TREE_SKILL_FOLDER}/SKILL.md**
-`;
-}
-export function treeCommandSkillMarkdown() {
-    return `---
-name: ${TREE_SKILL_NAME}
-description: "Render a visual flow tree for stages, gates, delegations (fulfillmentMode), ship closeout substate, artifacts, and per-harness playbooks."
----
-
-# /cc-view tree
-
 ## HARD-GATE
 
 Do not modify state in this command. It is a pure read/render operation.
@@ -108,7 +25,7 @@ Do not modify state in this command. It is a pure read/render operation.
    \`fulfillmentMode\` / \`evidenceRefs\`.
 3. Inspect \`${artifactsPath()}\` for per-stage artifact presence and stale copies,
    and for the retro artifact \`09-retro.md\`.
-4. Inspect \`${harnessPlaybooksDir()}\` for \`<harness>-playbook.md\` files.
+4. Use \`npx cclaw-cli doctor --explain\` for harness capability status when needed.
 5. Render one compact tree:
    - stage marker: passed/current/pending/skipped/stale,
    - gates summary,
@@ -124,8 +41,8 @@ Do not modify state in this command. It is a pure read/render operation.
      then \`next\`; the transient \`archived\` substate surfaces only if the
      archive step failed mid-run.
 7. Append a \`harnesses:\` branch. For each installed harness derive the tier
-   from the harness-gaps report and mark \`playbook ✓/✗ missing\` based on
-   \`${harnessPlaybooksDir()}/<harness>-playbook.md\` existence.
+   and fallback from cclaw capability metadata; use \`npx cclaw-cli doctor --explain\`
+   for remediation details when needed.
 8. If rewind records exist in \`${rewindLogPath()}\`, include latest rewind note in footer.
 
 ## Validation

package/dist/content/utility-skills.d.ts

@@ -1,26 +1,7 @@
 /**
- * Utility skills that complement the 8 flow stages.
- * These are contextual lenses, not flow stages.
- * Each skill: ~120-180 lines, under the 500-line progressive disclosure guideline.
+ * Opt-in language rule packs for stage hooks and the meta-skill router.
+ * These are generated under `.cclaw/rules/lang`, not as default skills.
  */
-export declare function securityReviewSkill(): string;
-export declare function debuggingSkill(): string;
-export declare function performanceSkill(): string;
-export declare function ciCdSkill(): string;
-export declare function docsSkill(): string;
-export declare function executingPlansSkill(): string;
-export declare function contextEngineeringSkill(): string;
-export declare function verificationBeforeCompletionSkill(): string;
-export declare function finishingDevelopmentBranchSkill(): string;
-export declare function sourceDrivenDevelopmentSkill(): string;
-export declare function frontendAccessibilitySkill(): string;
-export declare function landscapeCheckSkill(): string;
-export declare function knowledgeCurationSkill(): string;
-export declare function securityAuditSkill(): string;
-export declare function adversarialReviewSkill(): string;
-export declare function documentReviewSkill(): string;
-export declare function receivingCodeReviewSkill(): string;
-export declare function retrospectiveSkill(): string;
 export declare function languageTypescriptSkill(): string;
 export declare function languagePythonSkill(): string;
 export declare function languageGoSkill(): string;
@@ -47,11 +28,3 @@ export declare const LANGUAGE_RULE_PACK_GENERATORS: Record<string, () => string>
  * clean them up after the move to `.cclaw/rules/lang/`.
  */
 export declare const LEGACY_LANGUAGE_RULE_PACK_FOLDERS: readonly ["language-typescript", "language-python", "language-go"];
-export declare const UTILITY_SKILL_FOLDERS: readonly ["security", "debugging", "performance", "ci-cd", "docs", "executing-plans", "verification-before-completion", "finishing-a-development-branch", "context-engineering", "source-driven-development", "frontend-accessibility", "landscape-check", "adversarial-review", "security-audit", "knowledge-curation", "retrospective", "document-review", "receiving-code-review"];
-export type UtilitySkillFolder = (typeof UTILITY_SKILL_FOLDERS)[number];
-/**
- * One entry per `UTILITY_SKILL_FOLDERS` slot. Typed via the tuple so that
- * adding a folder without a generator (or vice versa) is a TypeScript
- * error — keeps the two sources of truth in lockstep at compile time.
- */
-export declare const UTILITY_SKILL_MAP: Record<UtilitySkillFolder, () => string>;