@bendyline/gilde 0.1.49 → 0.1.51

package/data/craftbook-templates/co/content-deck/versions/1.2.2/craftbook.json

@@ -0,0 +1,217 @@
+{
+  "id": "content-deck",
+  "name": "Slide Deck from Content",
+  "description": "Turn a body of source content into a presentation deck. Outlines the narrative first, designs a consistent slide look, then builds the deck (HTML slides), evaluating for narrative flow and visual consistency.\n\nA gallery craftbook generated from an archetype spec. It runs\n`phase → (per-phase gate) → … → evaluate → (loop) → finish`. Each build\nphase that produces a checkable artifact is followed by a **runtime\ngate-checkpoint** — the runtime verifies the artifact and routes with no\nmodel turn, looping back to redo the phase on a miss. The final `evaluate`\nstep holds a static deliverable gate plus a reviewer QA pass. What it adds\nover the generic `build-loop`: a specialist role per phase, a\ndomain-correct ordering, and a concrete per-phase quality bar.\n\nDeliverables marked \"artifact\" land in the project's artifacts drawer (`write_artifact` / `read_artifact`), not the shipped workspace — review output is not product source.\n\nPhases:\n\n1. Outline the deck (planner) — narrative arc + per-slide bullets from the source → gated on artifact `deck/outline.md` (markdown-notes)\n2. Slide design (designer) — a consistent slide template + palette → gated on artifact `deck/design-system.md` (markdown-notes)\n3. Build the deck (developer) — generate the slides to the template → gated on `index.html` (slide-deck)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "outline",
+  "triggers": [
+    "slide deck",
+    "powerpoint",
+    "presentation",
+    "build a deck"
+  ],
+  "steps": [
+    {
+      "id": "outline",
+      "name": "Outline the deck",
+      "description": "narrative arc + per-slide bullets from the source",
+      "prompt": "Read every supplied source file with workspace `read_file` before outlining. Build a source-grounded deck plan: a title slide, a clear narrative arc, 5-7 content slides with one idea and 2-4 bullets each, and a takeaways/CTA ending. Attach a source filename or source heading to every factual claim. Write an **acceptance-criteria checklist** (\"opens with a title slide\", \"one idea per slide\", \"ends with takeaways/CTA\", \"every claim traces to the source\"). Save the outline + checklist to artifact `{{workPath}}/outline.md` with `write_artifact`; note the path in task notes.",
+      "suggestedRole": "planner",
+      "advanceWhen": {
+        "file": "{{workPath}}/outline.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/outline.md",
+            "bytes": 700,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/outline.md",
+            "sniff": "nonempty",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/outline.md",
+            "pattern": "title slide|slide 1",
+            "flags": "i",
+            "label": "title slide",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/outline.md",
+            "pattern": "takeaway|CTA|call.to.action|recommendation",
+            "flags": "i",
+            "label": "closing slide",
+            "artifact": true
+          }
+        ],
+        "onReject": "outline",
+        "maxAttempts": 3
+      },
+      "next": "slide-design"
+    },
+    {
+      "id": "slide-design",
+      "name": "Slide design",
+      "description": "a consistent slide template + palette",
+      "prompt": "Read artifact `{{workPath}}/outline.md` with `read_artifact`. Design one reusable slide system: title position, body/grid layout, exact palette, type scale, spacing, progress affordance, and focused/inactive slide states. Include desktop and narrow-screen behavior plus keyboard/button navigation treatment. Consistency matters more than flourish. Save the template spec to artifact `{{workPath}}/design-system.md` with `write_artifact`; note the path in task notes. No slide content yet.",
+      "suggestedRole": "designer",
+      "consumes": [
+        {
+          "file": "deck/outline.md",
+          "artifact": true
+        }
+      ],
+      "advanceWhen": {
+        "file": "{{workPath}}/design-system.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/design-system.md",
+            "bytes": 500,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/design-system.md",
+            "sniff": "nonempty",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/design-system.md",
+            "pattern": "#[0-9a-f]{3,8}|rgb\\(|hsl\\(",
+            "flags": "i",
+            "label": "concrete palette",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/design-system.md",
+            "pattern": "keyboard|arrow|previous|next|navigation",
+            "flags": "i",
+            "label": "navigation treatment",
+            "artifact": true
+          }
+        ],
+        "onReject": "slide-design",
+        "maxAttempts": 3
+      },
+      "next": "build"
+    },
+    {
+      "id": "build",
+      "name": "Build the deck",
+      "description": "generate the slides to the template",
+      "prompt": "Read artifacts `{{workPath}}/outline.md` and `{{workPath}}/design-system.md` with `read_artifact`. Build the deck in workspace `index.html` with `write_file`: one semantic section per slide, inline CSS/JS, visible slide count/progress, previous/next controls, and ArrowLeft/ArrowRight keyboard navigation. Apply the template uniformly and use only claims in the outline/source. Keep it self-contained with no external assets. On a loop-back, fix only the named gaps. `write_task_note` the workspace path and slide count.",
+      "suggestedRole": "developer",
+      "consumes": [
+        {
+          "file": "deck/outline.md",
+          "artifact": true
+        },
+        {
+          "file": "deck/design-system.md",
+          "artifact": true
+        }
+      ],
+      "advanceWhen": {
+        "file": "index.html",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "index.html",
+            "bytes": 3600
+          },
+          {
+            "kind": "htmlLint",
+            "file": "index.html"
+          },
+          {
+            "kind": "cssMinBytes",
+            "bytes": 700,
+            "file": "index.html"
+          },
+          {
+            "kind": "jsParses",
+            "file": "index.html"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "ArrowLeft|ArrowRight|keydown",
+            "label": "keyboard navigation"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkContains",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html",
+              "pattern": "(?:slide|section|^---$)",
+              "flags": "im"
+            }
+          }
+        ],
+        "onReject": "build",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Read workspace `index.html` with `read_file` and artifacts `{{workPath}}/outline.md` and `{{workPath}}/design-system.md` with `read_artifact`. Check narrative flow (title opening, one idea per slide, takeaways ending), visual consistency, source fidelity, and both button and keyboard navigation. Render and exercise it if browser QA is available; otherwise trace the event handlers. Write PASS/FAIL per criterion.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"build\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "consumes": [
+        {
+          "file": "index.html"
+        }
+      ],
+      "next": "build"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
+      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
+      "suggestedRole": "developer",
+      "terminal": true
+    }
+  ],
+  "version": "1.2.2",
+  "releasedAt": "2026-08-14T00:00:00Z",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer for this run's intermediate files. Defaults to this task's own folder so concurrent runs never overwrite each other; override with a stable name only when runs should deliberately share working files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  }
+}

package/data/craftbook-templates/co/content-deck/versions/1.2.2/test.json

@@ -0,0 +1,169 @@
+{
+  "schemaVersion": 1,
+  "title": "Source-grounded HTML slide-deck workflow",
+  "objective": "Run the Slide Deck from Content craftbook and verify a source-cited outline and explicit design system precede a complete navigable HTML deck.",
+  "tags": [
+    "html-page",
+    "workflow"
+  ],
+  "prompt": "Use the Slide Deck from Content craftbook. Read workspace `source/field-notes.md`, then build workspace `index.html` for an operations leadership review. The deck needs a title slide, 5-7 content slides, a takeaways/CTA slide, consistent visual treatment, source-grounded claims, visible progress, previous/next controls, and ArrowLeft/ArrowRight navigation. Vanilla HTML/CSS/JS only, with no external assets or build step.",
+  "setup": {
+    "projectName": "Content Deck Eval",
+    "about": "Self-contained workflow eval for the Slide Deck from Content craftbook. Source notes are in the workspace, outline/design deliverables belong in artifacts, and the final deck belongs at workspace/index.html.",
+    "missionObjectives": "Turn the seeded field notes into a concise, source-grounded, navigable HTML slide deck with a locked slide design and reliable keyboard/button navigation.",
+    "files": [
+      {
+        "path": "source/field-notes.md",
+        "content": "# Field Notes: Returns Desk Pilot\n\nAudience: operations leadership deciding whether to expand the pilot.\n\n## Context\n- Harbor & Finch ships home-office accessories through three regional warehouses.\n- A March returns-desk pilot used guided intake forms, photo evidence, and a triage queue.\n- The goal was to cut preventable refunds without frustrating customers.\n\n## Results\n- Median first response improved from 18 hours to 6 hours.\n- Refund leakage fell from 14.2% to 8.9% on pilot SKUs.\n- Support escalations dropped 21% after agents received recommended resolution scripts.\n- Customers still complained about status silence after photo submission.\n\n## Risks\n- Warehouse teams need barcode exception training before national rollout.\n- Finance wants weekly exception exports before approving automation.\n- The photo review queue can exceed SLA on Monday mornings.\n\n## Recommendation\nExpand to the West warehouse for 30 days, add automated status emails, and hold national rollout until exception exports are reliable.\n"
+      }
+    ],
+    "worker": {
+      "name": "Sanne",
+      "role": "Developer"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "A craftbook task produces source-grounded outline/design artifacts and a complete navigable workspace/index.html deck.",
+    "deliverables": [
+      {
+        "path": "index.html",
+        "kind": "slide-deck",
+        "minBytes": 3600,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 700,
+            "file": "index.html"
+          },
+          {
+            "kind": "jsParses",
+            "file": "index.html"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "Returns Desk Pilot",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "18\\s*hours[\\s\\S]*6\\s*hours|6\\s*hours[\\s\\S]*18\\s*hours"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "14\\.2%[\\s\\S]*8\\.9%|8\\.9%[\\s\\S]*14\\.2%"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "takeaways|recommendation|CTA",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "previous|prev[\\s\\S]*next|next[\\s\\S]*(?:previous|prev)",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "ArrowLeft|ArrowRight|keydown"
+          }
+        ]
+      }
+    ],
+    "checks": [
+      {
+        "kind": "minBytes",
+        "file": "deck/outline.md",
+        "bytes": 700,
+        "artifact": true
+      },
+      {
+        "kind": "contains",
+        "file": "deck/outline.md",
+        "pattern": "(?:title slide|slide 1)[\\s\\S]*(?:takeaway|recommendation|CTA)",
+        "flags": "i",
+        "artifact": true
+      },
+      {
+        "kind": "minBytes",
+        "file": "deck/design-system.md",
+        "bytes": 500,
+        "artifact": true
+      },
+      {
+        "kind": "contains",
+        "file": "deck/design-system.md",
+        "pattern": "#[0-9a-f]{3,8}[\\s\\S]*(?:keyboard|arrow|navigation)",
+        "flags": "i",
+        "artifact": true
+      }
+    ],
+    "taskNotes": {
+      "minBytes": 160,
+      "checks": [
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "outline\\.md",
+          "flags": "i"
+        },
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "design-system\\.md",
+          "flags": "i"
+        },
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "index\\.html",
+          "flags": "i"
+        }
+      ],
+      "requireCraftbookTask": true
+    },
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    },
+    "unchangedFixtures": [
+      "source/field-notes.md"
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "index.html",
+      "kind": "html"
+    },
+    "axes": [
+      {
+        "name": "narrative",
+        "description": "The deck has a deliberate source-grounded arc with one clear idea per slide and a decision-oriented close."
+      },
+      {
+        "name": "design consistency",
+        "description": "Slides visibly share the locked palette, type scale, spacing, and active/inactive state treatment."
+      },
+      {
+        "name": "navigation",
+        "description": "Buttons, progress, and keyboard controls make the complete deck reliably traversable."
+      },
+      {
+        "name": "workflow evidence",
+        "description": "The outline and design artifacts are substantive and agree with the final rendered deck."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "craftbook attribution",
+    "source-first outline",
+    "artifact-to-workspace handoff",
+    "keyboard and button navigation"
+  ]
+}

package/data/craftbook-templates/co/contract-template/versions/1.0.2/test.json

@@ -19,9 +19,6 @@
     "worker": {
       "name": "Lotte",
       "role": "Document Drafter"
-    },
-    "craftbookParams": {
-      "workPath": "tasks/eval"
     }
   },
   "mocks": [],

package/data/craftbook-templates/co/cookbook-layout/versions/1.0.2/test.json

@@ -51,9 +51,6 @@
     "worker": {
       "name": "Ria",
       "role": "Designer"
-    },
-    "craftbookParams": {
-      "workPath": "tasks/eval"
     }
   },
   "mocks": [],

package/data/craftbook-templates/co/corpus-email-digest/versions/1.2.2/craftbook.json

@@ -0,0 +1,221 @@
+{
+  "id": "corpus-email-digest",
+  "name": "Daily Email Digest from a Corpus",
+  "description": "Produce an email-ready digest that summarizes a corpus of content (docs, feeds, notes) for a recurring send. Scopes what matters and the format first, drafts the digest in a consistent voice, then builds the email-ready output and evaluates for accuracy and scannability.\n\nA gallery craftbook generated from an archetype spec. It runs\n`phase → (per-phase gate) → … → evaluate → (loop) → finish`. Each build\nphase that produces a checkable artifact is followed by a **runtime\ngate-checkpoint** — the runtime verifies the artifact and routes with no\nmodel turn, looping back to redo the phase on a miss. The final `evaluate`\nstep holds a static deliverable gate plus a reviewer QA pass. What it adds\nover the generic `build-loop`: a specialist role per phase, a\ndomain-correct ordering, and a concrete per-phase quality bar.\n\nDeliverables marked \"artifact\" land in the project's artifacts drawer (`write_artifact` / `read_artifact`), not the shipped workspace — review output is not product source.\n\nPhases:\n\n1. Scope the digest (planner) — what to include, sections, format, length → gated on artifact `digest/scope.md` (markdown-notes)\n2. Draft the digest (copywriter) — write the digest from the corpus, with citations → gated on artifact `digest/draft.md` (markdown-doc)\n3. Build the email output (developer) — render to an email-ready format → gated on `digest.html` (html-page)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "daily summary",
+    "email digest",
+    "summarize this corpus",
+    "briefing"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the digest",
+      "description": "what to include, sections, format, length",
+      "prompt": "List and read every supplied corpus file with workspace tools before scoping. Decide the digest window, included sources, section structure (headline, top items, one line each), target length, tone, citation format, and subject-line convention. Write an **acceptance-criteria checklist** (\"≤ N items per section\", \"every item cites its source\", \"scannable in under a minute\", \"no item outside the window\", \"no invented facts\"). Save the scope + checklist to artifact `{{workPath}}/scope.md` with `write_artifact`; note the path in task notes.",
+      "suggestedRole": "planner",
+      "advanceWhen": {
+        "file": "{{workPath}}/scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/scope.md",
+            "bytes": 500,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/scope.md",
+            "pattern": "citation|source",
+            "flags": "i",
+            "label": "citation policy",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/scope.md",
+            "pattern": "window|fresh|date",
+            "flags": "i",
+            "label": "freshness window",
+            "artifact": true
+          }
+        ],
+        "onReject": "scope",
+        "maxAttempts": 3
+      },
+      "next": "draft"
+    },
+    {
+      "id": "draft",
+      "name": "Draft the digest",
+      "description": "write the digest from the corpus, with citations",
+      "prompt": "Read artifact `{{workPath}}/scope.md` with `read_artifact`, then re-read every included corpus source with workspace `read_file`. Write the digest to the scoped structure: a subject line, one tight line per item, and an adjacent source filename/citation for every item. Lead with what matters, keep a consistent voice, and do not invent or merge unsupported facts. Save the complete draft to artifact `{{workPath}}/draft.md` with `write_artifact`; note the path in task notes.",
+      "suggestedRole": "copywriter",
+      "consumes": [
+        {
+          "file": "digest/scope.md",
+          "artifact": true
+        }
+      ],
+      "advanceWhen": {
+        "file": "{{workPath}}/draft.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/draft.md",
+            "bytes": 700,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/draft.md",
+            "pattern": "subject\\s*:",
+            "flags": "i",
+            "label": "subject line",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/draft.md",
+            "pattern": "\\.md\\b|source\\s*:",
+            "flags": "i",
+            "label": "source citations",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/draft.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i",
+            "label": "at least one markdown heading",
+            "artifact": true
+          }
+        ],
+        "onReject": "draft",
+        "maxAttempts": 3
+      },
+      "next": "build"
+    },
+    {
+      "id": "build",
+      "name": "Build the email output",
+      "description": "render to an email-ready format",
+      "prompt": "Read artifacts `{{workPath}}/scope.md` and `{{workPath}}/draft.md` with `read_artifact`. Render the approved draft to workspace `digest.html` with `write_file`. Include the subject line in visible/preheader content, preserve every adjacent source citation, use semantic email-safe tables or blocks, and keep styles inline or in a small embedded style block with no external CSS, scripts, or network assets. On a loop-back, fix only the named gaps. `write_task_note` the workspace output path and item/source counts.",
+      "suggestedRole": "developer",
+      "consumes": [
+        {
+          "file": "digest/scope.md",
+          "artifact": true
+        },
+        {
+          "file": "digest/draft.md",
+          "artifact": true
+        }
+      ],
+      "advanceWhen": {
+        "file": "digest.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "digest.html",
+            "bytes": 2200
+          },
+          {
+            "kind": "htmlLint",
+            "file": "digest.html"
+          },
+          {
+            "kind": "cssMinBytes",
+            "bytes": 350,
+            "file": "digest.html"
+          },
+          {
+            "kind": "contains",
+            "file": "digest.html",
+            "pattern": "subject\\s*:",
+            "flags": "i",
+            "label": "subject line"
+          },
+          {
+            "kind": "contains",
+            "file": "digest.html",
+            "pattern": "\\.md\\b|source\\s*:",
+            "flags": "i",
+            "label": "source citations"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "digest.html"
+            }
+          }
+        ],
+        "onReject": "build",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Read workspace `digest.html` with `read_file`, artifacts `{{workPath}}/scope.md` and `{{workPath}}/draft.md` with `read_artifact`, and the original corpus files with workspace tools. Check accuracy (every item traces to a corpus fact, nothing invented), citations (each item names its source), scannability, section/item limits, and freshness window. Confirm the HTML preserves the approved draft and has no external dependencies. Write PASS/FAIL per criterion.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"build\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "consumes": [
+        {
+          "file": "digest.html"
+        }
+      ],
+      "next": "build"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
+      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
+      "suggestedRole": "developer",
+      "terminal": true
+    }
+  ],
+  "version": "1.2.2",
+  "releasedAt": "2026-08-14T00:00:00Z",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer for this run's intermediate files. Defaults to this task's own folder so concurrent runs never overwrite each other; override with a stable name only when runs should deliberately share working files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  }
+}