@bendyline/gilde 0.1.38 → 0.1.39

package/data/craftbook-templates/fa/family-story-chapter/versions/1.0.2/test.json

@@ -0,0 +1,111 @@
+{
+  "schemaVersion": 1,
+  "title": "Family Story Chapter — the emigration years",
+  "objective": "Measure whether the family-story-chapter craftbook writes a narrative chapter grounded entirely in the interviews and tree, with speculation explicitly marked and no invented events or dates.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "could you draft the chapter about the emigration years? use the interviews and the tree — chapters/emigration.md. dont invent anything",
+  "setup": {
+    "projectName": "Dijkstra Family Book",
+    "about": "Family history project for the Dijkstra family. The family record is workspace/tree.json; filed interview transcripts live under workspace/interviews; photo captions are in workspace/notes/photos.md; drafted chapters go under workspace/chapters.",
+    "missionObjectives": "Turn the family archive into book chapters: interviews and tree facts woven into narrative, speculation clearly dressed as speculation, holes in the record acknowledged. Grounded in the seeded sources only; no live services, no real credentials.",
+    "files": [
+      {
+        "path": "tree.json",
+        "content": "{\n  \"family\": \"Dijkstra\",\n  \"updated\": \"2026-06-15\",\n  \"people\": [\n    { \"id\": \"sietse\", \"name\": \"Sietse Dijkstra\", \"born\": 1908, \"died\": 1989, \"note\": \"emigrated to Canada 1952 with the family\" },\n    { \"id\": \"baukje\", \"name\": \"Baukje Dijkstra-Terpstra\", \"born\": 1912, \"died\": 1995 },\n    { \"id\": \"jouke\", \"name\": \"Jouke Dijkstra\", \"born\": 1936, \"died\": 2021, \"note\": \"eldest son; interviewed 2019\" },\n    { \"id\": \"tine\", \"name\": \"Tine Dijkstra\", \"born\": 1940 },\n    { \"id\": \"nel\", \"name\": \"Nel Dijkstra\", \"born\": 1944, \"note\": \"interviewed 2026\" },\n    { \"id\": \"auke\", \"name\": \"Auke Dijkstra\", \"born\": 1911, \"died\": 1984, \"note\": \"Sietse's brother — stayed on the farm at Marrum\" },\n    { \"id\": \"emigration\", \"name\": \"Emigration: Rotterdam to Halifax\", \"born\": 1952, \"note\": \"sailed on the Groote Beer, April 1952\" }\n  ]\n}\n"
+      },
+      {
+        "path": "interviews/nel-2026-05.md",
+        "content": "# Interview — Nel Dijkstra, filed 2026-05-09\n\nTeller: Nel Dijkstra (born 1944). Interviewer: her granddaughter Femke.\n\nI was eight when we left, so what I have are an eight-year-old's memories — I want that said honestly. I remember the quay at Rotterdam and my mother counting us out loud. Four children, and she counted us the whole crossing, at every doorway, the way you count change.\n\nThe decision was the harvest. The 1948 harvest failed and then the 1950 one drowned, and I remember my father Sietse standing in the wet field with his cap off — not praying, just standing. Jouke says the emigration papers were already in the drawer by Christmas 1950. I only remember the suitcases appearing.\n\nWe sailed in April 1952 on the Groote Beer. Eleven days. I was seasick for two and then it was the best holiday of my childhood, which shames me a little to say, because for my mother it was a funeral that kept moving. She left her mother on that quay and they never saw each other again.\n\nHalifax was fog. That is my whole memory of arriving: fog, and a man stamping papers who smiled at us, which nobody had told us to expect.\n\nThe first winter — 1953 now — we were in the hired house at the Bootsma farm and I went to school not speaking a word of English. By spring I dreamed in it. My mother never did. She wrote to her mother every Sunday of her life. The letter that came back in 1954 with the black edge — I remember the sound she made. I will not describe it. Some things are the family's to keep, not the book's.\n\nWhat I cannot tell you is why my uncle Auke stayed. Nobody ever said it in front of me. There was a coldness there. Ask what happened between the brothers, if anyone is left who knows.\n"
+      },
+      {
+        "path": "interviews/jouke-2019.md",
+        "content": "# Interview — Jouke Dijkstra, filed from the 2019 tapes\n\nTeller: Jouke Dijkstra (1936-2021), recorded 2019. Interviewer: Femke, for a school project — the only recording of him we have.\n\nI was sixteen on the boat, which meant I was furious. I had a girl in Marrum and a place on the ice team and my father traded it all for a brochure with a wheat field on it. I did not speak to him from Rotterdam to Halifax. Eleven days of silence — a sixteen-year-old can do it, I promise you.\n\nThe papers were in the drawer from Christmas 1950, whatever anyone tells you about it being sudden. Father and uncle Auke fought about the farm all through 1951. Auke called it deserting. Father called it arithmetic. They were both right, which is why it never healed.\n\nI worked the Bootsma farm beside my father for three years. In 1955 we had our own land — poor land, but ours — and by 1957 father had paid off the passage money and framed the receipt. He hung a receipt on the wall like other men hang a diploma. That tells you everything about him.\n\n1958 I married Ellen, whose people were from Groningen and had crossed in 1951, so between us we had one complete set of memories of home. Father went back to visit exactly once, in 1961, after his mother died. He came home to Canada saying the ditches were smaller than he remembered. He never went again.\n\nWas it worth it? You are asking the wrong question. It was done. We made it worth it afterwards — that is the only direction the arithmetic works.\n"
+      },
+      {
+        "path": "tasks/eval/photos.md",
+        "content": "# Photo captions — emigration box\n\n- Photo 1: The family on the quay at Rotterdam, April 1952. Baukje's mother is the small figure at the left edge, looking away from the camera.\n- Photo 2: The Groote Beer at the pier, 1952. Someone has inked an X over their cabin porthole.\n- Photo 3: The 1951 passport photograph — all six faces, nobody smiling.\n- Photo 4: First Christmas in Canada, 1953, in the hired house at the Bootsma farm. The table is set for eight; the Bootsmas joined them.\n- Photo 5: The framed passage receipt on the parlor wall, photographed 1957.\n- Photo 6: Sietse alone at the farm gate in Marrum, 1961 — the visit home. The last photograph of him in Friesland.\n"
+      }
+    ],
+    "worker": {
+      "name": "Nora",
+      "role": "Writer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "chapters/emigration.md is a substantial narrative chapter whose events and dates all trace to the interviews, tree, and captions, with speculation explicitly marked and the record's holes acknowledged.",
+    "deliverables": [
+      {
+        "path": "chapters/emigration.md",
+        "kind": "markdown-doc",
+        "minBytes": 2500,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "chapters/emigration.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "valuesSubsetOf",
+            "file": "chapters/emigration.md",
+            "sourceFiles": [
+              "interviews/*.md",
+              "tree.json",
+              "tasks/eval/photos.md"
+            ],
+            "pattern": "\\b(1[89]\\d{2}|20\\d{2})\\b",
+            "minMatches": 2,
+            "label": "every year in the chapter exists in the sources"
+          },
+          {
+            "kind": "judge",
+            "file": "chapters/emigration.md",
+            "rubric": "Every concrete event in the chapter traces to the interviews, the tree, or the photo captions; speculation is explicitly marked as speculation (e.g. 'family legend has it', 'she may have'); the unexplained rift between the brothers and Nel's withheld memory are acknowledged as holes, not filled in.",
+            "sourceFiles": [
+              "interviews/nel-2026-05.md",
+              "interviews/jouke-2019.md",
+              "tree.json",
+              "tasks/eval/photos.md"
+            ],
+            "label": "provenance and speculation discipline"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "chapters/emigration.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "narrative",
+        "description": "Reads as a real chapter with arc and momentum — the quay, the crossing, the arithmetic — not a stitched summary of sources."
+      },
+      {
+        "name": "faithfulness",
+        "description": "Every event, date, and detail traces to an interview, the tree, or a caption; the two tellers' differing vantage points are used, not blended into invention."
+      },
+      {
+        "name": "provenance marking",
+        "description": "Speculation is dressed as speculation, and the record's holes (the brothers' rift, the withheld grief) are acknowledged on the page."
+      },
+      {
+        "name": "warmth",
+        "description": "The chapter honors the family's voice — the counted children, the framed receipt — and respects what Nel asked to keep."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "sourced narrative",
+    "marked speculation",
+    "acknowledged gaps"
+  ]
+}

package/data/craftbook-templates/fa/faq-from-docs/versions/1.0.2/craftbook.json

@@ -0,0 +1,119 @@
+{
+  "id": "faq-from-docs",
+  "name": "FAQ from Source Docs",
+  "description": "Build a grounded FAQ page by mining real source documents for the questions users actually ask, then writing tight, accurate answers traced back to the source: it first researches the corpus to extract candidate questions, dedupes and groups them, and ranks by likely frequency, then writes clear question-and-answer pairs where every answer is supported by the docs. Covers FAQ generation, help center questions, support docs, knowledge mining, common questions, and self-service content. Mining the source before writing is the point: a small model that derives questions from the actual docs avoids inventing FAQs nobody asks and answers the docs cannot support.\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. Mine the questions (researcher) — extract, dedupe, group, and rank candidate questions from the docs → gated on artifact `{{workPath}}/mine.md` (markdown-notes)\n2. Write the FAQ (copywriter) — write grounded Q&A pairs in scannable sections → gated on `faq.md` (markdown-doc)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "mine",
+  "triggers": [
+    "create an faq",
+    "faq from docs",
+    "generate help questions",
+    "common questions page",
+    "support faq"
+  ],
+  "steps": [
+    {
+      "id": "mine",
+      "name": "Mine the questions",
+      "description": "extract, dedupe, group, and rank candidate questions from the docs",
+      "prompt": "1) Read all source documents/files in scope. 2) Extract every implicit and explicit question the docs answer — phrase each as a real user would ask it ('How do I reset my password?'), not as a doc heading. 3) Dedupe near-identical questions and group them into 3-6 topical sections. 4) Rank questions within each section by likely frequency/importance. 5) For each kept question, note the source location (file + section/anchor) that supports the answer, so the writer can ground it. Write an acceptance-criteria checklist (e.g. 'every question is answerable from the docs'; 'questions phrased in user language'; 'grouped into clear sections'; 'no fabricated questions or answers'; 'each Q maps to a source'). Use write_task_note for the question bank with sources + checklist, and write the same to the produces path. No final answers yet.\n\nThe deliverable `{{workPath}}/mine.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": "researcher",
+      "advanceWhen": {
+        "file": "{{workPath}}/mine.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/mine.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/mine.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "mine",
+        "maxAttempts": 3
+      },
+      "next": "write"
+    },
+    {
+      "id": "write",
+      "name": "Write the FAQ",
+      "description": "write grounded Q&A pairs in scannable sections",
+      "prompt": "Write the FAQ from the mined question bank. 1) Organize into the grouped sections, each with an H2 header. 2) For each question, write it as an H3 (or bold) line, then a concise answer (1-4 sentences) drawn strictly from the source docs — no speculation beyond what the docs support. 3) Where a doc has step-by-step detail, render the answer as a short numbered list. 4) Keep a consistent, plain, reassuring support voice. 5) Add a short intro line at the top and, where useful, a 'see also' link to the source doc. Output GitHub-flavored markdown. Save to the produces path and note total Q&A count and section count.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "faq.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "faq.md",
+            "bytes": 500
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkContains",
+            "scope": "standard",
+            "inputs": {
+              "file": "faq.md",
+              "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+              "flags": "i"
+            }
+          }
+        ],
+        "onReject": "write",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Read faq.md and cross-check against the mined question bank and the source docs. Check EACH criterion and write PASS/FAIL: (a) every answer is supported by the source docs (spot-check 4-5 against their cited source); (b) questions are phrased in natural user language; (c) Q&As are grouped into clear sections with headers; (d) no fabricated questions or unsupported answers; (e) answers are concise and consistently voiced. An FAQ with invented or unsupported answers FAILS — loop back to write and name the offending entries.\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: \"write\" })` 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": "faq.md"
+        }
+      ],
+      "next": "write"
+    },
+    {
+      "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/fa/faq-from-docs/versions/1.0.2/test.json

@@ -0,0 +1,113 @@
+{
+  "schemaVersion": 1,
+  "title": "FAQ from Source Docs smoke eval",
+  "objective": "Self-contained smoke eval for the FAQ from Source Docs craftbook using the corpus generic harness.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "We need a FAQ from source docs for the returns-desk work. The backgound info is in source/brief.md — have a look and write it up in report.md.",
+  "setup": {
+    "projectName": "FAQ from Source Docs Eval",
+    "about": "Self-contained eval project for faq-from-docs. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/report.md.",
+    "missionObjectives": "Use the FAQ from Source Docs craftbook/template, read the seeded local fixtures, and write report.md without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# FAQ from Source Docs 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: faq-from-docs - FAQ from Source Docs.\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Writer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "report.md is a source-grounded markdown artifact with required facts and actions.",
+    "deliverables": [
+      {
+        "path": "report.md",
+        "kind": "markdown-report",
+        "minBytes": 1000,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "source/brief\\.md|Brief",
+            "flags": "i",
+            "label": "cite or name the seeded source"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "18\\b[\\s\\S]{0,30}\\bSKUs",
+            "flags": "i",
+            "label": "include the 18-SKU pilot scope"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "18\\s*hours|6\\s*hours",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "14\\.2%|8\\.9%",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "status silence|photo submission",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "automated status emails|barcode|Finance",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "report.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "grounding",
+        "description": "Seeded facts appear faithfully and the source is cited."
+      },
+      {
+        "name": "structure",
+        "description": "Sections progress logically for the artifact class."
+      },
+      {
+        "name": "completeness",
+        "description": "Required elements (risks, next actions, scope) are all present."
+      },
+      {
+        "name": "tone",
+        "description": "The register fits the audience and artifact class."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "source-grounded prose",
+    "section structure",
+    "next-action clarity"
+  ]
+}

package/data/craftbook-templates/fa/favicon-set/versions/1.0.2/craftbook.json

@@ -0,0 +1,158 @@
+{
+  "id": "favicon-set",
+  "name": "Favicon & App-Icon Set",
+  "description": "Generate the complete favicon and app-icon set a modern site needs — the multi-size favicon, Apple touch icon, Android/maskable icons, and the web app manifest plus the exact HTML link/meta tags — from a single source mark, ensuring the icon stays legible at 16px and the maskable variant survives platform cropping. Lock FIRST the source mark, the exact size matrix, and the safe-area/padding rules (maskable icons need extra padding or platforms clip them) because favicon sets fail when the icon is illegible tiny or gets cropped on Android; then generate every size and emit the manifest + install snippet. Covers favicons, app icons, PWA icons, touch icons, maskable icons, and the web app manifest.\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 icon set (planner) — lock source mark, size matrix, and maskable safe-area → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Generate the icons (image-generator) — render every size, including a safe-area maskable → gated on `assets` (image-set)\n3. Manifest & install snippet (developer) — emit manifest.json and the HTML head snippet → 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": "scope",
+  "triggers": [
+    "generate a favicon set",
+    "make app icons",
+    "pwa icons and manifest",
+    "apple touch icon",
+    "favicon from my logo"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the icon set",
+      "description": "lock source mark, size matrix, and maskable safe-area",
+      "prompt": "1) Identify the source mark/logo (or a simplified glyph version suited to tiny sizes) and the brand background color. 2) Lock the SIZE MATRIX: favicon 16/32/48 (ICO + PNG), apple-touch-icon 180, Android/PWA 192 and 512, plus a 512 MASKABLE variant. 3) Lock the maskable SAFE-AREA rule: the icon content must sit within the central ~80% (≈10% padding each side) so Android's mask doesn't clip it, with a solid background fill. 4) Decide the manifest fields (name, short_name, theme_color, background_color, icons array with purpose: any/maskable). 5) Write an acceptance-criteria checklist: 'all matrix sizes produced', 'icon is legible at 16px (simplified if needed)', 'maskable variant keeps content in the safe area on a filled background', 'manifest.json is valid and lists every icon with correct sizes/purpose', 'the HTML link/meta snippet references the real files'. 6) Record matrix + rules + checklist via write_task_note AND to {{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": "planner",
+      "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 icons",
+      "description": "render every size, including a safe-area maskable",
+      "prompt": "1) Read scope.md. 2) Produce each size in the matrix from the source mark, saving into assets/ with conventional names (favicon-16.png, favicon-32.png, apple-touch-icon.png, icon-192.png, icon-512.png, maskable-512.png, and favicon.ico). 3) For the smallest sizes, use the SIMPLIFIED glyph so it stays legible at 16px — fine detail that vanishes tiny must be dropped. 4) For the maskable variant, render the icon within the central safe area on a solid background fill so platform masks (circle/squircle) never clip it. 5) Keep the mark and colors consistent across sizes. 6) Eyeball the 16px and the masked 512 to confirm legibility and no clipping. write_task_note the produced files. Good looks like: a crisp tiny favicon and a maskable icon that survives any crop.",
+      "suggestedRole": "image-generator",
+      "advanceWhen": {
+        "file": "assets",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "fileCount",
+            "ext": [
+              "png",
+              "jpg",
+              "jpeg",
+              "svg",
+              "webp"
+            ],
+            "min": 3,
+            "dir": "assets"
+          }
+        ],
+        "onReject": "generate",
+        "maxAttempts": 3
+      },
+      "next": "manifest"
+    },
+    {
+      "id": "manifest",
+      "name": "Manifest & install snippet",
+      "description": "emit manifest.json and the HTML head snippet",
+      "prompt": "1) Write manifest.json with name, short_name, theme_color, background_color, and an icons array entry for each generated icon (src, sizes, type, and purpose: \"any\" or \"maskable\" for the maskable one) — referencing the real files in assets/. 2) Build index.html whose <head> contains the full install snippet: the favicon link tags (ICO + PNG sizes), the apple-touch-icon link, the manifest link, and a theme-color meta — all pointing at the real assets/ paths — and whose body shows a small preview rendering each icon at its native size plus a 16px row. 3) Validate manifest.json parses and every src resolves to a real file. 4) On a loop-back, fix only named gaps (missing icon entry, wrong purpose, broken path). 5) write_task_note the manifest and page paths. The gated deliverable is index.html.",
+      "suggestedRole": "developer",
+      "consumes": [
+        {
+          "file": "assets"
+        }
+      ],
+      "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": "manifest",
+        "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": "1) Open assets/ and confirm every matrix size exists (16/32/48, 180, 192, 512, maskable-512, favicon.ico) (PASS/FAIL). 2) Open manifest.json — it parses, theme/background colors set, and every icon listed with correct sizes and purpose (any vs maskable) pointing at real files (PASS/FAIL). 3) Open index.html and verify the head snippet links the favicon, apple-touch-icon, and manifest at real paths; view the 16px preview row — is the icon legible tiny (PASS/FAIL)? 4) Inspect the maskable icon — is content within the safe area on a filled background so it won't clip (PASS/FAIL)? 5) Write PASS/FAIL per criterion. Missing sizes, illegible 16px, clipped maskable, or a broken manifest → loop back to manifest (or generate if an icon is wrong).\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: \"manifest\" })` 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": "manifest"
+    },
+    {
+      "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/fa/favicon-set/versions/1.0.2/test.json

@@ -0,0 +1,106 @@
+{
+  "schemaVersion": 1,
+  "title": "Favicon & App-Icon Set smoke eval",
+  "objective": "Self-contained smoke eval for the Favicon & App-Icon Set craftbook using the media generic harness.",
+  "tags": [
+    "media"
+  ],
+  "prompt": "Our media files are all listd in source/media-index.csv. Can you put together the production plan for them as media-plan.json?",
+  "setup": {
+    "projectName": "Favicon & App-Icon Set Eval",
+    "about": "Self-contained eval project for favicon-set. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/media-plan.json.",
+    "missionObjectives": "Use the Favicon & App-Icon Set craftbook/template, read the seeded local fixtures, and write media-plan.json without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Favicon & App-Icon Set 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: favicon-set - Favicon & App-Icon Set.\n"
+      },
+      {
+        "path": "source/media-index.csv",
+        "content": "filename,type,duration_or_size,notes\npilot-interview.wav,audio,00:02:15,mentions response time and status silence\nreturns-desk.png,image,1600x900,shows intake form and photo evidence step\nlaunch-clip.mp4,video,00:01:05,shows barcode exception handling\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Producer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "media-plan.json is a valid JSON media-production manifest grounded in seeded fixture metadata.",
+    "deliverables": [
+      {
+        "path": "media-plan.json",
+        "kind": "json",
+        "minBytes": 700,
+        "checks": [
+          {
+            "kind": "sniff",
+            "file": "media-plan.json",
+            "sniff": "json-valid"
+          },
+          {
+            "kind": "contains",
+            "file": "media-plan.json",
+            "pattern": "pilot-interview\\.wav|returns-desk\\.png|launch-clip\\.mp4",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "media-plan.json",
+            "pattern": "outputs|assets|steps|cues|verification",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "media-plan.json",
+            "pattern": "accessibility|alt|caption|transcript|metadata",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "media-plan.json",
+      "kind": "json"
+    },
+    "axes": [
+      {
+        "name": "completeness",
+        "description": "The manifest covers sources, outputs, and processing steps end to end."
+      },
+      {
+        "name": "grounding",
+        "description": "Only seeded media fixtures are referenced, with faithful metadata."
+      },
+      {
+        "name": "accessibility",
+        "description": "Alt text, captions, or transcripts are planned wherever the class requires."
+      },
+      {
+        "name": "precision",
+        "description": "Timestamps, crops, and cues are specific enough to execute."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "media fixture handling",
+    "structured manifest",
+    "verification metadata"
+  ],
+  "extensions": {
+    "legacySimulators": [
+      {
+        "id": "favicon-set-media-fixtures",
+        "kind": "data-source",
+        "status": "implemented",
+        "description": "Seeded local media index replacing real audio, video, image generation, and external media metadata services."
+      }
+    ]
+  }
+}