@bendyline/gilde 0.1.3 → 0.1.5

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

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

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

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "communicate-market",
+  "accents": [
+    "muted terracotta",
+    "dusty rose",
+    "sage"
+  ],
+  "sourceSummary": "Triage a batch of incoming emails or messages into priority buckets and draft replies for the ones that need them.",
+  "styleReference": "accessibility-audit-1910"
+}

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

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

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

@@ -0,0 +1,12 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "inspect-review",
+  "accents": [
+    "muted terracotta",
+    "sage"
+  ],
+  "sourceSummary": "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.",
+  "styleReference": "accessibility-audit-1910"
+}

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

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

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

@@ -0,0 +1,12 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "inspect-review",
+  "accents": [
+    "muted terracotta",
+    "sage"
+  ],
+  "sourceSummary": "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,…",
+  "styleReference": "accessibility-audit-1910"
+}

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

@@ -16,6 +16,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

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

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "write-publish",
+  "accents": [
+    "muted terracotta",
+    "muted indigo",
+    "sage"
+  ],
+  "sourceSummary": "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.",
+  "styleReference": "accessibility-audit-1910"
+}

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

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

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

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "build-code",
+  "accents": [
+    "muted indigo",
+    "terracotta",
+    "sage"
+  ],
+  "sourceSummary": "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.",
+  "styleReference": "accessibility-audit-1910"
+}

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

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

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

@@ -0,0 +1,12 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "inspect-review",
+  "accents": [
+    "muted terracotta",
+    "sage"
+  ],
+  "sourceSummary": "Systematic root-cause debugging procedure.",
+  "styleReference": "accessibility-audit-1910"
+}

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

@@ -12,6 +12,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "investigation"

package/data/craftbook-templates/in/investigate/versions/1.1.0/craftbook.json

@@ -0,0 +1,81 @@
+{
+  "id": "investigate",
+  "name": "Investigate",
+  "description": "Systematic root-cause debugging procedure. Six steps:\n\n1. **Gather symptoms** — observable signals, no theorizing yet\n2. **Search prior** — has this project seen this before? (memory)\n3. **Reproduce** — deterministic repro before any tracing\n4. **Trace to root cause** — keep asking 'and why is THAT?'\n5. **Propose fix** — state it; don't apply unless asked\n6. **Save learning** — stamp (symptom → root cause → fix) into memory\n\nPorted from gstack's `/investigate`. The principle is the Iron Law:\n**no fixes without investigation**. Jumping to a fix without root cause\neither ships a coincidence (the bug comes back), papers over the real\ncause (introduces tech debt), or fixes a symptom you didn't actually\nunderstand.\n\nWhere gstack used `~/.gstack/projects/{slug}/learnings.jsonl`, this\ncraftbook uses the per-gezel/project memory subsystem. The\n`search-prior.ts` script wraps `search_memory` with the symptom-shape\nquery; `save-learning.ts` wraps `save_memory` with structured metadata\nso future `search-prior` queries find the match.\n\nThe Iron Law is not literal: sometimes a one-line typo fix is the right\nmove. The principle is \"if you can't say *why* this fix works, you're\nguessing.\" The craftbook's structure makes that guessing visible.\n",
+  "entryStepId": "gather-symptoms",
+  "triggers": [
+    "investigate this",
+    "debug this",
+    "why is this broken",
+    "find the bug",
+    "root cause"
+  ],
+  "steps": [
+    {
+      "id": "gather-symptoms",
+      "name": "Gather symptoms",
+      "description": "Pull together every observable signal: error messages, stack traces, logs, repro steps, when it started.",
+      "prompt": "**For this task you are an investigator, not an author.** The Iron Law: no fixes without investigation. Resist the urge to `write_file` a fix — even if your default persona is a developer, this craftbook is about *understanding what broke* and the fix comes later (separate task).\n\n**Your first action this turn:** call `ask_user_question` with the four bullets below if any signal is missing from the chat. If the user already supplied the symptom in their message, skip to `write_task_note`.\n\nElicit (if missing):\n- What's the observable failure? (exact error message, screenshot, stack trace, log line)\n- When did it start? (recent commit? deploy? environment change?)\n- Is it reproducible? (every time? intermittent? specific input?)\n- What's the smallest input that triggers it?\n\nThen `write_task_note({ ref, content: <3-5 line symptom summary> })`. Do NOT theorize yet. Do NOT propose causes — that's the next step. Do NOT call `read_task_notes` to find the procedure; it's right here.",
+      "suggestedRole": "developer",
+      "next": "search-prior"
+    },
+    {
+      "id": "search-prior",
+      "name": "Search prior",
+      "description": "Have we seen this before? Search memory for prior investigations in this project.",
+      "prompt": "Run the `search-prior` script. It searches project memory for prior investigations matching the symptom signature. If we've seen this before, the model returns the prior learning + the fix that landed.\n\nIf there's a match: state what the prior investigation found, and ask the user if this looks like the same bug (with `ask_user_question`). If yes, jump straight to the fix. If no, proceed to fresh investigation.\n\nIf there's no match: note 'no prior matches' to task notes and advance.",
+      "suggestedRole": "developer",
+      "onExit": {
+        "name": "search-prior",
+        "autoAdvanceWhen": {
+          "op": "ok"
+        }
+      },
+      "next": "reproduce"
+    },
+    {
+      "id": "reproduce",
+      "name": "Reproduce",
+      "description": "Get a deterministic repro. Often the longest step. Cannot fix what can't be reproduced.",
+      "prompt": "Get the bug to fire on demand. Strategies:\n\n1. **Read the failing path** — find the function/route from the stack trace (use `read_file` / `search_files`).\n2. **Walk inputs backward** — what user action triggered this? What's the request shape?\n3. **Try the minimal trigger** — strip the user's repro down. Half the bugs disappear when you isolate.\n4. **Run a small script if needed** — `run_nodejs_script` against a synthetic input.\n5. **If it won't reproduce**: state that explicitly. Either get more info from the user (`ask_user_question`) or escalate.\n\nWhen you have a repro, write the minimal trigger to task notes. Do not move on without one.",
+      "suggestedRole": "developer",
+      "next": "trace"
+    },
+    {
+      "id": "trace",
+      "name": "Trace to root cause",
+      "description": "Follow the data from the failure point back to the smallest 'this is the thing that's wrong.'",
+      "prompt": "Trace backward from the failure. Read the code path. The Iron Law: **the cause is not 'the function returned the wrong thing,' it's WHY the function returned the wrong thing.** Keep asking 'and why is THAT?' until you hit one of:\n\n- A coding bug (assignment swapped, condition inverted, type mismatch)\n- A bad invariant (assumed X but the data has Y)\n- A wrong assumption about a dependency (the API returns null in this case)\n- An environment / config issue (the staging DB doesn't have this column)\n\nDocument the chain in task notes. Bullet form is fine. End with: 'Root cause: <one sentence>.'",
+      "suggestedRole": "developer",
+      "next": "propose-fix"
+    },
+    {
+      "id": "propose-fix",
+      "name": "Propose fix",
+      "description": "State the fix. Don't apply it yet — let the user (or a separate craftbook) decide.",
+      "prompt": "Now the easy part. State the fix in plain language:\n\n- What file/function changes?\n- What's the new behavior?\n- What did NOT change (so the user knows you didn't gold-plate)?\n- What test would catch this regressing?\n\nDo NOT apply the fix unless the user explicitly asks. Investigation lives separate from edit-the-code so the diff stays minimal and reviewable. Advance.",
+      "suggestedRole": "developer",
+      "next": "save-learning"
+    },
+    {
+      "id": "save-learning",
+      "name": "Save learning",
+      "description": "Stamp the (symptom → root cause → fix) triple into project memory so future investigations find it.",
+      "prompt": "Run the `save-learning` script with the symptom, root cause, and proposed fix. It saves them to project memory with appropriate tags so `search-prior` finds them next time.\n\nThen report DONE with a one-line summary: 'Investigated <symptom>; root cause: <cause>; fix proposed: <fix>.'",
+      "suggestedRole": "developer",
+      "onExit": {
+        "name": "save-learning",
+        "autoAdvanceWhen": {
+          "op": "ok"
+        }
+      },
+      "terminal": true
+    }
+  ],
+  "scripts": {
+    "search-prior": "import { defineScript, gezel } from '@bendyline/gezel-sdk';\n\nexport const meta = defineScript({\n  name: 'search-prior',\n  description:\n    'Search project memory for prior investigations matching a symptom signature. Stamps {matches: number, hits: [{text, score}]}.',\n  inputs: {\n    symptom: {\n      type: 'string',\n      description: 'Short symptom description (1-3 sentences). Used as the search query.',\n      required: true,\n    },\n  },\n  outputs: {\n    matches: { type: 'number', description: 'Number of memory hits returned.' },\n    hits: {\n      type: 'array',\n      description: 'Top matches, each with text + score.',\n      itemType: 'object',\n    },\n  },\n  requires: ['memory.read'],\n});\n\ninterface MemoryHit {\n  text: string;\n  score: number;\n}\n\nasync function main(): Promise<void> {\n  const input = gezel.input as { symptom: string };\n  const query = `investigation: ${input.symptom}`;\n  const results = (await gezel.memory.search(query)) as MemoryHit[];\n  const filtered = (results ?? []).filter(\n    (r): r is MemoryHit => Boolean(r) && typeof r.text === 'string' && typeof r.score === 'number',\n  );\n  gezel.log(`Memory search for \"${query}\" returned ${filtered.length} hit(s)`);\n  gezel.output({ matches: filtered.length, hits: filtered.slice(0, 5) });\n}\n\nawait main();\n",
+    "save-learning": "import { defineScript, gezel } from '@bendyline/gezel-sdk';\n\nexport const meta = defineScript({\n  name: 'save-learning',\n  description:\n    'Stamp a (symptom → root cause → fix) investigation triple into project memory so future `search-prior` queries find it.',\n  inputs: {\n    symptom: { type: 'string', description: 'Observable failure.', required: true },\n    rootCause: { type: 'string', description: 'Root cause in one sentence.', required: true },\n    fix: { type: 'string', description: 'Proposed fix.', required: true },\n    files: {\n      type: 'string',\n      description: 'Comma-separated list of files touched (or expected to be touched).',\n    },\n  },\n  outputs: {\n    ok: { type: 'boolean', description: 'True on successful save.' },\n  },\n  requires: ['memory.write'],\n});\n\nasync function main(): Promise<void> {\n  const input = gezel.input as {\n    symptom: string;\n    rootCause: string;\n    fix: string;\n    files?: string;\n  };\n  const text = [\n    'investigation:',\n    `symptom: ${input.symptom}`,\n    `root cause: ${input.rootCause}`,\n    `fix: ${input.fix}`,\n    ...(input.files ? [`files: ${input.files}`] : []),\n  ].join('\\n');\n  await gezel.memory.save(text, {\n    kind: 'investigation',\n    ...(input.files ? { files: input.files } : {}),\n  });\n  gezel.log('Saved investigation to memory.');\n  gezel.output({ ok: true });\n}\n\nawait main();\n"
+  },
+  "version": "1.1.0",
+  "releasedAt": "2026-07-28T00:00:00Z"
+}

package/data/craftbook-templates/in/investigate/versions/1.1.0/test.json

@@ -0,0 +1,122 @@
+{
+  "schemaVersion": 1,
+  "title": "Root-cause investigation notes",
+  "objective": "Measure whether the investigate craftbook keeps a local model in diagnosis mode: gather symptoms, inspect a seeded failing path, identify root cause, propose a fix, and write durable task notes without requiring a code edit.",
+  "tags": [
+    "investigation"
+  ],
+  "prompt": "In the `Investigate Eval` project, investigate this failure without applying a code fix: `npm run accept` fails because cursor pagination skips records at page boundaries. The smallest repro is walking `lib/paginate.mjs` with limit 3 over the seeded 10-item fixture in `accept.mjs`; the acceptance script prints CASE failures. Read the code and acceptance script, find the root cause, and write task notes with Symptom, Minimal repro, Root cause, Proposed fix, and Regression test. Do not modify source files for this eval.",
+  "setup": {
+    "projectName": "Investigate Eval",
+    "about": "Self-contained eval project for the investigate craftbook. The target output is task notes, not a code change.",
+    "missionObjectives": "Investigate the seeded pagination failure, identify the exact root cause, propose a minimal fix and regression test, and leave source files unchanged.",
+    "files": [
+      {
+        "path": "package.json",
+        "content": "{\n  \"name\": \"investigate-eval\",\n  \"private\": true,\n  \"type\": \"module\",\n  \"scripts\": { \"accept\": \"node accept.mjs\" }\n}\n"
+      },
+      {
+        "path": "lib/paginate.mjs",
+        "content": "export function encodeCursor(index) {\n  return Buffer.from(`idx:${index}`, 'utf8').toString('base64url');\n}\n\nexport function decodeCursor(cursor) {\n  const raw = Buffer.from(cursor, 'base64url').toString('utf8');\n  if (!raw.startsWith('idx:')) throw new Error(`malformed cursor: ${cursor}`);\n  const index = Number(raw.slice(4));\n  if (!Number.isInteger(index) || index < 0) throw new Error(`malformed cursor: ${cursor}`);\n  return index;\n}\n\nexport function paginate(items, options = {}) {\n  const limit = options.limit ?? 3;\n  if (!Number.isInteger(limit) || limit < 1) throw new Error(`limit must be a positive integer, got ${limit}`);\n  const start = options.cursor == null ? 0 : decodeCursor(options.cursor) + 1;\n  const page = items.slice(start, start + limit);\n  const nextIndex = start + page.length;\n  const nextCursor = nextIndex < items.length ? encodeCursor(nextIndex) : null;\n  return { items: page, nextCursor };\n}\n"
+      },
+      {
+        "path": "accept.mjs",
+        "content": "import { paginate } from './lib/paginate.mjs';\n\nconst ITEMS = Array.from({ length: 10 }, (_, i) => ({ id: `item-${i + 1}` }));\n\nfunction walk(limit) {\n  const seen = [];\n  let cursor = null;\n  for (let hops = 0; hops < 10; hops += 1) {\n    const page = paginate(ITEMS, { limit, cursor });\n    seen.push(...page.items.map((item) => item.id));\n    cursor = page.nextCursor;\n    if (!cursor) break;\n  }\n  return seen;\n}\n\nconst expected = ITEMS.map((item) => item.id);\nconst got = walk(3);\nif (JSON.stringify(got) !== JSON.stringify(expected)) {\n  console.log(`CASE boundary: expected ${JSON.stringify(expected)} got ${JSON.stringify(got)}`);\n  process.exit(1);\n}\nconsole.log('ALL CASES PASS');\n"
+      }
+    ],
+    "worker": {
+      "name": "Theo",
+      "role": "Developer"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "A task created from investigate has notes naming the symptom, minimal repro, root cause, proposed fix, and regression test.",
+    "taskNotes": {
+      "minBytes": 400,
+      "checks": [
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "symptom",
+          "flags": "i"
+        },
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "minimal repro|repro",
+          "flags": "i"
+        },
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "root cause",
+          "flags": "i"
+        },
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "decodeCursor|cursor",
+          "flags": "i"
+        },
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "\\+\\s*1|one item",
+          "flags": "i"
+        },
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "proposed fix|remove",
+          "flags": "i"
+        },
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "regression test|accept",
+          "flags": "i"
+        }
+      ]
+    }
+  },
+  "rubric": {
+    "artifact": {
+      "path": "task-notes.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "safety",
+        "description": "Dry-run posture is explicit: no real credentials, clear stop-before-side-effect boundary."
+      },
+      {
+        "name": "mapping",
+        "description": "Fake endpoints/commands are mapped completely to the workflow steps."
+      },
+      {
+        "name": "signals",
+        "description": "Success, failure, retry, and abort conditions are all defined."
+      },
+      {
+        "name": "containment",
+        "description": "The plan cannot accidentally reach a real service from a mock context."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "no-fix-before-root-cause",
+    "task-note deliverable",
+    "seeded repro"
+  ],
+  "extensions": {
+    "legacySimulators": [
+      {
+        "id": "investigate-fake-service-fixture",
+        "kind": "data-source",
+        "status": "implemented",
+        "description": "Seeded local fake service contract replacing live CLIs, HTTP APIs, credentials, and side effects."
+      }
+    ]
+  }
+}

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

@@ -0,0 +1,12 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "inspect-review",
+  "accents": [
+    "muted terracotta",
+    "sage"
+  ],
+  "sourceSummary": "Debug a defect or production incident down to its true root cause and document the diagnosis with evidence, instead of patching the first symptom.",
+  "styleReference": "accessibility-audit-1910"
+}

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

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

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

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "design-media",
+  "accents": [
+    "muted terracotta",
+    "sage",
+    "muted indigo"
+  ],
+  "sourceSummary": "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.",
+  "styleReference": "accessibility-audit-1910"
+}

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

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

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

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "operate-maintain",
+  "accents": [
+    "sage",
+    "ochre",
+    "muted terracotta"
+  ],
+  "sourceSummary": "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.",
+  "styleReference": "accessibility-audit-1910"
+}

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

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

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

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "write-publish",
+  "accents": [
+    "muted terracotta",
+    "muted indigo",
+    "sage"
+  ],
+  "sourceSummary": "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.",
+  "styleReference": "accessibility-audit-1910"
+}

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

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"