@bendyline/gilde 0.1.38 → 0.1.40

package/data/craftbook-templates/wh/whitepaper/versions/1.0.2/test.json

@@ -0,0 +1,113 @@
+{
+  "schemaVersion": 1,
+  "title": "Whitepaper smoke eval",
+  "objective": "Self-contained smoke eval for the Whitepaper craftbook using the corpus generic harness.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "We need a whitepaper for the returns-desk work. The backgound info is in source/brief.md — have a look and write it up in tasks/eval/report.md.",
+  "setup": {
+    "projectName": "Whitepaper Eval",
+    "about": "Self-contained eval project for whitepaper. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/report.md.",
+    "missionObjectives": "Use the Whitepaper craftbook/template, read the seeded local fixtures, and write tasks/eval/report.md without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Whitepaper 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: whitepaper - Whitepaper.\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Writer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "tasks/eval/report.md is a source-grounded markdown artifact with required facts and actions.",
+    "deliverables": [
+      {
+        "path": "tasks/eval/report.md",
+        "kind": "markdown-report",
+        "minBytes": 1000,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "source/brief\\.md|Brief",
+            "flags": "i",
+            "label": "cite or name the seeded source"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "18\\b[\\s\\S]{0,30}\\bSKUs",
+            "flags": "i",
+            "label": "include the 18-SKU pilot scope"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "18\\s*hours|6\\s*hours",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "14\\.2%|8\\.9%",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "status silence|photo submission",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "automated status emails|barcode|Finance",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/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/ye/year-in-review/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "year-in-review",
   "role": "general",
+  "category": "media",
   "name": "Year in Review",
   "description": "Build the year-in-review that makes someone cry the good way: every month represented or its gap acknowledged, the people balanced, the closing image chosen on purpose — the annual ritual the whole photo archive exists for. Locks the year and the coverage criteria FIRST, then curates the selection month by month, then narrates the year's thread. Use for year-in-review albums, annual photo retrospectives, 'the year in photos', December album rituals, and closing out the year's archive.",
   "tags": [

package/data/craftbook-templates/ye/year-in-review/versions/1.0.2/craftbook.json

@@ -0,0 +1,127 @@
+{
+  "id": "year-in-review",
+  "name": "Year in Review",
+  "description": "Build the year-in-review that makes someone cry the good way: every month represented or its gap acknowledged, the people balanced, the closing image chosen on purpose — the annual ritual the whole photo archive exists for. Locks the year and the coverage criteria FIRST, then curates the selection month by month, then narrates the year's thread. Use for year-in-review albums, annual photo retrospectives, 'the year in photos', December album rituals, and closing out the year's archive.\n\nA gallery craftbook generated from an archetype spec. It runs\n`phase → (per-phase gate) → … → evaluate → (loop) → finish`. Each build\nphase that produces a checkable artifact is followed by a **runtime\ngate-checkpoint** — the runtime verifies the artifact and routes with no\nmodel turn, looping back to redo the phase on a miss. The final `evaluate`\nstep holds a static deliverable gate plus a reviewer QA pass. What it adds\nover the generic `build-loop`: a specialist role per phase, a\ndomain-correct ordering, and a concrete per-phase quality bar.\n\nDeliverables marked \"artifact\" land in the project's artifacts drawer (`write_artifact` / `read_artifact`), not the shipped workspace — review output is not product source.\n\nPhases:\n\n1. Scope the year (archivist) — the year's months mapped, coverage criteria locked → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Curate the year (curator) — month-by-month picks, cast balanced, opener and closer chosen\n3. Narrate the year (copywriter) — month sections, gaps named kindly, the year's thread → 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": [
+    "year in review album",
+    "the year in photos",
+    "build the annual album",
+    "december photo ritual",
+    "year in review"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the year",
+      "description": "the year's months mapped, coverage criteria locked",
+      "prompt": "Define the year before picking a photo. Step 1: read photos/index.json from the workspace and establish the year under review — the span the index covers — month by month: how many photos each month holds and where the thin months are. Step 2: read the caption notes alongside the photos (photos/*.txt) and confirm with the owner who and what mattered this year — the people who should be present, the events that anchor it. Step 3: lock the coverage criteria — every month is represented by at least one pick or its gap is named honestly in the review; the people balance out across the year rather than one face filling every page; the opening and closing images are chosen on purpose, not by timestamp. Step 4: write an acceptance-criteria checklist ('every month represented or its gap acknowledged in the review', 'every pick exists in the photo index', 'people balanced across the selection', 'opener and closer chosen with stated reasons', 'the review names the year's thread'). Call write_task_note with the per-month counts + 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": "archivist",
+      "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": "curate"
+    },
+    {
+      "id": "curate",
+      "name": "Curate the year",
+      "description": "month-by-month picks, cast balanced, opener and closer chosen",
+      "prompt": "Curate the year's selection. Step 1: walk the index month by month and shortlist the frames that carry each month — the caption notes tell you what the camera saw. Step 2: balance the cast — if one person dominates the shortlist, trade near-equal frames toward the people who are missing. Step 3: choose the opener and the closer deliberately — the image that starts the year's story and the one that ends it — and note why. Step 4: write the selection manifest into albums/ named for the year (year-<yyyy>.json) — a JSON array, one record per pick with file, month, and caption, the file spelled exactly as the index spells it. Call write_task_note with the pick count per month and the opener/closer choices.",
+      "suggestedRole": "curator",
+      "next": "narrate"
+    },
+    {
+      "id": "narrate",
+      "name": "Narrate the year",
+      "description": "month sections, gaps named kindly, the year's thread",
+      "prompt": "Write the year's review to sit beside the album. Step 1: open with the year's thread — the sentence the whole album argues. Step 2: a short section per month — what the month held, carried by its picks' captions; where a month is thin or empty, say so plainly and kindly, because the gap is part of the year too. Step 3: close on the closing image — why it ends the year. Step 4: keep it the kind of thing someone reads aloud at the table in December. Write {{workPath}}/report.md and call write_task_note with the report path and the year's thread.\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": "copywriter",
+      "advanceWhen": {
+        "file": "{{workPath}}/report.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/report.md",
+            "bytes": 1500,
+            "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": "narrate",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Open the year manifest in albums/, {{workPath}}/report.md, and photos/index.json and verify every criterion from {{workPath}}/scope.md: every month of the year is represented in the manifest or its gap named in the review (check the thin months especially), every pick's file appears in the photo index exactly, the cast is balanced rather than one face throughout, the opener and closer are identified with reasons, and the review carries a month-by-month shape with the year's thread stated. Write PASS/FAIL per criterion; on any failure, name the gap and loop back to curate.\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: \"curate\" })` 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": "curate"
+    },
+    {
+      "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/ye/year-in-review/versions/1.0.2/test.json

@@ -0,0 +1,148 @@
+{
+  "schemaVersion": 1,
+  "title": "Year in Review smoke eval",
+  "objective": "Task-specific eval for the Year in Review craftbook: a year of indexed photos (March empty) becomes a 12+ pick manifest that exists entirely in the index, and a review that acknowledges the March gap while carrying the year's thread.",
+  "tags": [
+    "data"
+  ],
+  "prompt": "its december — time for the year in reveiw album. the photo index has the whole year and the caption notes are alongside it",
+  "setup": {
+    "projectName": "Photo Curator — Year in Review Eval",
+    "about": "Self-contained eval project for year-in-review. The watched-folder import has indexed the whole year into photos/index.json (files + timestamps), with caption notes for standout frames as photos/IMG_NNNN.txt. The selection manifest goes under albums/ and the review goes to tasks/eval/report.md.",
+    "missionObjectives": "Use the Year in Review craftbook/template, curate from the seeded photo index only, and finish with the year manifest under albums/ plus tasks/eval/report.md. No live services or real photo tools — the index and caption notes are the whole record.",
+    "files": [
+      {
+        "path": "photos/index.json",
+        "content": "[\n  {\n    \"file\": \"IMG_5001.jpg\",\n    \"taken\": \"2026-01-03T10:12:00\"\n  },\n  {\n    \"file\": \"IMG_5002.jpg\",\n    \"taken\": \"2026-01-08T13:19:00\"\n  },\n  {\n    \"file\": \"IMG_5003.jpg\",\n    \"taken\": \"2026-01-13T16:26:00\"\n  },\n  {\n    \"file\": \"IMG_5004.jpg\",\n    \"taken\": \"2026-01-18T10:33:00\"\n  },\n  {\n    \"file\": \"IMG_5005.jpg\",\n    \"taken\": \"2026-02-03T10:12:00\"\n  },\n  {\n    \"file\": \"IMG_5006.jpg\",\n    \"taken\": \"2026-02-08T13:19:00\"\n  },\n  {\n    \"file\": \"IMG_5007.jpg\",\n    \"taken\": \"2026-02-13T16:26:00\"\n  },\n  {\n    \"file\": \"IMG_5008.jpg\",\n    \"taken\": \"2026-02-18T10:33:00\"\n  },\n  {\n    \"file\": \"IMG_5009.jpg\",\n    \"taken\": \"2026-02-23T13:40:00\"\n  },\n  {\n    \"file\": \"IMG_5010.jpg\",\n    \"taken\": \"2026-04-03T10:12:00\"\n  },\n  {\n    \"file\": \"IMG_5011.jpg\",\n    \"taken\": \"2026-04-08T13:19:00\"\n  },\n  {\n    \"file\": \"IMG_5012.jpg\",\n    \"taken\": \"2026-04-13T16:26:00\"\n  },\n  {\n    \"file\": \"IMG_5013.jpg\",\n    \"taken\": \"2026-04-18T10:33:00\"\n  },\n  {\n    \"file\": \"IMG_5014.jpg\",\n    \"taken\": \"2026-05-03T10:12:00\"\n  },\n  {\n    \"file\": \"IMG_5015.jpg\",\n    \"taken\": \"2026-05-08T13:19:00\"\n  },\n  {\n    \"file\": \"IMG_5016.jpg\",\n    \"taken\": \"2026-05-13T16:26:00\"\n  },\n  {\n    \"file\": \"IMG_5017.jpg\",\n    \"taken\": \"2026-05-18T10:33:00\"\n  },\n  {\n    \"file\": \"IMG_5018.jpg\",\n    \"taken\": \"2026-05-23T13:40:00\"\n  },\n  {\n    \"file\": \"IMG_5019.jpg\",\n    \"taken\": \"2026-06-03T10:12:00\"\n  },\n  {\n    \"file\": \"IMG_5020.jpg\",\n    \"taken\": \"2026-06-08T13:19:00\"\n  },\n  {\n    \"file\": \"IMG_5021.jpg\",\n    \"taken\": \"2026-06-13T16:26:00\"\n  },\n  {\n    \"file\": \"IMG_5022.jpg\",\n    \"taken\": \"2026-06-18T10:33:00\"\n  },\n  {\n    \"file\": \"IMG_5023.jpg\",\n    \"taken\": \"2026-06-23T13:40:00\"\n  },\n  {\n    \"file\": \"IMG_5024.jpg\",\n    \"taken\": \"2026-06-28T16:47:00\"\n  },\n  {\n    \"file\": \"IMG_5025.jpg\",\n    \"taken\": \"2026-07-03T10:12:00\"\n  },\n  {\n    \"file\": \"IMG_5026.jpg\",\n    \"taken\": \"2026-07-08T13:19:00\"\n  },\n  {\n    \"file\": \"IMG_5027.jpg\",\n    \"taken\": \"2026-07-13T16:26:00\"\n  },\n  {\n    \"file\": \"IMG_5028.jpg\",\n    \"taken\": \"2026-07-18T10:33:00\"\n  },\n  {\n    \"file\": \"IMG_5029.jpg\",\n    \"taken\": \"2026-07-23T13:40:00\"\n  },\n  {\n    \"file\": \"IMG_5030.jpg\",\n    \"taken\": \"2026-07-28T16:47:00\"\n  },\n  {\n    \"file\": \"IMG_5031.jpg\",\n    \"taken\": \"2026-08-03T10:12:00\"\n  },\n  {\n    \"file\": \"IMG_5032.jpg\",\n    \"taken\": \"2026-08-08T13:19:00\"\n  },\n  {\n    \"file\": \"IMG_5033.jpg\",\n    \"taken\": \"2026-08-13T16:26:00\"\n  },\n  {\n    \"file\": \"IMG_5034.jpg\",\n    \"taken\": \"2026-08-18T10:33:00\"\n  },\n  {\n    \"file\": \"IMG_5035.jpg\",\n    \"taken\": \"2026-08-23T13:40:00\"\n  },\n  {\n    \"file\": \"IMG_5036.jpg\",\n    \"taken\": \"2026-09-03T10:12:00\"\n  },\n  {\n    \"file\": \"IMG_5037.jpg\",\n    \"taken\": \"2026-09-08T13:19:00\"\n  },\n  {\n    \"file\": \"IMG_5038.jpg\",\n    \"taken\": \"2026-09-13T16:26:00\"\n  },\n  {\n    \"file\": \"IMG_5039.jpg\",\n    \"taken\": \"2026-09-18T10:33:00\"\n  },\n  {\n    \"file\": \"IMG_5040.jpg\",\n    \"taken\": \"2026-10-03T10:12:00\"\n  },\n  {\n    \"file\": \"IMG_5041.jpg\",\n    \"taken\": \"2026-10-08T13:19:00\"\n  },\n  {\n    \"file\": \"IMG_5042.jpg\",\n    \"taken\": \"2026-10-13T16:26:00\"\n  },\n  {\n    \"file\": \"IMG_5043.jpg\",\n    \"taken\": \"2026-10-18T10:33:00\"\n  },\n  {\n    \"file\": \"IMG_5044.jpg\",\n    \"taken\": \"2026-10-23T13:40:00\"\n  },\n  {\n    \"file\": \"IMG_5045.jpg\",\n    \"taken\": \"2026-11-03T10:12:00\"\n  },\n  {\n    \"file\": \"IMG_5046.jpg\",\n    \"taken\": \"2026-11-08T13:19:00\"\n  },\n  {\n    \"file\": \"IMG_5047.jpg\",\n    \"taken\": \"2026-11-13T16:26:00\"\n  },\n  {\n    \"file\": \"IMG_5048.jpg\",\n    \"taken\": \"2026-11-18T10:33:00\"\n  },\n  {\n    \"file\": \"IMG_5049.jpg\",\n    \"taken\": \"2026-12-03T10:12:00\"\n  },\n  {\n    \"file\": \"IMG_5050.jpg\",\n    \"taken\": \"2026-12-08T13:19:00\"\n  },\n  {\n    \"file\": \"IMG_5051.jpg\",\n    \"taken\": \"2026-12-13T16:26:00\"\n  },\n  {\n    \"file\": \"IMG_5052.jpg\",\n    \"taken\": \"2026-12-18T10:33:00\"\n  }\n]\n"
+      },
+      {
+        "path": "photos/IMG_5002.txt",
+        "content": "CAPTION NOTE (pre-extracted from IMG_5002.jpg)\n\nJanuary sledding on the reservoir hill - Ada airborne, Milo bracing for the crash that followed.\n"
+      },
+      {
+        "path": "photos/IMG_5007.txt",
+        "content": "CAPTION NOTE (pre-extracted from IMG_5007.jpg)\n\nFebruary - Oma's eightieth, four generations squeezed onto one couch, nobody looking at the same camera.\n"
+      },
+      {
+        "path": "photos/IMG_5011.txt",
+        "content": "CAPTION NOTE (pre-extracted from IMG_5011.jpg)\n\nApril - first garden day, seed trays on every windowsill, muddy handprint on the door.\n"
+      },
+      {
+        "path": "photos/IMG_5024.txt",
+        "content": "CAPTION NOTE (pre-extracted from IMG_5024.jpg)\n\nJuly - the lake weekend, cannonball mid-air, the summer's loudest hour.\n"
+      },
+      {
+        "path": "photos/IMG_5040.txt",
+        "content": "CAPTION NOTE (pre-extracted from IMG_5040.jpg)\n\nOctober - homemade robot costume with the cardboard arms that fell off by the third house.\n"
+      },
+      {
+        "path": "photos/IMG_5049.txt",
+        "content": "CAPTION NOTE (pre-extracted from IMG_5049.jpg)\n\nDecember - solstice walk, everyone's breath visible, the year's last golden light through the birches.\n"
+      }
+    ],
+    "worker": {
+      "name": "Loes",
+      "role": "Curator"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "albums/year-2026.json is a schema-clean manifest of 12+ picks that all exist in the photo index, and tasks/eval/report.md narrates the year month by month — with empty March acknowledged honestly instead of papered over.",
+    "deliverables": [
+      {
+        "path": "albums/year-2026.json",
+        "kind": "json",
+        "minBytes": 400,
+        "checks": [
+          {
+            "kind": "recordSchema",
+            "file": "albums/year-2026.json",
+            "fields": [
+              {
+                "name": "file",
+                "type": "nonempty"
+              },
+              {
+                "name": "month",
+                "type": "nonempty"
+              },
+              {
+                "name": "caption",
+                "type": "nonempty"
+              }
+            ],
+            "minRows": 12
+          },
+          {
+            "kind": "valuesSubsetOf",
+            "file": "albums/year-2026.json",
+            "sourceFiles": [
+              "photos/index.json"
+            ],
+            "pattern": "(IMG_\\d{4}\\.jpg)",
+            "flags": "gi",
+            "minMatches": 12
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/report.md",
+        "kind": "markdown-report",
+        "minBytes": 1200,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "March",
+            "flags": "i",
+            "label": "the empty March is acknowledged, not papered over"
+          },
+          {
+            "kind": "judge",
+            "file": "tasks/eval/report.md",
+            "rubric": "The review has an emotional arc: a year's thread stated up front, carried through month sections that lean on the picks' captions, ending on a deliberately chosen closing image — and the photo-less March is named honestly and kindly.",
+            "label": "the arc earns December"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/report.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "emotional-arc",
+        "description": "A year's thread stated up front and carried to a deliberate closing image — the review reads aloud well at a December table."
+      },
+      {
+        "name": "coverage-honesty",
+        "description": "Every month is represented in the manifest or its gap is named plainly in the review — especially empty March."
+      },
+      {
+        "name": "selection",
+        "description": "Picks exist in the index, the caption-noted anchors are present, and no single face dominates the year."
+      },
+      {
+        "name": "captions",
+        "description": "Manifest captions are specific and warm, building on the caption notes where they exist."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "coverage honesty",
+    "no invented photos",
+    "deliberate opener and closer"
+  ]
+}

package/data/craftbook-templates/yo/youtube-chapters-seo/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "youtube-chapters-seo",
   "role": "general",
+  "category": "marketing",
   "name": "YouTube Chapters & SEO Metadata",
   "description": "Turn a video (or its transcript) into a complete, paste-ready YouTube publishing kit — SEO title options, an optimized description with timestamped chapters, tags/keywords, and thumbnail text ideas — so an upload ranks and is navigable. Scopes the target keyword and metadata limits FIRST, analyzes the transcript for chapter boundaries, then writes the SEO-optimized metadata kit. Doing keyword research and pulling real chapter timestamps before writing is what makes the description both discoverable and accurate, instead of clickbait that doesn't match the video.",
   "tags": [

package/data/craftbook-templates/yo/youtube-chapters-seo/versions/1.0.2/craftbook.json

@@ -0,0 +1,146 @@
+{
+  "id": "youtube-chapters-seo",
+  "name": "YouTube Chapters & SEO Metadata",
+  "description": "Turn a video (or its transcript) into a complete, paste-ready YouTube publishing kit — SEO title options, an optimized description with timestamped chapters, tags/keywords, and thumbnail text ideas — so an upload ranks and is navigable. Scopes the target keyword and metadata limits FIRST, analyzes the transcript for chapter boundaries, then writes the SEO-optimized metadata kit. Doing keyword research and pulling real chapter timestamps before writing is what makes the description both discoverable and accurate, instead of clickbait that doesn't match the video.\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. SEO & metadata scope (planner) — target keyword, limits, sections, chapter format → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Find chapters & keywords (data-analyst) — topic-shift timestamps + keyword extraction → gated on artifact `{{workPath}}/analysis.json` (json)\n3. Write the metadata kit (copywriter) — title options, description+chapters, tags, thumbnail text → gated on `youtube-metadata.md` (markdown-doc)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "youtube description and chapters",
+    "seo title for my video",
+    "youtube metadata",
+    "optimize my video description",
+    "video tags and chapters"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "SEO & metadata scope",
+      "description": "target keyword, limits, sections, chapter format",
+      "prompt": "Lock the SEO plan BEFORE writing. Step 1: record the video (title intent, transcript path, duration) and the primary target keyword/phrase plus 2-3 secondary ones the audience would search. Step 2: capture the platform limits as hard rules: title ≤ 100 chars (front-load the keyword), description first ~150 chars are the visible/snippet zone, chapters need ≥3 markers with the FIRST at `00:00`, tags within the char budget. Step 3: define the description structure (hook line with keyword -> 2-3 sentence summary -> CHAPTERS list -> links/CTA -> hashtags). Step 4: define thumbnail-text guidance (≤4 punchy words). Write an acceptance-criteria checklist (title ≤100 chars with keyword up front, description opens with the keyword in the first line, ≥3 chapters with first at 00:00 and monotonic timestamps within duration, tag list present, 3 title options, thumbnail text ideas) and decisions to `{{workPath}}/scope.md` via write_task_note AND the produces path.\n\nThe deliverable `{{workPath}}/scope.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "planner",
+      "advanceWhen": {
+        "file": "{{workPath}}/scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "scope",
+        "maxAttempts": 3
+      },
+      "next": "analyze"
+    },
+    {
+      "id": "analyze",
+      "name": "Find chapters & keywords",
+      "description": "topic-shift timestamps + keyword extraction",
+      "prompt": "Mine the transcript for structure and terms. Step 1: read the transcript with timestamps and detect topic boundaries where the subject clearly shifts. Step 2: for each boundary record a `MM:SS`/`HH:MM:SS` timestamp and a short keyword-aware title; force the first to `00:00`. Step 3: enforce ≥3 chapters, monotonic timestamps within the duration, and reasonable spacing. Step 4: extract the recurring topics/terms the video actually covers (frequency + relevance) to inform tags and ensure the title/description match the content. Step 5: write the chapters and a candidate keyword/tag list to `{{workPath}}/analysis.json` via write_task_note AND the produces path. On a loop-back, adjust only the flagged chapters/terms.\n\nThe deliverable `{{workPath}}/analysis.json` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "data-analyst",
+      "advanceWhen": {
+        "file": "{{workPath}}/analysis.json",
+        "minBytes": 1,
+        "sniff": "json-valid",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/analysis.json",
+            "bytes": 2,
+            "artifact": true
+          }
+        ],
+        "onReject": "analyze",
+        "maxAttempts": 3
+      },
+      "next": "write"
+    },
+    {
+      "id": "write",
+      "name": "Write the metadata kit",
+      "description": "title options, description+chapters, tags, thumbnail text",
+      "prompt": "Assemble the paste-ready kit from the analysis. Step 1: write 3 title options, each ≤100 chars with the primary keyword front-loaded; mark a recommended one. Step 2: write the description: a hook FIRST line containing the keyword (this is the search snippet), a 2-3 sentence summary, then the CHAPTERS block as plain `00:00 Title` lines (first line `00:00`) pasted from the analysis, then a links/CTA section, then 3-5 hashtags. Step 3: write a comma-separated tags line from the keyword analysis within the budget. Step 4: give 2-3 thumbnail text ideas (≤4 words each). Step 5: assemble everything into `youtube-metadata.md` under clear headers. Keep claims accurate to the video — no clickbait that the content does not deliver. write_task_note the path and chapter count. On a loop-back, fix only the flagged sections.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "youtube-metadata.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "youtube-metadata.md",
+            "bytes": 500
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkContains",
+            "scope": "standard",
+            "inputs": {
+              "file": "youtube-metadata.md",
+              "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+              "flags": "i"
+            }
+          }
+        ],
+        "onReject": "write",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Validate the kit against platform rules. Step 1: confirm `youtube-metadata.md` has all sections (3 titles, description, chapters, tags, thumbnail text) — PASS/FAIL. Step 2: confirm each title is ≤100 chars with the keyword front-loaded, and the description's FIRST line contains the keyword. Step 3: confirm the chapters block has ≥3 markers, the first is `00:00`, timestamps are monotonic and within the video duration. Step 4: spot-check 2 chapter timestamps against the transcript — real topic shifts? Step 5: confirm tags fit the budget and titles/description honestly match the content (no clickbait). Write PASS/FAIL per criterion.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"write\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "consumes": [
+        {
+          "file": "youtube-metadata.md"
+        }
+      ],
+      "next": "write"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
+      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
+      "suggestedRole": "developer",
+      "terminal": true
+    }
+  ],
+  "version": "1.0.2",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  },
+  "minGezelVersion": "1.26233"
+}