@bendyline/gilde 0.1.39 → 0.1.41

package/data/craftbook-templates/bu/bug-fix-tdd/versions/2.0.0/test.json

@@ -0,0 +1,222 @@
+{
+  "schemaVersion": 1,
+  "title": "Bug fix with red-then-green proof",
+  "objective": "The craftbook drives a disciplined fix of a seeded boundary bug: a failing reproduction test written into the real test layout, the smallest change at the real defect site, a green suite afterwards, and an enforced review — all verified mechanically, including a mutant run proving the regression guard bites.",
+  "tags": [
+    "code",
+    "bug-fix",
+    "tdd",
+    "tactical-fleet"
+  ],
+  "prompt": "Use the Reproduce-Then-Fix a Bug craftbook for this: customers report that buying exactly 10 of an item does not get the bulk discount, but the pricing page promises the discount at 10 or more. The report is in source/bug-report.md. Reproduce it with a failing test first, then fix it properly.",
+  "setup": {
+    "projectName": "Orderly Pricing",
+    "about": "A tiny order-pricing module for a web shop. Tests run with `npm run test` (node --test).",
+    "files": [
+      {
+        "path": "package.json",
+        "content": "{\n  \"name\": \"orderly\",\n  \"private\": true,\n  \"version\": \"1.0.0\",\n  \"type\": \"module\",\n  \"scripts\": {\n    \"test\": \"node --test\"\n  }\n}\n"
+      },
+      {
+        "path": "src/pricing.js",
+        "content": "const BULK_THRESHOLD = 10;\nconst BULK_DISCOUNT = 0.15;\n\nexport function lineTotal(unitPrice, qty) {\n  if (!Number.isFinite(unitPrice) || unitPrice < 0) throw new Error('bad unitPrice');\n  if (!Number.isInteger(qty) || qty < 0) throw new Error('bad qty');\n  const subtotal = unitPrice * qty;\n  if (qty > BULK_THRESHOLD) {\n    return round2(subtotal * (1 - BULK_DISCOUNT));\n  }\n  return round2(subtotal);\n}\n\nfunction round2(value) {\n  return Math.round(value * 100) / 100;\n}\n"
+      },
+      {
+        "path": "tests/pricing.test.mjs",
+        "content": "import assert from 'node:assert/strict';\nimport { test } from 'node:test';\nimport { lineTotal } from '../src/pricing.js';\n\ntest('small orders pay full price', () => {\n  assert.equal(lineTotal(4, 5), 20);\n});\n\ntest('large orders get the bulk discount', () => {\n  assert.equal(lineTotal(10, 20), 170);\n});\n\ntest('rejects bad quantities', () => {\n  assert.throws(() => lineTotal(4, -1));\n});\n"
+      },
+      {
+        "path": "source/bug-report.md",
+        "content": "# Bug report\n\nFrom support: \"Our pricing page says 'buy 10 or more, save 15%'. A customer bought exactly 10 units at 8.00 and was charged 80.00 - no discount. Buying 11 units gives the discount. Exactly 10 does not.\"\n\nExpected: 10 units at 8.00 with the 15% bulk discount = 68.00.\nActual: charged the full 80.00.\n"
+      },
+      {
+        "path": "tests/verify-pricing.mjs",
+        "content": "import assert from 'node:assert/strict';\nimport { execFileSync } from 'node:child_process';\nimport { cpSync, mkdirSync, readFileSync, readdirSync, rmSync, writeFileSync } from 'node:fs';\nimport { join } from 'node:path';\nimport { lineTotal } from '../src/pricing.js';\n\n// 1) Behavior: the boundary is fixed and the neighborhood still holds.\nassert.equal(lineTotal(8, 10), 68, 'exactly 10 units must get the bulk discount');\nassert.equal(lineTotal(8, 11), 74.8, 'above the threshold keeps the discount');\nassert.equal(lineTotal(8, 9), 72, 'below the threshold pays full price');\nassert.equal(lineTotal(4, 5), 20, 'small orders unchanged');\nconsole.log('BUGFIX_ORACLE behavior ok');\n\n// 2) Regression guard bites: rebuild the tree with the ORIGINAL seeded\n// defect and the test suite must now FAIL - proof that a reproduction\n// test exists and would catch a revert. The current tree's suite must\n// pass (green after the fix).\nconst root = process.cwd();\nconst mutantRoot = join(root, '.oracle-mutant');\nrmSync(mutantRoot, { recursive: true, force: true });\nmkdirSync(join(mutantRoot, 'src'), { recursive: true });\ncpSync(join(root, 'tests'), join(mutantRoot, 'tests'), { recursive: true });\nrmSync(join(mutantRoot, 'tests', 'verify-pricing.mjs'), { force: true });\ncpSync(join(root, 'package.json'), join(mutantRoot, 'package.json'));\nconst current = readFileSync(join(root, 'src', 'pricing.js'), 'utf8');\nconst mutant = current.replace(/qty\\s*>=\\s*BULK_THRESHOLD/g, 'qty > BULK_THRESHOLD').replace(/qty\\s*>=\\s*10/g, 'qty > 10');\nassert.notEqual(mutant, current, 'could not re-seed the defect - the fix should have made the threshold inclusive');\nwriteFileSync(join(mutantRoot, 'src', 'pricing.js'), mutant);\n\nfunction runSuite(cwd) {\n  try {\n    execFileSync(process.execPath, ['--test'], { cwd, stdio: 'pipe', timeout: 30000 });\n    return 0;\n  } catch (err) {\n    return typeof err.status === 'number' ? err.status : 1;\n  }\n}\n\nassert.equal(runSuite(root), 0, 'the suite must be green on the fixed tree');\nconsole.log('BUGFIX_ORACLE suite green');\nassert.notEqual(runSuite(mutantRoot), 0, 'reverting the fix must make at least one test fail - the regression guard is missing or toothless');\nconsole.log('BUGFIX_ORACLE mutant caught');\nconst testFiles = readdirSync(join(root, 'tests')).filter((f) => f.endsWith('.mjs') && f !== 'verify-pricing.mjs');\nassert.ok(testFiles.length >= 1, 'test layout missing');\nconsole.log('BUGFIX_ORACLE done');\n",
+        "surface": "harness"
+      }
+    ],
+    "craftbookParams": {
+      "workPath": "tasks/eval",
+      "scope": "Buying exactly 10 units does not get the bulk discount; see source/bug-report.md."
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The seeded boundary defect is fixed at the real site, the suite is green, a regression test catches a revert (mutant run), and every fleet artifact exists with honest citations.",
+    "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+Red evidence",
+            "flags": "im",
+            "label": "reproduction sections in order"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "tasks/eval/repro.md",
+            "minCitations": 2,
+            "artifact": true
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/diagnosis.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 600,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/diagnosis.md",
+            "pattern": "^##\\s+Defect site[\\s\\S]*^##\\s+Causal chain[\\s\\S]*^##\\s+Siblings checked",
+            "flags": "im",
+            "label": "diagnosis sections in order"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/diagnosis.md",
+            "pattern": "src/pricing\\.js",
+            "label": "names the real defect site"
+          }
+        ]
+      },
+      {
+        "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+Regression coverage[\\s\\S]*^##\\s+Risk[\\s\\S]*^##\\s+How to verify",
+            "flags": "im",
+            "label": "fix-notes sections in order"
+          },
+          {
+            "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+Suite[\\s\\S]*^##\\s+Result",
+            "flags": "im",
+            "label": "validation sections in order"
+          }
+        ]
+      },
+      {
+        "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/pricing.js",
+        "pattern": "qty\\s*>\\s*BULK_THRESHOLD|qty\\s*>\\s*10\\b",
+        "label": "the seeded exclusive-threshold defect is gone"
+      },
+      {
+        "kind": "sourceParses",
+        "file": "src/pricing.js"
+      },
+      {
+        "kind": "nodeRuns",
+        "file": "tests/pricing.test.mjs"
+      },
+      {
+        "kind": "nodeScriptPasses",
+        "script": "tests/verify-pricing.mjs",
+        "timeoutMs": 60000,
+        "requiredOutput": [
+          {
+            "pattern": "BUGFIX_ORACLE behavior ok",
+            "label": "boundary behavior fixed"
+          },
+          {
+            "pattern": "BUGFIX_ORACLE suite green",
+            "label": "suite green on the fixed tree"
+          },
+          {
+            "pattern": "BUGFIX_ORACLE mutant caught",
+            "label": "regression guard catches a revert"
+          }
+        ]
+      }
+    ],
+    "taskNotes": {
+      "minBytes": 120,
+      "checks": [
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "\\bDONE\\b[\\s\\S]*(npm\\s+run\\s+test|node\\s+--test)",
+          "flags": "i",
+          "label": "DONE note names the real test command"
+        }
+      ]
+    },
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    },
+    "unchangedFixtures": [
+      "source/bug-report.md",
+      "package.json"
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/fix-notes.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "Repro-first discipline",
+        "description": "A failing test was genuinely written and run before the fix, in the project's real test layout, and the red evidence quotes a real run rather than a claim."
+      },
+      {
+        "name": "Fix minimality",
+        "description": "The change is the smallest correct edit at the real defect site; no special-casing of the reported input, no unrelated churn."
+      },
+      {
+        "name": "Honest verification",
+        "description": "Validation re-ran the original reproduction, distinguishes verified results from anything unverified, and the review graded evidence rather than summaries."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "red-then-green proof",
+    "real-path citations",
+    "enforced review loop"
+  ]
+}

package/data/craftbook-templates/bu/build-loop/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "build-loop",
   "role": "general",
+  "category": "practice",
   "name": "Build Loop",
   "description": "Generic make-something procedure: scope the work and lock concrete acceptance criteria, build it, evaluate the result against those criteria, and loop back to building until every criterion is met — then finish. The fallback structure when no domain-specific craftbook fits.",
   "tags": [

package/data/craftbook-templates/ca/calendar-brief/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "calendar-brief",
   "role": "general",
+  "category": "business",
   "name": "Daily Calendar & Prep Brief",
   "description": "Assemble a morning brief from the day's calendar: a chronological agenda with per-meeting prep notes, conflicts flagged, and a short focus-time/priorities summary. Scopes the brief layout and prep rules FIRST (which meetings need prep, what prep means, how to flag conflicts and back-to-backs), then a developer pulls the day's events and assembles the brief deterministically against those rules. The scope-first ordering ensures the brief always flags double-bookings and attaches the right context (attendees, agenda, links) instead of just dumping a raw event list. Use for daily agenda briefs, meeting prep, morning planning, schedule rundowns, and turning a calendar into an actionable day plan.",
   "tags": [

package/data/craftbook-templates/ca/canvas-generative-art/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "canvas-generative-art",
   "role": "project-starter",
+  "category": "design",
   "name": "Canvas Generative Art",
   "description": "Build a single-file generative art piece on canvas — flow fields, particle systems, recursive trees, Voronoi, noise terrain, or geometric tilings — that produces a fresh composition each run from a seed, with parameters the viewer can tweak. Defines the aesthetic and the generative algorithm first, then implements a seeded, reproducible renderer with a regenerate control. Generative art is an algorithm-and-aesthetic problem, so the aesthetic-scope phase locks the visual rules and the seedable randomness before any drawing, the ordering that yields a deliberate piece rather than random noise.",
   "tags": [

package/data/craftbook-templates/ca/careful-mode/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "careful-mode",
   "role": "general",
+  "category": "practice",
   "name": "Careful Mode",
   "description": "Safety guardrails for destructive commands",
   "tags": [

package/data/craftbook-templates/ca/case-study/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "case-study",
   "role": "general",
+  "category": "marketing",
   "name": "Customer Case Study",
   "description": "Write a persuasive, evidence-backed customer success story in the classic challenge-solution-results arc: it first scopes the customer, the quantified before/after metrics, the approved customer quotes, and the single takeaway for prospects, then writes the case study with a results-forward summary, a relatable challenge, the solution narrative, and a measurable results section, then a review pass verifies every number and quote and the persuasive flow. Covers case study, customer success story, customer testimonial, success story, proof point, and B2B marketing content. Scoping the metrics and quotes before writing is the point: a small model that locks the quantified results first writes a credible story buyers trust, instead of a vague testimonial with adjectives but no proof.",
   "tags": [

package/data/craftbook-templates/ca/case-study-writeup/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "case-study-writeup",
   "role": "general",
+  "category": "marketing",
   "name": "Customer Case Study",
   "description": "Write a persuasive customer/case-study writeup that turns a customer's results into a credible marketing asset — challenge, solution, and quantified results in the classic before/after arc, with a pull-quote and a clear CTA. Scopes the customer story and the hard metrics FIRST (results without numbers are not a case study), writes the narrative copy in the proven challenge-solution-results structure, then builds a clean, branded single-page HTML asset with a results-highlight band and quote callout. Use for marketing case studies, customer success stories, and sales proof assets.",
   "tags": [

package/data/craftbook-templates/ch/changelog-cut/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "changelog-cut",
   "role": "general",
+  "category": "code-release",
   "name": "Changelog Cut",
   "description": "Cut a new versioned section into a Keep a Changelog / CHANGELOG.md style file for a release — moving entries out of the Unreleased section into a dated, semver-stamped version block under the standard Added / Changed / Deprecated / Removed / Fixed / Security headings, with a fresh empty Unreleased section left behind. A developer gathers the unreleased entries and reconciles them against actual merged changes before a copywriter normalizes them into terse, consistent changelog lines and stamps the version block. Use this whenever you 'cut a release', 'update the changelog', or roll the Unreleased section into a tagged version while keeping the file append-only and machine-comparable.",
   "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/ch/changelog-writeup/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "changelog-writeup",
   "role": "general",
+  "category": "code-release",
   "name": "Human-Readable Changelog",
   "description": "Turn raw commit/PR history into a human-readable changelog that users actually understand: a developer first gathers and triages the merged changes since the last release into user-facing buckets (Added, Changed, Fixed, Deprecated, Removed, Security), filtering out noise like internal refactors, then a copywriter rewrites each entry in plain, benefit-oriented language with breaking changes called out. Covers changelog, release notes, what's new, version notes, and Keep a Changelog format. Gathering and triaging before writing is the point: a small model that first separates user-facing changes from internal churn avoids the changelog that lists 'bump deps' next to a breaking API change with equal weight.",
   "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/ch/chapter-narration-run/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "chapter-narration-run",
   "role": "general",
+  "category": "media",
   "name": "Narrate a Chapter",
   "description": "Take one chapter from manuscript to narrated audio, deliberately: a narration script with pronunciations and pauses marked before anything renders, the audio driven through the project's narration capabilities with a run log, and a listen-check against the text — no skipped paragraphs, no mangled names. Locks the chapter and the style sheet FIRST (voice, pace, every proper noun's pronunciation), then preps the script, then renders, then checks coverage. Use for narrating a chapter, audiobook recording runs, text-to-speech passes, and 'read chapter two aloud'.",
   "tags": [

package/data/craftbook-templates/ch/chapter-weave/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "chapter-weave",
   "role": "general",
+  "category": "writing",
   "name": "Weave a Chapter",
   "description": "Weave the banked sessions into one memoir chapter in the teller's voice: every scene traceable to something actually said, gaps marked for a future session instead of invented — the ritual that turns interviews into a book. Locks the chapter's arc and the no-invention rules FIRST, then drafts from session material only, with a faithfulness pass that loops until every detail traces. Use for drafting a memoir chapter, weaving sessions into a story, and 'turn the interviews into a chapter'.",
   "tags": [

package/data/craftbook-templates/ch/character-sheet/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "character-sheet",
   "role": "general",
+  "category": "media",
   "name": "Character Sheet",
   "description": "Lock a character before the pages need them: reference images across the poses and expressions the story calls for, the palette and silhouette written down, and every seed and prompt persisted in a manifest — so page twelve's hero is page one's hero. Locks the character brief FIRST — silhouette, palette, expression and pose list — then generates the reference set with its manifest, then lays the contact sheet anyone can draw from. Use for character sheets, locking a character's look, reference sets before more pages, 'keep them looking the same', and building a comic's cast bible.",
   "tags": [

package/data/craftbook-templates/ch/character-turnaround/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "character-turnaround",
   "role": "general",
+  "category": "media",
   "name": "Character Turnaround",
   "description": "Give one character the full turnaround treatment: front, side, back, and three-quarter views generated against the same style anchor, every view manifest-recorded with the seed and prompt that made it — the reference every future sprite leans on. Locks the angle list and the style anchor FIRST, then generates the views as one consistent figure, then writes the records and the summary. Use for character turnarounds, 'we need the knight from all sides', sprite reference sets, model sheets for game characters, and locking a character before animation work.",
   "tags": [

package/data/craftbook-templates/ch/chart-pack/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "chart-pack",
   "role": "general",
+  "category": "research",
   "name": "Chart Pack from Data",
   "description": "Build a single interactive HTML page of charts that answers a defined set of questions about a dataset. Scopes the questions and the right chart type per question FIRST (so you don't make a pretty chart that answers nothing), then analyzes the data into chart-ready series, then builds one self-contained HTML page rendering every chart with titles, axis labels, and a one-line takeaway caption each. Use this for a dashboard of charts, a visualization pack, a metrics page, or turning a CSV into graphs and plots.",
   "tags": [

package/data/craftbook-templates/ch/chrome-extension/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "chrome-extension",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Browser Extension",
   "description": "Build a Manifest V3 browser extension scaffold — a popup, a content script, and the manifest — that does one concrete thing on the current page (highlight, count, extract, or toggle). Scopes the single capability and the required permissions first, designs the popup UI, then builds a valid manifest.json plus popup and content-script files wired by messaging. Extensions fail at the manifest and the popup↔content messaging boundary, so the scope phase pins the exact MV3 permissions and message contract before any code, keeping a small model from producing a manifest the browser rejects.",
   "tags": [

package/data/craftbook-templates/ci/ci-pipeline/manifest.json

@@ -3,15 +3,18 @@
   "kind": "craftbook-template",
   "id": "ci-pipeline",
   "role": "maintenance-review",
+  "category": "code-release",
   "name": "CI Pipeline from Scratch",
-  "description": "Build a continuous-integration pipeline that installs, lints, tests, and builds on every push/PR — fast, cached, and gating merges on green. Scopes the pipeline contract FIRST — triggers, the job/stage graph, the matrix, caching strategy, and the gates — then writes the CI workflow YAML, then a reviewer validates the syntax, stage ordering, caching, and that it actually fails on a broken build. Covers CI triggers, job/stage dependencies, dependency caching, build matrices, status checks, fail-fast gating, and a valid workflow file.",
+  "description": "Author a CI pipeline grounded in what the repo actually has: inventory the real package scripts, write the workflow at the conventional location with caching and merge-gating on green, and verify every command it invokes against the manifests — honest that CI itself cannot run locally. Adds a publish-on-tag release job only when the repo shows one.",
   "tags": [
-    "gallery",
     "ci",
     "devops",
     "pipeline",
     "automation",
-    "github-actions"
+    "github-actions",
+    "cd",
+    "release",
+    "yaml"
   ],
   "maintainer": {
     "name": "Gezel"