cclaw-cli 7.7.1 → 8.1.1

package/dist/content/decision-protocol.d.ts

@@ -1,12 +1 @@
-/**
- * Shared wording blocks for Decision Protocol + structured ask fallback.
- *
- * Keep stage/utility prompt surfaces consistent and reduce wording drift.
- */
-export declare const STRUCTURED_ASK_TOOL_LIST_GENERIC = "`AskUserQuestion` / `AskQuestion` / `question` / `request_user_input`";
-export declare const STRUCTURED_ASK_TOOL_LIST_REVIEW = "`AskUserQuestion` on Claude, `AskQuestion` on Cursor, `question` on OpenCode with `permission.question: \"allow\"`, `request_user_input` on Codex in Plan/Collaboration mode";
-export declare const STRUCTURED_ASK_TOOL_LIST_IDEATE = "`AskUserQuestion` on Claude, `AskQuestion` on Cursor, `question` on OpenCode when `permission.question: \"allow\"` is set, `request_user_input` on Codex in Plan / Collaboration mode";
-export declare function structuredAskFallbackSentence(toolList?: string): string;
-export declare function decisionProtocolInstruction(subject: string, optionsClause: string, recommendationClause: string, toolList?: string): string;
-export declare function structuredAskSingleChoiceInstruction(subject: string, choicesClause: string, toolList?: string): string;
-export declare function ideaStructuredAskToolsWithFallback(): string;
+export declare const DECISION_PROTOCOL = "# Decision protocol (short form)\n\nA decision exists only when there is a real choice between at least two options. The full schema, FMT, and pre-mortem rules live in `lib/agents/architect.md`. This page covers only the question \"is this a decision at all?\"\n\n## What is not a decision\n\n- \"Use the library that is already in the project.\"\n- \"Match the existing pattern\" (unless two competing patterns exist).\n- \"Pick what the user asked for.\"\n\nIf you find yourself writing one of these, do not open a `D-N`. Capture the choice as a one-line note in `flows/<slug>/plan.md` if it is worth remembering at all.\n\n## What every D-N must carry\n\n`Context \u00B7 Considered options (>= 2) \u00B7 Selected \u00B7 Rationale \u00B7 Rejected because \u00B7 Consequences \u00B7 Refs`. Add **Failure Mode Table** + **Pre-mortem** for every product-grade or ideal tier decision (see architect.md).\n\n## Worked examples\n\nSee `lib/examples/decision-bm25-search.md`, `lib/examples/decision-permission-cache.md`, `lib/examples/decision-forward-only-migration.md`.\n\n## Refactoring decisions\n\nDecisions are immutable once shipped. To revisit:\n\n- in the active run, edit the existing `D-N` and append a \"Revised:\" subsection;\n- after ship, write a new `D-N` in the refining slug and reference the prior `D-N` in its Refs section.\n";

package/dist/content/decision-protocol.js

@@ -1,20 +1,27 @@
-/**
- * Shared wording blocks for Decision Protocol + structured ask fallback.
- *
- * Keep stage/utility prompt surfaces consistent and reduce wording drift.
- */
-export const STRUCTURED_ASK_TOOL_LIST_GENERIC = "\`AskUserQuestion\` / \`AskQuestion\` / \`question\` / \`request_user_input\`";
-export const STRUCTURED_ASK_TOOL_LIST_REVIEW = "\`AskUserQuestion\` on Claude, \`AskQuestion\` on Cursor, \`question\` on OpenCode with \`permission.question: \"allow\"\`, \`request_user_input\` on Codex in Plan/Collaboration mode";
-export const STRUCTURED_ASK_TOOL_LIST_IDEATE = "\`AskUserQuestion\` on Claude, \`AskQuestion\` on Cursor, \`question\` on OpenCode when \`permission.question: \"allow\"\` is set, \`request_user_input\` on Codex in Plan / Collaboration mode";
-export function structuredAskFallbackSentence(toolList = STRUCTURED_ASK_TOOL_LIST_GENERIC) {
-    return `If the harness's native structured-ask tool is available (${toolList}), send exactly ONE question per call, validate fields against the runtime schema, and on schema error immediately fall back to a plain-text lettered list instead of retrying guessed payloads.`;
-}
-export function decisionProtocolInstruction(subject, optionsClause, recommendationClause, toolList = STRUCTURED_ASK_TOOL_LIST_GENERIC) {
-    return `For ${subject}: use the Decision Protocol — ${optionsClause}. Do NOT use a numeric Completeness rubric; ${recommendationClause}. ${structuredAskFallbackSentence(toolList)}`;
-}
-export function structuredAskSingleChoiceInstruction(subject, choicesClause, toolList = STRUCTURED_ASK_TOOL_LIST_GENERIC) {
-    return `For ${subject}: use the native structured-ask tool (${toolList}) only if runtime schema is confirmed; otherwise collect ${choicesClause} with a plain-text single-choice prompt.`;
-}
-export function ideaStructuredAskToolsWithFallback() {
-    return `${STRUCTURED_ASK_TOOL_LIST_IDEATE}; fall back to a plain-text lettered list when the tool is hidden or errors`;
-}
+export const DECISION_PROTOCOL = `# Decision protocol (short form)
+
+A decision exists only when there is a real choice between at least two options. The full schema, FMT, and pre-mortem rules live in \`lib/agents/architect.md\`. This page covers only the question "is this a decision at all?"
+
+## What is not a decision
+
+- "Use the library that is already in the project."
+- "Match the existing pattern" (unless two competing patterns exist).
+- "Pick what the user asked for."
+
+If you find yourself writing one of these, do not open a \`D-N\`. Capture the choice as a one-line note in \`flows/<slug>/plan.md\` if it is worth remembering at all.
+
+## What every D-N must carry
+
+\`Context · Considered options (>= 2) · Selected · Rationale · Rejected because · Consequences · Refs\`. Add **Failure Mode Table** + **Pre-mortem** for every product-grade or ideal tier decision (see architect.md).
+
+## Worked examples
+
+See \`lib/examples/decision-bm25-search.md\`, \`lib/examples/decision-permission-cache.md\`, \`lib/examples/decision-forward-only-migration.md\`.
+
+## Refactoring decisions
+
+Decisions are immutable once shipped. To revisit:
+
+- in the active run, edit the existing \`D-N\` and append a "Revised:" subsection;
+- after ship, write a new \`D-N\` in the refining slug and reference the prior \`D-N\` in its Refs section.
+`;

package/dist/content/examples.d.ts

@@ -1,43 +1,9 @@
-import type { FlowStage } from "../types.js";
-/**
- * short bad → good behavior anchor per stage.
- *
- * Each entry is rendered exactly once in the corresponding stage skill md
- * (via `behaviorAnchorBlock` in `skills.ts`) and exactly once in the stage's
- * artifact template (via `renderBehaviorAnchorTemplateLine`). Anchors are
- * deliberately attached to a real artifact section name so the cross-check
- * test in `tests/unit/behavior-anchors.test.ts` can verify the section
- * exists in the stage's schema.
- *
- * Constraints enforced by the unit test:
- * - Exactly one entry per FlowStage (8 total).
- * - `bad` and `good` must be distinct across stages and ≤ 40 words each.
- * - `section` must match a section name present in
- *   `stageSchema(stage).artifactRules.artifactValidation`.
- */
-export interface BehaviorAnchor {
-    stage: FlowStage;
-    section: string;
-    bad: string;
-    good: string;
-    ruleHint?: string;
+export interface ExampleArtifact {
+    id: string;
+    fileName: string;
+    title: string;
+    description: string;
+    body: string;
 }
-export declare const BEHAVIOR_ANCHORS: ReadonlyArray<BehaviorAnchor>;
-export declare function behaviorAnchorFor(stage: FlowStage): BehaviorAnchor | null;
-/**
- * Render the one-line "Behavior anchor (bad → good)" pointer used at the top
- * of each artifact template (01..08). Templates carry the anchor inline so
- * agents see it before they start filling sections; the prose itself lives
- * only in `BEHAVIOR_ANCHORS` to avoid duplication.
- */
-export declare function renderBehaviorAnchorTemplateLine(stage: FlowStage): string;
-export declare function stageGoodBadExamples(stage: FlowStage): string;
-/**
- * Returns the full example artifact body for tests and internal quality checks.
- * Generated user projects keep only short inline shape cues.
- */
-export declare function stageFullArtifactExampleMarkdown(stage: FlowStage): string | null;
-/**
- * Returns short inline shape cues rendered directly inside the stage skill.
- */
-export declare function stageExamples(stage: FlowStage): string;
+export declare const EXAMPLES: ExampleArtifact[];
+export declare const EXAMPLES_INDEX: string;