@bendyline/gilde 0.1.38 → 0.1.40

package/data/craftbook-templates/na/narrated-slideshow/versions/1.1.2/craftbook.json

@@ -0,0 +1,193 @@
+{
+  "id": "narrated-slideshow",
+  "name": "Animated Content Slideshow",
+  "description": "Turn source content into a real MP4 slideshow video and animated GIF without recruiting a Developer to build an HTML player. A planner locks the story and one message per scene. A copywriter writes slideshow.md as ordinary Markdown with one H1 per scene. A video specialist uses the pre-authorized DocBlocks toolset to perform one atomic MP4+GIF conversion, preview representative frames, repair the Markdown when needed, and save {{workPath}}/slideshow.mp4 and {{workPath}}/slideshow.gif in the artifacts drawer.\n\nThe source of truth is Markdown. DocBlocks selects compatible templates automatically; get_authoring_context is optional when exact animation, theme, or target guidance is useful. The rendered targets require the DocBlocks media runtime (Chromium and FFmpeg); if unavailable, report that blocker instead of substituting HTML.\n\nWorking files under {{workPath}}/, reviews/, and reports/ live in the project artifacts drawer and must be read and written with the artifact tools. User-facing source files remain in the workspace.",
+  "entryStepId": "outline",
+  "triggers": [
+    "animated slideshow",
+    "turn this content into a video",
+    "make an animated gif from this content",
+    "content to mp4",
+    "markdown to video",
+    "explainer slideshow",
+    "make a video from slides"
+  ],
+  "toolsets": [
+    {
+      "toolsetId": "docblocks",
+      "sourceId": "bundled",
+      "autoAllow": true,
+      "reason": "convert slideshow.md to MP4 and animated GIF, preview frames, and save both rendered files without a prompt per call"
+    }
+  ],
+  "steps": [
+    {
+      "id": "outline",
+      "name": "Outline the scenes",
+      "description": "Lock the audience, story arc, one message per scene, and media acceptance criteria.",
+      "prompt": "Plan the animated slideshow before authoring it. 1. Identify the audience, viewing context, aspect/orientation, and one takeaway. 2. Draft 6-12 scenes unless the user requests another length: each scene needs a title, one message, 2-4 short on-screen points, and an optional caption line. 3. Mark where an existing image or small table genuinely helps; do not invent or download unapproved assets. 4. Choose landscape or portrait and a restrained motion style. 5. Write acceptance criteria: every outlined scene appears once and in order, text stays readable at video size, source facts remain grounded, frames show a consistent theme, the MP4 plays, the GIF loops, and both real files are saved in artifacts. Write {{workPath}}/outline.md and call write_task_note with scene count, orientation, and takeaway. Do not build HTML or media bytes.\n\nStore `{{workPath}}/outline.md` in the artifacts drawer with `write_artifact`, then verify it with `read_artifact`; do not write this working file to the workspace.",
+      "suggestedRole": "planner",
+      "advanceWhen": {
+        "file": "{{workPath}}/outline.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/outline.md",
+            "bytes": 180,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/outline.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "outline",
+        "maxAttempts": 3
+      },
+      "next": "write"
+    },
+    {
+      "id": "write",
+      "name": "Write the Markdown slideshow",
+      "description": "Write slideshow.md with one H1 heading per scene.",
+      "prompt": "Write slideshow.md to {{workPath}}/outline.md. 1. Use exactly one `#` level-one heading per scene; each H1 is a deliberate scene boundary. Do not add `---` separators unless a visible horizontal rule is intended. 2. Under each H1, use 2-4 short bullet phrases, a compact table, or a brief caption—not paragraphs. 3. Bold the load-bearing fact or phrase. 4. Use only source-grounded facts and existing workspace assets with meaningful alt text. 5. Keep the first scene a title/setup and the final scene the takeaway or next action. 6. On loop-back, repair only the frames the reviewer names. Call write_task_note with the path and H1 scene count. Do not create HTML, JavaScript, MP4, GIF, or base64.\n\nOpen `{{workPath}}/outline.md` from the artifacts drawer with `read_artifact` before working.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "slideshow.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "slideshow.md",
+            "bytes": 650
+          },
+          {
+            "kind": "contains",
+            "file": "slideshow.md",
+            "pattern": "(?:^|\\n)#\\s+\\S",
+            "label": "at least one H1 scene heading"
+          }
+        ],
+        "onReject": "write",
+        "maxAttempts": 4
+      },
+      "next": "publish",
+      "consumes": [
+        {
+          "file": "{{workPath}}/outline.md",
+          "artifact": true
+        }
+      ]
+    },
+    {
+      "id": "publish",
+      "name": "Publish the video and GIF",
+      "description": "Convert slideshow.md once to MP4 and animated GIF, preview frames, and save both files.",
+      "prompt": "Publish slideshow.md with the pre-authorized DocBlocks tools. 1. Call list_roots first and identify the read-enabled workspace root and write-enabled artifacts root. If there is no write root, report the blocker instead of substituting HTML. 2. Call get_authoring_context with targetFormat \"mp4\", goal \"visual-polish\", and the slideshow.md file source only when exact animation or theme guidance would help; ordinary Markdown needs no preflight. 3. Call convert_document ONCE with source `{ \"kind\": \"file\", \"rootId\": <workspace root id>, \"path\": \"slideshow.md\" }`, targets for MP4 and GIF in the orientation from {{workPath}}/outline.md, `animationsEnabled: true`, moderate fps, a readable captionStyle, GIF `loop: 0`, an audience-appropriate theme, and `autoTemplates: true`. One call keeps both outputs on the same normalized source and rolls back the batch on failure. 4. Call preview_document on both artifact URIs and inspect representative frames: expected scene count/order, readable text, consistent theme, no clipping, final action present. Repair slideshow.md and reconvert on failure. 5. Call save_artifact for the GIF first with destination path {{workPath}}/slideshow.gif, then call save_artifact for the MP4 with destination path {{workPath}}/slideshow.mp4 in the artifacts root and `ifExists: \"error\"`; saving MP4 last lets the step advance only after both files exist. On loop-back, replace only with each file's current expectedSha256. 6. Call write_task_note with both paths, dimensions, fps, theme, and preview result. If Chromium or FFmpeg is unavailable, report that exact media-runtime blocker; do not build an HTML player.\n\nOpen `{{workPath}}/outline.md` from the artifacts drawer with `read_artifact` before working.",
+      "suggestedRole": "video-generator",
+      "advanceWhen": {
+        "file": "{{workPath}}/slideshow.mp4",
+        "minBytes": 1,
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/slideshow.mp4",
+            "bytes": 1000,
+            "artifact": true
+          },
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/slideshow.gif",
+            "bytes": 1000,
+            "artifact": true
+          }
+        ],
+        "onReject": "publish",
+        "maxAttempts": 4
+      },
+      "next": "evaluate",
+      "consumes": [
+        {
+          "file": "{{workPath}}/outline.md",
+          "artifact": true
+        },
+        {
+          "file": "slideshow.md"
+        }
+      ]
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Review the saved MP4 and GIF against the story and visual criteria.",
+      "prompt": "Review artifacts/slideshow.mp4 and artifacts/slideshow.gif against every criterion in {{workPath}}/outline.md. Use list_roots to identify the artifacts root and preview_document on each file source. Confirm both files open, the MP4 contains every scene in order, the GIF loops, text is readable, source facts are preserved, the theme and motion are consistent, nothing clips, and the final takeaway is present. Write PASS/FAIL for every criterion and name the frame/scene for any failure.\n\nThen route:\n\n- Every criterion PASSES → call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- Any criterion FAILS → write the exact gaps to task notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"write\" })`.\n\nNever route to finish while any criterion is unmet. After about three unproductive loops, stop with DONE_WITH_CONCERNS.\n\nOpen `{{workPath}}/outline.md`, `{{workPath}}/slideshow.mp4` from the artifacts drawer with `read_artifact` before working.",
+      "suggestedRole": "reviewer",
+      "next": "write",
+      "consumes": [
+        {
+          "file": "{{workPath}}/outline.md",
+          "artifact": true
+        },
+        {
+          "file": "{{workPath}}/slideshow.mp4",
+          "artifact": true
+        },
+        {
+          "file": "{{workPath}}/slideshow.gif",
+          "artifact": true
+        }
+      ]
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All story, frame, and media-file checks passed.",
+      "prompt": "Every acceptance criterion passed. Call write_task_note with a short DONE summary naming slideshow.md as the source and artifacts/slideshow.mp4 plus artifacts/slideshow.gif as the finished deliverables, with dimensions, scene count, and confirmation that both previews passed. Then report DONE.\n\nOpen `{{workPath}}/slideshow.mp4` from the artifacts drawer with `read_artifact` before working.",
+      "suggestedRole": "video-generator",
+      "terminal": true,
+      "consumes": [
+        {
+          "file": "slideshow.md"
+        },
+        {
+          "file": "{{workPath}}/slideshow.mp4",
+          "artifact": true
+        },
+        {
+          "file": "{{workPath}}/slideshow.gif",
+          "artifact": true
+        }
+      ]
+    }
+  ],
+  "version": "1.1.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/na/narrated-slideshow/versions/1.1.2/test.json

@@ -0,0 +1,89 @@
+{
+  "schemaVersion": 1,
+  "title": "Animated Content Slideshow Markdown-source smoke eval",
+  "objective": "Verify that the media workflow produces concise scene-structured Markdown before DocBlocks MP4/GIF conversion; catalog contract tests cover the media toolset and dual artifact gate.",
+  "tags": [
+    "media"
+  ],
+  "prompt": "Read source/brief.md and write slideshow.md for a seven-scene animated operations update. Use one H1 heading per scene, short on-screen bullets, and a final next-actions scene. Do not create HTML.",
+  "setup": {
+    "projectName": "Animated Content Slideshow Eval",
+    "about": "The slideshow source is Markdown and will be rendered to MP4 and GIF by DocBlocks.",
+    "missionObjectives": "Create concise, source-grounded slideshow.md with one H1 per scene and no HTML intermediary.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Boreal Desk Returns Pilot\n\nAudience: operations leads.\n\nFacts:\n- Pilot coverage: 18 SKUs.\n- Median first response: 18 hours to 6 hours.\n- Preventable refund leakage: 14.2% to 8.9%.\n- Top unresolved complaint: status silence after photo submission.\n- Next actions: automated status emails, barcode-exception training, weekly Finance exception export.\n\nDo not invent other metrics."
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Copywriter"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "slideshow.md is a concise, source-grounded scene sequence ready for DocBlocks MP4/GIF conversion.",
+    "deliverables": [
+      {
+        "path": "slideshow.md",
+        "kind": "markdown-doc",
+        "minBytes": 650,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "slideshow.md",
+            "pattern": "(?:^|\\n)#\\s+.+",
+            "flags": "m"
+          },
+          {
+            "kind": "contains",
+            "file": "slideshow.md",
+            "pattern": "18\\s+SKUs|18\\s+hours|6\\s+hours|14\\.2%|8\\.9%",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "slideshow.md",
+            "pattern": "automated status emails|barcode-exception training|weekly Finance exception export",
+            "flags": "i"
+          },
+          {
+            "kind": "notContains",
+            "file": "slideshow.md",
+            "pattern": "<html|<script|<style|base64",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "slideshow.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "story",
+        "description": "The scenes form a coherent update with one message per scene and a clear final action."
+      },
+      {
+        "name": "grounding",
+        "description": "Every metric and action comes from the seeded brief."
+      },
+      {
+        "name": "renderability",
+        "description": "One H1 per scene and concise blocks make the source suitable for rendered MP4/GIF output."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "one H1 per scene",
+    "source grounding",
+    "no HTML intermediary"
+  ]
+}

package/data/craftbook-templates/ne/newsletter-issue/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "newsletter-issue",
   "role": "general",
+  "category": "marketing",
   "name": "Newsletter Issue",
   "description": "Produce a single polished, email-client-safe newsletter issue — intro, a few curated stories with links, a featured section, and a CTA — that renders correctly across email clients. Outlines the issue's theme and section lineup FIRST, writes scannable, personable copy with working links, then builds the email-safe HTML using inline styles and table layout so it survives Gmail/Outlook. Use for recurring email newsletters, product updates, and curated digests sent to subscribers.",
   "tags": [

package/data/craftbook-templates/ne/newsletter-issue/versions/1.0.2/craftbook.json

@@ -0,0 +1,155 @@
+{
+  "id": "newsletter-issue",
+  "name": "Newsletter Issue",
+  "description": "Produce a single polished, email-client-safe newsletter issue — intro, a few curated stories with links, a featured section, and a CTA — that renders correctly across email clients. Outlines the issue's theme and section lineup FIRST, writes scannable, personable copy with working links, then builds the email-safe HTML using inline styles and table layout so it survives Gmail/Outlook. Use for recurring email newsletters, product updates, and curated digests sent to subscribers.\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. Outline the issue (planner) — theme, section lineup, story picks, and the one CTA → gated on artifact `{{workPath}}/outline.md` (markdown-notes)\n2. Write the copy (copywriter) — scannable, personable copy with links and one CTA → gated on artifact `{{workPath}}/write.md` (markdown-notes)\n3. Build the email HTML (developer) — render index.html email-safe: inline styles, table layout, ~600px → 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": "outline",
+  "triggers": [
+    "newsletter issue",
+    "write a newsletter",
+    "email newsletter",
+    "build a newsletter",
+    "weekly update email",
+    "subscriber email"
+  ],
+  "steps": [
+    {
+      "id": "outline",
+      "name": "Outline the issue",
+      "description": "theme, section lineup, story picks, and the one CTA",
+      "prompt": "Plan the issue before writing. Step 1: name this issue's theme/hook and the audience. Step 2: lay out the section lineup in order — subject line + preheader, a short personal intro, 3-5 curated stories (each: title, link, 1-2 line take), a featured/deep-dive block, and a single clear CTA. Step 3: pick the actual stories/links to include and note the angle for each; cut anything off-theme. Step 4: decide the one primary action you want readers to take. Step 5: write an acceptance-criteria checklist ('has a subject line + preheader', 'intro is short and personable', '3-5 stories each with a working link and a one-line take', 'exactly one primary CTA', 'scannable in under two minutes'). Write the lineup + checklist via write_task_note AND to {{workPath}}/outline.md. No copy or HTML yet.\n\nThe deliverable `{{workPath}}/outline.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}}/outline.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/outline.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/outline.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "outline",
+        "maxAttempts": 3
+      },
+      "next": "write"
+    },
+    {
+      "id": "write",
+      "name": "Write the copy",
+      "description": "scannable, personable copy with links and one CTA",
+      "prompt": "Write the newsletter copy from the outline in a warm, scannable voice. Step 1: write a subject line (under ~50 chars, curiosity or value) and a preheader that complements it. Step 2: write a short, personable intro (2-4 sentences) tied to the theme. Step 3: for each curated story write a punchy title and a 1-2 line take that gives the reader a reason to click, with the link. Step 4: write the featured/deep-dive block — a few sentences with a clear payoff. Step 5: write the one CTA with action-oriented button copy. Keep paragraphs short, use the second person, and make it skimmable. Do not invent links — use the ones from the outline. Write the section-by-section copy via write_task_note AND to {{workPath}}/write.md.\n\nThe deliverable `{{workPath}}/write.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}}/write.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/write.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/write.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "write",
+        "maxAttempts": 3
+      },
+      "next": "build"
+    },
+    {
+      "id": "build",
+      "name": "Build the email HTML",
+      "description": "render index.html email-safe: inline styles, table layout, ~600px",
+      "prompt": "Build the issue as a single self-contained index.html that renders in real email clients. Step 1: use a table-based layout centered at ~600px with all CSS INLINE on elements (email clients strip <style> and ignore fl/grid) — no external stylesheets, no web fonts, web-safe font stacks only. Step 2: lay out the sections per the outline order (preheader text first, hidden but present; intro; story list; featured block; CTA button) with the approved copy verbatim. Step 3: render the CTA as a bulletproof button (a padded, background-colored anchor styled as a table cell) and make every story link a real working <a href>. Step 4: keep images optional and provide alt text; ensure it degrades gracefully with images off. Step 5: include a footer with an (illustrative) unsubscribe link. On a loop-back, fix ONLY the named gaps. Write the path via write_task_note.",
+      "suggestedRole": "developer",
+      "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": "QA the newsletter against the locked criteria. Step 1: open/render index.html. Step 2: confirm email-safety: table layout, inline styles only (no reliance on <style>/flex/grid), centered ~600px, web-safe fonts. Step 3: check EACH acceptance criterion: subject line + preheader present, short personable intro, 3-5 stories each with a working <a href> link and a one-line take, exactly one primary CTA rendered as a tappable button, footer with unsubscribe. Step 4: confirm it is scannable in under two minutes and links are real (from the outline, not invented). Write PASS/FAIL per criterion with the offending section on any FAIL.\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/ne/newsletter-issue/versions/1.0.2/test.json

@@ -0,0 +1,113 @@
+{
+  "schemaVersion": 1,
+  "title": "Newsletter Issue smoke eval",
+  "objective": "Self-contained smoke eval for the Newsletter Issue craftbook using the corpus generic harness.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "We need a newsletter issue 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": "Newsletter Issue Eval",
+    "about": "Self-contained eval project for newsletter-issue. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/report.md.",
+    "missionObjectives": "Use the Newsletter Issue 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": "# Newsletter Issue 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: newsletter-issue - Newsletter Issue.\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/no/notification-router/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "notification-router",
   "role": "general",
+  "category": "code-build",
   "name": "Notification Router",
   "description": "Build an event-to-channel notification router: a small module that takes incoming events and routes each to the right destination (Slack channel, email, PagerDuty, webhook) based on type, severity, and quiet-hours rules — with dedupe, throttling, and a fallback channel. Scopes the routing matrix and policy FIRST (event taxonomy, channel map, severity→destination rules, dedupe key, rate limits, fallback), then a developer implements the router module to that matrix, then writes tests covering each routing branch. Scoping the matrix before coding is what guarantees every event type has a defined destination and that critical events can never be silently dropped. Use for notification routing, alert fan-out, event dispatch, webhook routing, and on-call/Slack notification systems.",
   "tags": [