@bendyline/gilde 0.1.38 → 0.1.39

package/data/craftbook-templates/te/test-suite-backfill/versions/1.0.2/test.json

@@ -0,0 +1,95 @@
+{
+  "schemaVersion": 1,
+  "title": "Test Suite Backfill smoke eval",
+  "objective": "Self-contained smoke eval for the Test Suite Backfill craftbook using the code generic harness.",
+  "tags": [
+    "code"
+  ],
+  "prompt": "We need a small Node helper for this — the requirments are in source/requirements.md. Put it in src/solution.mjs.",
+  "setup": {
+    "projectName": "Test Suite Backfill Eval",
+    "about": "Self-contained eval project for test-suite-backfill. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/src/solution.mjs.",
+    "missionObjectives": "Use the Test Suite Backfill craftbook/template, read the seeded local fixtures, and write src/solution.mjs without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Test Suite Backfill Eval Brief\n\nClient: Boreal Desk, a home-office accessories company.\nAudience: operations leads who need an artifact they can use this week.\n\nFixed source facts for grounding:\n- The returns desk pilot covered 18 SKUs.\n- Median first response improved from 18 hours to 6 hours.\n- Preventable refund leakage fell from 14.2% to 8.9%.\n- The top unresolved complaint is status silence after photo submission.\n- Required next actions are automated status emails, barcode-exception training, and a weekly Finance exception export.\n\nUse these facts when the task asks for prose, analysis, copy, UI content, or test data. Do not use live web services, real credentials, or current outside data.\n\nCraftbook under test: test-suite-backfill - Test Suite Backfill.\n"
+      },
+      {
+        "path": "source/requirements.md",
+        "content": "# Runner Requirements\n\nBuild a dependency-free Node ESM helper for Boreal Desk support operations. Export at least one function. Include a tiny self-test section using node:assert or an equivalent assertion helper. Use fixture values for 18 -> 6 hour response time and 14.2 -> 8.9 refund leakage.\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Developer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "src/solution.mjs is a local ESM module with basic self-test scaffolding.",
+    "deliverables": [
+      {
+        "path": "src/solution.mjs",
+        "kind": "code-with-tests",
+        "minBytes": 1500,
+        "checks": [
+          {
+            "kind": "esmImports",
+            "file": "src/solution.mjs"
+          },
+          {
+            "kind": "contains",
+            "file": "src/solution.mjs",
+            "pattern": "export\\s+(function|const|class)|export\\s*\\{",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "src/solution.mjs",
+            "pattern": "assert|test|describe|it|expect",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "src/solution.mjs",
+            "pattern": "18|6|14\\.2|8\\.9|Boreal",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "src/solution.mjs",
+      "kind": "typescript"
+    },
+    "axes": [
+      {
+        "name": "correctness",
+        "description": "The module does what the requirements ask, with sensible edge handling."
+      },
+      {
+        "name": "verification",
+        "description": "Self-tests exercise real behavior, not trivial truths."
+      },
+      {
+        "name": "clarity",
+        "description": "Exports, naming, and structure make the module usable without reading every line."
+      },
+      {
+        "name": "robustness",
+        "description": "Invalid input and boundary cases fail loudly rather than silently."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "runnable ESM",
+    "test scaffolding",
+    "local fixtures"
+  ]
+}

package/data/craftbook-templates/th/thank-you-batch/versions/1.0.2/craftbook.json

@@ -0,0 +1,155 @@
+{
+  "id": "thank-you-batch",
+  "name": "Thank-You Note Batch",
+  "description": "Clear the owed-thanks list with notes that sound like you: read who is owed and for what from the correspondence roster, draft one note per person that names the actual gift or kindness — no template smell — then log every note so nobody who mattered goes unanswered. Locks the household voice and the coverage rules FIRST, then drafts the batch, then records it in the roster with a short run summary. Use for thank-you notes, clearing the owed-thanks list, 'we owe thank yous from the party', and post-holiday gratitude sweeps.\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 batch (letter-writer) — owed list from the roster, voice guide, coverage rules → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Draft the notes (copywriter) — one personal note per owed person, in the household voice → gated on `letters/thank-you.md` (markdown-doc)\n3. Log the batch (archivist) — record each note in the roster, write the run summary → gated on artifact `{{workPath}}/report.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": [
+    "draft the thank you notes",
+    "clear the owed thanks list",
+    "we owe thank yous",
+    "write the thank you cards",
+    "thank you note batch"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the batch",
+      "description": "owed list from the roster, voice guide, coverage rules",
+      "prompt": "Define the batch before drafting a word. Step 1: read correspondents.json from the workspace — who is owed thanks, for what gift or kindness, and how long each has been owed. Step 2: read the household's voice notes if they exist ({{workPath}}/voice.md or a voice field on the roster) — the phrases this family actually uses, how they open and sign off, and what they would never say. Step 3: confirm with the owner anyone to add or defer, and how the notes go out (card, email, hand-delivered) since that shapes length. Step 4: write an acceptance-criteria checklist ('every owed person gets a note or an explicit deferral with a reason', 'every note names the actual gift or kindness — a generic thanks is a miss', 'the voice guide is respected and no two notes are interchangeable', 'every drafted note is logged against the roster'). Call write_task_note with the owed count + 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": "letter-writer",
+      "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": "draft"
+    },
+    {
+      "id": "draft",
+      "name": "Draft the notes",
+      "description": "one personal note per owed person, in the household voice",
+      "prompt": "Draft the whole batch against the locked rules. Step 1: write one section per person in letters/thank-you.md — a heading with their name, then the note. Step 2: open each note with the specific gift or kindness from the roster in the first two sentences — the detail IS the thanks; 'thank you for the lovely gift' is a rejection. Step 3: vary the shape — if two notes could swap recipients without anyone noticing, rewrite one of them. Step 4: keep the household's voice throughout — warm, theirs, sized for how each note will be sent. Step 5: call write_task_note with the note count and anyone you had to defer.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "letters/thank-you.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "letters/thank-you.md",
+            "bytes": 1200
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkContains",
+            "scope": "standard",
+            "inputs": {
+              "file": "letters/thank-you.md",
+              "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+              "flags": "i"
+            }
+          }
+        ],
+        "onReject": "draft",
+        "maxAttempts": 3
+      },
+      "next": "log"
+    },
+    {
+      "id": "log",
+      "name": "Log the batch",
+      "description": "record each note in the roster, write the run summary",
+      "prompt": "Close the batch. Step 1: for each drafted note, record it against the person's entry through the project's correspondence capabilities (or note the exact roster update) so the owed-thanks tracking clears. Step 2: write the run summary — who got a note and what it names, who was deferred and why, and what still has to physically happen (addresses to find, stamps to buy). Step 3: keep it short and factual — this is a household ritual, not paperwork. Write {{workPath}}/report.md and call write_task_note with the drafted and deferred counts.\n\nThe deliverable `{{workPath}}/report.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": "archivist",
+      "advanceWhen": {
+        "file": "{{workPath}}/report.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/report.md",
+            "bytes": 600,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i",
+            "label": "at least one markdown heading",
+            "artifact": true
+          }
+        ],
+        "onReject": "log",
+        "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 letters/thank-you.md and {{workPath}}/report.md and verify every criterion from {{workPath}}/scope.md: every owed person in correspondents.json has a note or an explicit deferral with a reason, every note names the actual gift or kindness from the roster — spot-check each against the record, a note that thanks someone for the wrong thing is worse than none — no two notes are interchangeable, the voice matches the household's guide, and every drafted note is logged. Write PASS/FAIL per criterion; on any failure, name the person and the gap and loop back to draft.\n\nThe deliverable lives in the project's artifacts drawer — open `{{workPath}}/report.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: \"draft\" })` 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}}/report.md",
+          "artifact": true
+        }
+      ],
+      "next": "draft"
+    },
+    {
+      "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/th/thank-you-batch/versions/1.0.2/test.json

@@ -0,0 +1,144 @@
+{
+  "schemaVersion": 1,
+  "title": "Thank-You Note Batch — owed list to logged notes",
+  "objective": "Measure whether the thank-you-batch craftbook turns a seeded correspondence roster and voice guide into one personal, specific note per owed person, logged with a run summary.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "we owe thank yous from the aniversary party — the list is in correspondents.json and how we like to sound is in tasks/eval/voice.md. can you draft them all and log them?",
+  "setup": {
+    "projectName": "Vandermeer Correspondence Desk",
+    "about": "Correspondence desk for the Vandermeer household. The roster lives at workspace/correspondents.json; drafted letters go under workspace/letters. The household voice guide is workspace/notes/voice.md.",
+    "missionObjectives": "Keep the household's correspondence answered and warm. Notes are grounded in the roster's records — no live services, no real credentials.",
+    "files": [
+      {
+        "path": "correspondents.json",
+        "content": "{\n  \"household\": \"the Vandermeers\",\n  \"correspondents\": [\n    {\n      \"name\": \"Ruth Okafor\",\n      \"relation\": \"next-door neighbor\",\n      \"owedThanks\": true,\n      \"for\": \"the hand-quilted table runner she made for the anniversary\",\n      \"occasion\": \"40th anniversary party\"\n    },\n    {\n      \"name\": \"Stan Pollard\",\n      \"relation\": \"old fishing friend\",\n      \"owedThanks\": true,\n      \"for\": \"lending the big canvas tent and setting it up in the rain the night before\",\n      \"occasion\": \"40th anniversary party\"\n    },\n    {\n      \"name\": \"Mei Chu\",\n      \"relation\": \"friend from the pottery class\",\n      \"owedThanks\": true,\n      \"for\": \"the pair of hand-thrown teacups from her own studio\",\n      \"occasion\": \"40th anniversary party\"\n    },\n    {\n      \"name\": \"Deacon Ellis\",\n      \"relation\": \"nephew\",\n      \"owedThanks\": true,\n      \"for\": \"driving Grandma both ways and staying past midnight to help clean up\",\n      \"occasion\": \"40th anniversary party\"\n    },\n    {\n      \"name\": \"Priya Raman\",\n      \"relation\": \"college roommate\",\n      \"owedThanks\": true,\n      \"for\": \"the framed watercolor she painted of the old lake house\",\n      \"occasion\": \"40th anniversary party\"\n    },\n    {\n      \"name\": \"Tomas Herrera\",\n      \"relation\": \"across-the-street neighbor\",\n      \"owedThanks\": true,\n      \"for\": \"the case of orchard cider and the toast that made everyone cry\",\n      \"occasion\": \"40th anniversary party\"\n    },\n    {\n      \"name\": \"Gwen Fowler\",\n      \"relation\": \"cousin\",\n      \"owedThanks\": false,\n      \"note\": \"thanked in person for the flowers — nothing owed\"\n    }\n  ]\n}\n"
+      },
+      {
+        "path": "tasks/eval/voice.md",
+        "content": "# How we sound\n\n- We open every note with \"Dear\" and the person's first name. Always.\n- We sign off \"with love from the whole crew\" or \"yours over the fence\" for neighbors.\n- Short sentences. Warm. One small joke allowed per note, never two.\n- Always name the thing. \"Your lovely gift\" is banned in this house.\n- We never say \"esteemed\", \"heartfelt\", or anything that sounds like a greeting-card rack.\n"
+      }
+    ],
+    "worker": {
+      "name": "Lotte",
+      "role": "Letter writer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "letters/thank-you.md holds one personal note per owed person, each naming the actual gift or kindness in the household voice; tasks/eval/report.md logs the run.",
+    "deliverables": [
+      {
+        "path": "letters/thank-you.md",
+        "kind": "markdown-doc",
+        "minBytes": 1200,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "letters/thank-you.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S"
+          },
+          {
+            "kind": "valuesSubsetOf",
+            "file": "letters/thank-you.md",
+            "sourceFiles": [
+              "correspondents.json"
+            ],
+            "pattern": "Dear\\s+([A-Z][A-Za-z'-]+)",
+            "minMatches": 6,
+            "label": "a salutation per owed person, names from the roster"
+          },
+          {
+            "kind": "contains",
+            "file": "letters/thank-you.md",
+            "pattern": "quilt|table runner",
+            "flags": "i",
+            "label": "Ruth's gift named"
+          },
+          {
+            "kind": "contains",
+            "file": "letters/thank-you.md",
+            "pattern": "tent|teacup",
+            "flags": "i",
+            "label": "Stan's or Mei's gift named"
+          },
+          {
+            "kind": "contains",
+            "file": "letters/thank-you.md",
+            "pattern": "watercolor|lake house|cider|toast",
+            "flags": "i",
+            "label": "Priya's or Tomas's gift named"
+          },
+          {
+            "kind": "contains",
+            "file": "letters/thank-you.md",
+            "pattern": "driv|midnight|clean",
+            "flags": "i",
+            "label": "Deacon's kindness named"
+          },
+          {
+            "kind": "judge",
+            "file": "letters/thank-you.md",
+            "rubric": "Each note names the giver's actual gift or kindness from the roster and follows the household voice guide; no two notes are interchangeable.",
+            "sourceFiles": [
+              "tasks/eval/voice.md",
+              "correspondents.json"
+            ]
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/report.md",
+        "kind": "markdown-report",
+        "minBytes": 600,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "logged|recorded",
+            "flags": "i",
+            "label": "notes logged against the roster"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "letters/thank-you.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "warmth",
+        "description": "The notes read like a person, not a template — warm and sized for how they will be sent."
+      },
+      {
+        "name": "specificity",
+        "description": "Each note names the actual gift or kindness from the roster in its opening lines."
+      },
+      {
+        "name": "voice",
+        "description": "The household voice guide is followed — openings, sign-offs, and the banned phrases stay banned."
+      },
+      {
+        "name": "completeness",
+        "description": "Every owed person is covered or explicitly deferred with a reason; nobody quietly dropped."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "per-note specificity",
+    "household voice",
+    "full coverage"
+  ]
+}

package/data/craftbook-templates/th/thank-you-sweep/versions/1.0.2/craftbook.json

@@ -0,0 +1,155 @@
+{
+  "id": "thank-you-sweep",
+  "name": "Post-Event Thank-You Sweep",
+  "description": "Close the event the way it deserves: every gift-giver and every helper matched to a personal note, drafted in one sitting and tracked to sent — so 'the thank-yous actually go out' becomes a checklist instead of a lingering guilt. Locks the coverage rule FIRST — every giver, every helper, one personal detail each — then drafts the batch, then records each note to sent in the event's books. Use for post-event thank-yous, thanking the helpers after a party, gift thank-you notes, and 'the party's done, sweep the thank yous'.\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 sweep (ceremoniemeester) — gift and helper roster, coverage rule, tracking rule → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Draft the notes (copywriter) — one personal note per giver and helper → gated on `letters/thank-you.md` (markdown-doc)\n3. Record and report (archivist) — track each note in the books, write the coverage summary → gated on artifact `{{workPath}}/report.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": [
+    "sweep the thank yous",
+    "post event thank yous",
+    "thank the helpers",
+    "gift thank you notes",
+    "thank you sweep after the party"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the sweep",
+      "description": "gift and helper roster, coverage rule, tracking rule",
+      "prompt": "Define the sweep before drafting. Step 1: read gifts.json from the workspace — who gave what — and guests.json for the people who helped without a gift attached: setup, kitchen, driving, cleanup. Step 2: lock the coverage rule with the owner: every giver AND every helper gets a note, one personal detail each — the actual gift for givers, the actual deed for helpers — and helpers never get a gift-shaped form note. Step 3: settle how notes go out and what 'tracked to sent' means in the event's books. Step 4: write an acceptance-criteria checklist ('every giver and every helper covered or explicitly deferred with a reason', 'each note names the specific gift or deed from the record', 'no two notes interchangeable', 'every note recorded drafted and tracked to sent'). Call write_task_note with the giver + helper counts and the 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": "ceremoniemeester",
+      "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": "draft"
+    },
+    {
+      "id": "draft",
+      "name": "Draft the notes",
+      "description": "one personal note per giver and helper",
+      "prompt": "Draft the whole batch against the locked coverage rule. Step 1: one section per person in letters/thank-you.md — a heading with their name, then the note. Step 2: givers get the gift named in the first two sentences and a line about how it will be used or where it now lives. Step 3: helpers get the actual deed named — the grill run all afternoon, the chairs stacked at midnight — never a generic 'thanks for your help'. Step 4: vary the shape so no two notes could swap recipients. Step 5: call write_task_note with the note count split by givers and helpers.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "letters/thank-you.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "letters/thank-you.md",
+            "bytes": 1200
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkContains",
+            "scope": "standard",
+            "inputs": {
+              "file": "letters/thank-you.md",
+              "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+              "flags": "i"
+            }
+          }
+        ],
+        "onReject": "draft",
+        "maxAttempts": 3
+      },
+      "next": "record"
+    },
+    {
+      "id": "record",
+      "name": "Record and report",
+      "description": "track each note in the books, write the coverage summary",
+      "prompt": "Close the sweep. Step 1: record each note against the person's entry through the project's event books so every one is tracked drafted and then sent. Step 2: write the run summary — the coverage count stated plainly ('X of Y covered'), who was deferred and why, and what still has to physically happen for the notes to actually go out. Step 3: keep it short and honest. Write {{workPath}}/report.md and call write_task_note with the coverage count.\n\nThe deliverable `{{workPath}}/report.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": "archivist",
+      "advanceWhen": {
+        "file": "{{workPath}}/report.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/report.md",
+            "bytes": 600,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i",
+            "label": "at least one markdown heading",
+            "artifact": true
+          }
+        ],
+        "onReject": "record",
+        "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 letters/thank-you.md and {{workPath}}/report.md and verify every criterion from {{workPath}}/scope.md: every giver in gifts.json and every helper in guests.json is covered or explicitly deferred with a reason — count them, the forgotten setup crew is the classic failure — each note names the specific gift or deed from the record (spot-check each against the stores), no two notes are interchangeable, and the report states the coverage count with each note tracked. Write PASS/FAIL per criterion; on any failure, name the person and the gap and loop back to draft.\n\nThe deliverable lives in the project's artifacts drawer — open `{{workPath}}/report.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: \"draft\" })` 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}}/report.md",
+          "artifact": true
+        }
+      ],
+      "next": "draft"
+    },
+    {
+      "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"
+}