cclaw-cli 0.48.35 → 0.51.0

package/dist/content/flow-map.d.ts

@@ -1,23 +0,0 @@
-/**
- * Relative path used by skills/commands to cite the consolidated flow map.
- * Stable contract — changing this value is a breaking change for doctor
- * policies and meta-skill links.
- */
-export declare const FLOW_MAP_REL_PATH = ".cclaw/references/flow-map.md";
-/**
- * Canonical one-page overview of cclaw's user-facing surface.
- *
- * Purpose: give the model (and any curious human) a single file that
- * answers "what does cclaw expose, where does my current stage fit, and
- * which files drive progress?" without forcing a walk of the 8 stage
- * skills plus the 4 router skills plus the meta-skill.
- *
- * Design rules:
- * - Keep it under ~150 lines; it is a map, not a manual.
- * - Only cite files that already exist under `.cclaw/`.
- * - Do not duplicate protocol text (decision/completion/ethos live in
- *   `.cclaw/references/protocols/`). Link, don't inline.
- * - Do not introduce new gates or hard rules here — flow-map is
- *   descriptive, not prescriptive.
- */
-export declare function flowMapMarkdown(): string;

package/dist/content/flow-map.js

@@ -1,134 +0,0 @@
-import { RUNTIME_ROOT } from "../constants.js";
-/**
- * Relative path used by skills/commands to cite the consolidated flow map.
- * Stable contract — changing this value is a breaking change for doctor
- * policies and meta-skill links.
- */
-export const FLOW_MAP_REL_PATH = `${RUNTIME_ROOT}/references/flow-map.md`;
-/**
- * Canonical one-page overview of cclaw's user-facing surface.
- *
- * Purpose: give the model (and any curious human) a single file that
- * answers "what does cclaw expose, where does my current stage fit, and
- * which files drive progress?" without forcing a walk of the 8 stage
- * skills plus the 4 router skills plus the meta-skill.
- *
- * Design rules:
- * - Keep it under ~150 lines; it is a map, not a manual.
- * - Only cite files that already exist under `.cclaw/`.
- * - Do not duplicate protocol text (decision/completion/ethos live in
- *   `.cclaw/references/protocols/`). Link, don't inline.
- * - Do not introduce new gates or hard rules here — flow-map is
- *   descriptive, not prescriptive.
- */
-export function flowMapMarkdown() {
-    return `# cclaw Flow Map
-
-One-page surface reference. Use this when you need the shape of cclaw
-without reading every skill — the stage quick-map, the user-facing
-slash commands, the Ralph Loop signal, and the key state files.
-
-For enforcement details, load the matching stage skill or command
-contract. For protocols (decision/completion/ethos) see
-\`${RUNTIME_ROOT}/references/protocols/\`.
-
-## Stages (8)
-
-| # | Stage | Goal | Primary artifact |
-|---|---|---|---|
-| 1 | brainstorm | Explore options and constraints | \`.cclaw/artifacts/00-idea.md\` (+ \`01-brainstorm.md\`) |
-| 2 | scope | Freeze scope (in/out, assumptions) | \`.cclaw/artifacts/02-scope.md\` |
-| 3 | design | Pick the shape of the change | \`.cclaw/artifacts/03-design.md\` |
-| 4 | spec | Turn design into testable acceptance criteria | \`.cclaw/artifacts/04-spec.md\` |
-| 5 | plan | Decompose spec into executable slices | \`.cclaw/artifacts/05-plan.md\` |
-| 6 | tdd | Drive each slice through RED → GREEN → REFACTOR (Ralph Loop) | \`.cclaw/artifacts/06-tdd.md\` + \`.cclaw/state/tdd-cycle-log.jsonl\` |
-| 7 | review | Cross-check correctness, spec coverage, and ethos | \`.cclaw/artifacts/07-review.md\` |
-| 8 | ship | Close out: retro, compound, archive | \`.cclaw/artifacts/08-ship.md\` (+ \`09-retro.md\`) |
-
-Track shortcuts (set in \`.cclaw/state/flow-state.json\`):
-
-- \`quick\` — spec → tdd → review → ship
-- \`medium\` — brainstorm → spec → plan → tdd → review → ship
-- \`standard\` — all 8 stages (default)
-
-## User-facing slash commands
-
-| Command | Role | Notes |
-|---|---|---|
-| \`/cc\` | Entry point. No args = resume. With prompt = classify + start. | Writes \`00-idea.md\` and picks the track. |
-| \`/cc-next\` | Advance or resume the current stage based on gates. | Soft nudge from Ralph Loop during \`tdd\`. |
-| \`/cc-ideate\` | Repo-improvement discovery, separate from product flow. | Produces ideas, not stage artifacts. |
-| \`/cc-view [status\\|tree\\|diff]\` | Read-only router. Never mutates flow state. | \`diff\` refreshes the snapshot baseline by design. |
-| \`/cc-ops [feature\\|tdd-log\\|retro\\|compound\\|archive\\|rewind]\` | Operations router for post-flow and side-channel actions. | Mutations are scoped to each subcommand. |
-
-Subcommand dispatch lives in \`${RUNTIME_ROOT}/commands/\` and the
-matching \`${RUNTIME_ROOT}/skills/flow-*/SKILL.md\`. The meta-skill
-(\`${RUNTIME_ROOT}/skills/using-cclaw/SKILL.md\`) decides which router to
-use before any substantive work.
-
-## Ralph Loop (TDD progress signal)
-
-When \`currentStage === "tdd"\`, SessionStart writes
-\`${RUNTIME_ROOT}/state/ralph-loop.json\` from the TDD cycle log. Fields
-worth acting on:
-
-- \`loopIteration\` — how many RED → GREEN cycles already landed.
-- \`redOpenSlices\` — slices with an unsatisfied RED. Non-empty means do
-  **not** advance to review.
-- \`acClosed\` — distinct acceptance-criterion IDs closed by a GREEN row
-  (requires \`acIds\` on the green log entry via \`/cc-ops tdd-log\`).
-- \`sliceCount\` — total distinct plan slices ever touched.
-
-Ralph Loop is a signal, not a gate. Stage advancement still runs
-through the normal \`flow-state.json\` gate catalog.
-
-## Compound readiness (auto-promotion signal)
-
-SessionStart also refreshes
-\`${RUNTIME_ROOT}/state/compound-readiness.json\` from \`knowledge.jsonl\`.
-The file lists clusters whose summed \`frequency\` reaches
-\`compound.recurrenceThreshold\` (default 3) or whose severity is
-\`critical\` (override). It surfaces a one-line nudge in the session
-digest only during \`review\` and \`ship\`, where lift-to-rule is in
-scope; earlier stages refresh the file silently. Promotion itself stays
-manual via \`/cc-ops compound\` so the signal never blocks flow.
-
-## Key state files
-
-| Path | What it holds |
-|---|---|
-| \`${RUNTIME_ROOT}/state/flow-state.json\` | Track, currentStage, completedStages, gate catalog, closeout substate. |
-| \`${RUNTIME_ROOT}/state/delegation-log.json\` | Per-stage mandatory agent status + fulfillmentMode + evidenceRefs. |
-| \`${RUNTIME_ROOT}/state/tdd-cycle-log.jsonl\` | Append-only RED/GREEN/REFACTOR entries (source of Ralph Loop). |
-| \`${RUNTIME_ROOT}/state/ralph-loop.json\` | Derived Ralph Loop status (TDD-only). |
-| \`${RUNTIME_ROOT}/state/compound-readiness.json\` | Derived compound-promotion readiness (refreshed each SessionStart). |
-| \`${RUNTIME_ROOT}/state/stage-activity.jsonl\` | Append-only stage-enter/exit and gate-pass signals. |
-| \`${RUNTIME_ROOT}/state/checkpoint.json\` | Latest session checkpoint (stage + timestamp). |
-| \`${RUNTIME_ROOT}/state/context-mode.json\` | Active context mode (\`default\`, \`headless\`, ...). |
-| \`${RUNTIME_ROOT}/state/harness-gaps.json\` | Per-harness tier, subagent fallback, playbook path (schemaVersion 2). |
-| \`${RUNTIME_ROOT}/knowledge.jsonl\` | Append-only learnings; surfaced to sessions via digest. |
-
-## Strictness and hooks
-
-Hook-driven guards respect the \`strictness\` field in
-\`${RUNTIME_ROOT}/config.yaml\`:
-
-- \`advisory\` (default) — hooks warn but never block tool calls.
-- \`strict\` — hooks block tool calls that violate their scope.
-
-Override per-session with \`CCLAW_STRICTNESS=advisory|strict\`.
-
-Hook wiring itself comes from a **single manifest** (\`src/content/hook-manifest.ts\`):
-the per-harness documents at \`.claude/hooks/hooks.json\`, \`.cursor/hooks.json\`,
-\`.codex/hooks.json\` are all derived from it. Inspect the live bindings with
-\`cclaw internal hook-manifest\` (add \`--json\` for machine-readable output).
-
-## When in doubt
-
-1. Read \`${RUNTIME_ROOT}/state/flow-state.json\` to know where you are.
-2. Load the matching stage skill only if you are about to do
-   substantive work (see \`using-cclaw\` meta-skill).
-3. Prefer \`/cc-next\` for progression. \`/cc-view\` for visibility.
-   \`/cc-ops\` for side-channel operations.
-`;
-}

package/dist/content/harness-doc.d.ts

@@ -1,2 +0,0 @@
-export declare function harnessIntegrationDocMarkdown(): string;
-export declare function harnessDocsOverviewMarkdown(): string;

package/dist/content/harness-doc.js

@@ -1,202 +0,0 @@
-import { HARNESS_ADAPTERS, harnessTier } from "../harness-adapters.js";
-import { STAGE_TO_SKILL_FOLDER } from "../constants.js";
-import { HOOK_EVENTS_BY_HARNESS, HOOK_SEMANTIC_EVENTS } from "./hook-events.js";
-import { HARNESS_PLAYBOOKS_DIR, harnessPlaybookFileName } from "./harness-playbooks.js";
-import { HARNESS_TOOL_REFS_DIR } from "./harness-tool-refs.js";
-function harnessTitle(harness) {
-    switch (harness) {
-        case "claude":
-            return "Claude Code";
-        case "cursor":
-            return "Cursor";
-        case "opencode":
-            return "OpenCode";
-        case "codex":
-            return "OpenAI Codex";
-    }
-}
-function tierDescription(tier) {
-    if (tier === "tier1")
-        return "full native automation";
-    if (tier === "tier2")
-        return "partial automation with waivers";
-    return "compatibility shim";
-}
-export function harnessIntegrationDocMarkdown() {
-    const harnesses = Object.keys(HARNESS_ADAPTERS);
-    const stageSkillRows = Object.entries(STAGE_TO_SKILL_FOLDER)
-        .map(([stage, skillFolder]) => `| \`${stage}\` | \`${skillFolder}\` |`)
-        .join("\n");
-    const hookCasingRows = [
-        "| Claude Code | `claude` | PascalCase (`SessionStart`, `PreToolUse`) |",
-        "| Cursor | `cursor` | camelCase (`sessionStart`, `preToolUse`) |",
-        "| OpenCode | `opencode` | camelCase (`sessionStart`, `preToolUse`) |",
-        "| OpenAI Codex | `codex` | PascalCase (`SessionStart`, `PreToolUse`) |"
-    ].join("\n");
-    const capabilityRows = harnesses
-        .map((harness) => {
-        const adapter = HARNESS_ADAPTERS[harness];
-        const tier = harnessTier(harness);
-        const caps = adapter.capabilities;
-        const playbook = `\`${HARNESS_PLAYBOOKS_DIR}/${harnessPlaybookFileName(harness)}\``;
-        return `| ${harnessTitle(harness)} | \`${harness}\` | \`${tier}\` (${tierDescription(tier)}) | ${caps.nativeSubagentDispatch} | ${caps.subagentFallback} | ${caps.hookSurface} | ${caps.structuredAsk} | ${playbook} |`;
-    })
-        .join("\n");
-    const hookRows = HOOK_SEMANTIC_EVENTS.map((eventName) => {
-        const columns = harnesses
-            .map((harness) => {
-            const mapping = HOOK_EVENTS_BY_HARNESS[harness][eventName];
-            return mapping ?? "missing";
-        })
-            .join(" | ");
-        return `| \`${eventName}\` | ${columns} |`;
-    }).join("\n");
-    return `# Harness Integration Matrix
-
-Generated from \`src/harness-adapters.ts\` capabilities and hook event mappings.
-
-## Capability tiers
-
-| Harness | ID | Tier | Native dispatch | Fallback | Hook surface | Structured ask | Playbook |
-|---|---|---|---|---|---|---|---|
-${capabilityRows}
-
-Fallback legend:
-
-- \`native\` — first-class named subagent dispatch (Claude).
-- \`generic-dispatch\` — generic Task dispatcher mapped to cclaw roles (Cursor).
-- \`role-switch\` — in-session role announce + delegation-log entry with evidenceRefs (OpenCode, Codex).
-- \`waiver\` — no parity path; reserved for harnesses that cannot role-switch (none shipped).
-
-## Parallel research dispatch semantics
-
-Design-stage research fleet uses the same parity model:
-
-- **Claude / Cursor**: dispatch all four research lenses in one turn
-  (stack, features, architecture, pitfalls) and synthesize into
-  \`.cclaw/artifacts/02a-research.md\`.
-- **OpenCode / Codex**: execute the same four lenses via sequential
-  role-switch, each with explicit announce -> execute -> evidence trail.
-  This preserves auditability when native parallel dispatch is unavailable.
-
-## Semantic hook event coverage
-
-| Event | Claude | Cursor | OpenCode | Codex |
-|---|---|---|---|---|
-${hookRows}
-
-## Hook event casing
-
-Hook keys are intentionally harness-native and must not be normalized:
-
-| Harness | ID | Event key casing |
-|---|---|---|
-${hookCasingRows}
-
-Use the exact event names from each harness schema. Treating all hooks as one
-shared casing silently breaks generated wiring.
-
-## Interpretation
-
-- \`tier1\`: full native delegation + structured asks + full hook surface.
-- \`tier2\`: usable flow with capability gaps; mandatory delegation can require waivers.
-- Codex-specific ceiling: \`PreToolUse\` can only intercept \`Bash\`. Direct
-  \`Write\`/\`Edit\` to \`.cclaw/state/flow-state.json\` cannot be hard-blocked
-  at hook level, so the canonical path is
-  \`node .cclaw/hooks/stage-complete.mjs <stage>\` plus the non-blocking
-  \`UserPromptSubmit\` state nudge.
-
-## Shared command contract
-
-All harnesses receive the same utility commands:
-
-- \`/cc\` - flow entry and resume
-- \`/cc-next\` - stage progression
-- \`/cc-ideate\` - ideate mode for ranked repo-improvement backlog
-- \`/cc-view\` - read-only router for status/tree/diff
-- \`/cc-ops\` - operations router for feature/tdd-log/retro/compound/archive/rewind
-
-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 ...\` - git-worktree feature isolation and routing
-- \`/cc-ops tdd-log ...\` - explicit RED/GREEN/REFACTOR evidence log
-- \`/cc-ops retro\` - mandatory retrospective gate before archive
-- \`/cc-ops compound\` - lift repeated learnings into durable rules/skills
-- \`/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\`
-
-## Stage -> skill folder mapping
-
-| Stage | Skill folder |
-|---|---|
-${stageSkillRows}
-
-This map is generated from \`src/constants.ts::STAGE_TO_SKILL_FOLDER\` so
-skill-path naming stays explicit and stable even when stage ids differ from
-folder names.
-
-## Install surfaces
-
-Always generated:
-
-- \`.cclaw/commands/*.md\`
-- \`.cclaw/skills/*/SKILL.md\`
-- \`.cclaw/references/**\`
-- \`.cclaw/state/*.json|*.jsonl\`
-- \`AGENTS.md\` managed block
-
-Harness-specific additions:
-
-- \`claude\`: \`.claude/commands/cc*.md\`, \`.claude/hooks/hooks.json\`
-- \`cursor\`: \`.cursor/commands/cc*.md\`, \`.cursor/hooks.json\`, \`.cursor/rules/cclaw-workflow.mdc\`
-- \`opencode\`: \`.opencode/commands/cc*.md\`, \`.opencode/plugins/cclaw-plugin.mjs\`, opencode plugin registration
-- \`codex\`: \`.agents/skills/cc/SKILL.md\`, \`.agents/skills/cc-next/SKILL.md\`, \`.agents/skills/cc-ideate/SKILL.md\`, \`.agents/skills/cc-view/SKILL.md\`, \`.agents/skills/cc-ops/SKILL.md\`, \`.codex/hooks.json\` (Codex CLI reads \`.agents/skills/\` for custom skills and consumes \`.codex/hooks.json\` on v0.114+ when \`[features] codex_hooks = true\` is set in \`~/.codex/config.toml\`. \`.codex/commands/\` and the legacy \`.agents/skills/cclaw-cc*/\` layout from v0.39.x are auto-cleaned on sync.)
-
-## Runtime observability
-
-- \`.cclaw/state/harness-gaps.json\` captures per-harness capability gaps for the active config.
-- \`cclaw doctor\` validates shim, hook, and lifecycle surfaces against this capability model.
-`;
-}
-export function harnessDocsOverviewMarkdown() {
-    const harnesses = Object.keys(HARNESS_ADAPTERS);
-    const rows = harnesses
-        .map((harness) => {
-        const tier = harnessTier(harness);
-        const toolMap = `\`.cclaw/${HARNESS_TOOL_REFS_DIR}/${harness}.md\``;
-        const playbook = `\`.cclaw/${HARNESS_PLAYBOOKS_DIR}/${harnessPlaybookFileName(harness)}\``;
-        return `| ${harnessTitle(harness)} | \`${harness}\` | \`${tier}\` | ${toolMap} | ${playbook} |`;
-    })
-        .join("\n");
-    return `# Harness Docs Overview
-
-Single entrypoint for harness-specific references generated by cclaw sync.
-
-## Core references
-
-- Integration matrix: \`.cclaw/references/harnesses.md\`
-- Tool-map index: \`.cclaw/references/${HARNESS_TOOL_REFS_DIR}/README.md\`
-- Playbook index: \`.cclaw/references/${HARNESS_PLAYBOOKS_DIR}/README.md\`
-
-## Per-harness quick links
-
-| Harness | ID | Tier | Tool map | Playbook |
-|---|---|---|---|---|
-${rows}
-
-## How to use this pack
-
-1. Start with \`harnesses.md\` to understand capability/tier differences.
-2. Open the harness-specific tool map before writing stage logic that depends on tool names.
-3. Open the harness-specific playbook before asserting delegation parity behavior.
-4. If docs disagree, treat \`harnesses.md\` + harness adapter capabilities as source of truth and regenerate.
-`;
-}

package/dist/content/harness-playbooks.d.ts

@@ -1,24 +0,0 @@
-/**
- * Per-harness parity playbooks.
- *
- * cclaw's subagent contracts (planner / reviewer / security-reviewer /
- * test-author / doc-updater) assume Claude-style isolated workers. On
- * harnesses without that primitive, the agent has to fulfil the role via a
- * documented fallback (generic Task dispatch, role-switch in-session, …).
- *
- * Each playbook is:
- *   1. short (≤ ~150 lines markdown),
- *   2. executable — reproducible by an agent without reading the whole repo,
- *   3. evidence-first — always records a delegation-log entry with
- *      `fulfillmentMode` and `evidenceRefs` so `cclaw doctor` can tell the
- *      role was actually performed.
- *
- * Playbooks are materialised at
- * `.cclaw/references/harnesses/<harness>-playbook.md` by install/sync/upgrade.
- */
-import type { HarnessId } from "../types.js";
-export declare const HARNESS_PLAYBOOKS_DIR = "references/harnesses";
-export declare function harnessPlaybookRelativePath(harness: HarnessId): string;
-export declare function harnessPlaybookFileName(harness: HarnessId): string;
-export declare function harnessPlaybookMarkdown(harness: HarnessId): string;
-export declare function harnessPlaybooksIndexMarkdown(): string;