@bendyline/gilde 0.1.38 → 0.1.40

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/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "character-turnaround",
   "role": "general",
+  "category": "media",
   "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.",
   "tags": [

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"
+}

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

@@ -0,0 +1,181 @@
+{
+  "schemaVersion": 1,
+  "title": "Character Turnaround — the knight from all sides, seeds kept",
+  "objective": "Measure whether the character-turnaround craftbook produces front, side, back, and three-quarter views of one consistent figure and records every view in the manifest with the seed and prompt that made it — paths real, ids unique.",
+  "tags": [
+    "data"
+  ],
+  "prompt": "can you do a full turnaround for the knight charcter? we'll need it for the sprite work later",
+  "setup": {
+    "projectName": "Foxglove Platformer Assets",
+    "about": "Asset foundry project. The library's records live at workspace/assets/manifest.json (a JSON array, one record per asset) and the style anchor at workspace/assets/style.md. The knight's turnaround lands in workspace/assets/characters/knight; the summary goes to workspace/report.md.",
+    "missionObjectives": "One figure, four angles, reproducible later: every view generated against the style anchor and recorded with its seed and prompt, and no manifest record pointing at a file that is not there. No live services, no real credentials.",
+    "files": [
+      {
+        "path": "assets/style.md",
+        "content": "# Asset library style anchor\n\n- Character art: 96x128 pixel figures, heroic proportion (5 heads tall).\n- Palette: iron gray #6e7681, brass trim #b08d3f, cloak red #7a2e2e,\n  highlight cream #e8dcb8, outline near-black #22201c.\n- Look: chunky 2px outlines, flat interior shading, one highlight edge\n  top-left. No gradients, no anti-aliased edges.\n- Turnarounds: assets/characters/<name>/<angle>.png — front, side, back,\n  three-quarter — same figure, same scale, same palette in every view.\n- Every shipped asset gets a manifest record: id, file, size, tags,\n  seed, prompt — the seed and prompt are how the next sprite stays in style.\n"
+      },
+      {
+        "path": "assets/manifest.json",
+        "content": "[\n  {\n    \"id\": \"tile-stone-01\",\n    \"file\": \"assets/tiles/tile-stone-01.png\",\n    \"size\": \"32x32\",\n    \"tags\": [\n      \"stone\",\n      \"ground\"\n    ]\n  },\n  {\n    \"id\": \"banner-keep\",\n    \"file\": \"assets/banners/banner-keep.png\",\n    \"size\": \"64x96\",\n    \"tags\": [\n      \"banner\",\n      \"keep\"\n    ]\n  }\n]\n"
+      },
+      {
+        "path": "assets/tiles/tile-stone-01.png",
+        "content": "placeholder tile image: stone ground\n"
+      },
+      {
+        "path": "assets/banners/banner-keep.png",
+        "content": "placeholder banner image: keep banner\n"
+      }
+    ],
+    "worker": {
+      "name": "Ellen",
+      "role": "Assetsmid"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "assets/characters/knight holds the four turnaround views; the manifest records each with seed and prompt; tasks/eval/report.md hands the set to the sprite work.",
+    "checks": [
+      {
+        "kind": "fileCount",
+        "ext": [
+          "png"
+        ],
+        "min": 4,
+        "dir": "assets/characters/knight"
+      }
+    ],
+    "deliverables": [
+      {
+        "path": "assets/manifest.json",
+        "kind": "json",
+        "minBytes": 400,
+        "checks": [
+          {
+            "kind": "sniff",
+            "file": "assets/manifest.json",
+            "sniff": "json-valid"
+          },
+          {
+            "kind": "recordSchema",
+            "file": "assets/manifest.json",
+            "fields": [
+              {
+                "name": "id",
+                "type": "nonempty"
+              },
+              {
+                "name": "file",
+                "type": "nonempty"
+              },
+              {
+                "name": "size",
+                "required": false
+              },
+              {
+                "name": "tags",
+                "required": false
+              },
+              {
+                "name": "seed",
+                "required": false
+              },
+              {
+                "name": "prompt",
+                "required": false
+              }
+            ],
+            "minRows": 6,
+            "uniqueBy": "id"
+          },
+          {
+            "kind": "contains",
+            "file": "assets/manifest.json",
+            "pattern": "\"seed\"",
+            "label": "seeds persisted in the records"
+          },
+          {
+            "kind": "contains",
+            "file": "assets/manifest.json",
+            "pattern": "\"prompt\"",
+            "label": "prompts persisted in the records"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "assets/manifest.json",
+            "pattern": "\"file\"\\s*:\\s*\"([^\"]+)\"",
+            "minCitations": 6,
+            "label": "every recorded file exists on disk"
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/report.md",
+        "kind": "markdown-report",
+        "minBytes": 600,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "front",
+            "flags": "i",
+            "label": "front view named"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "side|profile",
+            "flags": "i",
+            "label": "side view named"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "back",
+            "flags": "i",
+            "label": "back view named"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/report.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "angle coverage",
+        "description": "Front, side, back, and three-quarter are all present at the convention names — a usable model sheet, not a portrait set."
+      },
+      {
+        "name": "consistency",
+        "description": "The views read as one figure — same silhouette, proportions, palette, and scale in every view."
+      },
+      {
+        "name": "silhouette readability",
+        "description": "The knight reads clearly at sprite distance; the shape survives shrinking."
+      },
+      {
+        "name": "manifest quality",
+        "description": "Every view's record carries id, file, seed, and prompt; existing records untouched, ids unique, paths real."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "one consistent figure",
+    "seeds and prompts persisted",
+    "manifest honesty"
+  ]
+}

package/data/craftbook-templates/ch/chart-pack/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "chart-pack",
   "role": "general",
+  "category": "research",
   "name": "Chart Pack from Data",
   "description": "Build a single interactive HTML page of charts that answers a defined set of questions about a dataset. Scopes the questions and the right chart type per question FIRST (so you don't make a pretty chart that answers nothing), then analyzes the data into chart-ready series, then builds one self-contained HTML page rendering every chart with titles, axis labels, and a one-line takeaway caption each. Use this for a dashboard of charts, a visualization pack, a metrics page, or turning a CSV into graphs and plots.",
   "tags": [

package/data/craftbook-templates/ch/chart-pack/versions/1.0.2/craftbook.json

@@ -0,0 +1,160 @@
+{
+  "id": "chart-pack",
+  "name": "Chart Pack from Data",
+  "description": "Build a single interactive HTML page of charts that answers a defined set of questions about a dataset. Scopes the questions and the right chart type per question FIRST (so you don't make a pretty chart that answers nothing), then analyzes the data into chart-ready series, then builds one self-contained HTML page rendering every chart with titles, axis labels, and a one-line takeaway caption each. Use this for a dashboard of charts, a visualization pack, a metrics page, or turning a CSV into graphs and plots.\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 questions (planner) — lock the questions and the chart type that answers each → gated on artifact `{{workPath}}/question-scope.md` (markdown-notes)\n2. Analyze into chart-ready series (data-analyst) — aggregate the data into the exact series each chart needs → gated on `data/series.json` (json)\n3. Build the chart page (developer) — render every chart in one self-contained index.html → gated on `index.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": "question-scope",
+  "triggers": [
+    "make charts from data",
+    "chart pack",
+    "visualize this dataset",
+    "graphs from a csv",
+    "build a charts page"
+  ],
+  "steps": [
+    {
+      "id": "question-scope",
+      "name": "Scope the questions",
+      "description": "lock the questions and the chart type that answers each",
+      "prompt": "Decide WHAT the chart pack must answer before any analysis. Step 1: list 4-8 specific questions a reader has about this data (e.g. 'how did revenue trend by month?', 'which 5 categories are largest?', 'how are values distributed?'). Step 2: for EACH question pick the chart type that answers it best and say why (trend over time -> line; part-to-whole -> bar/stacked, not pie unless <=5 slices; distribution -> histogram; comparison -> grouped bar; relationship -> scatter). Step 3: name the exact columns and aggregation each chart needs. Step 4: write an acceptance-criteria checklist ('one chart per question', 'every chart has a title + axis labels', 'every chart has a one-line takeaway caption', 'chart type matches the question'). Call write_task_note and write the question->chart mapping + checklist to {{workPath}}/question-scope.md.\n\nThe deliverable `{{workPath}}/question-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": "planner",
+      "advanceWhen": {
+        "file": "{{workPath}}/question-scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/question-scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/question-scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "question-scope",
+        "maxAttempts": 3
+      },
+      "next": "analyze"
+    },
+    {
+      "id": "analyze",
+      "name": "Analyze into chart-ready series",
+      "description": "aggregate the data into the exact series each chart needs",
+      "prompt": "Transform the raw data into the precise series each scoped chart needs. Step 1: for each chart, group/aggregate the columns named in the scope (sum, count, average, bucketed histogram) and produce ordered (label, value) arrays. Step 2: sort sensibly (time ascending, categories by magnitude) and cap to a readable count (top-N + 'other' if needed). Step 3: write the computed takeaway caption for each chart from the numbers ('March was the peak at 4.2k, up 38% from Feb'). Step 4: emit the series as data/series.json keyed by chart id so the build phase reads it directly. Call write_task_note with the series summary and the captions.",
+      "suggestedRole": "data-analyst",
+      "advanceWhen": {
+        "file": "data/series.json",
+        "minBytes": 1,
+        "sniff": "json-valid"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "data/series.json",
+            "bytes": 2
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkJsonValid",
+            "scope": "standard",
+            "inputs": {
+              "file": "data/series.json"
+            }
+          }
+        ],
+        "onReject": "analyze",
+        "maxAttempts": 3
+      },
+      "next": "build"
+    },
+    {
+      "id": "build",
+      "name": "Build the chart page",
+      "description": "render every chart in one self-contained index.html",
+      "prompt": "Build a single self-contained index.html that renders every scoped chart from data/series.json. Step 1: use inline <canvas>/SVG drawing or a single inlined chart library — no external network asset that could fail offline; if you embed the series, keep it in sync with the JSON. Step 2: render each chart with its title, labeled axes, readable ticks, and a legend where needed. Step 3: place the one-line takeaway caption under each chart. Step 4: lay the charts out responsively in a grid that reads top-to-bottom in the scoped order. Step 5: ensure no console errors and that charts have real data, not placeholders. On a loop-back, fix only the named gaps. Call write_task_note with the path and chart count.",
+      "suggestedRole": "developer",
+      "consumes": [
+        {
+          "file": "data/series.json"
+        }
+      ],
+      "advanceWhen": {
+        "file": "index.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "index.html",
+            "bytes": 800
+          },
+          {
+            "kind": "htmlLint",
+            "file": "index.html"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html"
+            }
+          }
+        ],
+        "onReject": "build",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Open index.html (render it if a browser capability exists, else trace the source). Verify: there is one chart per scoped question; each chart has a title, labeled axes, and a takeaway caption; the chart type matches the question from the scope; charts render real values from the series, not placeholders; and there are no console errors. Spot-check two charts' values against data/series.json. Write PASS/FAIL per criterion; any FAIL loops back to build.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"build\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "consumes": [
+        {
+          "file": "index.html"
+        }
+      ],
+      "next": "build"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
+      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
+      "suggestedRole": "developer",
+      "terminal": true
+    }
+  ],
+  "version": "1.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"
+}