@bendyline/gilde 0.1.38 → 0.1.39

package/data/craftbook-templates/he/hero-image/versions/1.0.2/craftbook.json

@@ -0,0 +1,166 @@
+{
+  "id": "hero-image",
+  "name": "Marketing Hero Image",
+  "description": "Create a single high-impact marketing hero image from a brief and place it into a working hero section. Lock the brief FIRST — aspect ratio, subject, mood, palette, focal point, and crucially the safe zone where headline and CTA text will overlay — because a beautiful hero that has no room for copy (or whose focal point sits under the button) is useless. Then generate the image to the brief and place it behind real overlaid text to prove it works. Covers hero banners, marketing imagery, landing-page art, website headers, and key visuals.\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. Hero brief (visual-designer) — lock ratio, subject, mood, palette, focal point, text safe-zone → gated on artifact `{{workPath}}/brief.md` (markdown-notes)\n2. Generate the hero (image-generator) — render the hero image to the brief → gated on `assets` (image-set)\n3. Place in a hero section (developer) — build index.html with the hero behind real overlaid text → 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": "brief",
+  "triggers": [
+    "make a hero image",
+    "marketing banner",
+    "landing page hero",
+    "website header image",
+    "key visual"
+  ],
+  "steps": [
+    {
+      "id": "brief",
+      "name": "Hero brief",
+      "description": "lock ratio, subject, mood, palette, focal point, text safe-zone",
+      "prompt": "1) Decide the aspect ratio and target use (e.g. 16:9 full-bleed web hero). 2) Lock the subject and scene, the mood/style, and the palette (hex) so the image will harmonize with the brand. 3) Define the FOCAL POINT and, critically, the TEXT SAFE ZONE — which third of the frame stays low-contrast/empty so an overlaid headline + CTA remains readable. 4) Note the headline and CTA copy that will sit on it (even placeholder) so placement is concrete. 5) Write an acceptance-criteria checklist: 'aspect ratio is <X>', 'focal point is off the text safe zone', 'palette matches <hex>', 'overlaid headline + CTA are readable against the image', 'image is delivered at usable resolution'. 6) Record brief + checklist via write_task_note AND to {{workPath}}/brief.md. No image yet.\n\nThe deliverable `{{workPath}}/brief.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}}/brief.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/brief.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/brief.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "brief",
+        "maxAttempts": 3
+      },
+      "next": "generate"
+    },
+    {
+      "id": "generate",
+      "name": "Generate the hero",
+      "description": "render the hero image to the brief",
+      "prompt": "1) Read brief.md. 2) Using the image-generation capability (or a tasteful CSS/SVG composition if no image model is available), produce the hero at the locked aspect ratio and palette. 3) Compose so the focal point lands OUTSIDE the declared text safe zone and that zone stays calm enough for overlaid copy. 4) Match the mood and avoid clutter near where text goes. 5) Save it to assets/ (e.g. assets/hero.png or hero.svg) at usable resolution. 6) Generate at least one alternate framing if quick, so placement has options. Good looks like: a striking image with obvious clear space for the headline.",
+      "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": "place"
+    },
+    {
+      "id": "place",
+      "name": "Place in a hero section",
+      "description": "build index.html with the hero behind real overlaid text",
+      "prompt": "1) Build a single index.html hero section that uses the generated image as a full-bleed background (object-fit: cover or background-size: cover) at the locked aspect ratio. 2) Overlay the real headline and CTA button positioned within the safe zone, with a subtle scrim/gradient ONLY if needed for contrast. 3) Make it responsive — the focal point must survive a mobile crop. 4) Reference the real assets/ file (relative path). 5) On a loop-back, fix only named gaps (unreadable text, focal point clipped, wrong ratio). 6) write_task_note the page path and image used. Good looks like: a hero you could ship, with crisp, readable copy over the art.",
+      "suggestedRole": "developer",
+      "consumes": [
+        {
+          "file": "assets"
+        }
+      ],
+      "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": "place",
+        "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) Confirm assets/ contains the hero image (PASS/FAIL). 2) Open index.html and verify the image renders full-bleed at the locked aspect ratio. 3) The decisive check: is the overlaid headline + CTA clearly READABLE against the image and is the focal point clear of the text (PASS/FAIL)? 4) Resize to a narrow viewport — does it survive the mobile crop? 5) Confirm the palette matches the brief. 6) Write PASS/FAIL per criterion. Unreadable/clashing text → loop back to place; bad image/focal point → note it for generate.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"place\" })` 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": "place"
+    },
+    {
+      "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/he/hero-image/versions/1.0.2/test.json

@@ -0,0 +1,106 @@
+{
+  "schemaVersion": 1,
+  "title": "Marketing Hero Image smoke eval",
+  "objective": "Self-contained smoke eval for the Marketing Hero Image 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": "Marketing Hero Image Eval",
+    "about": "Self-contained eval project for hero-image. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/media-plan.json.",
+    "missionObjectives": "Use the Marketing Hero Image 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": "# Marketing Hero Image 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: hero-image - Marketing Hero Image.\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": "hero-image-media-fixtures",
+        "kind": "data-source",
+        "status": "implemented",
+        "description": "Seeded local media index replacing real audio, video, image generation, and external media metadata services."
+      }
+    ]
+  }
+}

package/data/craftbook-templates/ho/holiday-card-run/versions/1.0.2/craftbook.json

@@ -0,0 +1,214 @@
+{
+  "id": "holiday-card-run",
+  "name": "Holiday Card Run",
+  "description": "Make the December run a pleasure instead of a panic: sweep the address list while there is still time to fix it, settle the card message, and produce the print-ready card and the address sheet in one sitting. Locks the roster sweep and the message criteria FIRST, then builds the card, then the address sheet, then reports the gaps that still need a human. Use for holiday cards, the annual card run, 'time for the holiday cards', address list cleanup before card season, and the December mailing.\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. Sweep the roster (letter-writer) — who's in, stale or missing addresses, message criteria → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Build the card (designer) — print-ready card front and inside message → gated on `cards/card.html` (html-page)\n3. Build the address sheet (archivist) — print-ready address sheet, roster fixes recorded → gated on `cards/addresses.html` (html-page)\n4. Write the run summary (letter-writer) — what went to print, gaps that need a human → gated on artifact `{{workPath}}/report.md` (markdown-report)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "run the holiday cards",
+    "time for the holiday cards",
+    "holiday card run",
+    "make the card and the address sheet",
+    "december card season"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Sweep the roster",
+      "description": "who's in, stale or missing addresses, message criteria",
+      "prompt": "Sweep the list before designing anything. Step 1: read correspondents.json from the workspace — who gets a card this run, and check every address: present, missing, or suspect (a move noted, an old date, a gap). Step 2: confirm the list with the owner — who is in, who is out this year, and anyone new. Step 3: settle the message criteria — the greeting's warmth and register, anything it must say or avoid, and that one message has to work for every household on the list. Step 4: write an acceptance-criteria checklist ('every household is in or out on purpose', 'stale and missing addresses are flagged by name', 'the card message is settled and fits everyone it goes to', 'card and address sheet are print-ready — proper page setup, nothing screen-only'). Call write_task_note with the list count + flagged addresses + checklist and write {{workPath}}/scope.md.\n\nThe deliverable `{{workPath}}/scope.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "letter-writer",
+      "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": "card"
+    },
+    {
+      "id": "card",
+      "name": "Build the card",
+      "description": "print-ready card front and inside message",
+      "prompt": "Build the card as one print-ready HTML file at cards/card.html. Step 1: the front — the settled greeting, designed to print well on a home printer: strong type, honest margins, colors that survive paper. Step 2: the inside — the message, with room left for a handwritten line. Step 3: style it for paper — an @page rule with the card's size and margins, print styles that drop any screen-only chrome, and page breaks exactly where the fold logic wants them. Step 4: proof the text letter by letter — a typo prints twenty times. Call write_task_note with the card file path and the settled message in one line.",
+      "suggestedRole": "designer",
+      "advanceWhen": {
+        "file": "cards/card.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "cards/card.html",
+            "bytes": 800
+          },
+          {
+            "kind": "htmlLint",
+            "file": "cards/card.html"
+          },
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "cards/card.html"
+          },
+          {
+            "kind": "contains",
+            "file": "cards/card.html",
+            "pattern": "@page|@media\\s+print",
+            "flags": "i",
+            "label": "print CSS"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "cards/card.html"
+            }
+          }
+        ],
+        "onReject": "card",
+        "maxAttempts": 3
+      },
+      "next": "addresses"
+    },
+    {
+      "id": "addresses",
+      "name": "Build the address sheet",
+      "description": "print-ready address sheet, roster fixes recorded",
+      "prompt": "Produce the address side of the run. Step 1: build cards/addresses.html — a print-ready address or label sheet with one block per household from the locked list, using each household's own label from the roster. Step 2: state the run count plainly on the sheet — how many households it covers. Step 3: where the owner has confirmed a correction for a flagged address, fix it on the sheet and record the update through the project's correspondence capabilities. Step 4: leave clearly-marked gaps for addresses still missing so the sheet never quietly drops a household. Call write_task_note with the covered count and the still-missing count.",
+      "suggestedRole": "archivist",
+      "advanceWhen": {
+        "file": "cards/addresses.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "cards/addresses.html",
+            "bytes": 800
+          },
+          {
+            "kind": "htmlLint",
+            "file": "cards/addresses.html"
+          },
+          {
+            "kind": "contains",
+            "file": "cards/addresses.html",
+            "pattern": "\\d+\\s*(?:households?|addresses|recipients?|cards)",
+            "flags": "i",
+            "label": "run count claim"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "cards/addresses.html"
+            }
+          }
+        ],
+        "onReject": "addresses",
+        "maxAttempts": 3
+      },
+      "next": "report"
+    },
+    {
+      "id": "report",
+      "name": "Write the run summary",
+      "description": "what went to print, gaps that need a human",
+      "prompt": "Write the run summary. Step 1: state what is ready — the card, the address sheet, and how many households the run covers. Step 2: list the stale and missing addresses by name with the concrete next step for each (who to ask, where to look). Step 3: note anything the owner still does by hand — signing, stamps, the mail date that makes the season. Step 4: keep it under a page. Write {{workPath}}/report.md and call write_task_note with the covered and outstanding counts.\n\nThe deliverable `{{workPath}}/report.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "letter-writer",
+      "advanceWhen": {
+        "file": "{{workPath}}/report.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/report.md",
+            "bytes": 600,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i",
+            "label": "at least one markdown heading",
+            "artifact": true
+          }
+        ],
+        "onReject": "report",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Open cards/card.html, cards/addresses.html, and {{workPath}}/report.md and verify every criterion from {{workPath}}/scope.md: the card is complete, print-styled, and carries the settled message; the address sheet covers every in-list household or marks the gap plainly — cross-check the names against correspondents.json, a household the sheet quietly dropped is the classic failure; the run count claim matches the sheet; and the report names every stale or missing address with a next step. Write PASS/FAIL per criterion; on any failure, name the gap and loop back to card.\n\nThe deliverable lives in the project's artifacts drawer — open `{{workPath}}/report.md` with `read_artifact`, not `read_file`.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"card\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "consumes": [
+        {
+          "file": "{{workPath}}/report.md",
+          "artifact": true
+        }
+      ],
+      "next": "card"
+    },
+    {
+      "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/ho/holiday-card-run/versions/1.0.2/test.json

@@ -0,0 +1,131 @@
+{
+  "schemaVersion": 1,
+  "title": "Holiday Card Run — roster sweep to print-ready card and address sheet",
+  "objective": "Measure whether the holiday-card-run craftbook sweeps a seeded address roster, produces a print-ready card and address sheet, and reports the stale and missing addresses instead of quietly dropping households.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "time for the holliday cards — can you do the card and the address sheet from the list? a few adresses might be stale. warm message, nothing over the top",
+  "setup": {
+    "projectName": "Bracken Lane Card Run",
+    "about": "Correspondence desk for the Miller-Osei household's annual card run. The address roster lives at workspace/correspondents.json; the run's print files go under workspace/cards.",
+    "missionObjectives": "Get the December run print-ready with a clean address list. Everything is grounded in the roster — no live services, no real credentials.",
+    "files": [
+      {
+        "path": "correspondents.json",
+        "content": "{\n  \"household\": \"the Miller-Oseis\",\n  \"cardList\": [\n    { \"family\": \"Barrett\", \"cardLabel\": \"The Barrett Family\", \"address\": \"14 Cedar Loop, Halstead, MN 55301\" },\n    { \"family\": \"Okonkwo\", \"cardLabel\": \"The Okonkwo Family\", \"address\": \"902 Birchwood Ave, Halstead, MN 55301\" },\n    { \"family\": \"Reyes\", \"cardLabel\": \"The Reyes Family\", \"address\": \"77 Quarry Rd, Duluth, MN 55803\" },\n    { \"family\": \"Lindqvist\", \"cardLabel\": \"The Lindqvist Family\", \"address\": \"5 Aspen Ct, Halstead, MN 55301\", \"note\": \"moved last spring — address unconfirmed\" },\n    { \"family\": \"Achterberg\", \"cardLabel\": \"The Achterberg Family\", \"address\": \"310 Mill Pond Ln, Roseau, MN 56751\" },\n    { \"family\": \"Nguyen\", \"cardLabel\": \"The Nguyen Family\", \"address\": null },\n    { \"family\": \"Castellano\", \"cardLabel\": \"The Castellano Family\", \"address\": \"48 Harbor View Dr, Bayfield, WI 54814\" },\n    { \"family\": \"Whitfield\", \"cardLabel\": \"The Whitfield Family\", \"address\": \"\" },\n    { \"family\": \"Dube\", \"cardLabel\": \"The Dube Family\", \"address\": \"221 Larkspur St, Halstead, MN 55301\" },\n    { \"family\": \"Petrov\", \"cardLabel\": \"The Petrov Family\", \"address\": \"1600 Winter Hill Rd, Grand Marais, MN 55604\" }\n  ]\n}\n"
+      }
+    ],
+    "worker": {
+      "name": "Sanne",
+      "role": "Designer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "cards/card.html is a print-styled card with the settled message; cards/addresses.html covers the roster with the gaps marked; tasks/eval/report.md names the stale and missing addresses.",
+    "deliverables": [
+      {
+        "path": "cards/card.html",
+        "kind": "html-page",
+        "minBytes": 1200,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "cards/card.html"
+          },
+          {
+            "kind": "contains",
+            "file": "cards/card.html",
+            "pattern": "@page|@media\\s+print",
+            "flags": "i",
+            "label": "print CSS"
+          }
+        ]
+      },
+      {
+        "path": "cards/addresses.html",
+        "kind": "html-page",
+        "minBytes": 1000,
+        "checks": [
+          {
+            "kind": "valuesSubsetOf",
+            "file": "cards/addresses.html",
+            "sourceFiles": [
+              "correspondents.json"
+            ],
+            "pattern": "The\\s+([A-Z][A-Za-z-]+)\\s+Family",
+            "minMatches": 8,
+            "label": "address blocks use the roster's own labels"
+          },
+          {
+            "kind": "contains",
+            "file": "cards/addresses.html",
+            "pattern": "\\d+\\s*(?:households?|addresses|recipients?|cards)",
+            "flags": "i",
+            "label": "run count stated on the sheet"
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/report.md",
+        "kind": "markdown-report",
+        "minBytes": 600,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "missing|stale|unconfirmed",
+            "flags": "i",
+            "label": "address gaps surfaced"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "Nguyen|Whitfield|Lindqvist",
+            "flags": "i",
+            "label": "flagged households named"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "cards/card.html",
+      "kind": "html"
+    },
+    "axes": [
+      {
+        "name": "print readiness",
+        "description": "The card and sheet carry real print styling — page setup, margins, breaks — not a screen layout with a print label."
+      },
+      {
+        "name": "address hygiene",
+        "description": "Stale and missing addresses are flagged by name; no household quietly dropped from the run."
+      },
+      {
+        "name": "message warmth",
+        "description": "The card message is warm and works for every household on the list."
+      },
+      {
+        "name": "run completeness",
+        "description": "Card, address sheet, and summary together make the run finishable in one sitting."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "print-ready output",
+    "address hygiene",
+    "no dropped households"
+  ]
+}