@bendyline/gilde 0.1.38 → 0.1.39

package/data/craftbook-templates/pr/price-tracker/versions/1.0.2/test.json

@@ -0,0 +1,153 @@
+{
+  "schemaVersion": 1,
+  "title": "Offline price tracker with fake product API",
+  "objective": "Use a simulator-backed HTTP/CLI fixture so the price-tracker craftbook can fetch deterministic product prices, update history, and compute lows.",
+  "tags": [
+    "data"
+  ],
+  "prompt": "In the `Price Tracker Eval` project, read `fixtures/product-feed-day1.json` and `fixtures/product-feed-day2.json`, then write `tracker.mjs`, `price-history.json`, and `run-log.md`. The tracker should be offline and deterministic: normalize numeric prices, append history for two days, dedupe repeated same-day runs, compute lowest price per SKU, and log the failing SKU.",
+  "setup": {
+    "projectName": "Price Tracker Eval",
+    "about": "Self-contained eval project for the price-tracker craftbook. Fixture product feeds stand in for a fake HTTP API.",
+    "missionObjectives": "Build an offline tracker script and materialize expected two-day history from the seeded feeds. No internet access or real product pages.",
+    "files": [
+      {
+        "path": "fixtures/product-feed-day1.json",
+        "content": "{\n  \"date\": \"2026-06-27\",\n  \"products\": [\n    {\n      \"sku\": \"COOP-BOX-S\",\n      \"name\": \"Small Produce Box\",\n      \"price\": \"$29.99\",\n      \"available\": true\n    },\n    {\n      \"sku\": \"COOP-BOX-L\",\n      \"name\": \"Large Produce Box\",\n      \"price\": \"$49.99\",\n      \"available\": true\n    },\n    {\n      \"sku\": \"JAM-APRICOT\",\n      \"name\": \"Apricot Jam\",\n      \"price\": \"$8.50\",\n      \"available\": true\n    },\n    {\n      \"sku\": \"ERR-404\",\n      \"error\": \"upstream 404\"\n    }\n  ]\n}"
+      },
+      {
+        "path": "fixtures/product-feed-day2.json",
+        "content": "{\n  \"date\": \"2026-06-28\",\n  \"products\": [\n    {\n      \"sku\": \"COOP-BOX-S\",\n      \"name\": \"Small Produce Box\",\n      \"price\": \"$27.99\",\n      \"available\": true\n    },\n    {\n      \"sku\": \"COOP-BOX-L\",\n      \"name\": \"Large Produce Box\",\n      \"price\": \"$52.49\",\n      \"available\": true\n    },\n    {\n      \"sku\": \"JAM-APRICOT\",\n      \"name\": \"Apricot Jam\",\n      \"price\": \"$8.50\",\n      \"available\": false\n    },\n    {\n      \"sku\": \"ERR-404\",\n      \"error\": \"upstream 404\"\n    }\n  ]\n}"
+      }
+    ],
+    "worker": {
+      "name": "Sanne",
+      "role": "Developer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The tracker writes a runnable script, a valid append-only history file, normalized numeric prices, dedupe-per-day behavior, and failure logs.",
+    "deliverables": [
+      {
+        "path": "tracker.mjs",
+        "kind": "code-module",
+        "minBytes": 1200,
+        "checks": [
+          {
+            "kind": "esmImports",
+            "file": "tracker.mjs"
+          },
+          {
+            "kind": "contains",
+            "file": "tracker.mjs",
+            "pattern": "product-feed-day1|product-feed-day2"
+          },
+          {
+            "kind": "contains",
+            "file": "tracker.mjs",
+            "pattern": "Number\\.parseFloat|parseFloat|replace",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tracker.mjs",
+            "pattern": "dedupe|Map|Set|same-day|date",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tracker.mjs",
+            "pattern": "lowest|minPrice|low",
+            "flags": "i"
+          }
+        ]
+      },
+      {
+        "path": "price-history.json",
+        "kind": "json",
+        "minBytes": 700,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "price-history.json",
+            "pattern": "COOP-BOX-S|COOP-BOX-L|JAM-APRICOT"
+          },
+          {
+            "kind": "contains",
+            "file": "price-history.json",
+            "pattern": "2026-06-27|2026-06-28"
+          },
+          {
+            "kind": "contains",
+            "file": "price-history.json",
+            "pattern": "29\\.99|27\\.99|49\\.99|52\\.49|8\\.5"
+          },
+          {
+            "kind": "contains",
+            "file": "price-history.json",
+            "pattern": "lowest|minPrice|low",
+            "flags": "i"
+          }
+        ]
+      },
+      {
+        "path": "run-log.md",
+        "kind": "markdown-notes",
+        "minBytes": 500,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "run-log.md",
+            "pattern": "ERR-404|upstream 404"
+          },
+          {
+            "kind": "contains",
+            "file": "run-log.md",
+            "pattern": "dedupe|idempotent|same-day",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "run-log.md",
+            "pattern": "normalized|numeric|price",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tracker.mjs",
+      "kind": "typescript"
+    },
+    "axes": [
+      {
+        "name": "accuracy",
+        "description": "Computed figures are correct against the seeded records."
+      },
+      {
+        "name": "grounding",
+        "description": "Every claim traces to the seeded data — nothing invented."
+      },
+      {
+        "name": "structure",
+        "description": "Tables and sections make the analysis checkable at a glance."
+      },
+      {
+        "name": "actionability",
+        "description": "Recommendations follow from the findings and are concretely doable."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "custom simulator",
+    "script correctness",
+    "idempotency",
+    "error handling"
+  ]
+}

package/data/craftbook-templates/pr/pricing-page/versions/1.0.2/craftbook.json

@@ -0,0 +1,196 @@
+{
+  "id": "pricing-page",
+  "name": "Pricing Page",
+  "description": "Build a single pricing or plan-comparison page with tiered plan cards, a feature comparison, a highlighted recommended plan, and optionally a monthly/annual toggle that updates prices. Scopes the plans, features, and pricing model first, designs a comparison layout that makes the recommended tier obvious, writes the plan copy, then builds responsive HTML with a working billing toggle. Pricing pages fail when the toggle does not update prices or the tiers are not genuinely comparable, so the offer-scope phase locks the exact plans and feature matrix before any markup.\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. Offer scope (planner) — plans, feature matrix, pricing model, recommended tier → gated on artifact `{{workPath}}/offer-scope.md` (markdown-notes)\n2. Visual design (visual-designer) — comparison layout + recommended-plan emphasis → gated on artifact `{{workPath}}/visual-design.md` (markdown-notes)\n3. Copywriting (copywriter) — plan names, taglines, feature labels, CTA → gated on artifact `{{workPath}}/copy.md` (markdown-notes)\n4. Build (developer) — implement index.html with plan cards + toggle → gated on `index.html` (html-marketing-site)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "offer-scope",
+  "triggers": [
+    "pricing page",
+    "plan comparison",
+    "subscription tiers",
+    "pricing table",
+    "build a pricing page",
+    "compare plans"
+  ],
+  "steps": [
+    {
+      "id": "offer-scope",
+      "name": "Offer scope",
+      "description": "plans, feature matrix, pricing model, recommended tier",
+      "prompt": "Lock the pricing offer. (1) Define each plan (name, price, who it is for) — typically 3 tiers. (2) Build the feature matrix: the rows of features and which plans include each (yes/no/limit). (3) Mark the ONE recommended/most-popular plan. (4) Decide the billing model: flat, or monthly/annual with the annual discount and the exact prices for each. (5) Each plan needs a CTA. (6) Write an acceptance-criteria checklist of 5-8 items, e.g. 'each plan shows its price and CTA', 'the recommended plan is visually distinguished', 'the feature comparison is present and consistent', 'a monthly/annual toggle updates all prices' (if applicable), 'responsive at 375px and 1280px', 'no console errors'. Write to {{workPath}}/offer-scope.md and via write_task_note. No design or HTML yet.\n\nThe deliverable `{{workPath}}/offer-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}}/offer-scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/offer-scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/offer-scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "offer-scope",
+        "maxAttempts": 3
+      },
+      "next": "visual-design"
+    },
+    {
+      "id": "visual-design",
+      "name": "Visual design",
+      "description": "comparison layout + recommended-plan emphasis",
+      "prompt": "Design the pricing layout. (1) Pick a palette (hex) with an accent reserved for the recommended plan and CTAs. (2) Lay out the plan cards side by side with the recommended one emphasized (border, badge, scale). (3) Design the feature comparison (per-card lists or a comparison table) so plans are easy to scan against each other. (4) Design the billing toggle and the CTA buttons. (5) Specify the responsive reflow (cards stack on mobile). Self-contained CSS. Write the visual spec to {{workPath}}/visual-design.md and via write_task_note. No HTML yet.\n\nThe deliverable `{{workPath}}/visual-design.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": "visual-designer",
+      "advanceWhen": {
+        "file": "{{workPath}}/visual-design.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/visual-design.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/visual-design.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "visual-design",
+        "maxAttempts": 3
+      },
+      "next": "copy"
+    },
+    {
+      "id": "copy",
+      "name": "Copywriting",
+      "description": "plan names, taglines, feature labels, CTA",
+      "prompt": "Write the pricing copy. (1) A page headline and subhead. (2) For each plan: a one-line tagline of who it is for. (3) Clear, consistent feature-row labels. (4) The CTA label per plan (and a note on the most-popular badge text). Keep it benefit-oriented and scannable. Write the copy keyed by plan/section to {{workPath}}/copy.md and via write_task_note.\n\nThe deliverable `{{workPath}}/copy.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "{{workPath}}/copy.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/copy.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/copy.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "copy",
+        "maxAttempts": 3
+      },
+      "next": "build"
+    },
+    {
+      "id": "build",
+      "name": "Build",
+      "description": "implement index.html with plan cards + toggle",
+      "prompt": "Implement index.html with inline CSS/JS to the offer, visual spec, and copy. (1) Palette as CSS variables; render the plan cards with prices, taglines, feature lists/table, and CTAs. (2) Visually distinguish the recommended plan (badge + emphasis). (3) If monthly/annual was scoped, build a toggle whose JS swaps every plan's displayed price to the right value. (4) Make the feature comparison consistent and scannable. (5) Responsive at 375px and 1280px; vanilla, no CDN. On a loop-back, fix only the named gaps without regressing passing criteria. write_task_note the path and passing criteria.",
+      "suggestedRole": "developer",
+      "advanceWhen": {
+        "file": "index.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "index.html",
+            "bytes": 1200
+          },
+          {
+            "kind": "htmlLint",
+            "file": "index.html"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html"
+            }
+          },
+          {
+            "name": "checkCssMinBytes",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html",
+              "minBytes": 600
+            }
+          }
+        ],
+        "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": "Evaluate the pricing page. Open/render index.html, flip the billing toggle if present, and resize. Check EACH criterion from {{workPath}}/offer-scope.md and write PASS/FAIL with a reason: does each plan show price and CTA, is the recommended plan visually distinguished, is the feature comparison present and consistent, does the monthly/annual toggle update ALL prices correctly, is it responsive? A toggle that does not update prices, or inconsistent feature rows, is a FAIL — loop 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"
+}

package/data/craftbook-templates/pr/pricing-page/versions/1.0.2/test.json

@@ -0,0 +1,100 @@
+{
+  "schemaVersion": 1,
+  "title": "Pricing Page smoke eval",
+  "objective": "Self-contained smoke eval for the Pricing Page craftbook using the html-page generic harness.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "Can you biuld us a little page for this? The content notes are in source/page-content.md. Save it as index.html — one file, nothing fancy needed on our end.",
+  "setup": {
+    "projectName": "Pricing Page Eval",
+    "about": "Self-contained eval project for pricing-page. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/index.html.",
+    "missionObjectives": "Use the Pricing Page craftbook/template, read the seeded local fixtures, and write index.html without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Pricing Page 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: pricing-page - Pricing Page.\n"
+      },
+      {
+        "path": "source/page-content.md",
+        "content": "# Boreal Desk Support Board\n\nBuild content around a support operations board. Required labels: Open issues, Status silence, Response time, Refund leakage, Next action. Required metric text: 18 hours to 6 hours and 14.2% to 8.9%.\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Developer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "index.html is a source-grounded self-contained HTML page/tool.",
+    "deliverables": [
+      {
+        "path": "index.html",
+        "kind": "html-page",
+        "minBytes": 3000,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "index.html"
+          },
+          {
+            "kind": "jsParses",
+            "file": "index.html"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "Boreal|Support Board|returns",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "18\\s*hours|6\\s*hours|14\\.2%|8\\.9%",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "button|input|filter|tab|card|section|nav",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "index.html",
+      "kind": "html"
+    },
+    "axes": [
+      {
+        "name": "structure",
+        "description": "Layout and hierarchy fit the content; sections are scannable and coherent."
+      },
+      {
+        "name": "grounding",
+        "description": "Seeded source content is used faithfully — no invented facts or dropped requirements."
+      },
+      {
+        "name": "interactivity",
+        "description": "Controls and states the page claims to offer actually work."
+      },
+      {
+        "name": "polish",
+        "description": "Styling is intentional and responsive rather than unstyled or broken."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "self-contained UI",
+    "source grounding",
+    "responsive structure"
+  ]
+}

package/data/craftbook-templates/pr/product-descriptions/versions/1.0.2/craftbook.json

@@ -0,0 +1,117 @@
+{
+  "id": "product-descriptions",
+  "name": "Bulk Product Descriptions",
+  "description": "Generate consistent, on-brand product descriptions in bulk from a list of products and their attributes: it first locks the brand voice, the field schema (title, short blurb, long description, bullet features, SEO meta), and a worked exemplar, then drafts every product to that exact template so the whole catalog reads as one voice. Covers ecommerce product copy, catalog descriptions, Shopify/Amazon listings, bulk SKU copywriting, and product detail pages. Locking the voice and one exemplar before the batch is the key move: it stops a small model from drifting in tone and structure across items, which is the classic failure of bulk copy.\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. Voice & schema scope (planner) — lock brand voice, the per-product field schema, and one exemplar → gated on artifact `{{workPath}}/voice-scope.md` (markdown-notes)\n2. Draft all descriptions (copywriter) — write every product to the locked template and voice → gated on `product-descriptions.json` (json)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "voice-scope",
+  "triggers": [
+    "write product descriptions",
+    "bulk product copy",
+    "ecommerce listings",
+    "shopify descriptions",
+    "catalog copy"
+  ],
+  "steps": [
+    {
+      "id": "voice-scope",
+      "name": "Voice & schema scope",
+      "description": "lock brand voice, the per-product field schema, and one exemplar",
+      "prompt": "1) Define the brand voice in 3-5 adjectives plus 2 do's and 2 don'ts (e.g. 'warm, expert, concise; do use sensory detail; don't use hype superlatives'). 2) Define the per-product field schema and length limits: title (<=60 chars), short blurb (1 sentence), long description (40-80 words), 3-5 feature bullets, and an SEO meta description (<=155 chars). 3) Identify the product input (a list, CSV, or attributes) and confirm every product has the data the schema needs. 4) Write ONE fully worked exemplar for a sample product, filling every field, as the template the batch must match. Write an acceptance-criteria checklist (e.g. 'every product has all schema fields'; 'all fields within length limits'; 'consistent voice across items'; 'no invented specs not in the input'; 'titles are unique and descriptive'). Use write_task_note for the voice + schema + exemplar + checklist, and write the same to the produces path. No batch yet.\n\nThe deliverable `{{workPath}}/voice-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}}/voice-scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/voice-scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/voice-scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "voice-scope",
+        "maxAttempts": 3
+      },
+      "next": "draft"
+    },
+    {
+      "id": "draft",
+      "name": "Draft all descriptions",
+      "description": "write every product to the locked template and voice",
+      "prompt": "Produce a description for EVERY product in the input, each matching the exemplar's schema and the locked voice. 1) For each product, fill every field: title, short blurb, long description, feature bullets, SEO meta. 2) Use only attributes present in the input — never invent specs, materials, or measurements. 3) Keep the voice identical across all items; vary the wording, not the tone. 4) Respect every length limit. 5) Output a single valid JSON array, one object per product, with consistent keys matching the schema (e.g. {\"sku\", \"title\", \"shortBlurb\", \"longDescription\", \"bullets\", \"seoMeta\"}). Do not skip any product. Save to the produces path and note the product count covered.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "product-descriptions.json",
+        "minBytes": 1,
+        "sniff": "json-valid"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "product-descriptions.json",
+            "bytes": 2
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkJsonValid",
+            "scope": "standard",
+            "inputs": {
+              "file": "product-descriptions.json"
+            }
+          }
+        ],
+        "onReject": "draft",
+        "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": "Parse product-descriptions.json (must be valid JSON) and grade against the checklist. Check EACH and write PASS/FAIL: (a) every product from the input has an object with all schema fields populated; (b) all fields are within their length limits; (c) the voice and structure are consistent across items (spot-check 3-4); (d) no invented specs absent from the input; (e) titles are unique and descriptive. A batch that drifts in tone, skips products, or fabricates attributes FAILS — loop back to draft and name the offending SKUs.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"draft\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "consumes": [
+        {
+          "file": "product-descriptions.json"
+        }
+      ],
+      "next": "draft"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
+      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
+      "suggestedRole": "developer",
+      "terminal": true
+    }
+  ],
+  "version": "1.0.2",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  },
+  "minGezelVersion": "1.26233"
+}