@bendyline/gilde 0.1.4 → 0.1.5

package/data/craftbook-templates/me/memory-prompt-session/versions/1.0.1/craftbook.json

@@ -1,116 +0,0 @@
-{
-  "id": "memory-prompt-session",
-  "name": "Memory Session",
-  "description": "Run one guided memory session and bank it properly: pick the theme the timeline is hungriest for, follow the thread of feeling through the recorded conversation, and file the session with the follow-up questions that keep the next one alive. Locks the theme and question set FIRST, then captures the session in the teller's own words, then files it in the store with the threads to pull next time. Use for memory sessions, filing an interview with a parent or grandparent, memoir capture, and 'what should I ask next time'.\n\nA gallery craftbook generated from an archetype spec. It runs\n`phase → (per-phase gate) → … → evaluate → (loop) → finish`. Each build\nphase that produces a checkable artifact is followed by a **runtime\ngate-checkpoint** — the runtime verifies the artifact and routes with no\nmodel turn, looping back to redo the phase on a miss. The final `evaluate`\nstep holds a static deliverable gate plus a reviewer QA pass. What it adds\nover the generic `build-loop`: a specialist role per phase, a\ndomain-correct ordering, and a concrete per-phase quality bar.\n\nPhases:\n\n1. Scope the session (planner) — theme from the timeline's gaps, question set, capture rules → gated on `notes/scope.md` (markdown-notes)\n2. Capture the session (interviewer) — session record in the teller's own words under sessions/\n3. File the session (archivist) — store record updated, chapter-worthy moments, follow-up threads → gated on `report.md` (markdown-report)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
-  "entryStepId": "scope",
-  "triggers": [
-    "file the memory session",
-    "run a memory session",
-    "we recorded a session with mom",
-    "what should I ask next time",
-    "bank the interview"
-  ],
-  "steps": [
-    {
-      "id": "scope",
-      "name": "Scope the session",
-      "description": "theme from the timeline's gaps, question set, capture rules",
-      "prompt": "Choose the session's aim before pressing record — or before opening the transcript. Step 1: read sessions.json and timeline.md from the workspace — what has been captured already, and which years and themes the timeline is hungriest for. Step 2: pick the session theme with the owner and draft the question set — open questions that follow feeling, not chronology ('what did the kitchen smell like' beats 'what year was that'). Step 3: write an acceptance-criteria checklist ('the session file preserves the teller's own words and phrasings', 'the session is recorded in the store with its date and theme', 'the report names the moments worth a chapter, each with the teller's words', 'at least three follow-up threads, each with the question to open it'). Call write_task_note with the theme + question set + checklist and write notes/scope.md.",
-      "suggestedRole": "planner",
-      "advanceWhen": {
-        "file": "notes/scope.md",
-        "minBytes": 1,
-        "sniff": "nonempty"
-      },
-      "gate": {
-        "at": "completion",
-        "checks": [
-          {
-            "kind": "minBytes",
-            "file": "notes/scope.md",
-            "bytes": 120
-          },
-          {
-            "kind": "sniff",
-            "file": "notes/scope.md",
-            "sniff": "nonempty"
-          }
-        ],
-        "onReject": "scope",
-        "maxAttempts": 3
-      },
-      "next": "capture"
-    },
-    {
-      "id": "capture",
-      "name": "Capture the session",
-      "description": "session record in the teller's own words under sessions/",
-      "prompt": "Bank the session from the recording. Step 1: work from the session recording's transcript — through the project's transcription capabilities, or from a transcript file the owner provides. Step 2: shape it gently into a session record: keep the teller's own words and phrasings verbatim, keep the digressions (they are where the good material lives), and mark the interviewer's questions so the thread stays followable. Step 3: note the moments where the feeling changed — a laugh, a pause, a subject change — right where they happened. Step 4: save the session record in the sessions/ folder named for the date (for example sessions/2026-07-18-session.md) and call write_task_note with the path and the themes touched.",
-      "suggestedRole": "interviewer",
-      "next": "file"
-    },
-    {
-      "id": "file",
-      "name": "File the session",
-      "description": "store record updated, chapter-worthy moments, follow-up threads",
-      "prompt": "File the session and set up the next one. Step 1: record the session in the store through the project's memoir capabilities — date, teller, theme, and the session file's path — so sessions.json stays the index of everything banked. Step 2: write report.md: what was captured this session in a few warm lines, the moments worth a chapter (quote the teller's words for each), and at least three follow-up threads — each one a specific question for next time, aimed at a gap the session opened. Step 3: note anything the teller said to come back to, or asked to keep private — that instruction outranks everything. Call write_task_note with the chapter-worthy count and the top follow-up question.",
-      "suggestedRole": "archivist",
-      "advanceWhen": {
-        "file": "report.md",
-        "minBytes": 1,
-        "sniff": "nonempty"
-      },
-      "gate": {
-        "at": "completion",
-        "checks": [
-          {
-            "kind": "minBytes",
-            "file": "report.md",
-            "bytes": 1000
-          },
-          {
-            "kind": "fileCount",
-            "ext": [
-              "md"
-            ],
-            "min": 1,
-            "dir": "sessions",
-            "label": "the banked session record exists under sessions/"
-          }
-        ],
-        "scripts": [
-          {
-            "name": "checkContains",
-            "scope": "standard",
-            "inputs": {
-              "file": "report.md",
-              "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
-              "flags": "i"
-            }
-          }
-        ],
-        "onReject": "file",
-        "maxAttempts": 4
-      },
-      "next": "evaluate"
-    },
-    {
-      "id": "evaluate",
-      "name": "Evaluate",
-      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
-      "prompt": "Open report.md and the new session file under sessions/ and verify every criterion from notes/scope.md: the session file preserves the teller's own words (spot-check the report's quotes against the session file — they must be verbatim), the session is recorded in the store with date and theme, the chapter-worthy moments are named with the teller's words, and there are at least three follow-up threads each carrying a real question. Write PASS/FAIL per criterion; on any failure, name the gap and loop back to file.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"file\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
-      "suggestedRole": "reviewer",
-      "next": "file"
-    },
-    {
-      "id": "finish",
-      "name": "Finish",
-      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
-      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
-      "suggestedRole": "developer",
-      "terminal": true
-    }
-  ],
-  "version": "1.0.1",
-  "releasedAt": "2026-07-26T00:20:00.000Z"
-}

package/data/craftbook-templates/me/memory-prompt-session/versions/1.0.1/test.json

@@ -1,112 +0,0 @@
-{
-  "schemaVersion": 1,
-  "title": "Memory Session — the bakery years",
-  "objective": "Measure whether the memory-prompt-session craftbook banks a recorded session in the teller's own words, files it in the store, and produces real follow-up threads.",
-  "tags": [
-    "corpus"
-  ],
-  "prompt": "i recorded a long chat with mom about her bakery years — transcript is in recordings/session3.txt. can you file it as a sesion and tell me what to ask next time?",
-  "setup": {
-    "projectName": "Mam's Memoir",
-    "about": "Memoir studio project capturing Els's life story, one recorded session at a time. Session recordings land under workspace/recordings; banked sessions live under workspace/sessions with workspace/sessions.json as the index; workspace/timeline.md tracks which years are covered.",
-    "missionObjectives": "Bank every session faithfully — the teller's own words, filed and indexed — and keep the next session alive with follow-up questions. Grounded in the seeded transcript; no live services, no real credentials.",
-    "files": [
-      {
-        "path": "recordings/session3.txt",
-        "content": "Session 3 — recorded 2026-07-17, kitchen table. Teller: Mam (Els). Interviewer: Jip.\n\nJIP: You always call them the bakery years. Start wherever you want.\n\nELS: We took over the bakery on the Vissersdijk in 1978. Your father signed the papers with flour already on his sleeves, that is how sure he was. I was twenty-six and I had never once seen four o'clock in the morning. By that first winter I could tell the time by the ovens without looking at a clock.\n\nJIP: What did the mornings feel like?\n\nELS: Cold, then warm. That was the whole day, cold then warm. The front of the shop was ice until the ovens caught up. I kneaded with my coat on until six. The smell of the first proof — that is the smell I will want on my last day, I think. Yeast and warm linen.\n\nJIP: Who came in?\n\nELS: Everyone came in. The harbor men at five thirty, before anyone else was awake. They never spoke before the first roll, not one word, and I learned not to speak either. Mrs. Terpstra every Thursday for the raisin loaf, and she paid in coins she counted twice. Children after school with their cents pressed flat and sweaty in their hands.\n\nJIP: Was it ever bad?\n\nELS: The strike year was bad. I will not dress it up. Nineteen eighty-four, the flour price doubled in one season and we did not sleep for the mathematics of it. Your father wanted to sell. I said the ovens stay lit, and I took in mending in the afternoons so they could. Nobody in the town knew that. I did the mending in the back room with the curtain closed.\n\nJIP: I never knew that either.\n\nELS: You were four. You knew the mixing bowl and the licking spoon, that was your whole world. You used to sleep in the flour sacks like a cat. The customers asked after you like you were part of the inventory.\n\nJIP: Why did it end?\n\nELS: My hands, mostly. And the supermarket on the ring road, a little. We sold in 1990 to the Boonstra boy, who let it become a phone shop, which I have decided not to be bitter about. I kept the shop bell. It is in the box under the stairs with the wedding things. When I shake it I am twenty-six again, cold then warm.\n\nJIP: We should stop, your tea is cold.\n\nELS: The tea is always cold when the talking is good. Next time I will tell you about the wedding cakes. The ones I made and the one I never got to make. Ask me about that one, will you? Do not let me wriggle out of it.\n\n[recording ends 58:14]\n"
-      },
-      {
-        "path": "sessions.json",
-        "content": "{\n  \"teller\": \"Els\",\n  \"sessions\": [\n    {\n      \"date\": \"2026-06-07\",\n      \"theme\": \"the childhood house on the dike\",\n      \"summary\": \"Growing up in the 1950s, six siblings, the flood stories.\"\n    },\n    {\n      \"date\": \"2026-06-28\",\n      \"theme\": \"meeting Pa\",\n      \"summary\": \"The dance hall in 1971, the borrowed bicycle, the first winter together.\"\n    }\n  ]\n}\n"
-      },
-      {
-        "path": "timeline.md",
-        "content": "# Els — timeline coverage\n\n- 1950s — childhood on the dike: covered (session 1)\n- 1960s — school years, first job: thin, one anecdote only\n- 1971-1977 — meeting Pa, early marriage: covered (session 2)\n- 1978-1990 — the bakery years: BIGGEST GAP, nothing banked yet\n- 1990s — after the bakery: nothing\n"
-      }
-    ],
-    "worker": {
-      "name": "Milan",
-      "role": "Archivist"
-    }
-  },
-  "mocks": [],
-  "success": {
-    "summary": "The session is banked under sessions/ in the teller's own words, and report.md names the chapter-worthy moments with verbatim quotes plus at least three follow-up questions.",
-    "deliverables": [
-      {
-        "path": "report.md",
-        "kind": "markdown-report",
-        "minBytes": 1000,
-        "checks": [
-          {
-            "kind": "contains",
-            "file": "report.md",
-            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
-            "flags": "i"
-          },
-          {
-            "kind": "contains",
-            "file": "report.md",
-            "pattern": "follow",
-            "flags": "i",
-            "label": "follow-up threads present"
-          },
-          {
-            "kind": "contains",
-            "file": "report.md",
-            "pattern": "\\?",
-            "label": "real questions for next time"
-          },
-          {
-            "kind": "valuesSubsetOf",
-            "file": "report.md",
-            "sourceFiles": [
-              "recordings/session3.txt"
-            ],
-            "pattern": "[\"“]([^\"”\\n]{15,120})[\"”]",
-            "label": "quoted teller phrases are verbatim from the transcript"
-          }
-        ]
-      }
-    ],
-    "checks": [
-      {
-        "kind": "fileCount",
-        "ext": [
-          "md"
-        ],
-        "min": 1,
-        "dir": "sessions"
-      }
-    ]
-  },
-  "rubric": {
-    "artifact": {
-      "path": "report.md",
-      "kind": "markdown"
-    },
-    "axes": [
-      {
-        "name": "listening",
-        "description": "The report follows the feeling of the session — the mending secret, the shop bell — not just the chronology."
-      },
-      {
-        "name": "capture fidelity",
-        "description": "The banked session preserves the teller's own words and phrasings; report quotes are verbatim."
-      },
-      {
-        "name": "follow-threads",
-        "description": "At least three specific follow-up questions aimed at gaps the session opened, including the one the teller explicitly asked to be asked."
-      },
-      {
-        "name": "warmth",
-        "description": "Reads like family archiving, not data entry."
-      }
-    ]
-  },
-  "qualityFocus": [
-    "verbatim capture",
-    "follow-up questions",
-    "session filing"
-  ]
-}

package/data/craftbook-templates/pa/page-spread/versions/1.0.1/craftbook.json

@@ -1,94 +0,0 @@
-{
-  "id": "page-spread",
-  "name": "Page Spread",
-  "description": "Produce one page spread from script to panels: beats planned, panel art generated against the character sheets — never freehand from memory — lettered and laid out as the page the reader turns to. Locks the panel plan FIRST — each panel naming the sheet references that anchor it and the caption text it carries — then generates the panels from those anchors, then assembles the lettered spread. Use for producing a comic page, 'let's do page three', panel-and-letter passes, turning a script page into art, and the per-page ritual of a whole book.\n\nA gallery craftbook generated from an archetype spec. It runs\n`phase → (per-phase gate) → … → evaluate → (loop) → finish`. Each build\nphase that produces a checkable artifact is followed by a **runtime\ngate-checkpoint** — the runtime verifies the artifact and routes with no\nmodel turn, looping back to redo the phase on a miss. The final `evaluate`\nstep holds a static deliverable gate plus a reviewer QA pass. What it adds\nover the generic `build-loop`: a specialist role per phase, a\ndomain-correct ordering, and a concrete per-phase quality bar.\n\nPhases:\n\n1. Plan the panels (verhalenverteller) — script beats to panels, each anchored to a character sheet → gated on `notes/scope.md` (markdown-notes)\n2. Generate the panels (image-generator) — panel art from the sheet anchors, never from memory\n3. Assemble the spread (designer) — panels laid in reading order, captions and balloons lettered\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
-  "entryStepId": "scope",
-  "triggers": [
-    "produce the page spread",
-    "let's do the next page",
-    "panel out the script",
-    "turn the script page into panels",
-    "lay up the spread"
-  ],
-  "steps": [
-    {
-      "id": "scope",
-      "name": "Plan the panels",
-      "description": "script beats to panels, each anchored to a character sheet",
-      "prompt": "Break the page before generating a pixel. Step 1: read the page's script from the story notes and the character kits under characters/ — each character's manifest carries the references, seeds, and prompts that lock their look. Step 2: break the script into beats and assign each beat a panel — the moment, the framing, and who is in frame. Step 3: for every character in every panel, name the exact sheet reference (and its seed and prompt from the manifest) that anchors how they are drawn — a panel drawn from memory instead of the sheet is how page twelve stops matching page one. Step 4: copy the caption and balloon text for each panel verbatim from the script — the letterer changes nothing. Step 5: write an acceptance-criteria checklist ('every script beat has a panel', 'every figure anchored to a named sheet reference', 'captions and balloons verbatim from the script', 'panels read in order on the assembled page'). Call write_task_note with the panel count + checklist and write notes/scope.md.",
-      "suggestedRole": "verhalenverteller",
-      "advanceWhen": {
-        "file": "notes/scope.md",
-        "minBytes": 1,
-        "sniff": "nonempty"
-      },
-      "gate": {
-        "at": "completion",
-        "checks": [
-          {
-            "kind": "minBytes",
-            "file": "notes/scope.md",
-            "bytes": 120
-          },
-          {
-            "kind": "sniff",
-            "file": "notes/scope.md",
-            "sniff": "nonempty"
-          }
-        ],
-        "onReject": "scope",
-        "maxAttempts": 3
-      },
-      "next": "panels"
-    },
-    {
-      "id": "panels",
-      "name": "Generate the panels",
-      "description": "panel art from the sheet anchors, never from memory",
-      "prompt": "Generate the page's panels into pages/<number>/ (the folder named for the page). Step 1: for each planned panel, build the generation prompt FROM the anchors — start from the sheet reference's persisted prompt and seed out of the character's manifest, then add the panel's moment and framing; the sheet is the source of truth for how every character looks. Step 2: generate through the project's image capabilities, at least three panels, saved as pages/<number>/panel-1.png, panel-2.png, and so on in reading order. Step 3: after each panel, check it against the plan — right characters, right moment, silhouette and palette matching the sheet; regenerate what drifted before moving on. Call write_task_note with the panel count and which sheet references anchored each. The gate counts the actual image files under `pages/` — a panel that was planned but never rendered does not count, and neither does a placeholder file with an image name. If a generation call fails, say so and retry it; do not move on to assembly with panels missing.",
-      "suggestedRole": "image-generator",
-      "next": "assemble",
-      "gate": {
-        "maxAttempts": 4,
-        "checks": [
-          {
-            "kind": "fileCount",
-            "ext": [
-              "png"
-            ],
-            "min": 3,
-            "dir": "pages",
-            "label": "at least three rendered panel images exist under pages/ before lettering",
-            "verifyImageBytes": true
-          }
-        ]
-      }
-    },
-    {
-      "id": "assemble",
-      "name": "Assemble the spread",
-      "description": "panels laid in reading order, captions and balloons lettered",
-      "prompt": "Assemble the page at pages/<number>/spread.html. Step 1: lay the panels in reading order with honest gutters — the eye should never wonder which panel is next. Step 2: letter it — the captions and balloon text from the plan, verbatim from the script, placed with the panel they belong to, tails pointing at the speaker. Step 3: style it as a page — panel borders, gutter rhythm, type that reads at page size, all in one self-contained file. Step 4: read the finished page top to bottom once as a reader would and fix anything that stumbles. Call write_task_note with the spread path and the panel order.",
-      "suggestedRole": "designer",
-      "next": "evaluate"
-    },
-    {
-      "id": "evaluate",
-      "name": "Evaluate",
-      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
-      "prompt": "Open the page folder under pages/ beside notes/scope.md, the script, and the character manifests, and verify every criterion: every script beat has its panel and the panels sit in reading order; every figure traces to the sheet reference the plan named — check the plan's anchors against the characters/ manifests, continuity is the whole point of this book; the captions and balloons on the spread match the script verbatim — a letterer who paraphrases is rewriting the author; and the assembled page reads clean top to bottom. Write PASS/FAIL per criterion; on any failure, name the panel and the gap and loop back to panels.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"panels\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
-      "suggestedRole": "reviewer",
-      "next": "panels"
-    },
-    {
-      "id": "finish",
-      "name": "Finish",
-      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
-      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
-      "suggestedRole": "developer",
-      "terminal": true
-    }
-  ],
-  "version": "1.0.1",
-  "releasedAt": "2026-07-26T01:30:00.000Z"
-}

package/data/craftbook-templates/pa/page-spread/versions/1.0.1/test.json

@@ -1,133 +0,0 @@
-{
-  "schemaVersion": 1,
-  "title": "Page Spread — page 3 from script to lettered panels",
-  "objective": "Measure whether the page-spread craftbook produces page 3 as planned panels generated against the character kit's anchors and an assembled spread whose captions and balloons are conserved verbatim from the script.",
-  "tags": [
-    "html-page"
-  ],
-  "prompt": "lets do page 3 — the beats are in the story notes and Pips sheet is in the character kit. panel it out and lay up the sperad",
-  "setup": {
-    "projectName": "The Lighthouse Summer Comic",
-    "about": "Comic maker project. Scripts live under workspace/story (page 3 is workspace/story/page-3.md). Character kits live under workspace/characters — Pip's manifest is workspace/characters/pip/sheet.json. Page spreads land under workspace/pages/<number>: page 3's panels and spread.html go in workspace/pages/3.",
-    "missionObjectives": "Continuity over convenience: every figure anchored to the character kit's persisted references, captions and balloons verbatim from the script. No live services, no real credentials.",
-    "files": [
-      {
-        "path": "story/page-3.md",
-        "content": "# Page 3 — The Missed Ferry\n\nBEAT 1 — Wide on the empty dock, morning light. The ferry is a speck on the water.\nCAPTION: The ferry left without them.\n\nBEAT 2 — Pip at the dock's edge, scarf whipped by wind, determined face.\nPIP: We can still make the lighthouse by dark.\n\nBEAT 3 — Close on Marta hoisting the rowboat's rope, skeptical, hair escaping her cap.\nMARTA: In THAT boat? It leaks on Tuesdays.\n\nBEAT 4 — The little rowboat pushing off, Pip at the bow like a figurehead, town shrinking behind.\nCAPTION: It was, unfortunately, a Tuesday.\n"
-      },
-      {
-        "path": "characters/pip/sheet.json",
-        "content": "[\n  {\n    \"pose\": \"sitting\",\n    \"file\": \"characters/pip/ref-sit.png\",\n    \"seed\": 411203,\n    \"prompt\": \"wire-haired terrier Pip, sand-yellow coat, mustard scarf, one ear up one folded, sitting on harbor wall, storm-blue background, clean comic ink and flat color\"\n  },\n  {\n    \"pose\": \"running\",\n    \"file\": \"characters/pip/ref-run.png\",\n    \"seed\": 411207,\n    \"prompt\": \"wire-haired terrier Pip, sand-yellow coat, mustard scarf streaming, one ear up one folded, running flat-out, side view, storm-blue background, clean comic ink and flat color\"\n  },\n  {\n    \"pose\": \"determined\",\n    \"file\": \"characters/pip/ref-determined.png\",\n    \"seed\": 411211,\n    \"prompt\": \"wire-haired terrier Pip, close-up, leaning forward, determined brow, mustard scarf, one ear up one folded, storm-blue background, clean comic ink and flat color\"\n  },\n  {\n    \"pose\": \"worried\",\n    \"file\": \"characters/pip/ref-worried.png\",\n    \"seed\": 411219,\n    \"prompt\": \"wire-haired terrier Pip, both ears down, knotted brow, mustard scarf, sitting small, storm-blue background, clean comic ink and flat color\"\n  }\n]\n"
-      },
-      {
-        "path": "characters/pip/ref-sit.png",
-        "content": "placeholder reference image: Pip sitting\n"
-      },
-      {
-        "path": "characters/pip/ref-run.png",
-        "content": "placeholder reference image: Pip running\n"
-      },
-      {
-        "path": "characters/pip/ref-determined.png",
-        "content": "placeholder reference image: Pip determined\n"
-      },
-      {
-        "path": "characters/pip/ref-worried.png",
-        "content": "placeholder reference image: Pip worried\n"
-      }
-    ],
-    "worker": {
-      "name": "Joost",
-      "role": "Verhalenverteller"
-    }
-  },
-  "mocks": [],
-  "success": {
-    "summary": "pages/3 holds 3+ panel images generated from the kit's anchors and a lettered spread.html whose captions and balloons match the script word for word.",
-    "checks": [
-      {
-        "kind": "fileCount",
-        "ext": [
-          "png"
-        ],
-        "min": 3,
-        "dir": "pages/3",
-        "verifyImageBytes": true
-      }
-    ],
-    "deliverables": [
-      {
-        "path": "pages/3/spread.html",
-        "kind": "html-page",
-        "minBytes": 1500,
-        "checks": [
-          {
-            "kind": "cssMinBytes",
-            "bytes": 650,
-            "file": "pages/3/spread.html"
-          },
-          {
-            "kind": "contains",
-            "file": "pages/3/spread.html",
-            "pattern": "make the lighthouse by dark",
-            "flags": "i",
-            "label": "Pip's balloon conserved verbatim"
-          },
-          {
-            "kind": "contains",
-            "file": "pages/3/spread.html",
-            "pattern": "The ferry left without them",
-            "flags": "i",
-            "label": "opening caption conserved verbatim"
-          },
-          {
-            "kind": "contains",
-            "file": "pages/3/spread.html",
-            "pattern": "It leaks on Tuesdays",
-            "flags": "i",
-            "label": "Marta's balloon conserved verbatim"
-          },
-          {
-            "kind": "judge",
-            "file": "pages/3/spread.html",
-            "rubric": "The spread lays the panels in reading order with captions and balloons attached to the right panels; the panel plan anchored every figure to the character manifest's references (seeds/prompts) rather than describing the characters from memory.",
-            "sourceFiles": [
-              "story/page-3.md",
-              "characters/pip/sheet.json"
-            ],
-            "label": "continuity and lettering"
-          }
-        ]
-      }
-    ]
-  },
-  "rubric": {
-    "artifact": {
-      "path": "pages/3/spread.html",
-      "kind": "html"
-    },
-    "axes": [
-      {
-        "name": "continuity",
-        "description": "Figures are generated from the kit's persisted anchors — page 3's Pip is the sheet's Pip, same silhouette, palette, and scarf."
-      },
-      {
-        "name": "panel flow",
-        "description": "Panels follow the script's beats in reading order; the eye never wonders where to go next."
-      },
-      {
-        "name": "lettering",
-        "description": "Captions and balloons are verbatim from the script, placed with their panels, tails pointing at the speaker."
-      },
-      {
-        "name": "storytelling",
-        "description": "Framing choices serve the beats — the wide dock feels empty, the rowboat launch feels small and brave."
-      }
-    ]
-  },
-  "qualityFocus": [
-    "sheet-anchored panels",
-    "verbatim lettering",
-    "reading order"
-  ]
-}

package/data/craftbook-templates/pl/plan/versions/1.0.1/craftbook.json

@@ -1,104 +0,0 @@
-{
-  "id": "plan",
-  "name": "Plan",
-  "description": "Author a PLAN for a piece of work as a reviewable **draft task** — the gezel equivalent of `/plan` in other tools.\n\nUnlike a normal craftbook, this one's deliverable is not a workspace file: it's a high-quality *draft task* (a plan) that the user reviews and then activates to run. Invoke it via the `start_plan` tool, which creates the draft and an authoring task that walks this craftbook. The authoring gates inspect the draft being built (via the authoring task's `craftbookParams.draftRef`), so a weak model can't skip the parts that make a plan good.\n\nSteps:\n\n1. **Frame the goal** (planner) — write a strong \"about\" on the draft and set 3–8 concrete **outcomes** (what should be created or updated at success). Gated by `checkPlanFramed`.\n2. **Design the build steps** (planner) — add ordered build steps to the draft, each given a concrete static deliverable + enforced gate via `set_step_deliverable`. Gated by `checkStepsHaveDeliverables`.\n3. **Add the verification step** (planner) — append a terminal step (via `add_verification_step`) that confirms every outcome with evidence before the task can close. Gated by `checkVerificationStep`.\n4. **Review the plan** (planner) — sanity-check the whole graph. Gated by `checkPlanReady`, which returns one list of any remaining gaps.\n5. **Hand off to the user** (planner, terminal) — summarize the plan and tell the user to review and **activate** it.\n\nWhen activated (draft → active), the produced task runs its build steps — each looping back on a missed deliverable — and its terminal step verifies the outcomes were kept.\n",
-  "entryStepId": "frame",
-  "triggers": [
-    "plan this",
-    "make a plan",
-    "plan for",
-    "/plan"
-  ],
-  "steps": [
-    {
-      "id": "frame",
-      "name": "Frame the goal",
-      "description": "Write a strong 'about' and set the outcomes on the draft plan.",
-      "prompt": "You are drafting a PLAN. The plan is a separate **draft task** — its ref is in your task's `craftbookParams.draftRef` (shown in your task description / entry note). Everything you author here targets that draft via the `task` argument.\n\nYour next message must START with a tool call — not a description of what you are about to do. Make exactly these two calls, in this order, then stop:\n\n1. `update_task({ task: \"<draftRef>\", description })` — the job-to-be-done from the user's perspective, 120+ characters.\n2. `set_outcomes({ task: \"<draftRef>\", outcomes: [ ... ] })` — 3–8 concrete, individually-verifiable statements of what gets created or updated.\n\nNeither call is optional and prose is not a substitute for either: the gate reads the draft itself and rejects until both landed.\n\n**Detail:**\n\n1. **Write a strong \"about\".** Call `update_task({ task: \"<draftRef>\", description })` with a clear job-to-be-done from the user's perspective — what success looks like, in 120+ characters.\n2. **Set the outcomes.** Call `set_outcomes({ task: \"<draftRef>\", outcomes: [ ... ] })` with 3–8 concrete, individually-verifiable statements of what should be **created or updated** at completion (e.g. \"An index.html with a playable snake game and a game-over/restart screen\", \"A README documenting how to run it\").\n\nWhen done, call `advance_task_step({ ref, stepId: \"frame\", next: \"outline\" })`. The gate rejects until the draft has a real about and at least 3 outcomes — fix what it names and advance again.",
-      "suggestedRole": "planner",
-      "gate": {
-        "at": "completion",
-        "scripts": [
-          {
-            "name": "checkPlanFramed",
-            "scope": "standard",
-            "inputs": {}
-          }
-        ],
-        "onReject": "frame",
-        "maxAttempts": 4
-      },
-      "next": "outline"
-    },
-    {
-      "id": "outline",
-      "name": "Design the build steps",
-      "description": "Add ordered build steps to the draft, each gated on a concrete static deliverable.",
-      "prompt": "Design the implementation as an ordered series of **build steps** on the draft (`craftbookParams.draftRef`). Each build step must produce a **concrete static file** with an enforced gate.\n\nThe draft starts with one placeholder step named **\"Implement\"**. First call `craftbook_read({ task: \"<draftRef>\" })` and note the actual id of that placeholder step. Then either:\n- repurpose that exact step with `craftbook_update_step({ task: \"<draftRef>\", stepId: \"<actualId>\", name, prompt, suggestedRole })`, then immediately call `set_step_deliverable({ task: \"<draftRef>\", stepId: \"<actualId>\", path, kind })`; or\n- remove that exact step with `craftbook_remove_step({ task: \"<draftRef>\", stepId: \"<actualId>\" })` after you have added the real build steps.\n\nFor each added step, in order:\n1. `craftbook_add_step({ task: \"<draftRef>\", name, prompt, suggestedRole })` — a concrete, instructive step (e.g. name \"Build the game\", role \"developer\", a prompt that says exactly what to make).\n2. Call `craftbook_read({ task: \"<draftRef>\" })` and use the actual id of the step you just added.\n3. `set_step_deliverable({ task: \"<draftRef>\", stepId: \"<actualId>\", path, kind })` — declare the named file it produces and auto-attach the gate. Pick `kind` to match the artifact: `html-page` / `html-game` / `markdown-report` / `code-with-tests` / `json` / etc.\n\nDo not invent step ids like `build` unless `craftbook_read` shows that exact id. Do not advance while any build step lacks `advanceWhen`/`gate`. Order the steps so each builds on the last. When every build step has a deliverable, call `advance_task_step({ ref, stepId: \"outline\", next: \"verify-step\" })`. The gate lists any step still missing a deliverable.",
-      "suggestedRole": "planner",
-      "gate": {
-        "at": "completion",
-        "scripts": [
-          {
-            "name": "checkStepsHaveDeliverables",
-            "scope": "standard",
-            "inputs": {}
-          }
-        ],
-        "onReject": "outline",
-        "maxAttempts": 4
-      },
-      "next": "verify-step"
-    },
-    {
-      "id": "verify-step",
-      "name": "Add the verification step",
-      "description": "Append a terminal verification step that checks the outcomes were kept.",
-      "prompt": "Add the final **verification step** to the draft (`craftbookParams.draftRef`): call `add_verification_step({ task: \"<draftRef>\" })`. This appends a terminal step — gated by `checkOutcomesMet` — that makes the executor confirm each outcome (with evidence) before the task can close. Pass a custom `prompt` only if you need domain-specific verification instructions.\n\nThen call `advance_task_step({ ref, stepId: \"verify-step\", next: \"review\" })`. The gate rejects until the draft has a terminal step that verifies the outcomes.",
-      "suggestedRole": "planner",
-      "gate": {
-        "at": "completion",
-        "scripts": [
-          {
-            "name": "checkVerificationStep",
-            "scope": "standard",
-            "inputs": {}
-          }
-        ],
-        "onReject": "verify-step",
-        "maxAttempts": 4
-      },
-      "next": "review"
-    },
-    {
-      "id": "review",
-      "name": "Review the plan",
-      "description": "Sanity-check the whole plan before handing it to the user.",
-      "prompt": "Final check before handing the plan to the user. `craftbook_read({ task: \"<draftRef>\" })` and sanity-check: the steps are ordered sensibly, each build step has a deliverable, and the last step verifies the outcomes. Fix anything off with the `craftbook_*` / `set_step_deliverable` tools on the draft.\n\nWhen the plan is solid, call `advance_task_step({ ref, stepId: \"review\", next: \"done\" })`. The gate returns a single list of anything still missing (thin about, fewer than 3 outcomes, ungated steps, or no verification step).",
-      "suggestedRole": "planner",
-      "gate": {
-        "at": "completion",
-        "scripts": [
-          {
-            "name": "checkPlanReady",
-            "scope": "standard",
-            "inputs": {}
-          }
-        ],
-        "onReject": "review",
-        "maxAttempts": 4
-      },
-      "next": "done"
-    },
-    {
-      "id": "done",
-      "name": "Hand off to the user",
-      "description": "Summarize the plan and tell the user to review and activate it.",
-      "prompt": "The plan is ready. Summarize it for the user in your reply: mention the draft task **<draftRef>** by its ref (so it renders as a reviewable plan card), and recap the about, the outcomes, and the build steps. Tell the user they can **review and activate** the plan to run it — or ask you to tweak it first. Then report DONE.",
-      "suggestedRole": "planner",
-      "terminal": true
-    }
-  ],
-  "version": "1.0.1",
-  "releasedAt": "2026-07-26T01:30:00.000Z"
-}