@bendyline/gilde 0.1.39 → 0.1.41

package/data/craftbook-templates/ho/hotfix-flow/versions/2.0.0/test.json

@@ -0,0 +1,221 @@
+{
+  "schemaVersion": 1,
+  "title": "Hotfix with minimal blast radius and a rollback path",
+  "objective": "The craftbook drives an urgent fix of a seeded null-guard crash in a receipts formatter: reproduction with the least machinery, the smallest change at the real defect site, honest validation with a rollback path, and an enforced review — verified mechanically, including a mutant re-seed proving the patch engaged the real site.",
+  "tags": [
+    "code",
+    "bug-fix",
+    "hotfix",
+    "tactical-fleet"
+  ],
+  "prompt": "Use the Hotfix Flow craftbook for this emergency: the nightly receipts export is crashing in production on orders without a gift note. The incident report is in source/incident.md. Reproduce it with the least machinery that shows it, patch minimally at the real defect site, and leave a rollback path.",
+  "setup": {
+    "projectName": "Receiptline",
+    "about": "A tiny order-receipt formatting module behind a nightly export. No test suite - the export script is the only runnable surface.",
+    "files": [
+      {
+        "path": "package.json",
+        "content": "{\n  \"name\": \"receiptline\",\n  \"private\": true,\n  \"version\": \"1.0.0\",\n  \"type\": \"module\"\n}\n",
+        "modelInput": false
+      },
+      {
+        "path": "src/format-order.js",
+        "content": "export function formatOrder(order) {\n  const lines = [];\n  lines.push('Order ' + order.id + ' for ' + order.customer);\n  for (const item of order.items) {\n    lines.push('  ' + item.qty + ' x ' + item.name + ' @ ' + money(item.unitPrice));\n  }\n  lines.push('Total: ' + money(orderTotal(order)));\n  lines.push('Gift note: ' + order.giftNote.trim());\n  return lines.join('\\n');\n}\n\nexport function orderTotal(order) {\n  let total = 0;\n  for (const item of order.items) {\n    total += item.qty * item.unitPrice;\n  }\n  return Math.round(total * 100) / 100;\n}\n\nfunction money(value) {\n  return value.toFixed(2);\n}\n"
+      },
+      {
+        "path": "data/orders.json",
+        "content": "[\n  {\n    \"id\": \"A-1041\",\n    \"customer\": \"Ana Torres\",\n    \"items\": [{ \"qty\": 1, \"name\": \"Ceramic Vase\", \"unitPrice\": 30 }],\n    \"giftNote\": \"  Happy birthday, Ana!  \"\n  },\n  {\n    \"id\": \"A-1042\",\n    \"customer\": \"Ben Ito\",\n    \"items\": [{ \"qty\": 2, \"name\": \"Stone Mug\", \"unitPrice\": 9.5 }]\n  },\n  {\n    \"id\": \"A-1043\",\n    \"customer\": \"Priya Shah\",\n    \"items\": [\n      { \"qty\": 3, \"name\": \"Linen Napkin\", \"unitPrice\": 4 },\n      { \"qty\": 1, \"name\": \"Oak Tray\", \"unitPrice\": 18 }\n    ]\n  }\n]\n",
+        "modelInput": false
+      },
+      {
+        "path": "scripts/print-receipts.mjs",
+        "content": "import { readFileSync } from 'node:fs';\nimport { formatOrder } from '../src/format-order.js';\n\nconst orders = JSON.parse(\n  readFileSync(new URL('../data/orders.json', import.meta.url), 'utf8'),\n);\nfor (const order of orders) {\n  console.log(formatOrder(order));\n  console.log('---');\n}\n",
+        "modelInput": false
+      },
+      {
+        "path": "source/incident.md",
+        "content": "# Incident: receipts export crashing\n\n02:14 - the nightly receipts export died partway through and retail has no morning receipts. Support traced it to orders without a gift note:\n\n    TypeError: Cannot read properties of undefined (reading 'trim')\n        at formatOrder (src/format-order.js)\n\n`node scripts/print-receipts.mjs` reproduces it: the first order (which has a gift note) prints fine, then the export falls over on the second order in `data/orders.json`.\n\nWhat must hold once this is fixed:\n\n- Orders with a gift note keep printing the trimmed note line.\n- Orders without one print a normal receipt with NO gift-note line.\n- Item lines and totals unchanged.\n\nWe need the smallest safe patch now. The proper cleanup of the formatter can wait for daylight - write it down instead of doing it.\n"
+      },
+      {
+        "path": "tests/verify-hotfix.mjs",
+        "content": "import assert from 'node:assert/strict';\nimport { execFileSync } from 'node:child_process';\nimport { cpSync, mkdirSync, rmSync, writeFileSync } from 'node:fs';\nimport { join } from 'node:path';\nimport { formatOrder, orderTotal } from '../src/format-order.js';\n\nconst root = process.cwd();\n\n// 1) The crash case is fixed: an order without a gift note formats cleanly.\nconst plain = {\n  id: 'A-1042',\n  customer: 'Ben Ito',\n  items: [{ qty: 2, name: 'Stone Mug', unitPrice: 9.5 }],\n};\nconst plainReceipt = formatOrder(plain);\nassert.ok(!plainReceipt.includes('undefined'), 'a receipt must not leak \"undefined\"');\nassert.ok(!/Gift note:/.test(plainReceipt), 'an order without a gift note must not print a gift-note line');\nassert.ok(plainReceipt.includes('Total: 19.00'), 'totals must survive the patch');\nconsole.log('HOTFIX_ORACLE crash case fixed');\n\n// 2) Neighborhood intact: gift notes still print trimmed, totals still add up.\nconst gifted = {\n  id: 'A-1041',\n  customer: 'Ana Torres',\n  items: [{ qty: 1, name: 'Ceramic Vase', unitPrice: 30 }],\n  giftNote: '  Happy birthday, Ana!  ',\n};\nconst giftedReceipt = formatOrder(gifted);\nassert.ok(giftedReceipt.includes('Gift note: Happy birthday, Ana!'), 'gift notes must still print, trimmed');\nconst multi = {\n  id: 'A-1043',\n  customer: 'Priya Shah',\n  items: [\n    { qty: 3, name: 'Linen Napkin', unitPrice: 4 },\n    { qty: 1, name: 'Oak Tray', unitPrice: 18 },\n  ],\n};\nassert.equal(orderTotal(multi), 30, 'orderTotal must be untouched');\nconsole.log('HOTFIX_ORACLE neighborhood intact');\n\n// 3) The export the incident names runs clean end to end.\nconst exportOut = execFileSync(process.execPath, ['scripts/print-receipts.mjs'], {\n  cwd: root,\n  stdio: 'pipe',\n  timeout: 30000,\n}).toString();\nassert.ok(exportOut.includes('A-1043'), 'the export must reach the last order');\nconsole.log('HOTFIX_ORACLE export green');\n\n// 4) Re-seed the original defect into a mutant tree: the crash must come\n// back, proving the patch engaged the real site rather than the callers\n// or the data (both of which are pinned fixtures anyway).\nconst ORIGINAL = `export function formatOrder(order) {\n  const lines = [];\n  lines.push('Order ' + order.id + ' for ' + order.customer);\n  for (const item of order.items) {\n    lines.push('  ' + item.qty + ' x ' + item.name + ' @ ' + money(item.unitPrice));\n  }\n  lines.push('Total: ' + money(orderTotal(order)));\n  lines.push('Gift note: ' + order.giftNote.trim());\n  return lines.join('\\\\n');\n}\n\nexport function orderTotal(order) {\n  let total = 0;\n  for (const item of order.items) {\n    total += item.qty * item.unitPrice;\n  }\n  return Math.round(total * 100) / 100;\n}\n\nfunction money(value) {\n  return value.toFixed(2);\n}\n`;\nconst mutantRoot = join(root, '.oracle-mutant');\nrmSync(mutantRoot, { recursive: true, force: true });\nmkdirSync(join(mutantRoot, 'src'), { recursive: true });\ncpSync(join(root, 'scripts'), join(mutantRoot, 'scripts'), { recursive: true });\ncpSync(join(root, 'data'), join(mutantRoot, 'data'), { recursive: true });\ncpSync(join(root, 'package.json'), join(mutantRoot, 'package.json'));\nwriteFileSync(join(mutantRoot, 'src', 'format-order.js'), ORIGINAL);\nlet mutantStatus = 0;\ntry {\n  execFileSync(process.execPath, ['scripts/print-receipts.mjs'], {\n    cwd: mutantRoot,\n    stdio: 'pipe',\n    timeout: 30000,\n  });\n} catch (err) {\n  mutantStatus = typeof err.status === 'number' ? err.status : 1;\n}\nassert.notEqual(mutantStatus, 0, 're-seeding the original defect must restore the crash - the patch did not engage the real site');\nconsole.log('HOTFIX_ORACLE mutant caught');\nconsole.log('HOTFIX_ORACLE done');\n",
+        "surface": "harness"
+      }
+    ],
+    "craftbookParams": {
+      "workPath": "tasks/eval",
+      "scope": "The nightly receipts export crashes on orders without a gift note; see source/incident.md. Smallest safe patch now - the proper cleanup is deferred, not attempted."
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The seeded null-guard crash is fixed at the real site with minimal blast radius, the export runs clean, a mutant re-seed restores the crash, and the fleet artifacts carry honest evidence, a Follow-up debt record, and a runnable rollback.",
+    "deliverables": [
+      {
+        "path": "tasks/eval/repro.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 500,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/repro.md",
+            "pattern": "^##\\s+Symptom[\\s\\S]*^##\\s+Repro command[\\s\\S]*^##\\s+Expected[\\s\\S]*^##\\s+Actual[\\s\\S]*^##\\s+Evidence",
+            "flags": "im",
+            "label": "reproduction sections in order"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "tasks/eval/repro.md",
+            "minCitations": 2,
+            "artifact": true
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/fix-notes.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 700,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/fix-notes.md",
+            "pattern": "^##\\s+Problem[\\s\\S]*^##\\s+Change[\\s\\S]*^##\\s+Files touched[\\s\\S]*^##\\s+Risk[\\s\\S]*^##\\s+How to verify[\\s\\S]*^##\\s+Follow-up",
+            "flags": "im",
+            "label": "fix-notes sections in order, Follow-up included"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/fix-notes.md",
+            "pattern": "src/format-order\\.js",
+            "label": "names the real defect site"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "tasks/eval/fix-notes.md",
+            "minCitations": 2,
+            "artifact": true
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/validation.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 400,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/validation.md",
+            "pattern": "^##\\s+Repro re-run[\\s\\S]*^##\\s+Result[\\s\\S]*^##\\s+Rollback",
+            "flags": "im",
+            "label": "validation sections in order, Rollback included"
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/review.md",
+        "kind": "markdown-report",
+        "artifact": true,
+        "minBytes": 400,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/review.md",
+            "pattern": "Verdict:\\s*(?:PASS|REVISE)",
+            "flags": "i",
+            "label": "explicit reviewer verdict"
+          }
+        ]
+      }
+    ],
+    "checks": [
+      {
+        "kind": "notContains",
+        "file": "src/format-order.js",
+        "pattern": "\\btry\\s*\\{|\\bcatch\\s*\\(",
+        "label": "the crash is fixed at the site, not swallowed with try/catch"
+      },
+      {
+        "kind": "sourceParses",
+        "file": "src/format-order.js"
+      },
+      {
+        "kind": "nodeRuns",
+        "file": "scripts/print-receipts.mjs",
+        "timeoutMs": 30000
+      },
+      {
+        "kind": "nodeScriptPasses",
+        "script": "tests/verify-hotfix.mjs",
+        "timeoutMs": 60000,
+        "requiredOutput": [
+          {
+            "pattern": "HOTFIX_ORACLE crash case fixed",
+            "label": "the null-guard crash is gone"
+          },
+          {
+            "pattern": "HOTFIX_ORACLE neighborhood intact",
+            "label": "gift notes and totals still behave"
+          },
+          {
+            "pattern": "HOTFIX_ORACLE export green",
+            "label": "the incident's export runs end to end"
+          },
+          {
+            "pattern": "HOTFIX_ORACLE mutant caught",
+            "label": "re-seeding the defect restores the crash"
+          }
+        ]
+      }
+    ],
+    "taskNotes": {
+      "minBytes": 120,
+      "checks": [
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "\\bDONE\\b[\\s\\S]*validation\\.md",
+          "flags": "i",
+          "label": "DONE note names the validation deliverable"
+        }
+      ]
+    },
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    },
+    "unchangedFixtures": [
+      "source/incident.md",
+      "package.json",
+      "data/orders.json",
+      "scripts/print-receipts.mjs"
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/fix-notes.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "Minimal blast radius",
+        "description": "The change is the smallest that stops the failure at the real defect site - no refactor, rename, or cleanup rode along with the emergency patch."
+      },
+      {
+        "name": "Honest evidence under pressure",
+        "description": "Reproduction and validation quote real observed behavior, and anything that could not actually be run is labeled unverified rather than claimed."
+      },
+      {
+        "name": "Deferred debt discipline",
+        "description": "Follow-up records the proper fix and the debt the patch leaves (with a backport note where relevant) instead of attempting a deeper repair mid-incident, and Rollback is a concrete, runnable path."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "minimal-diff discipline",
+    "honest verification",
+    "runnable rollback"
+  ]
+}

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

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "html-arcade-game",
   "role": "project-starter",
+  "category": "code-build",
   "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": [

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

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "html-puzzle-game",
   "role": "project-starter",
+  "category": "code-build",
   "name": "HTML Puzzle Game",
   "description": "Build a single-file HTML logic or puzzle game such as a match-3, sliding tile, Sokoban, 2048, minesweeper, or sudoku. Locks the rule system, the solve/fail condition, and the win detection first, then a clean grid visual language, then implements deterministic board state with valid-move enforcement. Puzzle games live or die on correct rules and reliable win detection, so the design phase pins the exact legal-move and victory logic before any rendering — the ordering that prevents a small model from shipping a grid that looks right but never registers a win.",
   "tags": [

package/data/craftbook-templates/ic/icon-pack/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "icon-pack",
   "role": "general",
+  "category": "design",
   "name": "Coherent Icon Pack",
   "description": "Produce a coherent set of UI icons that look like they belong to one family — consistent grid, stroke weight, corner radius, optical sizing, and metaphor language — from a named list of concepts. Lock the style system (grid, stroke, padding, keyline shapes) BEFORE drawing any icon, because icon-set quality is almost entirely about consistency: a pack of individually-nice icons with mismatched strokes looks broken. Then generate every icon to the system and assemble a previewable sheet. Covers icon sets, UI icons, SVG icon libraries, glyph packs, and design systems.",
   "tags": [

package/data/craftbook-templates/id/idea-office-hours/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "idea-office-hours",
   "role": "general",
+  "category": "practice",
   "name": "Idea Office Hours",
   "description": "Pressure-test a product idea with forcing questions before jumping to solutions, then capture the decision in a short design doc — a structured 'office hours' diagnostic.",
   "tags": [

package/data/craftbook-templates/id/idle-clicker-game/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "idle-clicker-game",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Idle / Incremental Game",
   "description": "Build a single-file idle or incremental clicker game such as a cookie/factory clicker with upgrades, generators, and exponential growth. Designs the resource economy — base click yield, generator costs, cost-scaling factor, and per-second production — first, then the layout, then implements a tick loop with persistent-feeling progression. Idle games are an economy problem before a UI problem: if costs and yields are not tuned the game is boring in 10 seconds or unwinnable, so the economy phase locks the exact numbers and growth curve before any rendering.",
   "tags": [

package/data/craftbook-templates/im/image-batch-edit/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "image-batch-edit",
   "role": "general",
+  "category": "media",
   "name": "Batch Image Transform",
   "description": "Apply a consistent transform across a whole folder of images — resize, crop to a ratio, convert format, compress, watermark, or recolor — and verify every file came out correct. Scope the exact transform and a verification rule FIRST (target dimensions, format, quality, naming) so the batch is deterministic and reproducible, then process every file and prove the output count, dimensions, and format match the spec. Covers bulk image processing, resizing, format conversion, compression, watermarking, and folder-wide edits.",
   "tags": [

package/data/craftbook-templates/im/image-dedup-cluster/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "image-dedup-cluster",
   "role": "general",
+  "category": "media",
   "name": "Image Dedup & Cluster",
   "description": "Find and group near-duplicate images across a folder — exact dupes, resized/re-encoded copies, and visually similar shots from the same burst — using perceptual hashing or visual similarity, then report clusters with a recommended keeper per group. Lock the similarity definition and thresholds FIRST (what counts as a duplicate vs merely similar) because the whole result hinges on that line; then analyze pairwise, cluster, and produce a human-reviewable report. Covers deduplication, near-duplicate detection, perceptual hashing, image clustering, burst grouping, and library cleanup.",
   "tags": [

package/data/craftbook-templates/im/image-palette-extract/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "image-palette-extract",
   "role": "general",
+  "category": "design",
   "name": "Image Palette Extraction",
   "description": "Extract a usable color palette from an image or a set of images — the dominant and accent colors as hex/RGB with proportions — and emit it as design tokens (CSS variables / JSON) plus a swatch preview, so a brand or theme can be built from a reference photo. Lock FIRST how many colors, the color space and clustering method, and accessibility constraints (e.g. text/background pairs must meet a contrast ratio) because a raw dominant-color dump is rarely directly usable as a theme; then extract, name, and present the palette. Covers color extraction, palette generation, design tokens, theme-from-image, dominant colors, and brand color sampling.",
   "tags": [

package/data/craftbook-templates/im/image-seo-rename/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "image-seo-rename",
   "role": "general",
+  "category": "media",
   "name": "Image SEO Rename & Tag",
   "description": "Rename and tag a folder of images for SEO and findability — descriptive, hyphenated, keyword-rich filenames plus consistent metadata (title, caption, keyword tags) — driven by what each image actually depicts, while preserving a mapping back to the originals so links don't break silently. Scope FIRST the naming convention, keyword strategy, and collision/mapping rules, because bulk-renaming without a plan creates duplicate-name clashes and broken references; then process the folder and emit the rename map. Covers image SEO, filename optimization, descriptive renaming, alt/metadata tagging, and asset findability.",
   "tags": [

package/data/craftbook-templates/im/image-set-index/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "image-set-index",
   "role": "general",
+  "category": "media",
   "name": "Index & Describe an Image Set",
   "description": "Given a folder of images, produce a structured index that describes each one (caption, tags, notable content) in a consistent schema, then validates coverage and consistency. For cataloguing, search, or alt-text generation over an image collection.",
   "tags": [

package/data/craftbook-templates/in/inbox-triage/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "inbox-triage",
   "role": "general",
+  "category": "business",
   "name": "Inbox Triage & Reply Drafts",
   "description": "Triage a batch of incoming emails or messages into priority buckets and draft replies for the ones that need them. Locks the triage rules and bucket taxonomy FIRST (urgent / needs-reply / FYI / archive, plus the criteria for each and a reply policy), then classifies every message deterministically against those rules, then a copywriter drafts on-voice replies only for the messages flagged needs-reply. The rules-before-triage ordering is what stops a small model from inventing ad-hoc categories and gives the reviewer something to grade. Use for inbox zero, support-queue triage, email sorting, message prioritization, and auto-drafting responses.",
   "tags": [

package/data/craftbook-templates/in/incident-comms-templates/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "incident-comms-templates",
   "role": "general",
+  "category": "code-ops",
   "name": "Incident Communication Templates",
   "description": "Author a reusable set of incident communication templates: status-page posts and stakeholder update messages for each phase of an incident (Investigating, Identified, Monitoring, Resolved) across severities, with fill-in variables and a cadence guide. Scopes the audiences, phases, and tone rules FIRST (who reads each channel, the phase ladder, what may and may not be said, the variable set), then a copywriter writes the on-brand templates with bracketed placeholders, then a reviewer checks coverage, tone, and that no template over-promises or leaks blame. Scoping audiences and phases before drafting is what produces calm, honest, copy-paste-ready updates instead of ad-hoc panic posts. Use for incident comms, status page templates, customer incident updates, outage communication, and stakeholder messaging during an incident.",
   "tags": [

package/data/craftbook-templates/in/incident-postmortem/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "incident-postmortem",
   "role": "maintenance-review",
+  "category": "code-ops",
   "name": "Incident Postmortem",
   "description": "Write a blameless incident postmortem after a production outage or degradation — a structured, factual document covering the impact, a precise timeline (detection → diagnosis → mitigation → resolution), the root cause and contributing factors via a five-whys analysis, what went well and what went poorly, and concrete, owned, dated action items that prevent recurrence. A researcher assembles the verified timeline and evidence from logs/alerts/chat, a copywriter writes the blameless narrative and root-cause analysis, and a reviewer checks the timeline is accurate, the analysis reaches a true root cause, and every action item is specific and owned. Use this for outage retrospectives, severity-incident reviews, and any 'what happened and how do we prevent it' writeup.",
   "tags": [

package/data/craftbook-templates/in/insurance-inventory/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "insurance-inventory",
   "role": "general",
+  "category": "business",
   "name": "Insurance Inventory",
   "description": "Compile the inventory nobody has until the day they desperately need it: every cataloged item with its value, photo reference, and acquisition info in one document, the gaps (no photo, no value) named instead of papered over, and the total stated with its basis. Locks the completeness criteria FIRST, then compiles the full table, then writes the cover note — the quiet payoff of keeping the catalog honest. Use for insurance inventories, 'our agent wants a full inventory', documenting the collection for coverage, and preparing a collection record for a claim.",
   "tags": [

package/data/craftbook-templates/in/interactive-quiz/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "interactive-quiz",
   "role": "project-starter",
+  "category": "personal",
   "name": "Interactive Quiz Widget",
   "description": "Build a single-file interactive quiz or assessment — multiple-choice, true/false, or a scored personality quiz — that asks questions one at a time, tracks the score, gives feedback, and shows a results screen. Authors the question bank, answer keys, and scoring logic first, designs the question and results UI, then implements stateful question flow with correct scoring. Quizzes break when the score is miscounted or the results screen never appears, so the content phase locks the answer key and the score-to-result mapping before any markup.",
   "tags": [

package/data/craftbook-templates/in/investigate/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "investigate",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Investigate",
   "description": "Systematic root-cause debugging procedure. Iron Law: no fixes without investigation. Gathers symptoms, reproduces, traces, finds root cause, saves the learning.",
   "tags": [
@@ -14,6 +15,9 @@
   },
   "logo": "logo.webp",
   "license": "MIT",
-  "yankedVersions": [],
+  "yankedVersions": [
+    "1.0.0",
+    "1.1.0"
+  ],
   "workflow": "investigation"
 }

package/data/craftbook-templates/in/investigate-root-cause/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "investigate-root-cause",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Root-Cause Investigation",
   "description": "Debug a defect or production incident down to its true root cause and document the diagnosis with evidence, instead of patching the first symptom. First reproduces the failure reliably and locks what 'understood' means (a confirmed repro, the failing assertion, the exact trigger condition), then narrows the cause by forming and testing hypotheses, bisecting, reading stack traces and logs, and tracing the data path until one hypothesis is proven, then writes a root-cause report with the evidence chain, the smallest fix, and how to prevent recurrence. Use this for debugging, root-cause analysis, investigating a bug or flaky test, diagnosing an incident, or figuring out why something breaks — it produces a proven cause backed by evidence, not a guess.",
   "tags": [
@@ -18,6 +19,10 @@
   },
   "logo": "logo.webp",
   "license": "MIT",
-  "yankedVersions": [],
+  "yankedVersions": [
+    "1.0.0",
+    "1.0.1",
+    "1.0.2"
+  ],
   "workflow": "build-loop"
 }

package/data/craftbook-templates/in/invitation-design/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "invitation-design",
   "role": "general",
+  "category": "personal",
   "name": "Design the Invitations",
   "description": "Produce the invitation the day deserves and get the facts beyond doubt: the date, time, venue, and RSVP instructions checked letter-for-letter against the event record — because a beautiful card with the wrong date is the classic disaster. Locks the fact checklist and the look brief FIRST, then designs the print-ready invitation, then proofs every fact against the record before anything reaches a printer. Use for party invitations, designing the invites, birthday and anniversary invitations, and 'make the invitation printable'.",
   "tags": [

package/data/craftbook-templates/in/invoice-generator/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "invoice-generator",
   "role": "general",
+  "category": "business",
   "name": "Invoice Generator",
   "description": "Generate a clean, professional, print-ready invoice from billing details — sender/recipient, line items with quantity and rate, subtotal, tax, total, invoice number, dates, and payment instructions. Scopes the required fields and the tax/total math FIRST (a wrong total is the one unforgivable invoice bug), then builds a polished single-file HTML invoice with an itemized table and correctly computed totals. Use for freelancer/contractor billing, one-off invoices, and invoice templates.",
   "tags": [

package/data/craftbook-templates/in/invoice-run/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "invoice-run",
   "role": "general",
+  "category": "business",
   "name": "Monthly Invoice Run",
   "description": "Run the month's invoicing in one calm pass from the office's own books: an invoice per client built from the tracked work in the ledger, numbering that continues the sequence without a skip or a repeat, due dates per each client's terms, everything recorded as sent — plus a one-page summary of what went out. Unlike a one-off invoice generator, this is the standing monthly ritual over the client roster and ledger, ending in print-ready invoices and updated books. Use for the monthly invoice run, end-of-month invoicing, 'bill the clients for this month', and closing the billing month.",
   "tags": [