cclaw-cli 7.7.1 → 8.1.0

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

@@ -0,0 +1,2 @@
+export declare const IDEA_COMMAND_BODY = "# /cc-idea \u2014 capture an idea outside of any active flow\n\nThis command does **not** participate in plan/build/review/ship. Its only job is to drop a half-formed idea into the backlog without spinning up a full flow.\n\n## Behaviour\n\n1. Open `.cclaw/ideas.md`. If it does not exist, seed it from `.cclaw/lib/templates/ideas.md`.\n2. Append a new entry with this shape:\n\n   ```\n   ## YYYY-MM-DDTHH:MM:SSZ \u2014 <one-line summary>\n\n   <short paragraph or bullet list with the idea body>\n   ```\n\n3. Save the file. Do not slugify, do not create artifacts under `.cclaw/flows/<slug>/`, do not modify `flow-state.json`, do not invoke specialists.\n\n## Hard rules\n\n- One entry per invocation. If the user pastes multiple ideas, ask whether to file them as one entry or several.\n- Never auto-promote an idea to a plan. Promotion happens only when the user explicitly invokes `/cc <task>`.\n- Never delete or edit prior ideas inside `/cc-idea`. Trimming the backlog is a separate manual step.\n\n## Suggested entry shape\n\n```\n## 2026-05-07T19:30:12Z \u2014 switch knowledge.jsonl to ndjson\n\nRight now `.cclaw/knowledge.jsonl` is one JSON object per line, but tooling\nexpects RFC 8259-compliant NDJSON. Worth verifying once the tooling adopts\nthe standard formally.\n```\n\nThe orchestrator surfaces ideas back to the user only when an explicit `/cc` invocation references them; otherwise they stay quiet.\n";
+export declare function renderIdeaCommand(): string;

package/dist/content/idea-command.js

@@ -0,0 +1,38 @@
+export const IDEA_COMMAND_BODY = `# /cc-idea — capture an idea outside of any active flow
+
+This command does **not** participate in plan/build/review/ship. Its only job is to drop a half-formed idea into the backlog without spinning up a full flow.
+
+## Behaviour
+
+1. Open \`.cclaw/ideas.md\`. If it does not exist, seed it from \`.cclaw/lib/templates/ideas.md\`.
+2. Append a new entry with this shape:
+
+   \`\`\`
+   ## YYYY-MM-DDTHH:MM:SSZ — <one-line summary>
+
+   <short paragraph or bullet list with the idea body>
+   \`\`\`
+
+3. Save the file. Do not slugify, do not create artifacts under \`.cclaw/flows/<slug>/\`, do not modify \`flow-state.json\`, do not invoke specialists.
+
+## Hard rules
+
+- One entry per invocation. If the user pastes multiple ideas, ask whether to file them as one entry or several.
+- Never auto-promote an idea to a plan. Promotion happens only when the user explicitly invokes \`/cc <task>\`.
+- Never delete or edit prior ideas inside \`/cc-idea\`. Trimming the backlog is a separate manual step.
+
+## Suggested entry shape
+
+\`\`\`
+## 2026-05-07T19:30:12Z — switch knowledge.jsonl to ndjson
+
+Right now \`.cclaw/knowledge.jsonl\` is one JSON object per line, but tooling
+expects RFC 8259-compliant NDJSON. Worth verifying once the tooling adopts
+the standard formally.
+\`\`\`
+
+The orchestrator surfaces ideas back to the user only when an explicit \`/cc\` invocation references them; otherwise they stay quiet.
+`;
+export function renderIdeaCommand() {
+    return IDEA_COMMAND_BODY;
+}

package/dist/content/iron-laws.d.ts

@@ -1,141 +1,7 @@
-import type { FlowStage } from "../types.js";
-export type IronLawEnforcementPoint = "PreToolUse" | "PostToolUse" | "SessionStart" | "Stop" | "advisory";
-export type IronLawSeverity = "hard-gate" | "soft-gate";
-export interface IronLawDefinition {
+export interface IronLaw {
     id: string;
     title: string;
-    rule: string;
-    rationale: string;
-    enforcement: IronLawEnforcementPoint;
-    severity: IronLawSeverity;
-    appliesTo: "all" | FlowStage[];
-    hookMatcher?: {
-        toolPattern?: string;
-        payloadPattern?: string;
-    };
+    description: string;
 }
-export interface IronLawRuntimeRecord {
-    id: string;
-    title: string;
-    rule: string;
-    enforcement: IronLawEnforcementPoint;
-    severity: IronLawSeverity;
-    appliesTo: "all" | FlowStage[];
-    strict: boolean;
-    hookMatcher?: {
-        toolPattern?: string;
-        payloadPattern?: string;
-    };
-}
-export interface IronLawRuntimeDocument {
-    version: 1;
-    generatedAt: string;
-    mode: "advisory" | "strict";
-    strictLaws: string[];
-    laws: IronLawRuntimeRecord[];
-}
-export declare const IRON_LAWS: readonly [{
-    readonly id: "tdd-red-before-write";
-    readonly title: "RED before production write";
-    readonly rule: "Do not edit production code in tdd stage before a failing RED test exists for the slice.";
-    readonly rationale: "Prevents implementation-first behavior and keeps RED as executable specification.";
-    readonly enforcement: "PreToolUse";
-    readonly severity: "hard-gate";
-    readonly appliesTo: ["tdd"];
-    readonly hookMatcher: {
-        readonly toolPattern: "write|edit|multiedit|applypatch|shell|bash";
-        readonly payloadPattern: "\\.(ts|tsx|js|jsx|py|go|java|rs|rb|php|c|cc|cpp|h|hpp)";
-    };
-}, {
-    readonly id: "plan-requires-approval";
-    readonly title: "No implementation before plan approval";
-    readonly rule: "Do not perform write-like actions while plan stage is pending WAIT_FOR_CONFIRM approval.";
-    readonly rationale: "Locks intent before execution and reduces expensive rework from unapproved paths.";
-    readonly enforcement: "PreToolUse";
-    readonly severity: "hard-gate";
-    readonly appliesTo: ["plan"];
-}, {
-    readonly id: "runtime-writes-managed-only";
-    readonly title: "Runtime writes are managed";
-    readonly rule: "Do not mutate .cclaw/state, .cclaw/hooks, or .cclaw/skills by ad-hoc edits unless using cclaw-managed commands.";
-    readonly rationale: "Protects generated runtime integrity and avoids drift that silently breaks hooks or skills.";
-    readonly enforcement: "PreToolUse";
-    readonly severity: "hard-gate";
-    readonly appliesTo: "all";
-    readonly hookMatcher: {
-        readonly toolPattern: "write|edit|multiedit|delete|applypatch|shell|bash";
-        readonly payloadPattern: "\\.cclaw/(state|hooks|skills)";
-    };
-}, {
-    readonly id: "flow-state-read-fresh";
-    readonly title: "Fresh flow-state read required";
-    readonly rule: "Before mutating actions, a fresh read of .cclaw/state/flow-state.json must exist within guard freshness window.";
-    readonly rationale: "Prevents stale-stage mutations after context shifts or multi-agent divergence.";
-    readonly enforcement: "PreToolUse";
-    readonly severity: "hard-gate";
-    readonly appliesTo: "all";
-}, {
-    readonly id: "review-layer-order";
-    readonly title: "Review layers are sequential";
-    readonly rule: "Review stage must complete Layer 1 spec compliance before Layer 2 quality/security passes.";
-    readonly rationale: "Stops premature quality discussion when acceptance criteria are not yet satisfied.";
-    readonly enforcement: "PreToolUse";
-    readonly severity: "hard-gate";
-    readonly appliesTo: ["review"];
-}, {
-    readonly id: "review-criticals-close-before-ship";
-    readonly title: "No ship with open criticals";
-    readonly rule: "Ship decisions are blocked when review-army contains open Critical findings or ship blockers.";
-    readonly rationale: "Enforces explicit risk closure before release finalization.";
-    readonly enforcement: "PreToolUse";
-    readonly severity: "hard-gate";
-    readonly appliesTo: ["ship"];
-}, {
-    readonly id: "ship-preflight-required";
-    readonly title: "Preflight required before finalization";
-    readonly rule: "Do not execute release finalization actions until ship preflight gate is passed.";
-    readonly rationale: "Catches regressions before irreversible release steps.";
-    readonly enforcement: "PreToolUse";
-    readonly severity: "hard-gate";
-    readonly appliesTo: ["ship"];
-}, {
-    readonly id: "review-coverage-complete-before-ship";
-    readonly title: "Review layer coverage before ship";
-    readonly rule: "Block ship finalization when review-army does not confirm full Layer 1/2 coverage map.";
-    readonly rationale: "Prevents finalization when multi-pass review evidence is incomplete or partially missing.";
-    readonly enforcement: "PreToolUse";
-    readonly severity: "hard-gate";
-    readonly appliesTo: ["ship"];
-}, {
-    readonly id: "subagent-task-self-contained";
-    readonly title: "Subagent tasks are self-contained";
-    readonly rule: "Delegated tasks must include explicit objective, constraints, and expected output, not just references.";
-    readonly rationale: "Avoids context loss and low-quality delegation in isolated worker contexts.";
-    readonly enforcement: "advisory";
-    readonly severity: "soft-gate";
-    readonly appliesTo: "all";
-}, {
-    readonly id: "no-secrets-in-artifacts";
-    readonly title: "Never log secrets in artifacts";
-    readonly rule: "Secrets/tokens/passwords must not be written to review, ship, or runtime state artifacts.";
-    readonly rationale: "Prevents accidental credential leakage through generated workflow artifacts.";
-    readonly enforcement: "PostToolUse";
-    readonly severity: "hard-gate";
-    readonly appliesTo: "all";
-}, {
-    readonly id: "stop-clean-or-handoff";
-    readonly title: "Stop only from clean handoff";
-    readonly rule: "Do not end a session with dirty state unless the current artifact records unresolved work and blockers.";
-    readonly rationale: "Protects continuity and prevents silent half-finished sessions.";
-    readonly enforcement: "Stop";
-    readonly severity: "hard-gate";
-    readonly appliesTo: "all";
-}];
-export declare function isIronLawId(value: string): boolean;
-export declare function normalizeStrictLawIds(ids: string[] | undefined): string[];
-export declare function ironLawRuntimeDocument(options?: {
-    mode?: "advisory" | "strict";
-    strictLaws?: string[];
-    nowIso?: string;
-}): IronLawRuntimeDocument;
-export declare function ironLawsSkillMarkdown(): string;
+export declare const IRON_LAWS: IronLaw[];
+export declare function ironLawsMarkdown(): string;

package/dist/content/iron-laws.js

@@ -1,210 +1,31 @@
-import { RUNTIME_ROOT } from "../constants.js";
 export const IRON_LAWS = [
     {
-        id: "tdd-red-before-write",
-        title: "RED before production write",
-        rule: "Do not edit production code in tdd stage before a failing RED test exists for the slice.",
-        rationale: "Prevents implementation-first behavior and keeps RED as executable specification.",
-        enforcement: "PreToolUse",
-        severity: "hard-gate",
-        appliesTo: ["tdd"],
-        hookMatcher: {
-            toolPattern: "write|edit|multiedit|applypatch|shell|bash",
-            payloadPattern: "\\.(ts|tsx|js|jsx|py|go|java|rs|rb|php|c|cc|cpp|h|hpp)"
-        }
+        id: "think-before-coding",
+        title: "Think Before Coding",
+        description: "Read enough of the codebase to write the change correctly the first time. Skipping the read step is the most common cause of cascading errors and hallucinated actions."
     },
     {
-        id: "plan-requires-approval",
-        title: "No implementation before plan approval",
-        rule: "Do not perform write-like actions while plan stage is pending WAIT_FOR_CONFIRM approval.",
-        rationale: "Locks intent before execution and reduces expensive rework from unapproved paths.",
-        enforcement: "PreToolUse",
-        severity: "hard-gate",
-        appliesTo: ["plan"]
+        id: "simplicity-first",
+        title: "Simplicity First",
+        description: "Pick the smallest design that satisfies the acceptance criteria. Resist abstractions, configuration knobs, and indirection that no AC asks for."
     },
     {
-        id: "runtime-writes-managed-only",
-        title: "Runtime writes are managed",
-        rule: `Do not mutate ${RUNTIME_ROOT}/state, ${RUNTIME_ROOT}/hooks, or ${RUNTIME_ROOT}/skills by ad-hoc edits unless using cclaw-managed commands.`,
-        rationale: "Protects generated runtime integrity and avoids drift that silently breaks hooks or skills.",
-        enforcement: "PreToolUse",
-        severity: "hard-gate",
-        appliesTo: "all",
-        hookMatcher: {
-            toolPattern: "write|edit|multiedit|delete|applypatch|shell|bash",
-            payloadPattern: "\\.cclaw/(state|hooks|skills)"
-        }
+        id: "surgical-changes",
+        title: "Surgical Changes",
+        description: "Touch only what each AC requires. If a change starts pulling in unrelated files, stop and split the task — scope creep is one of the five review failure modes."
     },
     {
-        id: "flow-state-read-fresh",
-        title: "Fresh flow-state read required",
-        rule: `Before mutating actions, a fresh read of ${RUNTIME_ROOT}/state/flow-state.json must exist within guard freshness window.`,
-        rationale: "Prevents stale-stage mutations after context shifts or multi-agent divergence.",
-        enforcement: "PreToolUse",
-        severity: "hard-gate",
-        appliesTo: "all"
+        id: "goal-driven-execution",
+        title: "Goal-Driven Execution",
+        description: "Every action must move a specific AC closer to committed status. If the action does not, do not run it; record the question for the user."
     },
     {
-        id: "review-layer-order",
-        title: "Review layers are sequential",
-        rule: "Review stage must complete Layer 1 spec compliance before Layer 2 quality/security passes.",
-        rationale: "Stops premature quality discussion when acceptance criteria are not yet satisfied.",
-        enforcement: "PreToolUse",
-        severity: "hard-gate",
-        appliesTo: ["review"]
-    },
-    {
-        id: "review-criticals-close-before-ship",
-        title: "No ship with open criticals",
-        rule: "Ship decisions are blocked when review-army contains open Critical findings or ship blockers.",
-        rationale: "Enforces explicit risk closure before release finalization.",
-        enforcement: "PreToolUse",
-        severity: "hard-gate",
-        appliesTo: ["ship"]
-    },
-    {
-        id: "ship-preflight-required",
-        title: "Preflight required before finalization",
-        rule: "Do not execute release finalization actions until ship preflight gate is passed.",
-        rationale: "Catches regressions before irreversible release steps.",
-        enforcement: "PreToolUse",
-        severity: "hard-gate",
-        appliesTo: ["ship"]
-    },
-    {
-        id: "review-coverage-complete-before-ship",
-        title: "Review layer coverage before ship",
-        rule: "Block ship finalization when review-army does not confirm full Layer 1/2 coverage map.",
-        rationale: "Prevents finalization when multi-pass review evidence is incomplete or partially missing.",
-        enforcement: "PreToolUse",
-        severity: "hard-gate",
-        appliesTo: ["ship"]
-    },
-    {
-        id: "subagent-task-self-contained",
-        title: "Subagent tasks are self-contained",
-        rule: "Delegated tasks must include explicit objective, constraints, and expected output, not just references.",
-        rationale: "Avoids context loss and low-quality delegation in isolated worker contexts.",
-        enforcement: "advisory",
-        severity: "soft-gate",
-        appliesTo: "all"
-    },
-    {
-        id: "no-secrets-in-artifacts",
-        title: "Never log secrets in artifacts",
-        rule: "Secrets/tokens/passwords must not be written to review, ship, or runtime state artifacts.",
-        rationale: "Prevents accidental credential leakage through generated workflow artifacts.",
-        enforcement: "PostToolUse",
-        severity: "hard-gate",
-        appliesTo: "all"
-    },
-    {
-        id: "stop-clean-or-handoff",
-        title: "Stop only from clean handoff",
-        rule: "Do not end a session with dirty state unless the current artifact records unresolved work and blockers.",
-        rationale: "Protects continuity and prevents silent half-finished sessions.",
-        enforcement: "Stop",
-        severity: "hard-gate",
-        appliesTo: "all"
+        id: "red-before-green",
+        title: "No Production Code Without a Failing Test First",
+        description: "Build is a TDD cycle. Every AC starts with a failing test (RED), then the minimal implementation that makes it pass (GREEN), then the refactor that keeps it passing (REFACTOR). The RED failure is the spec; never write production code before it exists."
     }
 ];
-export function isIronLawId(value) {
-    return IRON_LAWS.some((law) => law.id === value);
-}
-export function normalizeStrictLawIds(ids) {
-    if (!Array.isArray(ids))
-        return [];
-    const unique = new Set();
-    for (const id of ids) {
-        if (typeof id !== "string")
-            continue;
-        const trimmed = id.trim();
-        if (!trimmed || !isIronLawId(trimmed))
-            continue;
-        unique.add(trimmed);
-    }
-    return [...unique];
-}
-export function ironLawRuntimeDocument(options = {}) {
-    const mode = options.mode === "strict" ? "strict" : "advisory";
-    const strictLawSet = new Set(normalizeStrictLawIds(options.strictLaws));
-    const laws = IRON_LAWS.map((law) => ({
-        id: law.id,
-        title: law.title,
-        rule: law.rule,
-        enforcement: law.enforcement,
-        severity: law.severity,
-        appliesTo: law.appliesTo === "all" ? "all" : [...law.appliesTo],
-        strict: mode === "strict" || strictLawSet.has(law.id),
-        hookMatcher: "hookMatcher" in law ? law.hookMatcher : undefined
-    }));
-    return {
-        version: 1,
-        generatedAt: options.nowIso ?? new Date().toISOString(),
-        mode,
-        strictLaws: [...strictLawSet],
-        laws
-    };
-}
-function appliesToLabel(law) {
-    return law.appliesTo === "all" ? "all stages" : law.appliesTo.join(", ");
-}
-function hardGateReference(law) {
-    if (law.appliesTo === "all") {
-        return "the active stage `HARD-GATE` block in `.cclaw/skills/<stage>/SKILL.md`";
-    }
-    return law.appliesTo
-        .map((stage) => `\`${RUNTIME_ROOT}/skills/${stage}/SKILL.md\` (${stage} HARD-GATE)`)
-        .join(", ");
-}
-export function ironLawsSkillMarkdown() {
-    // Phase A purged the `PreToolUse` / `PostToolUse` / pre-tool
-    // pipeline handlers, so `review-coverage-complete-before-ship` is no
-    // longer hook-enforced — it now lives in the ship stage HARD-GATE.
-    // Only `stop-clean-or-handoff` (Stop hook) is still hook-enforced;
-    // everything else is stage-owned advisory.
-    const enforcedLawIds = new Set([
-        "stop-clean-or-handoff"
-    ]);
-    const enforced = IRON_LAWS.filter((law) => enforcedLawIds.has(law.id));
-    const advisory = IRON_LAWS.filter((law) => !enforcedLawIds.has(law.id));
-    const enforcedSections = enforced.map((law, index) => {
-        return `### ${index + 1}. ${law.title}
-
-- **ID:** \`${law.id}\`
-- **Rule:** ${law.rule}
-- **Why:** ${law.rationale}
-- **Applies to:** ${appliesToLabel(law)}
-- **Enforced by:** ${law.enforcement} (${law.severity})
-`;
-    }).join("\n");
-    const advisoryList = advisory
-        .map((law) => `- \`${law.id}\` — applies to ${appliesToLabel(law)}; see ${hardGateReference(law)}.`)
-        .join("\n");
-    return `---
-name: iron-laws
-description: "Non-negotiable workflow constraints enforced by cclaw hooks and routing."
----
-
-# Iron Laws
-
-These are cclaw's non-negotiable constraints for harness sessions.  
-Use them as the final arbitration layer when local instructions conflict.
-
-## Hook-Enforced Runtime Laws
-
-${enforcedSections}
-
-## Advisory Laws (Stage-Owned)
-
-The following laws remain active guidance, but their canonical enforcement surface
-is each stage's \`HARD-GATE\` contract:
-
-${advisoryList}
-
-## Practical rule
-
-If a law says stop, stop and surface the blocking reason with the smallest safe
-next step.
-`;
+export function ironLawsMarkdown() {
+    const sections = IRON_LAWS.map((law, index) => `${index + 1}. **${law.title}** — ${law.description}`).join("\n");
+    return `## Iron Laws (Karpathy)\n\n${sections}\n`;
 }

package/dist/content/meta-skill.d.ts

@@ -1,3 +1 @@
-export declare const META_SKILL_NAME = "using-cclaw";
-export declare const META_SKILL_GENERATED_HELPER_SKILLS: readonly ["subagent-dev", "parallel-dispatch", "session", "iron-laws"];
-export declare function usingCclawSkillMarkdown(): string;
+export declare const META_SKILL = "---\nname: cclaw-meta\ntrigger: always-on; loaded with every /cc invocation\n---\n\n# Meta-skill \u2014 how to be a cclaw orchestrator\n\nThis skill is loaded by the harness with every `/cc` invocation. It does not duplicate `/cc` itself; it tells you **how to use** the rest of cclaw's content.\n\n## What is in your context\n\nWhen `/cc` runs, the harness has access to:\n\n- `.cursor/commands/cc.md` \u2014 your operating manual (also in `.cursor/skills/cclaw/` mirrors).\n- `.cclaw/lib/agents/*.md` \u2014 six specialist prompts.\n- `.cclaw/lib/skills/*.md` \u2014 six auto-trigger skills.\n- `.cclaw/lib/templates/*.md` \u2014 ten artifact templates.\n- `.cclaw/lib/runbooks/*.md` \u2014 four stage runbooks.\n- `.cclaw/lib/patterns/*.md` \u2014 eight task patterns.\n- `.cclaw/lib/research/*.md` \u2014 five research playbooks.\n- `.cclaw/lib/recovery/*.md` \u2014 five recovery playbooks.\n- `.cclaw/lib/decision-protocol.md` \u2014 D-N record format.\n- `.cclaw/lib/examples/*.md` \u2014 thirteen worked examples.\n- `.cclaw/lib/antipatterns.md` \u2014 twelve known failure modes.\n\n## How to read this content efficiently\n\nYou do not need to read everything. The right loading pattern:\n\n1. **Always read `/cc`** \u2014 your operating manual.\n2. **Read the runbook** for the stage you are in (`.cclaw/lib/runbooks/<stage>.md`).\n3. **Read the pattern(s)** that match the task (`.cclaw/lib/patterns/`).\n4. **Read the specialist prompt** when you invoke a specialist (`.cclaw/lib/agents/<id>.md`).\n5. **Read the recovery playbook** when an automated check fails.\n6. **Read examples** when authoring an artifact you have not seen before.\n\nDon't read research playbooks unless you're invoking planner mode=`research`. Don't read antipatterns proactively; the reviewer cites them as findings.\n\n## Your responsibilities as orchestrator\n\n1. **Sanity check first.** Always verify `flow-state.json` schemaVersion=2 before doing anything.\n2. **Detect existing plans.** Always run existing-plan detection before authoring a new plan.\n3. **Calibrate routing.** Always run Phase 0 calibration; never skip to specialists for a trivial task.\n4. **Ask before invoking specialists.** Never silently invoke. The user picks.\n5. **Ask before push / PR.** Always; every time; per turn.\n6. **Surface, don't decide.** When a checkpoint, conflict, or cap-reached situation appears, present options to the user. Do not decide on their behalf.\n7. **Cite, don't invent.** Every file:line reference in your output must be real. Reviewer adversarial mode will catch you.\n\n## Your boundaries\n\n- You do not write code. `slice-builder` does.\n- You do not author decisions alone. `architect` does.\n- You do not enforce AC traceability. `commit-helper.mjs` does.\n- You do not delete artifacts. `/cc-cancel` does.\n- You do not push or open PRs without explicit user approval.\n\n## Iron laws (always-on)\n\n1. **Think before coding.** Read the targets first. Cite `file:line`.\n2. **Simplicity first.** The smallest correct change wins.\n3. **Surgical changes.** Touch only declared files.\n4. **Goal-driven execution.** AC are the contract; everything else is implementation detail.\n\n## Five failure modes (always-on)\n\nWhen in doubt, ask: am I about to commit one of these?\n\n1. Hallucinated actions (invented files / ids / flags).\n2. Scope creep (changes outside declared AC).\n3. Cascading errors (fix breaks something else).\n4. Context loss (forgot earlier decision).\n5. Tool misuse (wrong mode / destructive action).\n\nIf yes, stop and surface.\n\n## When the user pushes back\n\nTrust the user's calibration. If they say \"this feels weak\", they are not asking for reassurance \u2014 they are asking for more depth. Open more content (patterns, examples, recovery), broaden the AC set, invoke the missing specialist. Do not defend the current state.\n\nIf they say \"this feels overcomplicated\", they are asking for less. Skip specialists, shorten Context, drop optional sections. Trivial tasks should not run the full chain.\n";