@bendyline/gilde 0.1.37 → 0.1.39

package/data/craftbook-templates/ch/chapter-weave/versions/1.0.2/test.json

@@ -0,0 +1,101 @@
+{
+  "schemaVersion": 1,
+  "title": "Weave a Chapter — the bakery years",
+  "objective": "Measure whether the chapter-weave craftbook drafts a memoir chapter built only from session material, surfacing the sessions' contradiction and marking gaps instead of inventing.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "can you weave the three bakery sessions into a chapter? theyre in sessions/ — draft to chapters/chapter-04.md",
+  "setup": {
+    "projectName": "Mam's Memoir",
+    "about": "Memoir studio project capturing Els's life story. Banked sessions live under workspace/sessions; drafted chapters go under workspace/chapters. The tellers' words are the only source material.",
+    "missionObjectives": "Turn the banked sessions into book chapters in the teller's voice: every scene traceable to something actually said, contradictions surfaced, gaps marked for a future session. No live services, no real credentials.",
+    "files": [
+      {
+        "path": "sessions/2026-05-14-session.md",
+        "content": "# Session — 2026-05-14 — taking over the bakery\n\nTeller: Els. Interviewer: Jip.\n\nWe took over the bakery on the Vissersdijk in 1978. Your father signed the papers with flour already on his sleeves, that is how sure he was. I was twenty-six and I had never once seen four o'clock in the morning.\n\nThe front of the shop was ice until the ovens caught up. Cold, then warm — that was the whole day. I kneaded with my coat on until six. The smell of the first proof is the smell I will want on my last day. Yeast and warm linen.\n\nThe harbor men came at five thirty, before anyone else was awake. They never spoke before the first roll, not one word, and I learned not to speak either. Mrs. Terpstra came every Thursday for the raisin loaf and paid in coins she counted twice.\n\n[Jip's note: she got up mid-session to find the shop bell in the box under the stairs. Held it the rest of the hour.]\n"
+      },
+      {
+        "path": "sessions/2026-06-02-session.md",
+        "content": "# Session — 2026-06-02 — the strike year\n\nTeller: Els. Interviewer: Jip.\n\nThe strike year was bad. I will not dress it up. Nineteen eighty-four, the flour price doubled in one season and we did not sleep for the mathematics of it. Your father wanted to sell. I said the ovens stay lit.\n\nI took in mending in the afternoons so they could stay lit. Nobody in the town knew. I did the mending in the back room with the curtain closed, and I hid the sewing basket in the flour store when customers came through to the back. Mrs. Terpstra nearly caught me twice.\n\nYou were four that year. You slept in the flour sacks like a cat. The customers asked after you like you were part of the inventory.\n\nWhat I remember best from the bad year is the morning your father hung the strike poster in the window and then baked for the strikers anyway, free, before dawn, so no one would see them take the bread. He never once called it charity. He called it keeping the ovens honest.\n"
+      },
+      {
+        "path": "sessions/2026-06-21-session.md",
+        "content": "# Session — 2026-06-21 — the shop, start to finish\n\nTeller: Els. Interviewer: Jip.\n\nWe opened the doors in the spring of 1979 — I remember because the tulip men still had their stalls out when we swept the front the first time. [Jip's note: session 1 says 1978; she was certain both times. Did the papers get signed in 1978 and the doors open later? Not resolved.]\n\nThe wedding cakes were my department. I made forty-one wedding cakes in twelve years. I counted, because each one went up in the window on the Friday and the whole street came to look. The one I never got to make was for my sister Riet. She called off the wedding two weeks before, and the fruit was already soaking. We ate the fruit at Christmas for three years and never once said what it was for.\n\nMy hands ended it, mostly. And the supermarket on the ring road, a little. We sold in 1990 to the Boonstra boy, who let it become a phone shop, which I have decided not to be bitter about. I kept the shop bell. When I shake it I am twenty-six again, cold then warm.\n"
+      }
+    ],
+    "worker": {
+      "name": "Vera",
+      "role": "Writer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "chapters/chapter-04.md is a substantial woven chapter in the teller's voice: events trace to the sessions, the 1978/1979 contradiction is surfaced rather than silently resolved, and gaps are marked inline.",
+    "deliverables": [
+      {
+        "path": "chapters/chapter-04.md",
+        "kind": "markdown-doc",
+        "minBytes": 2500,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "chapters/chapter-04.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "chapters/chapter-04.md",
+            "pattern": "\\[gap|ask about|another telling|she remembered it as",
+            "flags": "i",
+            "label": "gaps or contradictions marked on the page"
+          },
+          {
+            "kind": "judge",
+            "file": "chapters/chapter-04.md",
+            "rubric": "Every concrete event and detail in the chapter appears in one of the session files — nothing invented. The contradiction between the sessions about when the bakery opened is surfaced in the text, not silently resolved to one year.",
+            "sourceFiles": [
+              "sessions/2026-05-14-session.md",
+              "sessions/2026-06-02-session.md",
+              "sessions/2026-06-21-session.md"
+            ],
+            "label": "faithfulness to session material"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "chapters/chapter-04.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "faithfulness",
+        "description": "Every scene traces to something actually said in a session; no invented events, dates, or dialogue."
+      },
+      {
+        "name": "narrative craft",
+        "description": "The chapter has an arc and momentum — real prose, not stitched-together excerpts."
+      },
+      {
+        "name": "voice preservation",
+        "description": "The teller's phrasings survive — 'cold then warm', 'keeping the ovens honest' — rather than being paraphrased away."
+      },
+      {
+        "name": "gap honesty",
+        "description": "Holes and contradictions are visible on the page (gap marks, both tellings kept), never papered over."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "no invented events",
+    "contradiction surfacing",
+    "teller's voice"
+  ]
+}

package/data/craftbook-templates/ch/character-sheet/versions/1.0.2/craftbook.json

@@ -0,0 +1,94 @@
+{
+  "id": "character-sheet",
+  "name": "Character Sheet",
+  "description": "Lock a character before the pages need them: reference images across the poses and expressions the story calls for, the palette and silhouette written down, and every seed and prompt persisted in a manifest — so page twelve's hero is page one's hero. Locks the character brief FIRST — silhouette, palette, expression and pose list — then generates the reference set with its manifest, then lays the contact sheet anyone can draw from. Use for character sheets, locking a character's look, reference sets before more pages, 'keep them looking the same', and building a comic's cast bible.\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. Write the character brief (tekenaar) — silhouette, palette, expression and pose list from the story → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Generate the reference set (image-generator) — pose and expression references, every seed and prompt persisted\n3. Lay the contact sheet (designer) — one page showing the set with palette, silhouette, and usage notes\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "make a character sheet",
+    "lock the character's look",
+    "reference images for the character",
+    "keep them looking the same",
+    "character bible page"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Write the character brief",
+      "description": "silhouette, palette, expression and pose list from the story",
+      "prompt": "Pin the character down in words before a single image. Step 1: read the story notes in the workspace and the owner's ask — who this character is, what they do in the pages, and any look already established. Step 2: write the identity spec — the silhouette in one sentence (the shape you'd know in shadow), the palette as a short list of specific colors, the two or three features that make them THEM, and what they would never look like. Step 3: list the poses and expressions the pages actually need — at least four (a neutral standing turn, an action pose, and the emotional beats the story calls for). Step 4: write an acceptance-criteria checklist ('at least four references covering the pose and expression list', 'every reference recorded in the manifest with its seed and prompt', 'palette and silhouette written on the sheet', 'the manifest lists only files that really exist'). Call write_task_note with the character name + pose list + 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": "tekenaar",
+      "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": "generate"
+    },
+    {
+      "id": "generate",
+      "name": "Generate the reference set",
+      "description": "pose and expression references, every seed and prompt persisted",
+      "prompt": "Build the reference set under characters/<name>/ (lowercase folder named for the character). Step 1: generate each reference through the project's image capabilities — one image per pose or expression on the brief's list, at least four, every one honoring the identity spec (silhouette, palette, signature features), saved as characters/<name>/ref-<pose>.png. Step 2: persist the manifest at characters/<name>/sheet.json as a top-level JSON array with EXACTLY one record per reference and exactly these fields: \"pose\" (which pose or expression it is), \"file\" (the workspace-relative path, e.g. characters/pip/ref-sit.png), \"seed\" (the seed that made it), and \"prompt\" (the full prompt used). The seeds and prompts ARE the character's reproducibility — a reference without them cannot be drawn again. Step 3: re-list the folder and check the manifest against it — every file listed exists, every image generated is listed. Call write_task_note with the reference count and the manifest path.",
+      "suggestedRole": "image-generator",
+      "next": "sheet"
+    },
+    {
+      "id": "sheet",
+      "name": "Lay the contact sheet",
+      "description": "one page showing the set with palette, silhouette, and usage notes",
+      "prompt": "Lay the contact sheet at characters/<name>/sheet.html — the one page a future artist opens before drawing this character. Step 1: show every reference from the manifest with its pose label. Step 2: write the identity spec onto the sheet — the palette as labeled swatches with color values, the silhouette line, the signature features, and the never-looks-like notes. Step 3: add the usage notes — which reference anchors which kind of panel, and where the seeds and prompts live for regenerating. Step 4: keep it one self-contained file with honest styling — this page gets opened for the life of the book. Call write_task_note with the sheet path.",
+      "suggestedRole": "designer",
+      "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 the character's folder under characters/ and verify every criterion from {{workPath}}/scope.md: at least four references exist covering the brief's pose and expression list; the manifest lists every reference with its pose, file, seed, and prompt — cross-check the file paths against the actual folder listing in both directions, a manifest that lies is the classic failure; the contact sheet shows the set with the palette, silhouette, and usage notes written down; and the whole kit would let a stranger draw this character the same way next month. Write PASS/FAIL per criterion; on any failure, name the reference or the gap and loop back to generate.\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: \"generate\" })` 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",
+      "next": "generate"
+    },
+    {
+      "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/ch/character-sheet/versions/1.0.2/test.json

@@ -0,0 +1,146 @@
+{
+  "schemaVersion": 1,
+  "title": "Character Sheet — Pip locked, seeds and all",
+  "objective": "Measure whether the character-sheet craftbook produces a reusable character kit: reference images covering the story's poses and expressions, a manifest that records pose, file, seed, and prompt for every reference and lists only real files, and a contact sheet with the identity written down.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "we need a character sheet for Pip the dog before doing more pages — a few poses and expresions, and keep whatever you need to draw him the same later",
+  "setup": {
+    "projectName": "The Lighthouse Summer Comic",
+    "about": "Comic maker project. Story notes live under workspace/story. Character kits live under workspace/characters/<name> — Pip's kit is workspace/characters/pip: reference images, the sheet.json manifest, and the sheet.html contact sheet.",
+    "missionObjectives": "The kit must make Pip reproducible: every reference recorded in the manifest with its seed and prompt, the palette and silhouette written down, and the manifest listing only files that really exist. No live services, no real credentials.",
+    "files": [
+      {
+        "path": "story/outline.md",
+        "content": "# The Lighthouse Summer — story notes\n\nOur hero: **Pip**, a small wire-haired terrier with fur the color of wet sand,\none ear permanently up and one folded down, and a mustard-yellow scarf he has\nworn since page one. Short legs, big square head, brush of a tail. In shadow\nyou would know him by the square head and the folded ear.\n\nPip is brave the way small dogs are brave — first through every door, worried\nabout it afterwards. The pages ahead need him: sitting on the harbor wall,\nrunning flat-out along the pier, sniffing at the lighthouse door, plus his\nthree faces — happy (tongue out, ear flopping), worried (ears both down, brow\nknotted), and determined (leaning forward, scarf streaming).\n\nPalette so far: sand-yellow coat, mustard scarf, storm-blue backgrounds.\n"
+      }
+    ],
+    "worker": {
+      "name": "Saar",
+      "role": "Tekenaar"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "characters/pip holds 4+ references, an honest sheet.json manifest with pose/file/seed/prompt per reference, and a contact sheet carrying the palette, silhouette, and usage notes.",
+    "checks": [
+      {
+        "kind": "fileCount",
+        "ext": [
+          "png"
+        ],
+        "min": 4,
+        "dir": "characters/pip"
+      }
+    ],
+    "deliverables": [
+      {
+        "path": "characters/pip/sheet.json",
+        "kind": "json",
+        "minBytes": 300,
+        "checks": [
+          {
+            "kind": "sniff",
+            "file": "characters/pip/sheet.json",
+            "sniff": "json-valid"
+          },
+          {
+            "kind": "recordSchema",
+            "file": "characters/pip/sheet.json",
+            "fields": [
+              {
+                "name": "pose",
+                "type": "nonempty"
+              },
+              {
+                "name": "file",
+                "type": "nonempty"
+              },
+              {
+                "name": "seed"
+              },
+              {
+                "name": "prompt",
+                "type": "nonempty"
+              }
+            ],
+            "minRows": 4,
+            "uniqueBy": "file"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "characters/pip/sheet.json",
+            "pattern": "\"file\"\\s*:\\s*\"([^\"]+)\"",
+            "minCitations": 4,
+            "label": "every manifest file exists on disk"
+          }
+        ]
+      },
+      {
+        "path": "characters/pip/sheet.html",
+        "kind": "html-page",
+        "minBytes": 1200,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 400,
+            "file": "characters/pip/sheet.html"
+          },
+          {
+            "kind": "contains",
+            "file": "characters/pip/sheet.html",
+            "pattern": "Pip",
+            "label": "it is Pip's sheet"
+          },
+          {
+            "kind": "contains",
+            "file": "characters/pip/sheet.html",
+            "pattern": "pose|expression",
+            "flags": "i",
+            "label": "references labeled"
+          },
+          {
+            "kind": "contains",
+            "file": "characters/pip/sheet.html",
+            "pattern": "palette|color|silhouette",
+            "flags": "i",
+            "label": "identity spec written down"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "characters/pip/sheet.html",
+      "kind": "html"
+    },
+    "axes": [
+      {
+        "name": "consistency spec",
+        "description": "Silhouette, palette, and signature features are written down concretely enough that a stranger could draw Pip."
+      },
+      {
+        "name": "coverage",
+        "description": "The references cover the poses and expressions the story notes actually call for."
+      },
+      {
+        "name": "reusability",
+        "description": "Seeds and prompts are persisted per reference — the kit can regenerate Pip, not just remember him."
+      },
+      {
+        "name": "character warmth",
+        "description": "The sheet reads like a beloved character's bible, not a file listing."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "manifest honesty",
+    "persisted seeds and prompts",
+    "pose coverage"
+  ]
+}

package/data/craftbook-templates/ch/character-turnaround/versions/1.0.2/craftbook.json

@@ -0,0 +1,133 @@
+{
+  "id": "character-turnaround",
+  "name": "Character Turnaround",
+  "description": "Give one character the full turnaround treatment: front, side, back, and three-quarter views generated against the same style anchor, every view manifest-recorded with the seed and prompt that made it — the reference every future sprite leans on. Locks the angle list and the style anchor FIRST, then generates the views as one consistent figure, then writes the records and the summary. Use for character turnarounds, 'we need the knight from all sides', sprite reference sets, model sheets for game characters, and locking a character before animation work.\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. Lock the turnaround (assetsmid) — character read, angle list, style anchor, consistency rules → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Generate the views (image-generator) — front, side, back, three-quarter — one figure, one style\n3. Record and summarize (data-analyst) — manifest records with seeds and prompts, plus the 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": [
+    "do a character turnaround",
+    "we need the character from all sides",
+    "model sheet for the character",
+    "turnaround for the sprite work",
+    "front side and back views"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Lock the turnaround",
+      "description": "character read, angle list, style anchor, consistency rules",
+      "prompt": "Lock the turnaround before generating a view. Step 1: read the style notes in assets/ and assets/manifest.json — the palette, proportions, and outline rules the library already lives by, and any existing art of this character. Step 2: write the character read — silhouette in one sentence, the palette entries this character owns, and the two or three features every view must carry. Step 3: lock the angle list — front, side, back, and three-quarter at minimum — and the consistency rule: every view is the SAME figure at the same scale in the same style, generated from the same anchor, not four separate drawings. Step 4: write an acceptance-criteria checklist ('all four angles present at the convention names', 'the figure reads as the same character in every view', 'every view recorded in the manifest with its seed and prompt', 'the manifest stays valid and honest'). Call write_task_note with the character + angle list + 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": "assetsmid",
+      "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": "generate"
+    },
+    {
+      "id": "generate",
+      "name": "Generate the views",
+      "description": "front, side, back, three-quarter — one figure, one style",
+      "prompt": "Generate the views into assets/characters/<name>/ (lowercase folder named for the character). Step 1: build one base prompt from the character read and the style anchor, then vary ONLY the angle per view — front, side, back, three-quarter — through the project's image capabilities, saved as assets/characters/<name>/<angle>.png. Step 2: keep the figure consistent — same proportions, same palette, same scale in frame; a back view that grew a different haircut fails the whole set. Step 3: after each view, check it against the character read and regenerate what drifted. Step 4: note every seed and prompt as you go — the manifest step persists them. Call write_task_note with the views generated and their seeds.",
+      "suggestedRole": "image-generator",
+      "next": "record"
+    },
+    {
+      "id": "record",
+      "name": "Record and summarize",
+      "description": "manifest records with seeds and prompts, plus the summary",
+      "prompt": "Write the turnaround into the library's books. Step 1: append one record per view to the top-level JSON array in assets/manifest.json, keeping existing records untouched — each with exactly these fields: \"id\" (e.g. knight-front), \"file\" (the workspace-relative path, e.g. assets/characters/knight/front.png), \"size\", \"tags\" (include the character's name and 'turnaround'), \"seed\", and \"prompt\" — the seed and prompt are the point: they are how the next sprite gets drawn in the same style. Step 2: re-read the manifest — valid JSON, ids unique, every recorded path resolving to a real file. Step 3: write {{workPath}}/report.md — the character read, the angle list with each view's file, where the seeds live, and the one thing to watch when the sprite work starts. Write {{workPath}}/report.md and call write_task_note with the view count and the manifest total.\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": "data-analyst",
+      "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": "sniff",
+            "file": "assets/manifest.json",
+            "sniff": "json-valid",
+            "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 the character's folder under assets/characters/, assets/manifest.json, and {{workPath}}/report.md against {{workPath}}/scope.md and verify every criterion: all four angles exist at the convention names; the views read as ONE figure — same silhouette, palette, and scale, checked against the character read, a turnaround of four different characters is the classic failure; every view's manifest record carries its seed and prompt and every recorded path resolves to a real file; and the report says where the sprite work picks up. Write PASS/FAIL per criterion; on any failure, name the view or record and loop back to generate.\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: \"generate\" })` 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": "generate"
+    },
+    {
+      "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"
+}