@bendyline/gilde 0.1.95 → 0.2.1

package/data/craftbook-templates/ex/explain-code-folder/versions/1.0.0/craftbook.json

@@ -0,0 +1,233 @@
+{
+  "id": "explain-code-folder",
+  "name": "Explain a code folder",
+  "description": "A plain-language tour of a folder of code: what it does, how the files are organised, how to run it, and the three files to read first. Every file and command it names comes from the folder itself. Good for a project you inherited, an open-source tool you want to understand, or your own code after a long break.\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 reads the code and never runs or changes it. No code to hand? Try it on the sample, a tiny to-do app for the command line.",
+  "entryStepId": "explain",
+  "triggers": [
+    "explain a code folder",
+    "explain this codebase",
+    "what does this code do",
+    "overview of this repo",
+    "walk me through this code"
+  ],
+  "samples": [
+    {
+      "id": "todo-cli",
+      "title": "a tiny to-do app for the command line",
+      "param": "source",
+      "files": [
+        "samples/todo-cli/README.md",
+        "samples/todo-cli/package.json",
+        "samples/todo-cli/src/index.js",
+        "samples/todo-cli/src/store.js",
+        "samples/todo-cli/src/format.js",
+        "samples/todo-cli/test/store.test.js"
+      ]
+    }
+  ],
+  "paramSchema": {
+    "type": "object",
+    "required": [
+      "source"
+    ],
+    "properties": {
+      "source": {
+        "type": "string",
+        "title": "Code folder",
+        "description": "The folder of code to explain: 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": "explain",
+      "name": "Explain the folder",
+      "description": "Read the code and write a plain-language overview of it.",
+      "prompt": "Explain the code folder in the `source` input to someone who has never seen it, in `{{workPath}}/overview.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 the files with the tool named on the `source` line under Invocation parameters: the README first, if there is one, then the file that names the project and its commands (package.json, pyproject.toml, Cargo.toml, a Makefile or similar), then the entry point, then the rest. If there are more than 15 files, read those first and then the files they name, 15 at most.\n3. Write `{{workPath}}/overview.md` with `write_artifact`, under exactly these four headings:\n   - `## What it does`: two or three sentences in plain words.\n   - `## How it is organised`: a markdown table with the columns `File` and `What it holds`, one row per file you read, each path in backticks and relative to the folder (`src/app.js`, not the full drawer path).\n   - `## How to run it`: the commands the README or the project file actually gives, in a code block. If they give none, say so.\n   - `## Three things to read first`: a numbered list of three files, each with one line on why.\n\nName only files that are in the file list and commands the files state. Never invent a file, a function or a command.\n\nIf the folder holds no file you can read, do not write `overview.md`. Write a task note with `write_task_note` that says what you found, then end your turn.",
+      "suggestedRole": "developer",
+      "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}}/overview.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/overview.md",
+            "bytes": 800,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/overview.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*What it does",
+            "flags": "i",
+            "label": "a \"## What it does\" section",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/overview.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*How it is organised",
+            "flags": "i",
+            "label": "a \"## How it is organised\" section",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/overview.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*How to run it",
+            "flags": "i",
+            "label": "a \"## How to run it\" section",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/overview.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*Three things to read first",
+            "flags": "i",
+            "label": "a \"## Three things to read first\" section",
+            "artifact": true
+          },
+          {
+            "kind": "tableShape",
+            "file": "{{workPath}}/overview.md",
+            "requiredColumns": [
+              "File",
+              "What it holds"
+            ],
+            "minRows": 2,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/overview.md",
+            "pattern": "`[^`\\n]+\\.[A-Za-z0-9]{1,10}`",
+            "label": "file paths from the folder, in backticks",
+            "artifact": true
+          }
+        ],
+        "onReject": "explain",
+        "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": "developer",
+      "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/ex/explain-code-folder/versions/1.0.0/samples/todo-cli/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/ex/explain-code-folder/versions/1.0.0/samples/todo-cli/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/ex/explain-code-folder/versions/1.0.0/samples/todo-cli/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/ex/explain-code-folder/versions/1.0.0/samples/todo-cli/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/ex/explain-code-folder/versions/1.0.0/samples/todo-cli/src/store.js

@@ -0,0 +1,45 @@
+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;
+  await saveTodos(file, todos);
+  return todo;
+}
+
+export async function removeTodo(file, number) {
+  const todos = await loadTodos(file);
+  pick(todos, number);
+  const [removed] = todos.splice(number - 1, 1);
+  await saveTodos(file, todos);
+  return removed;
+}

package/data/craftbook-templates/ex/explain-code-folder/versions/1.0.0/samples/todo-cli/test/store.test.js

@@ -0,0 +1,61 @@
+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, completeTodo, 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('done marks the numbered to-do and saves it', () =>
+  withFile(async (file) => {
+    await addTodo(file, 'Buy oat milk');
+    await addTodo(file, 'Call the plumber');
+    await completeTodo(file, 2);
+    const todos = await loadTodos(file);
+    assert.equal(todos[0].done, false);
+    assert.equal(todos[1].done, true);
+  }));
+
+test('remove takes out the numbered to-do', () =>
+  withFile(async (file) => {
+    await addTodo(file, 'Buy oat milk');
+    await addTodo(file, 'Call the plumber');
+    await addTodo(file, 'Water the plants');
+    const removed = await removeTodo(file, 1);
+    assert.equal(removed.text, 'Buy oat milk');
+    const todos = await loadTodos(file);
+    assert.deepEqual(
+      todos.map((todo) => todo.text),
+      ['Call the plumber', 'Water the plants'],
+    );
+  }));
+
+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/ex/explain-code-folder/versions/1.0.0/test.json

@@ -0,0 +1,106 @@
+{
+  "schemaVersion": 1,
+  "mode": "workflow",
+  "title": "Explain a code folder on the todo-cli sample",
+  "objective": "Prove that a small local model can run the Explain a code folder craftbook on its bundled todo-cli sample, offline, and reach the terminal step with an overview that names only real files and commands.",
+  "tags": [
+    "first-project",
+    "sample",
+    "code"
+  ],
+  "prompt": "Explain this little command-line to-do app to me: what it does, how it is put together, and how to run it.",
+  "setup": {
+    "projectName": "Todo CLI",
+    "about": "A tiny made-up Node.js to-do app for the command line, six files in source/todo-cli. Nothing needs to be run or installed; read the code.",
+    "missionObjectives": "Run the craftbook on source/todo-cli and leave overview.md in the task folder, naming only files and commands that are really there.",
+    "files": [
+      {
+        "path": "source/todo-cli/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/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/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/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/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  await saveTodos(file, todos);\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, 1);\n  await saveTodos(file, todos);\n  return removed;\n}\n"
+      },
+      {
+        "path": "source/todo-cli/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, completeTodo, 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('done marks the numbered to-do and saves it', () =>\n  withFile(async (file) => {\n    await addTodo(file, 'Buy oat milk');\n    await addTodo(file, 'Call the plumber');\n    await completeTodo(file, 2);\n    const todos = await loadTodos(file);\n    assert.equal(todos[0].done, false);\n    assert.equal(todos[1].done, true);\n  }));\n\ntest('remove takes out the numbered to-do', () =>\n  withFile(async (file) => {\n    await addTodo(file, 'Buy oat milk');\n    await addTodo(file, 'Call the plumber');\n    await addTodo(file, 'Water the plants');\n    const removed = await removeTodo(file, 1);\n    assert.equal(removed.text, 'Buy oat milk');\n    const todos = await loadTodos(file);\n    assert.deepEqual(\n      todos.map((todo) => todo.text),\n      ['Call the plumber', 'Water the plants'],\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"
+    },
+    "worker": {
+      "name": "Developer",
+      "role": "developer",
+      "about": "A patient developer who explains code to people who are new to it. Follow the craftbook steps exactly, read the code you are given, and never invent a file or a command."
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The explain-code-folder task read the sample folder, wrote overview.md with all four sections and a File / What it holds table naming real files and the README commands, and reached its terminal step without external services.",
+    "deliverables": [
+      {
+        "path": "{{task.dir}}/overview.md",
+        "kind": "markdown-report",
+        "artifact": true,
+        "minBytes": 800,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "{{task.dir}}/overview.md",
+            "pattern": "store\\.js",
+            "label": "the store module",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{task.dir}}/overview.md",
+            "pattern": "node src/index\\.js|npm (?:run )?test",
+            "label": "a run command the README gives",
+            "artifact": true
+          }
+        ]
+      }
+    ],
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    }
+  },
+  "rubric": {
+    "artifact": {
+      "path": "{{task.dir}}/overview.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "grounding",
+        "description": "Every file, function and command in overview.md exists in the sample folder; nothing is invented."
+      },
+      {
+        "name": "clarity",
+        "description": "Someone who has never seen the app understands what it does, where the data lives, and how to run it and its tests."
+      }
+    ],
+    "contextNote": "Advisory only. Deterministic pass/fail comes from the craftbook runtime gates, the deliverable checks, attribution, and terminal progress."
+  },
+  "qualityFocus": [
+    "real explain-code-folder craftbook task attribution",
+    "only real files and commands",
+    "all four required sections and the organisation table",
+    "terminal workflow progress offline"
+  ]
+}

package/data/craftbook-templates/fa/family-story-chapter/manifest.json

@@ -4,6 +4,10 @@
   "id": "family-story-chapter",
   "role": "general",
   "category": "writing",
+  "interests": [
+    "home",
+    "content"
+  ],
   "name": "Family Story Chapter",
   "description": "Write one chapter of the family story from the record you actually have — interviews and tree facts woven into narrative, speculation clearly dressed as speculation — the ritual that turns an archive into the book every family means to write. Locks the chapter's arc and the sourcing rules FIRST, then drafts from the record only, with a faithfulness pass that loops until every event traces. Use for drafting a family history chapter, writing up the emigration years, turning interviews into narrative, and 'write the family story'.",
   "tags": [

package/data/craftbook-templates/fo/forecast-model/manifest.json

@@ -4,6 +4,10 @@
   "id": "forecast-model",
   "role": "general",
   "category": "research",
+  "interests": [
+    "data",
+    "work"
+  ],
   "name": "Simple Forecast / Trend Model",
   "description": "Build a simple, defensible forecast of a time series (revenue, demand, signups, usage) with the assumptions and method stated up front and the projection plus a confidence band as the output. Scopes the series, horizon, method, and assumptions FIRST (so the forecast isn't an unexplained black box), then builds the projection with a baseline and an interval, then reviews it for sanity against history and overfitting. Use this for forecasting a metric, projecting a trend, estimating future demand, a simple time-series projection, or a 'what will this be next quarter' estimate.",
   "tags": [

package/data/craftbook-templates/ga/game-with-screens/manifest.json

@@ -4,6 +4,10 @@
   "id": "game-with-screens",
   "role": "project-starter",
   "category": "code-build",
+  "interests": [
+    "software",
+    "play"
+  ],
   "name": "Full Game with Title & Game-Over Screens",
   "description": "Build a complete single-file HTML game with the full screen flow — a title/start screen, the gameplay screen, a game-over screen showing the score, and a restart back to a fresh game — wrapping any core arcade or survival mechanic. Designs the mechanic and the screen-state machine first, a cohesive visual look across all screens, then implements a screen manager so transitions are clean and restart truly resets. Many small models nail gameplay but ship with no start or game-over screen; this archetype makes the screen flow a first-class, gated requirement.",
   "tags": [

package/data/craftbook-templates/gl/glossary-build/manifest.json

@@ -4,6 +4,9 @@
   "id": "glossary-build",
   "role": "general",
   "category": "code-docs",
+  "interests": [
+    "work"
+  ],
   "name": "Domain Glossary",
   "description": "Build a consistent, accurate glossary for a domain: a planner sets the domain scope, the term-selection criteria, and the entry template, a researcher gathers the canonical definition and usage for each term with sources, and a copywriter writes the alphabetized glossary with cross-references and consistent entries. The ordering matters because terms picked ad hoc leave gaps and inconsistent entries confuse readers; locking the scope, what makes a term in-scope, and a fixed entry template first guarantees coverage and a uniform, cross-linked glossary. Use this for building a domain or product glossary, a terms/definitions reference, an acronym list, onboarding vocabulary, and 'define all the key terms in X' requests.",
   "tags": [

package/data/craftbook-templates/ha/handbook-section/manifest.json

@@ -4,6 +4,9 @@
   "id": "handbook-section",
   "role": "general",
   "category": "writing",
+  "interests": [
+    "work"
+  ],
   "name": "Team Handbook Section",
   "description": "Write a clear, reference-grade section of a team/company handbook — a policy, process, or how-we-work doc that a new hire can read once and act on correctly. Scopes the policy's intent, audience, and edge cases FIRST, writes unambiguous prose with concrete examples, a quick-reference summary, and FAQ, then has a reviewer check it for ambiguity and contradictions with how things actually work. Use for onboarding docs, policy pages, process documentation, and internal wikis.",
   "tags": [

package/data/craftbook-templates/he/hero-image/manifest.json

@@ -4,6 +4,10 @@
   "id": "hero-image",
   "role": "general",
   "category": "media",
+  "interests": [
+    "content",
+    "business"
+  ],
   "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.",
   "tags": [

package/data/craftbook-templates/ht/html-arcade-game/manifest.json

@@ -4,6 +4,10 @@
   "id": "html-arcade-game",
   "role": "project-starter",
   "category": "code-build",
+  "interests": [
+    "software",
+    "play"
+  ],
   "name": "HTML Arcade Game",
   "description": "Build a playable single-file HTML/canvas arcade game (shooter, runner, dodger, etc.). Splits design into game-mechanics and visual look, builds, then evaluates against a playability bar and loops until it is actually fun and bug-free.",
   "tags": [