@bendyline/gilde 0.1.95 → 0.2.1

package/data/craftbook-templates/re/reading-list/manifest.json

@@ -4,6 +4,9 @@
   "id": "reading-list",
   "role": "general",
   "category": "research",
+  "interests": [
+    "learning"
+  ],
   "name": "Curated Annotated Reading List",
   "description": "Curate an annotated reading list on a topic for a defined reader: a planner sets the reader, their goal, and the selection and ordering criteria, then a researcher curates and annotates each pick with why it matters, what it covers, and a suggested reading order. The ordering matters because a list assembled without a reader and a goal becomes a random link dump, and one without annotations forces the reader to guess what to read first; fixing who it is for and what 'good for this reader' means up front turns it into a guided learning path. Use this for curated reading lists, a syllabus or learning path, 'what should I read to learn X', resource roundups, and annotated bibliographies of recommended materials.",
   "tags": [

package/data/craftbook-templates/re/receipt-intake/manifest.json

@@ -4,6 +4,10 @@
   "id": "receipt-intake",
   "role": "general",
   "category": "business",
+  "interests": [
+    "home",
+    "business"
+  ],
   "name": "Receipt Intake",
   "description": "Empty the shoebox inbox properly: every waiting receipt becomes a dated, categorized ledger entry that names its source file, likely duplicates get flagged instead of double-counted, and the genuinely ambiguous ones become owner questions instead of guesses. Locks the intake rules FIRST, then works the inbox receipt by receipt, then reports the totals and the question list — the year-round habit that makes April an afternoon. Use for receipt intake, emptying the receipt inbox, 'get these into the ledger', and monthly shoebox catch-ups.",
   "tags": [

package/data/craftbook-templates/re/receipt-ocr-ledger/manifest.json

@@ -4,6 +4,9 @@
   "id": "receipt-ocr-ledger",
   "role": "general",
   "category": "business",
+  "interests": [
+    "business"
+  ],
   "name": "Receipts to Expense Ledger",
   "description": "Turn a folder of receipt photos/PDFs into a clean expense ledger: OCR each receipt, extract vendor, date, line items, tax, and total, assign an expense category, and reconcile that each extracted total matches its line items. Locks the per-receipt field schema, the category set, and the math/reconciliation rules FIRST, then OCRs and extracts each receipt into rows, then verifies every receipt was processed, totals reconcile, currencies/dates are normalized, and low-confidence reads are flagged for review. Defining the schema and the total-equals-line-items check before extraction is what keeps an expense ledger trustworthy for reimbursement or tax.",
   "tags": [

package/data/craftbook-templates/re/recurring-invoice-run/manifest.json

@@ -4,6 +4,9 @@
   "id": "recurring-invoice-run",
   "role": "general",
   "category": "business",
+  "interests": [
+    "business"
+  ],
   "name": "Generate and Send Recurring Invoices",
   "description": "Run a recurring billing batch: for each active client/subscription due this period, generate a correctly-numbered, line-itemed invoice with taxes and totals, render it, and send it — once, idempotently, with a sent-log. Locks the invoice template, the numbering scheme, the tax/total math, and the due/idempotency rules FIRST, then builds the generate-render-send batch keyed to a billing-run log, then verifies every due client was invoiced exactly once, totals are arithmetically correct, and numbers are sequential with no gaps or dupes. Locking numbering and math up front is what keeps recurring billing audit-clean instead of producing duplicate or mis-totaled invoices.",
   "tags": [

package/data/craftbook-templates/re/release-announcement/manifest.json

@@ -4,6 +4,10 @@
   "id": "release-announcement",
   "role": "general",
   "category": "marketing",
+  "interests": [
+    "software",
+    "content"
+  ],
   "name": "Release Announcement",
   "description": "Write a public-facing release announcement that turns a shipped version into a compelling story for users — a blog-post / email-style piece that leads with the headline value, shows the marquee features with concrete before/after benefits, links to the full release notes and upgrade path, and ends with a clear call to action. A planner picks the 2-4 things actually worth announcing and the audience/channel, a copywriter writes the benefit-led announcement in the brand voice, and a reviewer checks it is accurate, on-message, and that every claim traces to a real shipped change. Use this for product launch posts, 'what's new' announcements, version launch emails, and changelog-to-marketing translations.",
   "tags": [

package/data/craftbook-templates/re/resume-cv/manifest.json

@@ -4,6 +4,9 @@
   "id": "resume-cv",
   "role": "general",
   "category": "business",
+  "interests": [
+    "learning"
+  ],
   "name": "Résumé / CV",
   "description": "Build a clean, ATS-friendly résumé or CV from a person's background, tailored to a target role. Scopes the target role and the highlight reel of achievements FIRST (so the résumé is targeted, not a life history), then designs a single-column, parser-safe layout, then writes impact-led bullets with metrics that fit one to two pages. Use for job applications, LinkedIn-to-résumé conversions, and role-targeted CV rewrites.",
   "tags": [

package/data/craftbook-templates/re/review-code-folder/manifest.json

@@ -0,0 +1,25 @@
+{
+  "schemaVersion": 1,
+  "kind": "craftbook-template",
+  "id": "review-code-folder",
+  "role": "general",
+  "category": "code-review",
+  "interests": [
+    "software"
+  ],
+  "name": "Review a code folder",
+  "description": "A careful colleague's review of a folder of code: a short summary, each real problem with its file and line, how serious it is, what goes wrong and a suggested fix, and what the code does well. It reads the code without running it and reports only problems it can point to in a line.",
+  "tags": [
+    "gallery",
+    "first-project",
+    "code",
+    "review",
+    "bugs",
+    "quality"
+  ],
+  "maintainer": {
+    "name": "Gezel"
+  },
+  "license": "MIT",
+  "yankedVersions": []
+}

package/data/craftbook-templates/re/review-code-folder/versions/1.0.0/craftbook.json

@@ -0,0 +1,223 @@
+{
+  "id": "review-code-folder",
+  "name": "Review a code folder",
+  "description": "A careful colleague's review of a folder of code: a short summary, each real problem with its file and line, how serious it is, what goes wrong and a suggested fix, and what the code does well. It reads the code without running it and reports only problems it can point to in a line.\n\nIt works on the folder you choose when you launch it: a folder in this project, or one you pick from your computer. It never runs or changes the code. No code to hand? Try it on the sample, a small to-do app.",
+  "entryStepId": "review",
+  "triggers": [
+    "review a code folder",
+    "review this folder of code",
+    "find bugs in this code",
+    "what is wrong with this code"
+  ],
+  "samples": [
+    {
+      "id": "todo-cli-bugs",
+      "title": "a small to-do app's code",
+      "param": "source",
+      "files": [
+        "samples/todo-cli-bugs/README.md",
+        "samples/todo-cli-bugs/package.json",
+        "samples/todo-cli-bugs/src/index.js",
+        "samples/todo-cli-bugs/src/store.js",
+        "samples/todo-cli-bugs/src/format.js",
+        "samples/todo-cli-bugs/test/store.test.js"
+      ]
+    }
+  ],
+  "paramSchema": {
+    "type": "object",
+    "required": [
+      "source"
+    ],
+    "properties": {
+      "source": {
+        "type": "string",
+        "title": "Code folder",
+        "description": "The folder of code to review: a folder in this project, or one you pick from your computer.",
+        "input": {
+          "kind": "folder",
+          "accept": [
+            ".js",
+            ".mjs",
+            ".cjs",
+            ".jsx",
+            ".ts",
+            ".tsx",
+            ".py",
+            ".rb",
+            ".go",
+            ".rs",
+            ".java",
+            ".kt",
+            ".cs",
+            ".php",
+            ".swift",
+            ".c",
+            ".h",
+            ".cpp",
+            ".hpp",
+            ".sh",
+            ".sql",
+            ".html",
+            ".css",
+            ".scss",
+            ".vue",
+            ".svelte",
+            ".md",
+            ".txt",
+            ".json",
+            ".toml",
+            ".yaml",
+            ".yml",
+            ".ini",
+            ".cfg",
+            ".xml"
+          ]
+        }
+      },
+      "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}}",
+        "askUser": false
+      }
+    }
+  },
+  "steps": [
+    {
+      "id": "review",
+      "name": "Review the code",
+      "description": "Read the code and write a review of the real problems in it.",
+      "prompt": "Review the code in the `source` input the way a careful colleague would, and write the review to `{{workPath}}/review.md`.\n\n1. Open the file list `{{task.dir}}/inputs/source.json` with `read_artifact`. It lists every file in the folder and the drawer they are in.\n2. Read every source file and test with the tool named on the `source` line under Invocation parameters. If there are more than 20, read the entry point and the files it uses first, 20 at most.\n3. Look for real defects. Follow one concrete input through each function: does it return the right thing, change the right item, save what it changed, wait for what it starts, and handle the errors it can hit? Watch for counting that is off by one, a missing `await`, a change that is never saved, an error that is swallowed, input that is never checked, and a crash on an empty or missing value.\n4. Write `{{workPath}}/review.md` with `write_artifact`, under exactly these three headings:\n   - `## Summary`: two or three sentences on what the code does and how sound it is.\n   - `## Findings`: one entry per real problem, the most serious first. Give each one its file and line (`path/to/file.js:12`), a severity of high, medium or low, what goes wrong with a concrete example, and a suggested fix. If you find no real problem, write `No problems found.`\n   - `## What is good`: two or three things the code does well.\n\nReport only problems you can point to in a line of the code you read. Never invent a file, a line or a bug, and do not pad the list: one real finding beats five guesses.\n\nIf the folder holds no file you can read, do not write `review.md`. Write a task note with `write_task_note` that says what you found, then end your turn.",
+      "suggestedRole": "reviewer",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "artifact",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      },
+      "consumes": [
+        {
+          "file": "{{task.dir}}/inputs/source.json",
+          "artifact": true
+        }
+      ],
+      "advanceWhen": {
+        "file": "{{workPath}}/review.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/review.md",
+            "bytes": 300,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/review.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*Summary",
+            "flags": "i",
+            "label": "a \"## Summary\" section",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/review.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*Findings",
+            "flags": "i",
+            "label": "a \"## Findings\" section",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/review.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*What is good",
+            "flags": "i",
+            "label": "a \"## What is good\" section",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/review.md",
+            "pattern": "[\\w./-]+\\.[A-Za-z0-9]{1,10}`?\\s*(?::|,?\\s*\\(?lines?\\s*)\\d+|lines?\\s+\\d+\\s+(?:of|in)\\s+`?[\\w./-]+\\.[A-Za-z0-9]{1,10}|No problems found",
+            "flags": "i",
+            "label": "a finding that names its file and line, or \"No problems found.\"",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/review.md",
+            "pattern": "\\b(?:high|medium|low)\\b|No problems found",
+            "flags": "i",
+            "label": "a severity of high, medium or low on the findings",
+            "artifact": true
+          }
+        ],
+        "onReject": "review",
+        "maxAttempts": 3
+      },
+      "next": "finish"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "The deliverable passed its checks. Stamp a short summary and report DONE.",
+      "prompt": "The deliverable passed its checks. Write a one-paragraph DONE summary to task notes via `write_task_note`: what you made, the deliverable path(s), and a one-line confirmation that each required section is there. Then report DONE.",
+      "suggestedRole": "reviewer",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "task-note"
+      },
+      "terminal": true
+    }
+  ],
+  "version": "1.0.0",
+  "releasedAt": "2026-10-12T00:00:00Z",
+  "minGezelVersion": "1.26285"
+}

package/data/craftbook-templates/re/review-code-folder/versions/1.0.0/samples/todo-cli-bugs/README.md

@@ -0,0 +1,29 @@
+# todo-cli
+
+A tiny to-do list for the command line. It keeps your to-dos in a JSON file
+in the current folder, so each project folder can have its own list.
+
+## Usage
+
+```sh
+node src/index.js add "Buy oat milk"
+node src/index.js list
+node src/index.js done 2
+node src/index.js remove 1
+```
+
+`list` prints every to-do with its number. `done` and `remove` take that
+number. Set `TODO_FILE` to keep the list somewhere else:
+
+```sh
+TODO_FILE=~/todos.json node src/index.js list
+```
+
+## Tests
+
+```sh
+npm test
+```
+
+The tests use Node's built-in test runner (Node 18 or newer). There are no
+dependencies to install.

package/data/craftbook-templates/re/review-code-folder/versions/1.0.0/samples/todo-cli-bugs/package.json

@@ -0,0 +1,17 @@
+{
+  "name": "todo-cli",
+  "version": "0.3.0",
+  "description": "A tiny to-do list for the command line.",
+  "type": "module",
+  "bin": {
+    "todo": "src/index.js"
+  },
+  "scripts": {
+    "start": "node src/index.js",
+    "test": "node --test"
+  },
+  "engines": {
+    "node": ">=18"
+  },
+  "license": "MIT"
+}

package/data/craftbook-templates/re/review-code-folder/versions/1.0.0/samples/todo-cli-bugs/src/format.js

@@ -0,0 +1,15 @@
+export function formatTodo(todo, index) {
+  const box = todo.done ? '[x]' : '[ ]';
+  return `${String(index + 1).padStart(2)}. ${box} ${todo.text}`;
+}
+
+export function formatList(todos) {
+  if (todos.length === 0) return 'Nothing to do. Add one with: todo add "..."';
+  return todos.map(formatTodo).join('\n');
+}
+
+export function formatSummary(todos) {
+  const open = todos.filter((todo) => !todo.done).length;
+  const word = open === 1 ? 'to-do' : 'to-dos';
+  return `${open} open ${word}, ${todos.length - open} done.`;
+}

package/data/craftbook-templates/re/review-code-folder/versions/1.0.0/samples/todo-cli-bugs/src/index.js

@@ -0,0 +1,50 @@
+#!/usr/bin/env node
+import { formatList, formatSummary } from './format.js';
+import { addTodo, completeTodo, loadTodos, removeTodo } from './store.js';
+
+const file = process.env.TODO_FILE ?? 'todos.json';
+const [command, ...rest] = process.argv.slice(2);
+
+function readNumber(value) {
+  const number = Number(value);
+  if (!Number.isInteger(number) || number < 1) {
+    throw new Error(`"${value}" is not a to-do number. Run "todo list" to see the numbers.`);
+  }
+  return number;
+}
+
+async function main() {
+  switch (command) {
+    case 'add': {
+      const text = rest.join(' ').trim();
+      if (!text) throw new Error('Say what to add: todo add "Buy oat milk"');
+      const todo = await addTodo(file, text);
+      console.log(`Added: ${todo.text}`);
+      break;
+    }
+    case 'list': {
+      const todos = await loadTodos(file);
+      console.log(formatList(todos));
+      console.log(formatSummary(todos));
+      break;
+    }
+    case 'done': {
+      const todo = await completeTodo(file, readNumber(rest[0]));
+      console.log(`Done: ${todo.text}`);
+      break;
+    }
+    case 'remove': {
+      const todo = await removeTodo(file, readNumber(rest[0]));
+      console.log(`Removed: ${todo.text}`);
+      break;
+    }
+    default:
+      console.log('Usage: todo <add|list|done|remove> [text or number]');
+      process.exitCode = command ? 1 : 0;
+  }
+}
+
+main().catch((error) => {
+  console.error(error.message);
+  process.exitCode = 1;
+});

package/data/craftbook-templates/re/review-code-folder/versions/1.0.0/samples/todo-cli-bugs/src/store.js

@@ -0,0 +1,44 @@
+import { readFile, writeFile } from 'node:fs/promises';
+
+export async function loadTodos(file) {
+  try {
+    const text = await readFile(file, 'utf8');
+    return JSON.parse(text);
+  } catch (error) {
+    if (error.code === 'ENOENT') return [];
+    throw error;
+  }
+}
+
+export async function saveTodos(file, todos) {
+  await writeFile(file, `${JSON.stringify(todos, null, 2)}\n`);
+}
+
+export async function addTodo(file, text) {
+  const todos = await loadTodos(file);
+  const todo = { text, done: false, added: new Date().toISOString().slice(0, 10) };
+  todos.push(todo);
+  await saveTodos(file, todos);
+  return todo;
+}
+
+function pick(todos, number) {
+  const todo = todos[number - 1];
+  if (!todo) throw new Error(`There is no to-do number ${number}.`);
+  return todo;
+}
+
+export async function completeTodo(file, number) {
+  const todos = await loadTodos(file);
+  const todo = pick(todos, number);
+  todo.done = true;
+  return todo;
+}
+
+export async function removeTodo(file, number) {
+  const todos = await loadTodos(file);
+  pick(todos, number);
+  const [removed] = todos.splice(number, 1);
+  await saveTodos(file, todos);
+  return removed;
+}

package/data/craftbook-templates/re/review-code-folder/versions/1.0.0/samples/todo-cli-bugs/test/store.test.js

@@ -0,0 +1,37 @@
+import assert from 'node:assert/strict';
+import { mkdtemp, rm } from 'node:fs/promises';
+import { tmpdir } from 'node:os';
+import { join } from 'node:path';
+import { test } from 'node:test';
+import { addTodo, loadTodos, removeTodo } from '../src/store.js';
+
+async function withFile(run) {
+  const dir = await mkdtemp(join(tmpdir(), 'todo-cli-'));
+  try {
+    await run(join(dir, 'todos.json'));
+  } finally {
+    await rm(dir, { recursive: true, force: true });
+  }
+}
+
+test('a missing file is an empty list', () =>
+  withFile(async (file) => {
+    assert.deepEqual(await loadTodos(file), []);
+  }));
+
+test('add keeps to-dos in the order they were added', () =>
+  withFile(async (file) => {
+    await addTodo(file, 'Buy oat milk');
+    await addTodo(file, 'Call the plumber');
+    const todos = await loadTodos(file);
+    assert.deepEqual(
+      todos.map((todo) => todo.text),
+      ['Buy oat milk', 'Call the plumber'],
+    );
+  }));
+
+test('a number past the end is an error', () =>
+  withFile(async (file) => {
+    await addTodo(file, 'Buy oat milk');
+    await assert.rejects(removeTodo(file, 3), /no to-do number 3/);
+  }));

package/data/craftbook-templates/re/review-code-folder/versions/1.0.0/test.json

@@ -0,0 +1,108 @@
+{
+  "schemaVersion": 1,
+  "mode": "workflow",
+  "title": "Review a code folder on the todo-cli-bugs sample",
+  "objective": "Prove that a small local model can run the Review a code folder craftbook on its bundled todo-cli-bugs sample, offline, and reach the terminal step with a review that finds the two real defects in store.js with their lines.",
+  "tags": [
+    "first-project",
+    "sample",
+    "code"
+  ],
+  "prompt": "Review the code of this small to-do app and tell me what is wrong with it.",
+  "setup": {
+    "projectName": "Todo CLI review",
+    "about": "A tiny made-up Node.js to-do app for the command line, six files in source/todo-cli-bugs. Nothing needs to be run or installed; read the code.",
+    "missionObjectives": "Run the craftbook on source/todo-cli-bugs and leave review.md in the task folder, reporting only problems that can be pointed to in a line.",
+    "files": [
+      {
+        "path": "source/todo-cli-bugs/README.md",
+        "content": "# todo-cli\n\nA tiny to-do list for the command line. It keeps your to-dos in a JSON file\nin the current folder, so each project folder can have its own list.\n\n## Usage\n\n```sh\nnode src/index.js add \"Buy oat milk\"\nnode src/index.js list\nnode src/index.js done 2\nnode src/index.js remove 1\n```\n\n`list` prints every to-do with its number. `done` and `remove` take that\nnumber. Set `TODO_FILE` to keep the list somewhere else:\n\n```sh\nTODO_FILE=~/todos.json node src/index.js list\n```\n\n## Tests\n\n```sh\nnpm test\n```\n\nThe tests use Node's built-in test runner (Node 18 or newer). There are no\ndependencies to install.\n"
+      },
+      {
+        "path": "source/todo-cli-bugs/package.json",
+        "content": "{\n  \"name\": \"todo-cli\",\n  \"version\": \"0.3.0\",\n  \"description\": \"A tiny to-do list for the command line.\",\n  \"type\": \"module\",\n  \"bin\": {\n    \"todo\": \"src/index.js\"\n  },\n  \"scripts\": {\n    \"start\": \"node src/index.js\",\n    \"test\": \"node --test\"\n  },\n  \"engines\": {\n    \"node\": \">=18\"\n  },\n  \"license\": \"MIT\"\n}\n"
+      },
+      {
+        "path": "source/todo-cli-bugs/src/format.js",
+        "content": "export function formatTodo(todo, index) {\n  const box = todo.done ? '[x]' : '[ ]';\n  return `${String(index + 1).padStart(2)}. ${box} ${todo.text}`;\n}\n\nexport function formatList(todos) {\n  if (todos.length === 0) return 'Nothing to do. Add one with: todo add \"...\"';\n  return todos.map(formatTodo).join('\\n');\n}\n\nexport function formatSummary(todos) {\n  const open = todos.filter((todo) => !todo.done).length;\n  const word = open === 1 ? 'to-do' : 'to-dos';\n  return `${open} open ${word}, ${todos.length - open} done.`;\n}\n"
+      },
+      {
+        "path": "source/todo-cli-bugs/src/index.js",
+        "content": "#!/usr/bin/env node\nimport { formatList, formatSummary } from './format.js';\nimport { addTodo, completeTodo, loadTodos, removeTodo } from './store.js';\n\nconst file = process.env.TODO_FILE ?? 'todos.json';\nconst [command, ...rest] = process.argv.slice(2);\n\nfunction readNumber(value) {\n  const number = Number(value);\n  if (!Number.isInteger(number) || number < 1) {\n    throw new Error(`\"${value}\" is not a to-do number. Run \"todo list\" to see the numbers.`);\n  }\n  return number;\n}\n\nasync function main() {\n  switch (command) {\n    case 'add': {\n      const text = rest.join(' ').trim();\n      if (!text) throw new Error('Say what to add: todo add \"Buy oat milk\"');\n      const todo = await addTodo(file, text);\n      console.log(`Added: ${todo.text}`);\n      break;\n    }\n    case 'list': {\n      const todos = await loadTodos(file);\n      console.log(formatList(todos));\n      console.log(formatSummary(todos));\n      break;\n    }\n    case 'done': {\n      const todo = await completeTodo(file, readNumber(rest[0]));\n      console.log(`Done: ${todo.text}`);\n      break;\n    }\n    case 'remove': {\n      const todo = await removeTodo(file, readNumber(rest[0]));\n      console.log(`Removed: ${todo.text}`);\n      break;\n    }\n    default:\n      console.log('Usage: todo <add|list|done|remove> [text or number]');\n      process.exitCode = command ? 1 : 0;\n  }\n}\n\nmain().catch((error) => {\n  console.error(error.message);\n  process.exitCode = 1;\n});\n"
+      },
+      {
+        "path": "source/todo-cli-bugs/src/store.js",
+        "content": "import { readFile, writeFile } from 'node:fs/promises';\n\nexport async function loadTodos(file) {\n  try {\n    const text = await readFile(file, 'utf8');\n    return JSON.parse(text);\n  } catch (error) {\n    if (error.code === 'ENOENT') return [];\n    throw error;\n  }\n}\n\nexport async function saveTodos(file, todos) {\n  await writeFile(file, `${JSON.stringify(todos, null, 2)}\\n`);\n}\n\nexport async function addTodo(file, text) {\n  const todos = await loadTodos(file);\n  const todo = { text, done: false, added: new Date().toISOString().slice(0, 10) };\n  todos.push(todo);\n  await saveTodos(file, todos);\n  return todo;\n}\n\nfunction pick(todos, number) {\n  const todo = todos[number - 1];\n  if (!todo) throw new Error(`There is no to-do number ${number}.`);\n  return todo;\n}\n\nexport async function completeTodo(file, number) {\n  const todos = await loadTodos(file);\n  const todo = pick(todos, number);\n  todo.done = true;\n  return todo;\n}\n\nexport async function removeTodo(file, number) {\n  const todos = await loadTodos(file);\n  pick(todos, number);\n  const [removed] = todos.splice(number, 1);\n  await saveTodos(file, todos);\n  return removed;\n}\n"
+      },
+      {
+        "path": "source/todo-cli-bugs/test/store.test.js",
+        "content": "import assert from 'node:assert/strict';\nimport { mkdtemp, rm } from 'node:fs/promises';\nimport { tmpdir } from 'node:os';\nimport { join } from 'node:path';\nimport { test } from 'node:test';\nimport { addTodo, loadTodos, removeTodo } from '../src/store.js';\n\nasync function withFile(run) {\n  const dir = await mkdtemp(join(tmpdir(), 'todo-cli-'));\n  try {\n    await run(join(dir, 'todos.json'));\n  } finally {\n    await rm(dir, { recursive: true, force: true });\n  }\n}\n\ntest('a missing file is an empty list', () =>\n  withFile(async (file) => {\n    assert.deepEqual(await loadTodos(file), []);\n  }));\n\ntest('add keeps to-dos in the order they were added', () =>\n  withFile(async (file) => {\n    await addTodo(file, 'Buy oat milk');\n    await addTodo(file, 'Call the plumber');\n    const todos = await loadTodos(file);\n    assert.deepEqual(\n      todos.map((todo) => todo.text),\n      ['Buy oat milk', 'Call the plumber'],\n    );\n  }));\n\ntest('a number past the end is an error', () =>\n  withFile(async (file) => {\n    await addTodo(file, 'Buy oat milk');\n    await assert.rejects(removeTodo(file, 3), /no to-do number 3/);\n  }));\n"
+      }
+    ],
+    "craftbookParams": {
+      "source": "source/todo-cli-bugs"
+    },
+    "worker": {
+      "name": "Reviewer",
+      "role": "reviewer",
+      "about": "A careful, fair code reviewer. Follow the craftbook steps exactly, read the code you are given, and report only problems you can point to in a line."
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The review-code-folder task read the sample folder, wrote review.md with all three sections, found the off-by-one in removeTodo and the unsaved done flag in completeTodo with their lines, and reached its terminal step without external services.",
+    "deliverables": [
+      {
+        "path": "{{task.dir}}/review.md",
+        "kind": "markdown-report",
+        "artifact": true,
+        "minBytes": 300,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "{{task.dir}}/review.md",
+            "pattern": "splice\\(\\s*number\\s*,|off[- ]by[- ]one|wrong (?:item|to-do|todo|entry)|next (?:item|to-do|todo)",
+            "flags": "i",
+            "label": "the off-by-one in removeTodo",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{task.dir}}/review.md",
+            "pattern": "(?:never|not|isn't|is not|doesn't|does not|without|missing|no)\\s+(?:\\w+\\s+){0,3}(?:sav\\w*|persist\\w*|writ\\w*|saveTodos)",
+            "flags": "i",
+            "label": "the done flag that is never saved",
+            "artifact": true
+          }
+        ]
+      }
+    ],
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    }
+  },
+  "rubric": {
+    "artifact": {
+      "path": "{{task.dir}}/review.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "accuracy",
+        "description": "The findings are the two real defects (removeTodo removes the item after the one asked for; completeTodo never saves the done flag), each with its file and line, and no invented bugs."
+      },
+      {
+        "name": "usefulness",
+        "description": "Each finding has a fair severity, a concrete example of what goes wrong, and a fix a developer could apply as written."
+      }
+    ],
+    "contextNote": "Advisory only. Deterministic pass/fail comes from the craftbook runtime gates, the deliverable checks, attribution, and terminal progress."
+  },
+  "qualityFocus": [
+    "real review-code-folder craftbook task attribution",
+    "findings pointed to a file and line",
+    "no invented bugs",
+    "terminal workflow progress offline"
+  ]
+}

package/data/craftbook-templates/sc/scrape-to-structured/manifest.json

@@ -4,6 +4,9 @@
   "id": "scrape-to-structured",
   "role": "general",
   "category": "code-data",
+  "interests": [
+    "data"
+  ],
   "name": "Scrape a Site to Structured Data",
   "description": "Turn one or more web pages into a clean, structured dataset (JSON or CSV) with a fixed schema — product listings, directory entries, articles, tables, or job posts. Scopes the exact fields and a sample-row target FIRST so extraction is verifiable, then crawls and parses each page into rows, then validates that every row matches the schema, types are coerced, required fields are non-empty, and there are no duplicates. The scope-before-scrape ordering is the point: a small model that locks the field list and one hand-written sample row extracts consistently instead of inventing keys per page.",
   "tags": [

package/data/craftbook-templates/sp/spa-dashboard/manifest.json

@@ -4,6 +4,10 @@
   "id": "spa-dashboard",
   "role": "project-starter",
   "category": "code-build",
+  "interests": [
+    "software",
+    "data"
+  ],
   "name": "Metrics / Admin Dashboard",
   "description": "Build a single-page metrics or admin dashboard with KPI summary cards, at least one chart, and a data table, rendered from sample or provided data. Locks the data model and which metrics matter first, then a scannable dashboard layout (grid of cards, chart placement, table), then builds the interactive HTML with a lightweight charting approach and a sortable/filterable table. Deciding the metrics and layout before coding prevents a small model from dumping raw data with no hierarchy; a dashboard's value is the at-a-glance summary up top.",
   "tags": [