@bendyline/gilde 0.1.38 → 0.1.40

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

@@ -0,0 +1,105 @@
+{
+  "schemaVersion": 1,
+  "title": "Plain-language service agreement template",
+  "objective": "Measure whether the contract-template craftbook produces a reusable template with placeholders, protective clauses, and a prominent non-legal-advice disclaimer.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "In the `Contract Template Eval` project, read `source/deal-brief.md` and write `contract.md`: a plain-language service agreement template for a bookkeeping cleanup engagement. Include marked fill-in fields, numbered clauses, signature block, lawyer-review flags, and a prominent non-legal-advice disclaimer.",
+  "setup": {
+    "projectName": "Contract Template Eval",
+    "about": "Self-contained eval project for contract-template. Deal structure is in workspace/source/deal-brief.md.",
+    "missionObjectives": "Draft a reusable service agreement template with placeholders, clauses, disclaimer, lawyer-review flags, and no hard-coded final legal advice.",
+    "files": [
+      {
+        "path": "source/deal-brief.md",
+        "content": "# Deal brief\n\nAgreement type: bookkeeping cleanup service agreement.\nParties: provider and client should remain placeholders.\nVariable terms: [PROVIDER_NAME], [CLIENT_NAME], [EFFECTIVE_DATE], [PROJECT_FEE], [PAYMENT_SCHEDULE], [TERM_LENGTH], [GOVERNING_LAW_STATE].\nRequired clauses: scope of work, client responsibilities, payment, term and termination, confidentiality, IP ownership of deliverables, limitation of liability, dispute resolution, governing law, signature block.\nFlag for lawyer review: liability cap, governing law, indemnity/dispute language.\n"
+      }
+    ],
+    "worker": {
+      "name": "Lotte",
+      "role": "Document Drafter"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "workspace/contract.md is a placeholder-driven agreement template with disclaimer, numbered clauses, signature block, and lawyer-review flags.",
+    "deliverables": [
+      {
+        "path": "contract.md",
+        "kind": "markdown-doc",
+        "minBytes": 2800,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "contract.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "contract.md",
+            "pattern": "not legal advice|qualified attorney|lawyer review",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "contract.md",
+            "pattern": "\\[PROVIDER_NAME\\]|\\[CLIENT_NAME\\]|\\[EFFECTIVE_DATE\\]|\\[PROJECT_FEE\\]",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "contract.md",
+            "pattern": "confidentiality|IP ownership|termination|governing law|dispute",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "contract.md",
+            "pattern": "limitation of liability|indemnity|\\[LAWYER REVIEW\\]",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "contract.md",
+            "pattern": "Signature|Name|Title|Date",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "contract.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "grounding",
+        "description": "Seeded facts appear faithfully and the source is cited."
+      },
+      {
+        "name": "structure",
+        "description": "Sections progress logically for the artifact class."
+      },
+      {
+        "name": "completeness",
+        "description": "Required elements (risks, next actions, scope) are all present."
+      },
+      {
+        "name": "tone",
+        "description": "The register fits the audience and artifact class."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "disclaimer",
+    "placeholder discipline",
+    "clause completeness"
+  ]
+}

package/data/craftbook-templates/co/cookbook-layout/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "cookbook-layout",
   "role": "general",
+  "category": "personal",
   "name": "Lay Out the Cookbook",
   "description": "Assemble the heirloom: every tested recipe in its chapter, the provenance kept beside the food — whose recipe it was, what table it came from — chapter intros in the family's voice, print-ready pages. The book that exists because someone finally sat down and made it. Locks the inclusion rule FIRST — tested recipes in, untested listed for the next round, never silently dropped — then lays out the chapters, then proofs every eligible recipe made it in with its story intact. Use for laying out the family cookbook, the heirloom recipe book, 'print the cookbook', and a recipe book for the grandchildren.",
   "tags": [

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

@@ -0,0 +1,133 @@
+{
+  "id": "cookbook-layout",
+  "name": "Lay Out the Cookbook",
+  "description": "Assemble the heirloom: every tested recipe in its chapter, the provenance kept beside the food — whose recipe it was, what table it came from — chapter intros in the family's voice, print-ready pages. The book that exists because someone finally sat down and made it. Locks the inclusion rule FIRST — tested recipes in, untested listed for the next round, never silently dropped — then lays out the chapters, then proofs every eligible recipe made it in with its story intact. Use for laying out the family cookbook, the heirloom recipe book, 'print the cookbook', and a recipe book for the grandchildren.\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 book (kitchen-master) — inclusion rule from the shelf, chapter order, page rules → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Lay out the book (designer) — cover, chapters, one recipe per page with provenance → gated on `book/cookbook.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": [
+    "lay out the cookbook",
+    "make the family cookbook",
+    "print the recipe book",
+    "heirloom cookbook",
+    "put the recipes into a book"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the book",
+      "description": "inclusion rule from the shelf, chapter order, page rules",
+      "prompt": "Read the shelf before laying out a page. Step 1: read recipes.json from the workspace and the recipe files under recipes/ — which recipes are tested and which still pending. Step 2: lock the inclusion rule: tested recipes go in; untested ones go on a short 'still to test' page at the back — listed, never silently dropped. Step 3: settle the chapter order with the owner — by course, by season, or by the family line each recipe came down — and the page rules: one recipe per page, the provenance line under every title, a short chapter intro in the family's voice, print styles throughout. Step 4: write an acceptance-criteria checklist ('every tested recipe appears in its chapter with its provenance line', 'untested recipes listed at the back, not dropped', 'the family's phrasings preserved, not rewritten into recipe-site prose', 'chapters ordered as agreed', 'the book prints cleanly, one recipe per page'). Call write_task_note with the tested/untested counts + chapter order + checklist and write {{workPath}}/scope.md.\n\nThe deliverable `{{workPath}}/scope.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "kitchen-master",
+      "advanceWhen": {
+        "file": "{{workPath}}/scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "scope",
+        "maxAttempts": 3
+      },
+      "next": "layout"
+    },
+    {
+      "id": "layout",
+      "name": "Lay out the book",
+      "description": "cover, chapters, one recipe per page with provenance",
+      "prompt": "Lay out the cookbook as one print-ready HTML file at book/cookbook.html. Step 1: the cover and a contents page listing the chapters. Step 2: each chapter opens with a short intro in the family's voice — two or three sentences that sound like the kitchen, not a food blog. Step 3: one recipe per page: the title, the provenance line right under it — whose recipe, where it came from — then ingredients and the method in the family's own phrasing from the recipe files, preserved word for word where it matters. Step 4: the 'still to test' page at the back listing the untested recipes by name. Step 5: print styles throughout — an @page rule, page breaks so every recipe starts fresh, type set for reading at arm's length in a working kitchen. Call write_task_note with the recipe count and the chapter list.",
+      "suggestedRole": "designer",
+      "advanceWhen": {
+        "file": "book/cookbook.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "book/cookbook.html",
+            "bytes": 8000
+          },
+          {
+            "kind": "htmlLint",
+            "file": "book/cookbook.html"
+          },
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "book/cookbook.html"
+          },
+          {
+            "kind": "contains",
+            "file": "book/cookbook.html",
+            "pattern": "@page|@media\\s+print|page-break|break-after",
+            "flags": "i",
+            "label": "print CSS"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "book/cookbook.html"
+            }
+          }
+        ],
+        "onReject": "layout",
+        "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": "Open book/cookbook.html against recipes.json and the recipes/ files and verify every criterion from {{workPath}}/scope.md: every tested recipe appears in its chapter with its provenance line — spot-check three against the shelf, a recipe that lost its story has lost the point — untested recipes are listed at the back and none silently dropped, the family's phrasings survive in the methods, chapters run in the agreed order, and the page styling would print one recipe per page. Write PASS/FAIL per criterion; on any failure, name the recipe and the gap and loop back to layout.\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: \"layout\" })` 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": "book/cookbook.html"
+        }
+      ],
+      "next": "layout"
+    },
+    {
+      "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.0.2",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  },
+  "minGezelVersion": "1.26233"
+}

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

@@ -0,0 +1,162 @@
+{
+  "schemaVersion": 1,
+  "title": "Lay Out the Cookbook — tested recipes to heirloom pages",
+  "objective": "Measure whether the cookbook-layout craftbook assembles the seeded recipe shelf into a print-ready book: every tested recipe in its chapter with its provenance line, untested recipes listed at the back, family phrasings preserved.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "i think weve got enough tested recipes — can you lay out the cookbok? one per grandchild eventually so make it printable",
+  "setup": {
+    "projectName": "Van Daalen Family Recipe Book",
+    "about": "Family recipe book project for the Van Daalens. The recipe index is workspace/recipes.json with one markdown file per recipe under workspace/recipes; the laid-out book goes under workspace/book.",
+    "missionObjectives": "Tested recipes go in with their provenance intact; untested ones are listed for the next round, never silently dropped. Everything is grounded in the shelf — no live services, no real credentials.",
+    "files": [
+      {
+        "path": "recipes.json",
+        "content": "{\n  \"family\": \"Van Daalen\",\n  \"chapters\": [\"Soups & Starters\", \"Mains\", \"Breads\", \"Sweets\"],\n  \"recipes\": [\n    { \"id\": \"split-pea\", \"title\": \"Oma Trudy's Split Pea Soup\", \"chapter\": \"Soups & Starters\", \"provenance\": \"Oma Trudy's — came over from Groningen in 1954\", \"tested\": true, \"file\": \"recipes/split-pea.md\" },\n    { \"id\": \"brown-bread\", \"title\": \"Saturday Brown Bread\", \"chapter\": \"Breads\", \"provenance\": \"Grandpa Wim's — baked every Saturday for thirty years\", \"tested\": true, \"file\": \"recipes/brown-bread.md\" },\n    { \"id\": \"pot-pie\", \"title\": \"Aunt Willa's Chicken Pot Pie\", \"chapter\": \"Mains\", \"provenance\": \"Aunt Willa's — the funeral casserole that became a birthday request\", \"tested\": true, \"file\": \"recipes/pot-pie.md\" },\n    { \"id\": \"strawberry-cake\", \"title\": \"Midsummer Strawberry Cake\", \"chapter\": \"Sweets\", \"provenance\": \"Mom's — invented the summer the freezer broke\", \"tested\": true, \"file\": \"recipes/strawberry-cake.md\" },\n    { \"id\": \"campfire-chili\", \"title\": \"Pa's Campfire Chili\", \"chapter\": \"Mains\", \"provenance\": \"Pa's — written on the inside of a matchbook, translated by Ria\", \"tested\": true, \"file\": \"recipes/campfire-chili.md\" },\n    { \"id\": \"lemon-custard\", \"title\": \"Lemon Custard for Sick Days\", \"chapter\": \"Sweets\", \"provenance\": \"Oma Trudy's — the one that fixed every flu since 1962\", \"tested\": true, \"file\": \"recipes/lemon-custard.md\" },\n    { \"id\": \"oliebollen\", \"title\": \"The Contested Oliebollen\", \"chapter\": \"Sweets\", \"provenance\": \"disputed between Ria and Aunt Willa — two versions exist\", \"tested\": false, \"file\": \"recipes/oliebollen.md\" },\n    { \"id\": \"maple-fudge\", \"title\": \"Maple Walnut Fudge\", \"chapter\": \"Sweets\", \"provenance\": \"from a fair stall in 1998 — nobody has dared it yet\", \"tested\": false, \"file\": \"recipes/maple-fudge.md\" }\n  ]\n}\n"
+      },
+      {
+        "path": "recipes/split-pea.md",
+        "content": "# Oma Trudy's Split Pea Soup\n\nOma Trudy's — came over from Groningen in 1954.\n\n## Ingredients\n- 500 g split peas\n- 1 smoked sausage (the good one, not the budget one — Oma's margin note)\n- 2 leeks, 1 celeriac, 2 carrots\n- a ham hock\n\n## Method\nSoak the peas while you argue about whether soaking is necessary. Simmer everything except the sausage for two hours until 'a spoon stands up in it'. Add the sausage for the last twenty minutes. Better tomorrow than today.\n"
+      },
+      {
+        "path": "recipes/brown-bread.md",
+        "content": "# Saturday Brown Bread\n\nGrandpa Wim's — baked every Saturday for thirty years.\n\n## Ingredients\n- 400 g wholemeal flour, 100 g rye\n- 7 g yeast, 10 g salt, a knob of butter\n- 350 ml warm water\n\n## Method\nKnead until your arms complain, then five minutes more. Rise under the tea towel with the blue stripe (any towel works; the blue stripe is tradition). Bake at 220 until it sounds hollow when you knock on the bottom.\n"
+      },
+      {
+        "path": "recipes/pot-pie.md",
+        "content": "# Aunt Willa's Chicken Pot Pie\n\nAunt Willa's — the funeral casserole that became a birthday request.\n\n## Ingredients\n- 1 whole chicken, poached and picked\n- carrots, peas, pearl onions\n- double crust, all butter, no shortcuts\n\n## Method\nMake the gravy from the poaching broth and do not rush it. Fill, lid, crimp with a fork the way Willa did — three presses, turn, three presses. Vent with her initials if you're feeling brave. Bake until deep gold.\n"
+      },
+      {
+        "path": "recipes/strawberry-cake.md",
+        "content": "# Midsummer Strawberry Cake\n\nMom's — invented the summer the freezer broke.\n\n## Ingredients\n- 250 g flour, 200 g sugar, 3 eggs, 200 g butter\n- a full kilo of strawberries, no apologies\n- whipped cream, double what seems sensible\n\n## Method\nBake the sponge, split it while warm. Sugar the berries and let them bleed a little. Assemble taller than is structurally wise. Eat outside or it doesn't count.\n"
+      },
+      {
+        "path": "recipes/campfire-chili.md",
+        "content": "# Pa's Campfire Chili\n\nPa's — written on the inside of a matchbook, translated by Ria.\n\n## Ingredients\n- 1 kg beef chuck, cut rough\n- two onions, 'more garlic than the recipe says'\n- dried anchos, a bottle of dark beer, a square of dark chocolate\n\n## Method\nBrown the beef in batches and don't crowd the pot — the matchbook underlines this twice. Low fire, three hours, stir when you think of it. The chocolate goes in at the end and you tell nobody.\n"
+      },
+      {
+        "path": "recipes/lemon-custard.md",
+        "content": "# Lemon Custard for Sick Days\n\nOma Trudy's — the one that fixed every flu since 1962.\n\n## Ingredients\n- 500 ml whole milk\n- 3 yolks, 80 g sugar, 30 g cornstarch\n- zest of two lemons, juice of one\n\n## Method\nWarm the milk with the zest. Whisk yolks, sugar, and cornstarch, then marry them slowly so nothing scrambles. Thicken on low until it coats the spoon. Serve warm, in the yellow bowl if the patient is under twelve.\n"
+      },
+      {
+        "path": "recipes/oliebollen.md",
+        "content": "# The Contested Oliebollen\n\nDisputed between Ria and Aunt Willa — two versions exist and neither yields.\n\n## Status\nNot yet tested side by side. The New Year's bake-off will settle it. Both versions are filed with the arbitration notes.\n"
+      },
+      {
+        "path": "recipes/maple-fudge.md",
+        "content": "# Maple Walnut Fudge\n\nFrom a fair stall in 1998 — nobody has dared it yet.\n\n## Status\nUntested. The card says 'soft-ball stage' with no thermometer number, which is why it has waited twenty-eight years.\n"
+      }
+    ],
+    "worker": {
+      "name": "Ria",
+      "role": "Designer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "book/cookbook.html is a print-ready book: all six tested recipes in their chapters with provenance lines, the two untested ones listed at the back, family phrasings preserved.",
+    "deliverables": [
+      {
+        "path": "book/cookbook.html",
+        "kind": "html-page",
+        "minBytes": 8000,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "book/cookbook.html"
+          },
+          {
+            "kind": "contains",
+            "file": "book/cookbook.html",
+            "pattern": "@page|@media\\s+print|page-break|break-after",
+            "flags": "i",
+            "label": "print CSS"
+          },
+          {
+            "kind": "contains",
+            "file": "book/cookbook.html",
+            "pattern": "Split Pea",
+            "label": "soup chapter recipe present"
+          },
+          {
+            "kind": "contains",
+            "file": "book/cookbook.html",
+            "pattern": "Brown Bread",
+            "label": "bread recipe present"
+          },
+          {
+            "kind": "contains",
+            "file": "book/cookbook.html",
+            "pattern": "Pot Pie",
+            "label": "mains recipe present"
+          },
+          {
+            "kind": "contains",
+            "file": "book/cookbook.html",
+            "pattern": "Strawberry Cake",
+            "label": "sweets recipe present"
+          },
+          {
+            "kind": "contains",
+            "file": "book/cookbook.html",
+            "pattern": "Campfire Chili",
+            "label": "second mains recipe present"
+          },
+          {
+            "kind": "contains",
+            "file": "book/cookbook.html",
+            "pattern": "Lemon Custard",
+            "label": "second sweets recipe present"
+          },
+          {
+            "kind": "contains",
+            "file": "book/cookbook.html",
+            "pattern": "Groningen|Oma Trudy",
+            "label": "provenance preserved"
+          },
+          {
+            "kind": "contains",
+            "file": "book/cookbook.html",
+            "pattern": "still to test|to be tested|untested|not yet tested",
+            "flags": "i",
+            "label": "untested recipes listed, not dropped"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "book/cookbook.html",
+      "kind": "html"
+    },
+    "axes": [
+      {
+        "name": "heirloom feel",
+        "description": "The book reads like a family object — chapter intros in the family's voice, not food-blog prose."
+      },
+      {
+        "name": "completeness",
+        "description": "All six tested recipes appear in their chapters; the two untested ones are listed at the back."
+      },
+      {
+        "name": "typography",
+        "description": "Type set for reading at arm's length in a working kitchen; one recipe per printed page."
+      },
+      {
+        "name": "provenance preservation",
+        "description": "Every recipe keeps its provenance line and the family's own phrasings survive in the methods."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "inclusion rule honored",
+    "provenance intact",
+    "print-ready book"
+  ]
+}

package/data/craftbook-templates/co/copy-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "copy-review",
   "role": "maintenance-review",
+  "category": "writing",
   "name": "Editorial & Tone Review",
   "description": "Run an editorial review on a piece of content for clarity, correctness, and brand voice, then produce a line-edit report and a clean revised version. First scopes the audience, purpose, and voice/style rules and locks an editorial checklist (grammar and spelling, clarity and concision, consistent terminology, active voice, reading level, tone match, scannability, and CTA strength), then reviews the copy line-by-line against those rules marking every issue with a suggested rewrite, then writes a report of categorized edits plus a clean revised draft. Use this for a copy review, editorial pass, proofreading, line edit, tone/voice review, or tightening writing — it returns specific tracked edits with rewrites and a polished final draft rather than 'tighten this up'.",
   "tags": [

package/data/craftbook-templates/co/copy-review/versions/1.0.2/craftbook.json

@@ -0,0 +1,153 @@
+{
+  "id": "copy-review",
+  "name": "Editorial & Tone Review",
+  "description": "Run an editorial review on a piece of content for clarity, correctness, and brand voice, then produce a line-edit report and a clean revised version. First scopes the audience, purpose, and voice/style rules and locks an editorial checklist (grammar and spelling, clarity and concision, consistent terminology, active voice, reading level, tone match, scannability, and CTA strength), then reviews the copy line-by-line against those rules marking every issue with a suggested rewrite, then writes a report of categorized edits plus a clean revised draft. Use this for a copy review, editorial pass, proofreading, line edit, tone/voice review, or tightening writing — it returns specific tracked edits with rewrites and a polished final draft rather than 'tighten this up'.\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 editorial review (reviewer) — lock audience, purpose, voice, and an edit checklist → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Line-edit the copy (copywriter) — mark every issue with a concrete rewrite → gated on artifact `{{workPath}}/review.md` (markdown-notes)\n3. Write the edit report + clean draft (copywriter) — categorized edits plus a revised draft → gated on artifact `{{workPath}}/copy-review.md` (markdown-report)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "copy review",
+    "editorial review",
+    "proofread this",
+    "line edit this",
+    "review the tone",
+    "tighten this writing"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the editorial review",
+      "description": "lock audience, purpose, voice, and an edit checklist",
+      "prompt": "Step 1: Read the content and identify the audience, the purpose (inform / persuade / convert / instruct), and the desired voice/tone (e.g. friendly-expert, formal, playful) — infer from any style guide or sample if none is given. Step 2: Write an editorial acceptance-criteria checklist covering: grammar/spelling/punctuation correctness, clarity (no ambiguous or convoluted sentences), concision (cut filler, redundancy, hedging), consistent terminology and capitalization, active voice and strong verbs, an appropriate reading level for the audience, tone matching the target voice, scannability (headings, short paragraphs, lists where helpful), and CTA/heading strength where applicable. Step 3: For each item state the pass condition for THIS piece (e.g. 'reading level ~grade 8', 'product name always rendered as <X>'). Step 4: Note the target word-count direction if length matters. Write the audience/purpose/voice + checklist to `write_task_note` AND `{{workPath}}/scope.md`. No edits yet.\n\nThe deliverable `{{workPath}}/scope.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "reviewer",
+      "advanceWhen": {
+        "file": "{{workPath}}/scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "scope",
+        "maxAttempts": 3
+      },
+      "next": "review"
+    },
+    {
+      "id": "review",
+      "name": "Line-edit the copy",
+      "description": "mark every issue with a concrete rewrite",
+      "prompt": "Step 1: Read the copy line-by-line. Step 2: For EACH checklist dimension, flag specific issues quoting the offending text and giving a concrete REWRITE, not just a note — e.g. 'ORIGINAL: \"We are committed to leveraging synergies\" → SUGGESTED: \"We connect your tools so they work together\"'. Step 3: Categorize each edit: Correctness (grammar/spelling/fact), Clarity, Concision, Consistency, Voice/Tone, or Structure/Scannability. Step 4: Check global consistency: terminology, capitalization, oxford-comma and number style, heading parallelism. Step 5: Assess the overall tone against the target and note where it drifts. Step 6: Track the substantive vs trivial edits so the report can prioritize. Good looks like: every flagged line has a ready-to-paste rewrite. Stage the edit list to `write_task_note`. Do not write the final report/draft yet.\n\nThe deliverable `{{workPath}}/review.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "{{workPath}}/review.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/review.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/review.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "review",
+        "maxAttempts": 3
+      },
+      "next": "report"
+    },
+    {
+      "id": "report",
+      "name": "Write the edit report + clean draft",
+      "description": "categorized edits plus a revised draft",
+      "prompt": "Step 1: Open `{{workPath}}/copy-review.md` and write a 2-3 sentence editorial summary: overall clarity/voice verdict and the top theme to fix. Step 2: Add an '## Edits' section grouped by category (Correctness, Clarity, Concision, Consistency, Voice, Structure); each entry shows the ORIGINAL and the SUGGESTED rewrite. Step 3: Add a '## Revised draft' section containing the FULL clean copy with every accepted edit applied — this is the shippable version. Step 4: Note any factual claims you could not verify. The revised draft must read smoothly end-to-end and match the target voice; every edit must include a concrete rewrite — no 'reword this'. On a loop-back, fix only the named gaps without losing good edits. `write_task_note` the report path and the count of edits by category.\n\nThe deliverable `{{workPath}}/copy-review.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "{{workPath}}/copy-review.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/copy-review.md",
+            "bytes": 1500,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/copy-review.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i",
+            "label": "at least one markdown heading",
+            "artifact": true
+          }
+        ],
+        "onReject": "report",
+        "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": "Open `{{workPath}}/copy-review.md` and grade it against the scope checklist. Check EACH criterion and write PASS/FAIL with a one-line reason: (1) every editorial dimension was assessed; (2) each edit includes the original AND a concrete rewrite; (3) edits are categorized; (4) a full revised draft is present and reads cleanly end-to-end; (5) the revised draft matches the target voice and reading level; (6) terminology/consistency was checked globally; (7) no vague 'tighten this' filler. Read the revised draft straight through to confirm it is shippable. If any criterion fails, name the exact gap and loop back.\n\nThe deliverable lives in the project's artifacts drawer — open `{{workPath}}/copy-review.md` with `read_artifact`, not `read_file`.\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: \"report\" })` 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": "{{workPath}}/copy-review.md",
+          "artifact": true
+        }
+      ],
+      "next": "report"
+    },
+    {
+      "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.0.2",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  },
+  "minGezelVersion": "1.26233"
+}