cclaw-cli 6.14.3 → 7.0.0

package/dist/content/subagents.js

@@ -18,7 +18,7 @@ function automaticStageDelegationTable() {
 |---|---|---|
 ${rows}
 
-> **Track-aware skip (Wave 24, v6.0.0):** mandatory agents are skipped entirely when \`track === "quick"\` OR \`taskClass === "software-bugfix"\`. Use \`mandatoryAgentsFor(stage, track, taskClass)\` from \`src/content/stage-schema.ts\` for the authoritative list at runtime. Proactive agents are trigger-driven opportunities, not a blanket completion gate, and lean/lightweight early-stage runs may intentionally record none.`;
+> **Track-aware skip:** mandatory agents are skipped entirely when \`track === "quick"\` OR \`taskClass === "software-bugfix"\`. Use \`mandatoryAgentsFor(stage, track, taskClass)\` from \`src/content/stage-schema.ts\` for the authoritative list at runtime. Proactive agents are trigger-driven opportunities, not a blanket completion gate, and lean/lightweight early-stage runs may intentionally record none.`;
 }
 function stageSummary(stage) {
     return stageDelegationSummary("standard").find((row) => row.stage === stage)
@@ -37,7 +37,7 @@ description: "Orchestrate implementation via isolated subagents — one fresh ag
 Use a **controller -> coder -> overseer** loop when building multi-step software work.
 
 - **Controller (parent agent):** owns the plan, gating, sequencing, and dispatch decisions; never mixes deep implementation context with review evidence.
-- **Coder / slice-implementer (subagent):** receives a **single self-contained task** and edits code only within that scope; exits with a structured status contract.
+- **Coder / slice-builder (subagent):** receives a **single self-contained task** and edits code only within that scope; exits with a structured status contract.
 - **Overseer / reviewer (subagent):** validates outputs against the specification **by reading code** and never edits during the overseer pass.
 
 This pattern is intentionally **Superpowers-style**: cheap parallelism where it doesn’t corrupt state, strict serialization where it would.
@@ -62,14 +62,15 @@ Reconcile findings into \`.cclaw/artifacts/07-review-army.json\` with explicit s
 
 ### TDD evidence protocol
 
-Treat RED, GREEN, and REFACTOR as phase intents inside one mandatory \`test-author\` delegation by default:
+Each parallel slice runs end-to-end inside one \`slice-builder\` delegation, with RED, GREEN, REFACTOR, and per-slice DOC as phase intents on a single span:
 
-- \`tdd-red\`: tests only, no production writes
-- \`tdd-green\`: minimal production implementation, no new RED tests
-- \`tdd-refactor\`: cleanup only after GREEN is proven
+- \`--phase red\`: failing tests only, no production writes
+- \`--phase green\`: minimal production implementation that passes the matching RED
+- \`--phase refactor\` (or \`--phase refactor-deferred --refactor-rationale "<why>"\`): behavior-preserving cleanup, only after GREEN is proven
+- \`--phase doc\`: write \`<artifacts-dir>/tdd-slices/S-<id>.md\` for the slice
 
 Set \`CCLAW_ACTIVE_AGENT\` to the active phase name when possible so workflow-guard
-can enforce phase-appropriate write boundaries. Use separate workers only when the harness and slice boundary make the split genuinely useful; the mandatory gate is the evidence-backed \`test-author\` row, not three default subagents.
+can enforce phase-appropriate write boundaries. The mandatory gate is the evidence-backed \`slice-builder\` row, not multiple default subagents.
 
 ## Model & Harness Routing Notes
 
@@ -111,7 +112,7 @@ The only time a \`harness_limitation\` waiver fires automatically is when every
 | Tier | Use for | Example agents |
 |---|---|---|
 | \`deep\` | one heavy reasoning pass per stage (planner, final reconciliation) | planner |
-| \`balanced\` | spec compliance + code/security review with enough context | reviewer, security-reviewer, test-author |
+| \`balanced\` | spec compliance + code/security review with enough context | reviewer, security-reviewer, slice-builder |
 | \`fast\` | bounded maintenance updates and doc hygiene | doc-updater |
 
 **Routing rules:**
@@ -128,7 +129,7 @@ Concrete per-stage rules so the controller does not have to guess which tier fit
 |---|---|---|---|---|
 | brainstorm | planner (only if ambiguity spans >1 module) | product-discovery / critic when product value or premise is uncertain | run in-thread research playbooks | promote to \`balanced\` critic if the do-nothing path may beat the idea |
 | scope | planner (always) | product-discovery / critic when mode changes value, trajectory, or boundaries | run \`research/git-history.md\` in-thread when churn is high | promote to \`balanced\` critic if scope mode is disputed |
-| design | planner (always) | critic, security-reviewer, test-author when alternatives/trust/testability apply | run \`research/framework-docs-lookup.md\` + \`research/best-practices-lookup.md\` in-thread | escalate one specialist to \`deep\` only if a failure mode is Critical-severity |
+| design | planner (always) | critic, security-reviewer when alternatives/trust apply | run \`research/framework-docs-lookup.md\` + \`research/best-practices-lookup.md\` in-thread | escalate one specialist to \`deep\` only if a failure mode is Critical-severity |
 | spec | — | spec-validator / spec-document-reviewer / reviewer (for long or high-risk specs) | — | escalate to \`deep\` only for spec ↔ design contradictions |
 | plan | planner (solo, always) | — | — | never fan out at plan stage; one owner for dependency graph |
 | tdd | — | ${formatAgentList(stageSummary("tdd").primaryAgents)} (per slice, carrying RED/GREEN/REFACTOR evidence) · reviewer (slice-local only when sliceReview triggers) | doc-updater (API surface changes) | escalate to \`deep\` only when a RED test cannot be expressed (design leak) |
@@ -139,7 +140,7 @@ Concrete per-stage rules so the controller does not have to guess which tier fit
 - If a \`deep\` planner run returns low-uncertainty output (single unambiguous plan), do **not** add a second \`deep\` pass in the same stage.
 - If a \`fast\` researcher's evidence is the only input to a decision, the consuming agent must be \`balanced\` or higher.
 - Review-stage reviewers should default to \`balanced\`; bump to \`deep\` only when findings cite architectural contradictions.
-- Refactor-only TDD slices (state-based, no behavioral change) can drop test-author to \`fast\` if the test pyramid stays green.
+- Refactor-only TDD slices (state-based, no behavioral change) can drop \`slice-builder\` to \`fast\` if the test pyramid stays green.
 
 ## HARD-GATE
 
@@ -398,7 +399,7 @@ ${conversationLanguagePolicyMarkdown()}
 
 Implementation that touches shared source trees must remain **sequential** unless you have proven disjoint filesystem ownership (rare) and an explicit merge protocol.
 
-When explicit bounded TDD fan-out is approved with parallel \`slice-implementer\` lanes, author \`.cclaw/artifacts/cohesion-contract.md\` + \`.json\` before launch and run \`integration-overseer\` after fan-in.
+When explicit bounded TDD fan-out is approved with parallel \`slice-builder\` lanes, author \`.cclaw/artifacts/cohesion-contract.md\` + \`.json\` before launch and run \`integration-overseer\` after fan-in.
 
 ## When to Use
 
@@ -423,7 +424,7 @@ When explicit bounded TDD fan-out is approved with parallel \`slice-implementer\
 ## Dispatch Protocol
 
 1. **Identify independent problem domains** (no file overlap; no shared mutable working assumptions).
-2. **Author cohesion contract first** whenever fan-out touches shared interfaces or bounded parallel \`slice-implementer\` lanes.
+2. **Author cohesion contract first** whenever fan-out touches shared interfaces or bounded parallel \`slice-builder\` lanes.
 3. **Craft one prompt per domain** with **full context pasted** — same HARD-GATE as SDD: no “go read X to learn why.”
 4. **Launch ALL agents in a single controller message** (multiple Task tool calls) so they start with comparable timelines.
 5. **Wait for all to return** before synthesis (avoid incremental confirmation bias).
@@ -666,34 +667,6 @@ Required output:
 - PATCH_RECOMMENDATIONS: minimal edits to make the spec plan-ready
 ${MARKDOWN_CODE_FENCE}
 
-`;
-}
-function sliceImplementerEnhancedBody() {
-    return `
-
-## Task Tool Delegation
-
-${MARKDOWN_CODE_FENCE}
-You are a slice-implementer subagent.
-
-SLICE: {single vertical slice — controller MUST dispatch you with --slice S-<id> --phase green --paths <comma-separated>}
-RED_EVIDENCE: {failing test and expected failure}
-ALLOWED_FILES: {explicit file boundaries — surfaced to scheduler as Files: <paths>}
-FORBIDDEN_CHANGES: {scope/compatibility limits}
-VERIFICATION: {commands expected}
-
-Rules:
-- Implement only the minimal GREEN change for the existing RED evidence.
-- Keep REFACTOR behavior-preserving.
-- Return the strict worker JSON schema first.
-
-Slice phase-event contract (v6.11.0):
-- Do NOT hand-edit \`## Watched-RED Proof\`, \`## Vertical Slice Cycle\`, \`## RED Evidence\`, or \`## GREEN Evidence\` markdown tables in 06-tdd.md. The linter auto-renders them between \`<!-- auto-start: tdd-slice-summary -->\` markers from \`delegation-events.jsonl\` slice phase rows.
-- Your dispatch row IS the evidence: the harness-generated delegation-record hook stamps \`sliceId=S-<id>\`, \`phase=green\`, and \`completedTs\` automatically. Attach evidenceRefs (test path, span ref, or pasted-output pointer) so the linter validates the row.
-- After REFACTOR, ask the controller to re-dispatch you with \`--phase refactor\` (or \`--phase refactor-deferred --refactor-rationale "<why>"\`); each call appends a new ledger row.
-- Per-slice prose summary lives in \`<artifacts-dir>/tdd-slices/S-<id>.md\` and is owned by the parallel \`slice-documenter\` (or the controller). You do NOT touch that file.
-${MARKDOWN_CODE_FENCE}
-
 `;
 }
 function performanceReviewerEnhancedBody() {
@@ -913,40 +886,6 @@ Requirements:
 - Close with SECURITY_VERDICT: SHIP | SHIP_WITH_HOTFIXES | NO_SHIP and cite top 3 drivers.
 ${MARKDOWN_CODE_FENCE}
 
-`;
-}
-function testAuthorEnhancedBody() {
-    return `
-
-## Task Tool Delegation
-
-Delegate TDD loops carefully — one behavioral slice per subagent to avoid clobbering tests.
-This agent runs in two explicit stage modes to respect cclaw hard-gates:
-- \`TEST_RED_ONLY\` (only failing tests + evidence; no production edits)
-- \`BUILD_GREEN_REFACTOR\` (implementation + full-suite green + refactor notes)
-
-${MARKDOWN_CODE_FENCE}
-You are a TDD implementer subagent.
-
-STAGE_MODE: {TEST_RED_ONLY | BUILD_GREEN_REFACTOR}
-FEATURE SLICE: {single behavior expressed as a user-observable outcome}
-CURRENT TEST COMMANDS: {exact command names + cwd assumptions}
-FIXTURES / PATTERNS: {links to helper modules by path + naming conventions}
-
-Process (mandatory):
-1) If STAGE_MODE=TEST_RED_ONLY:
-   - Controller dispatched you with \`--slice S-<id> --phase red\`. Add failing tests proving the gap (show failing output excerpt).
-   - Do NOT edit production code.
-   - Do NOT hand-edit \`## Watched-RED Proof\` / \`## RED Evidence\` markdown tables in 06-tdd.md — the linter auto-renders them from your dispatch row in \`delegation-events.jsonl\`. Just ensure your worker return includes evidenceRefs (test path, span ref, or pasted-output pointer) so the harness can stamp them on the ledger row.
-   - Report: TESTS_ADDED, RED_COMMAND_RUN, RED_EVIDENCE, STATUS: DONE|BLOCKED.
-2) If STAGE_MODE=BUILD_GREEN_REFACTOR:
-   - Controller dispatched you with \`--slice S-<id> --phase green\` (and later \`--phase refactor\` or \`--phase refactor-deferred --refactor-rationale "<why>"\`).
-   - GREEN — minimal production code to satisfy existing RED tests, rerun full suite.
-   - REFACTOR — only after full suite is green; preserve behavior.
-   - Do NOT hand-edit \`## Vertical Slice Cycle\` / \`## GREEN Evidence\` markdown tables — auto-rendered from your dispatch row.
-   - Report: FILES_EDITED, GREEN_COMMAND_RUN, REFACTOR_NOTES, STATUS: DONE|BLOCKED.
-${MARKDOWN_CODE_FENCE}
-
 `;
 }
 function implementerEnhancedBody() {

package/dist/content/templates.d.ts

@@ -1,5 +1,5 @@
 /**
- * Shared investigation discipline block (Round 5 / v6.6.0). Rendered once per
+ * Shared investigation discipline block. Rendered once per
  * elicitation/spec stage skill (brainstorm, scope, design, spec, plan, tdd,
  * review). The block enforces a four-step ladder before drafting and a
  * path-passing rule for delegations so token cost and "jumped into code"
@@ -12,15 +12,15 @@ export declare const RULEBOOK_MARKDOWN = "# Cclaw Rulebook\n\n## MUST_ALWAYS\n-
 /**
  * Always-on baseline rule materialized at `.cursor/rules/cclaw-guidelines.mdc`.
  * Independent of skill activation — kicks in even when the agent skips
- * loading skills. Three hard rules cover the most common Wave 22 regressions
+ * loading skills. Three hard rules cover the most common regressions
  * (premature draft, premature subagent dispatch, command-line echo to chat).
  */
-export declare const CURSOR_GUIDELINES_RULE_MDC = "---\ndescription: cclaw zero-install behavior baseline (always-on)\nglobs:\n  - \"**/*\"\nalwaysApply: true\n---\n\n<!-- cclaw-managed-cursor-guidelines-rule -->\n\n# Cclaw Baseline Guidelines\n\nThese three rules apply to every Cursor agent session in this project,\nregardless of whether stage skills loaded.\n\n## 1. Q&A floor before drafting (brainstorm/scope/design)\n\nBefore drafting any `.cclaw/artifacts/01-brainstorm-*.md`,\n`02-scope-*.md`, or `03-design-*.md`, verify that the artifact's\n`## Q&A Log` table demonstrates Ralph-Loop convergence: every\nforcing-question topic id is tagged `[topic:<id>]` on at least one row\n(see the stage's forcing-questions checklist for the id list), the last\n2 turns produce no new decision-changing impact, OR an explicit user\nstop-signal row is recorded. Walk the stage forcing questions one at a\ntime via the `AskQuestion` tool. If you find yourself proposing a\ndraft after 1-2 questions while forcing topic ids remain untagged, STOP\nand continue the loop.\n\nThe `qa_log_unconverged` linter rule will block `stage-complete` when\nconvergence has not been reached. Wave 24 (v6.0.0) made `[topic:<id>]`\ntagging mandatory; the English keyword fallback was removed because it\nmis-reported convergence on RU/UA Q&A logs.\n\n## 2. Mandatory subagents run after Q&A approval\n\nFor brainstorm / scope / design, mandatory subagents (\n`product-discovery`, `critic`, `planner`, `architect`,\n`test-author`) run **only AFTER the user approves the elicitation\noutcome**, never before the Q&A loop converges. Dispatching them early\npreempts the user dialogue and violates the elicitation contract \u2014 the\nlinter will block stage-complete.\n\nSee each stage's \"Run Phase: post-elicitation\" rows in the materialized\nAutomatic Subagent Dispatch table.\n\n## 3. Never echo cclaw command lines to chat\n\nThe user does not run cclaw helpers (`node .cclaw/hooks/...`) manually.\nNEVER paste full command lines, `--evidence-json '{...}'` payloads,\n`--waive-delegation=...`, or shell hash commands (`shasum`,\n`sha256sum`, `Get-FileHash`, `certutil`, etc.) into chat. Run the\nhelper via the tool layer and report only the resulting summary. On\nfailure, report a compact human-readable summary plus the helper JSON in\na single fenced `json` block.\n";
+export declare const CURSOR_GUIDELINES_RULE_MDC = "---\ndescription: cclaw zero-install behavior baseline (always-on)\nglobs:\n  - \"**/*\"\nalwaysApply: true\n---\n\n<!-- cclaw-managed-cursor-guidelines-rule -->\n\n# Cclaw Baseline Guidelines\n\nThese three rules apply to every Cursor agent session in this project,\nregardless of whether stage skills loaded.\n\n## 1. Q&A floor before drafting (brainstorm/scope/design)\n\nBefore drafting any `.cclaw/artifacts/01-brainstorm-*.md`,\n`02-scope-*.md`, or `03-design-*.md`, verify that the artifact's\n`## Q&A Log` table demonstrates Ralph-Loop convergence: every\nforcing-question topic id is tagged `[topic:<id>]` on at least one row\n(see the stage's forcing-questions checklist for the id list), the last\n2 turns produce no new decision-changing impact, OR an explicit user\nstop-signal row is recorded. Walk the stage forcing questions one at a\ntime via the `AskQuestion` tool. If you find yourself proposing a\ndraft after 1-2 questions while forcing topic ids remain untagged, STOP\nand continue the loop.\n\nThe `qa_log_unconverged` linter rule will block `stage-complete` when\nconvergence has not been reached. `[topic:<id>]` tagging is mandatory:\nEnglish keyword detection is intentionally absent because it mis-reports\nconvergence on RU/UA Q&A logs.\n\n## 2. Mandatory subagents run after Q&A approval\n\nFor brainstorm / scope / design, mandatory subagents (\n`product-discovery`, `critic`, `planner`, `architect`) run **only\nAFTER the user approves the elicitation outcome**, never before the Q&A\nloop converges. Dispatching them early preempts the user dialogue and\nviolates the elicitation contract \u2014 the linter will block stage-complete.\n\nSee each stage's \"Run Phase: post-elicitation\" rows in the materialized\nAutomatic Subagent Dispatch table.\n\n## 3. Never echo cclaw command lines to chat\n\nThe user does not run cclaw helpers (`node .cclaw/hooks/...`) manually.\nNEVER paste full command lines, `--evidence-json '{...}'` payloads,\n`--waive-delegation=...`, or shell hash commands (`shasum`,\n`sha256sum`, `Get-FileHash`, `certutil`, etc.) into chat. Run the\nhelper via the tool layer and report only the resulting summary. On\nfailure, report a compact human-readable summary plus the helper JSON in\na single fenced `json` block.\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- Stage completion claim requires `stage-complete` exit 0 in the current turn. Quote the single-line success JSON printed to stdout (e.g. `{\"ok\":true,\"command\":\"stage-complete\",...}`); do not paraphrase, do not infer success from empty stdout or from skipped retries.\n\n## Protocol label hygiene\n\n`skip` wording means different things depending on phase: brainstorm/scope/design Q&A stop-signals may still literal **skip**/enough/move-on wording; structured ship closeout retros and compound clustering prompts should expose **no changes** (or accept-as-is language) rather than labeling the passive path as skip. Keep the verbs aligned with the harness question copy you present to the human.\n- Do not mark gates passed from memory.\n- Keep evidence in `.cclaw/artifacts/`; archive through closeout via `/cc` or cancel early via `node .cclaw/hooks/cancel-run.mjs`.\n\n## Delegation And Approvals\n\n- Machine-only checks in design/plan/tdd/review/ship should auto-dispatch when tooling supports it.\n- **For brainstorm / scope / design stages**: ask user input continuously via adaptive elicitation (one question per turn through the harness-native question tool \u2014 `AskQuestion` in Cursor). Walk the stage forcing-questions list one-by-one. **Tag each Q&A Log row's `Decision impact` cell with `[topic:<id>]`** (the id is given in the stage's forcing-questions checklist) so the linter can verify coverage in any natural language. Do NOT batch and do NOT defer to a single approval gate at the end. The `qa_log_unconverged` linter rule will block `stage-complete` when convergence is not reached (forcing topic ids untagged AND last 2 turns still produce decision-changing rows AND no stop-signal).\n- **For other stages** (spec/plan/tdd/build/review/ship): ask user input only at explicit approval gates (scope mode, plan approval, challenge resolution, ship finalization), not for routine progress updates.\n- If you find yourself proposing a draft after 1-2 questions in brainstorm/scope/design, STOP \u2014 go back to the forcing-questions list and continue.\n- Mandatory subagents in brainstorm/scope/design run only AFTER the user approves the elicitation outcome (see each stage's \"Run Phase: post-elicitation\" rows). Dispatching them before the Q&A loop converges violates the contract.\n- Never echo cclaw command lines (`node .cclaw/hooks/...`, `--evidence-json '{...}'`) to chat \u2014 the user does not run cclaw manually. Run helpers via the tool layer; report only the resulting summary.\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";
 /**
- * v6.11.0 (S2) — per-slice prose file written by `slice-documenter`
- * (or the controller) to `<artifacts-dir>/tdd-slices/S-<id>.md`. The
- * main `06-tdd.md` is auto-indexed via `## Slices Index`.
+ * Per-slice prose file written by `slice-builder` (or the controller)
+ * to `<artifacts-dir>/tdd-slices/S-<id>.md`. The main `06-tdd.md` is
+ * auto-indexed via `## Slices Index`.
  */
 export declare function tddSliceFileTemplate(sliceId: string): string;
 export declare function buildRulesJson(): Record<string, unknown>;

package/dist/content/templates.js

@@ -19,7 +19,7 @@ const SEED_SHELF_SECTION = `## Seed Shelf Candidates (optional)
 |---|---|---|---|
 | .cclaw/seeds/SEED-YYYY-MM-DD-<slug>.md |  |  |  |`;
 /**
- * Shared investigation discipline block (Round 5 / v6.6.0). Rendered once per
+ * Shared investigation discipline block. Rendered once per
  * elicitation/spec stage skill (brainstorm, scope, design, spec, plan, tdd,
  * review). The block enforces a four-step ladder before drafting and a
  * path-passing rule for delegations so token cost and "jumped into code"
@@ -116,7 +116,7 @@ ${renderBehaviorAnchorTemplateLine("brainstorm")}
 | 1 |  |  | scope-shaping [topic:pain] |
 
 > Append-only by turn. Add one row after each user answer; do not rewrite prior rows.
-> **Topic tag is MANDATORY for forcing-question rows.** Stamp \`[topic:<id>]\` in the \`Decision impact\` cell so the linter can verify coverage in any natural language (RU/EN/UA/etc.). Brainstorm IDs: \`pain\`, \`direct-path\`, \`operator\`, \`no-go\`. Multiple tags allowed when one answer covers several topics. Stop-signal rows do NOT need a tag. Wave 24 (v6.0.0) removed the English keyword fallback; Round 6 (v6.7.0) retired the counterfactual \`do-nothing\` topic (Do-nothing consequence stays in the Problem Decision Record).
+> **Topic tag is MANDATORY for forcing-question rows.** Stamp \`[topic:<id>]\` in the \`Decision impact\` cell so the linter can verify coverage in any natural language (RU/EN/UA/etc.). Brainstorm IDs: \`pain\`, \`direct-path\`, \`operator\`, \`no-go\`. Multiple tags allowed when one answer covers several topics. Stop-signal rows do NOT need a tag. The counterfactual \`do-nothing\` topic is intentionally absent — Do-nothing consequence lives in the Problem Decision Record.
 
 ## Approach Tier
 - Tier: lite | standard | deep
@@ -242,7 +242,7 @@ ${renderBehaviorAnchorTemplateLine("scope")}
 | 1 |  |  | scope-shaping [topic:in-out] |
 
 > Append-only by turn. Add one row after each user answer; do not rewrite prior rows.
-> **Topic tag is MANDATORY for forcing-question rows.** Stamp \`[topic:<id>]\` in the \`Decision impact\` cell so the linter can verify coverage in any natural language (RU/EN/UA/etc.). Scope IDs: \`in-out\`, \`locked-upstream\`, \`rollback\`, \`failure-modes\`. Multiple tags allowed when one answer covers several topics. Stop-signal rows do NOT need a tag. Wave 24 (v6.0.0) removed the English keyword fallback.
+> **Topic tag is MANDATORY for forcing-question rows.** Stamp \`[topic:<id>]\` in the \`Decision impact\` cell so the linter can verify coverage in any natural language (RU/EN/UA/etc.). Scope IDs: \`in-out\`, \`locked-upstream\`, \`rollback\`, \`failure-modes\`. Multiple tags allowed when one answer covers several topics. Stop-signal rows do NOT need a tag.
 
 ## Pre-Scope System Audit
 | Check | Command | Findings |
@@ -346,7 +346,7 @@ ${renderBehaviorAnchorTemplateLine("scope")}
 > scope/design/spec/plan/review/ship; downstream artifacts reference these IDs
 > verbatim. If a decision is later dropped, keep the row and mark it
 > \`(superseded by D-Y)\`; if a new one is added mid-flow, append with the next
-> free D-number. Wave 22 (v4.0.0) removed the legacy LD#<sha8> hash anchor —
+> free D-number. The earlier LD#<sha8> hash anchor is gone —
 > existing artifacts with LD# anchors remain valid markdown but the linter only
 > tracks D-XX IDs.
 
@@ -483,7 +483,7 @@ ${renderBehaviorAnchorTemplateLine("design")}
 | 1 |  |  | architecture-shaping [topic:data-flow] |
 
 > Append-only by turn. Add one row after each user answer; do not rewrite prior rows.
-> **Topic tag is MANDATORY for forcing-question rows.** Stamp \`[topic:<id>]\` in the \`Decision impact\` cell so the linter can verify coverage in any natural language (RU/EN/UA/etc.). Design IDs: \`data-flow\`, \`seams\`, \`invariants\`, \`not-refactor\`. Multiple tags allowed when one answer covers several topics. Stop-signal rows do NOT need a tag. Wave 24 (v6.0.0) removed the English keyword fallback.
+> **Topic tag is MANDATORY for forcing-question rows.** Stamp \`[topic:<id>]\` in the \`Decision impact\` cell so the linter can verify coverage in any natural language (RU/EN/UA/etc.). Design IDs: \`data-flow\`, \`seams\`, \`invariants\`, \`not-refactor\`. Multiple tags allowed when one answer covers several topics. Stop-signal rows do NOT need a tag.
 
 ## Codebase Investigation
 | File | Current responsibility | Patterns discovered | Existing fit / reuse candidate |
@@ -743,7 +743,7 @@ ${renderBehaviorAnchorTemplateLine("spec")}
 |---|---|---|---|---|---|
 | AC-1 | R1 |  |  | false |  |
 
-> Standard ACs reference at least one \`R#\` from \`02-scope.md\`. Quick-track ACs may instead put \`Quick Reproduction Contract\` / bug-slice refs in the Requirement Ref column and \`N/A\` for Design Decision Ref. ACs are stable (never renumber): dropped ACs stay with Priority \`DROPPED\`; new ones append with the next free \`AC-#\`. **v6.13.0:** \`parallelSafe\` states whether this AC can be proven in parallel with others; \`touchSurface\` lists repo-relative globs or modules this AC is expected to touch (scheduler + slice planning).
+> Standard ACs reference at least one \`R#\` from \`02-scope.md\`. Quick-track ACs may instead put \`Quick Reproduction Contract\` / bug-slice refs in the Requirement Ref column and \`N/A\` for Design Decision Ref. ACs are stable (never renumber): dropped ACs stay with Priority \`DROPPED\`; new ones append with the next free \`AC-#\`. \`parallelSafe\` states whether this AC can be proven in parallel with others; \`touchSurface\` lists repo-relative globs or modules this AC is expected to touch (scheduler + slice planning).
 
 ## Quick Reproduction Contract
 > Required for quick bug-fix specs; use \`N/A\` for non-bugfix or standard/medium tracks. TDD turns this contract into the RED reproduction test.
@@ -985,7 +985,7 @@ ${renderBehaviorAnchorTemplateLine("tdd")}
 <!-- auto-start: slices-index -->
 ## Slices Index
 
-_Auto-rendered from \`tdd-slices/S-*.md\` once slice-documenter or controller writes per-slice files. Do not edit by hand._
+_Auto-rendered from \`tdd-slices/S-*.md\` once \`slice-builder\` or the controller writes per-slice files. Do not edit by hand._
 <!-- auto-end: slices-index -->
 
 ## Test Discovery
@@ -997,17 +997,17 @@ _Auto-rendered from \`tdd-slices/S-*.md\` once slice-documenter or controller wr
 | S-1 |  | covered/out-of-scope because  |
 
 ## RED Evidence
-> From v6.11.0 the per-slice RED rows are auto-satisfied by \`phase=red\` events in \`delegation-events.jsonl\` (controller dispatches \`test-author --slice S-<id> --phase red\`). Legacy hand-filled tables continue to validate as a fallback. Use \`Evidence: <path>\` or \`Evidence: spanId:<id>\` pointers if you prefer a manual reference.
+> Per-slice RED rows are auto-satisfied by \`phase=red\` events in \`delegation-events.jsonl\` (controller dispatches \`slice-builder --slice S-<id> --phase red\`). Use \`Evidence: <path>\` or \`Evidence: spanId:<id>\` pointers if you prefer a manual reference.
 
 ## Acceptance & Failure Map
 | Slice | Source ID | AC ID | Expected behavior | RED-link |
 |---|---|---|---|---|
 | S-1 | SRC-1 | AC-1 |  |  |
 
-> Each slice maps to the active track's source item (plan slice on standard/medium, or the \`Quick Reproduction Contract\` bug slice / spec acceptance item on quick) and to a spec criterion. The RED-link column is satisfied by either a \`spanId:<id>\` from the delegation ledger or an \`<artifacts-dir>/<file>\` evidence pointer. From v6.11.0 the column is auto-derivable: a \`phase=red\` event in \`delegation-events.jsonl\` with non-empty evidenceRefs auto-satisfies the row.
+> Each slice maps to the active track's source item (plan slice on standard/medium, or the \`Quick Reproduction Contract\` bug slice / spec acceptance item on quick) and to a spec criterion. The RED-link column is satisfied by either a \`spanId:<id>\` from the delegation ledger or an \`<artifacts-dir>/<file>\` evidence pointer. The column is also auto-derivable: a \`phase=red\` event in \`delegation-events.jsonl\` with non-empty evidenceRefs auto-satisfies the row.
 
 ## GREEN Evidence
-> From v6.11.0 GREEN rows are auto-satisfied by \`phase=green\` events in \`delegation-events.jsonl\` (controller dispatches \`slice-implementer --slice S-<id> --phase green\`). Legacy hand-filled tables continue to validate as a fallback. Use \`Evidence: <path>\` or \`Evidence: spanId:<id>\` pointers if you prefer a manual reference.
+> GREEN rows are auto-satisfied by \`phase=green\` events in \`delegation-events.jsonl\` (controller dispatches \`slice-builder --slice S-<id> --phase green\`). Use \`Evidence: <path>\` or \`Evidence: spanId:<id>\` pointers if you prefer a manual reference.
 
 ## REFACTOR Notes
 - What changed:
@@ -1027,7 +1027,7 @@ _Auto-rendered from \`tdd-slices/S-*.md\` once slice-documenter or controller wr
 <!-- auto-start: tdd-slice-summary -->
 ## Vertical Slice Cycle
 
-_Auto-rendered from \`delegation-events.jsonl\` once \`test-author\` and \`slice-implementer\` are dispatched with \`--slice <id> --phase red|green|refactor|refactor-deferred\`. Do not edit by hand._
+_Auto-rendered from \`delegation-events.jsonl\` once \`slice-builder\` is dispatched per slice with \`--slice <id> --phase red|green|refactor|refactor-deferred\`. Do not edit by hand._
 <!-- auto-end: tdd-slice-summary -->
 
 ## Assertion Correctness Notes
@@ -1219,7 +1219,7 @@ ${renderBehaviorAnchorTemplateLine("review")}
 | AC-1 | PASS/FAIL |  |
 
 ## Layer 2 Findings
-> Wave 23 (v5.0.0): Layer 2 categories OWNED by review = cross-slice correctness, security, dependency/version, observability, external-safety. Performance + architecture findings are CARRY-FORWARD from \`03-design-<slug>.md\` (Performance Budget, ADR) — cite, do NOT re-derive. Single-slice findings stay in \`06-tdd.md > Per-Slice Review\`; review may cite their IDs (severity/disposition must match — cross-artifact-duplication linter blocks otherwise).
+> Layer 2 categories OWNED by review = cross-slice correctness, security, dependency/version, observability, external-safety. Performance + architecture findings are CARRY-FORWARD from \`03-design-<slug>.md\` (Performance Budget, ADR) — cite, do NOT re-derive. Single-slice findings stay in \`06-tdd.md > Per-Slice Review\`; review may cite their IDs (severity/disposition must match — cross-artifact-duplication linter blocks otherwise).
 
 | ID | Severity | Category | File:line / no-line reason | Description | Status |
 |---|---|---|---|---|---|
@@ -1498,7 +1498,7 @@ delegate to a specialized agent or skill if the harness supports it. The primary
 /**
  * Always-on baseline rule materialized at `.cursor/rules/cclaw-guidelines.mdc`.
  * Independent of skill activation — kicks in even when the agent skips
- * loading skills. Three hard rules cover the most common Wave 22 regressions
+ * loading skills. Three hard rules cover the most common regressions
  * (premature draft, premature subagent dispatch, command-line echo to chat).
  */
 export const CURSOR_GUIDELINES_RULE_MDC = `---
@@ -1529,18 +1529,17 @@ draft after 1-2 questions while forcing topic ids remain untagged, STOP
 and continue the loop.
 
 The \`qa_log_unconverged\` linter rule will block \`stage-complete\` when
-convergence has not been reached. Wave 24 (v6.0.0) made \`[topic:<id>]\`
-tagging mandatory; the English keyword fallback was removed because it
-mis-reported convergence on RU/UA Q&A logs.
+convergence has not been reached. \`[topic:<id>]\` tagging is mandatory:
+English keyword detection is intentionally absent because it mis-reports
+convergence on RU/UA Q&A logs.
 
 ## 2. Mandatory subagents run after Q&A approval
 
 For brainstorm / scope / design, mandatory subagents (
-\`product-discovery\`, \`critic\`, \`planner\`, \`architect\`,
-\`test-author\`) run **only AFTER the user approves the elicitation
-outcome**, never before the Q&A loop converges. Dispatching them early
-preempts the user dialogue and violates the elicitation contract — the
-linter will block stage-complete.
+\`product-discovery\`, \`critic\`, \`planner\`, \`architect\`) run **only
+AFTER the user approves the elicitation outcome**, never before the Q&A
+loop converges. Dispatching them early preempts the user dialogue and
+violates the elicitation contract — the linter will block stage-complete.
 
 See each stage's "Run Phase: post-elicitation" rows in the materialized
 Automatic Subagent Dispatch table.
@@ -1623,9 +1622,9 @@ Track-specific skips are allowed only when \`flow-state.track\` + \`skippedStage
   them unless the stage or role changes.
 `;
 /**
- * v6.11.0 (S2) — per-slice prose file written by `slice-documenter`
- * (or the controller) to `<artifacts-dir>/tdd-slices/S-<id>.md`. The
- * main `06-tdd.md` is auto-indexed via `## Slices Index`.
+ * Per-slice prose file written by `slice-builder` (or the controller)
+ * to `<artifacts-dir>/tdd-slices/S-<id>.md`. The main `06-tdd.md` is
+ * auto-indexed via `## Slices Index`.
  */
 export function tddSliceFileTemplate(sliceId) {
     return `# Slice ${sliceId}

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

@@ -23,7 +23,7 @@ export declare const LANGUAGE_RULE_PACK_FILES: {
 export declare const LANGUAGE_RULE_PACK_DIR: readonly ["rules", "lang"];
 export declare const LANGUAGE_RULE_PACK_GENERATORS: Record<string, () => string>;
 /**
- * Legacy per-language folders under `.cclaw/skills/` used in v0.7.0. Listed
+ * Older per-language folders under `.cclaw/skills/`. Listed
  * here so `cclaw sync` and `sync` can surface drift and the installer can
  * clean them up after the move to `.cclaw/rules/lang/`.
  */

package/dist/content/utility-skills.js

@@ -149,7 +149,7 @@ export const LANGUAGE_RULE_PACK_GENERATORS = {
     go: languageGoSkill
 };
 /**
- * Legacy per-language folders under `.cclaw/skills/` used in v0.7.0. Listed
+ * Older per-language folders under `.cclaw/skills/`. Listed
  * here so `cclaw sync` and `sync` can surface drift and the installer can
  * clean them up after the move to `.cclaw/rules/lang/`.
  */