@bendyline/gilde 0.1.2 → 0.1.4

package/data/craftbook-templates/co/content-deck/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": "Turn a body of source content into a presentation deck.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/co/content-deck/manifest.json

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

package/data/craftbook-templates/co/contract-template/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": "Draft a reusable, plain-language agreement template — service agreement, NDA, freelance contract, or terms — with clearly marked fill-in fields, structured numbered clauses, and a prominent non-legal-advice disclaimer.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/co/contract-template/manifest.json

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

package/data/craftbook-templates/co/cookbook-layout/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": "Assemble the heirloom: every tested recipe in its chapter, the provenance kept beside the food — whose recipe it was, what table it came from — chapter intros in the family's voice, print-ready pages.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/co/cookbook-layout/manifest.json

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

package/data/craftbook-templates/co/copy-review/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 an editorial review on a piece of content for clarity, correctness, and brand voice, then produce a line-edit report and a clean revised version.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/co/copy-review/manifest.json

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

package/data/craftbook-templates/co/corpus-email-digest/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": "Produce an email-ready digest that summarizes a corpus of content (docs, feeds, notes) for a recurring send.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/co/corpus-email-digest/manifest.json

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

package/data/craftbook-templates/co/corpus-synthesis/art.json

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "research-learn",
+  "accents": [
+    "sage",
+    "muted indigo",
+    "terracotta"
+  ],
+  "sourceSummary": "Read a provided corpus of documents and synthesize it into a single coherent overview: a planner sets the synthesis question and the extraction schema, a researcher reads every document and extracts structured notes keyed back to each source, and a copywriter synthesizes the extracts into a unified narrative organized…",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/co/corpus-synthesis/manifest.json

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

package/data/craftbook-templates/co/cover-letter/art.json

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "people-events-growth",
+  "accents": [
+    "dusty rose",
+    "sage",
+    "muted terracotta"
+  ],
+  "sourceSummary": "Write a tailored, one-page cover letter that maps a candidate's real background to a specific job's requirements: it first scopes the role's key requirements, the company hook, and the 3-4 strongest matching proof points from the applicant's experience, then drafts a focused letter with a specific opening,…",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/co/cover-letter/manifest.json

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

package/data/craftbook-templates/cr/crm-update-batch/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": "Turn unstructured notes (call logs, meeting recaps, email threads) into a batch of structured CRM updates: per-contact field changes, activity logs, and next-step tasks as a validated import file.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/cr/crm-update-batch/manifest.json

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

package/data/craftbook-templates/cr/cron-job/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 scheduled batch job that runs on a cadence, processes a unit of work, is safe to re-run, and reports its outcome.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/cr/cron-job/manifest.json

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

package/data/craftbook-templates/cr/crossword-forge/art.json

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "people-events-growth",
+  "accents": [
+    "dusty rose",
+    "sage",
+    "muted terracotta"
+  ],
+  "sourceSummary": "Construct a personalized crossword and prove it works before anyone's pencil touches it: the grid actually interlocks, every entry sits in the grid exactly where its number says, every clue is tuned to the solver — and the whole thing ships as a printable page with the solution kept decently out of sight.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/cr/crossword-forge/manifest.json

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

package/data/craftbook-templates/cr/crossword-forge/versions/1.0.1/craftbook.json

@@ -0,0 +1,147 @@
+{
+  "id": "crossword-forge",
+  "name": "Forge a Crossword",
+  "description": "Construct a personalized crossword and prove it works before anyone's pencil touches it: the grid actually interlocks, every entry sits in the grid exactly where its number says, every clue is tuned to the solver — and the whole thing ships as a printable page with the solution kept decently out of sight. Locks the theme and the word list FIRST, then constructs the mechanically-verified grid, then renders the printable puzzle. Use for making a crossword, a personalized puzzle for the family, 'a crossword with the grandkids' names in it', and printable puzzle gifts.\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 puzzle (puzzle-maker) — theme and word list from the personal material, construction rules → gated on `notes/scope.md` (markdown-notes)\n2. Construct the grid (developer) — verified puzzle data — grid, entries, clues → gated on `puzzle.json` (json)\n3. Render the printable page (developer) — printable grid and clues, solution out of sight, shelf copy filed → gated on `puzzle.html` (html-page)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "make a crossword",
+    "crossword for the family",
+    "personalized crossword puzzle",
+    "forge a crossword",
+    "printable crossword"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the puzzle",
+      "description": "theme and word list from the personal material, construction rules",
+      "prompt": "Set the build before placing a letter. Step 1: gather the personal material — the task's params (theme, names, size) and any notes in the workspace about the solvers: names, places, pets, running jokes. Step 2: draft the word list — the personal entries first, filler words only where the grid needs them to interlock, everything spellable in plain uppercase letters. Step 3: lock the construction rules — grid size from the size param (small about 9x9, medium about 13x13, large about 15x15), every entry placed in the grid and crossing at least one other entry, no entry without a clue, clue difficulty tuned to the solvers. Step 4: write an acceptance-criteria checklist ('every entry reads out of the grid at its stated coordinates', 'every crossing agrees letter for letter', 'every entry has a clue at the target difficulty', 'the personal words made it into the grid', 'the rendered page prints cleanly with the solution out of casual sight'). Call write_task_note with the theme + word count + checklist and write notes/scope.md.",
+      "suggestedRole": "puzzle-maker",
+      "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": "construct"
+    },
+    {
+      "id": "construct",
+      "name": "Construct the grid",
+      "description": "verified puzzle data — grid, entries, clues",
+      "prompt": "Construct the puzzle as data at puzzle.json. Step 1: build the grid — uppercase letters in filled cells, '.' for blocks — placing every word from the locked list so the entries interlock. Step 2: write it as JSON with this exact shape: { \"title\": ..., \"size\": { \"rows\": N, \"cols\": N }, \"grid\": [ one string per row ], \"entries\": [ { \"number\", \"answer\", \"row\", \"col\", \"direction\": \"across\" or \"down\", \"clue\" } ] } — rows and columns zero-indexed from the top-left. Step 3: **verify mechanically, not mentally.** Reading a grid cell-by-cell in your head does not work at this size — every constructive puzzle needs a checker. If the project already has one (look under `checks/`), run it with `run_nodejs_script`. If it does not, write one first: a short dependency-free Node script at `checks/verify-puzzle.mjs` that loads puzzle.json, walks every entry, reads its letters out of the grid at its row/col in its direction, and prints the exact mismatches (entry number, expected answer, what the grid actually spells) — then `PUZZLE OK` when all entries agree. Run it, fix exactly what it names, and run it again until it is clean. Do not complete this step on an unverified grid: the gate re-checks this the same way and will name any entry that lies. Step 4: write the clues into the entries — personal entries clued with the in-jokes, fillers clued honestly at the target difficulty. Call write_task_note with the grid size, the entry count, and the checker's final output.",
+      "suggestedRole": "developer",
+      "advanceWhen": {
+        "file": "puzzle.json",
+        "minBytes": 1,
+        "sniff": "json-valid"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "puzzle.json",
+            "bytes": 400
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkJsonValid",
+            "scope": "standard",
+            "inputs": {
+              "file": "puzzle.json"
+            }
+          }
+        ],
+        "onReject": "construct",
+        "maxAttempts": 3
+      },
+      "next": "render"
+    },
+    {
+      "id": "render",
+      "name": "Render the printable page",
+      "description": "printable grid and clues, solution out of sight, shelf copy filed",
+      "prompt": "Render the playable, printable page at puzzle.html. Step 1: draw the empty numbered grid from puzzle.json — blocks and cell numbers exactly as the data has them — beside the across and down clue lists. Step 2: make it print-ready — an @page rule, print styles, the grid sized so a pencil fits in the squares. Step 3: keep the solution out of casual sight — behind a toggle on screen and on its own page in print, never beside the blank grid. Step 4: any script on the page must actually run — check it before completing. Step 5: file a dated copy of puzzle.json and puzzle.html into the puzzles/ shelf named for the theme, so the pack-layout ritual can find them later. Call write_task_note with the page path and the shelf copies.",
+      "suggestedRole": "developer",
+      "advanceWhen": {
+        "file": "puzzle.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "puzzle.html",
+            "bytes": 800
+          },
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "puzzle.html"
+          },
+          {
+            "kind": "contains",
+            "file": "puzzle.html",
+            "pattern": "@page|@media\\s+print",
+            "flags": "i",
+            "label": "print CSS"
+          },
+          {
+            "kind": "jsParses",
+            "file": "puzzle.html"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "puzzle.html"
+            }
+          }
+        ],
+        "onReject": "render",
+        "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 puzzle.json and puzzle.html and verify every criterion from notes/scope.md: read three entries out of the grid by their coordinates and confirm each matches its answer, check one crossing square agrees in both directions, confirm every entry has a clue and the personal words from the scope made it in, and check the rendered page — the grid matches the data, the clue numbers line up, and the solution stays out of sight on screen and in print. Write PASS/FAIL per criterion; on any failure, name the entry or cell and loop back to construct.\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: \"construct\" })` 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": "construct"
+    },
+    {
+      "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/cr/crossword-forge/versions/1.0.1/test.json

@@ -0,0 +1,135 @@
+{
+  "schemaVersion": 1,
+  "title": "Forge a Crossword — personal words to a verified printable grid",
+  "objective": "Measure whether the crossword-forge craftbook constructs a mechanically-valid interlocking crossword from the seeded family notes — entries readable out of the grid at their coordinates, every entry clued — rendered as a printable page with the solution out of sight.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "can you make a crossword for the grandkids with there names and our dog in it? printable pls",
+  "setup": {
+    "projectName": "Loon Lake Puzzle Almanac",
+    "about": "Puzzle almanac project for the Halloran family. Notes about the solvers live at workspace/notes/family.md; finished puzzles are filed on the workspace/puzzles shelf. The working puzzle is workspace/puzzle.json with its printable page at workspace/puzzle.html.",
+    "missionObjectives": "The grid must actually interlock and verify — every entry readable out of the grid at its coordinates, every entry clued. Personalization comes from the family notes. No live services, no real credentials.",
+    "files": [
+      {
+        "path": "notes/family.md",
+        "content": "# The solvers\n\nGrandkids: Nora (12, reigning flashlight-tag champion), Felix (10, dinosaur phase never ended),\nImani (9, reads above her grade and knows it), Theo (7, will need help with the long ones).\n\nThe dog: Biscuit — golden retriever, eats crayons, beloved.\n\nPlaces: the cabin at Loon Lake, the porch swing, Grandpa's garden.\n\nRunning jokes: Grandpa's burnt pancakes, the canoe that tipped twice in one day,\nflashlight tag after dark, \"who fed Biscuit already?\"\n"
+      },
+      {
+        "path": "checks/verify-puzzle.mjs",
+        "content": "// Eval-only re-check: verifies puzzle.json is a real, solvable crossword.\n// Exits 0 and prints PUZZLE OK when every entry reads out of the grid at its\n// coordinates, every entry has a clue, and the entries interlock.\nimport { readFileSync } from 'node:fs';\n\nfunction fail(message) {\n  console.error('PUZZLE BROKEN: ' + message);\n  process.exit(1);\n}\n\nlet puzzle;\ntry {\n  puzzle = JSON.parse(readFileSync('puzzle.json', 'utf8'));\n} catch (err) {\n  fail('puzzle.json missing or not valid JSON (' + err.message + ')');\n}\n\nconst grid = puzzle.grid;\nif (!Array.isArray(grid) || grid.length < 5 || !grid.every((r) => typeof r === 'string')) {\n  fail('grid must be an array of at least 5 row strings');\n}\nconst width = grid[0].length;\nfor (let r = 0; r < grid.length; r++) {\n  if (grid[r].length !== width) fail('row ' + r + ' width differs from row 0');\n  if (!/^[A-Z.]+$/.test(grid[r])) fail('row ' + r + ' has characters outside A-Z and \".\"');\n}\n\nconst entries = puzzle.entries;\nif (!Array.isArray(entries) || entries.length < 4) fail('need at least 4 entries');\n\nconst owners = new Map();\nlet across = 0;\nlet down = 0;\nfor (const e of entries) {\n  const label = typeof e.answer === 'string' && e.answer ? e.answer : 'entry #' + (e.number ?? '?');\n  if (typeof e.answer !== 'string' || !/^[A-Z]{2,}$/.test(e.answer)) fail(label + ': bad answer');\n  if (e.direction !== 'across' && e.direction !== 'down') fail(label + ': bad direction');\n  if (!Number.isInteger(e.row) || !Number.isInteger(e.col)) fail(label + ': bad coordinates');\n  if (typeof e.clue !== 'string' || e.clue.trim().length === 0) fail(label + ': missing clue');\n  if (e.direction === 'across') across++;\n  else down++;\n  for (let i = 0; i < e.answer.length; i++) {\n    const r = e.direction === 'down' ? e.row + i : e.row;\n    const c = e.direction === 'across' ? e.col + i : e.col;\n    if (r < 0 || r >= grid.length || c < 0 || c >= width) fail(label + ' runs off the grid');\n    if (grid[r][c] !== e.answer[i]) {\n      fail(label + ': grid has \"' + grid[r][c] + '\" at ' + r + ',' + c + ' expected \"' + e.answer[i] + '\"');\n    }\n    const key = r + ',' + c;\n    if (!owners.has(key)) owners.set(key, new Set());\n    owners.get(key).add(e.direction + ':' + label);\n  }\n}\nif (across === 0 || down === 0) fail('need both across and down entries');\n\nfor (const e of entries) {\n  let interlocks = false;\n  for (let i = 0; i < e.answer.length && !interlocks; i++) {\n    const r = e.direction === 'down' ? e.row + i : e.row;\n    const c = e.direction === 'across' ? e.col + i : e.col;\n    for (const owner of owners.get(r + ',' + c) ?? []) {\n      if (!owner.startsWith(e.direction + ':')) interlocks = true;\n    }\n  }\n  if (!interlocks) fail(e.answer + ' does not cross any other entry');\n}\n\nconsole.log('PUZZLE OK: ' + entries.length + ' entries (' + across + ' across, ' + down + ' down) verified');\n"
+      }
+    ],
+    "worker": {
+      "name": "Wouter",
+      "role": "Puzzle maker"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "puzzle.json is a verified interlocking crossword carrying the personal words; puzzle.html is a printable page with clue lists and the solution kept out of sight.",
+    "deliverables": [
+      {
+        "path": "puzzle.json",
+        "kind": "json",
+        "minBytes": 400,
+        "checks": [
+          {
+            "kind": "sniff",
+            "file": "puzzle.json",
+            "sniff": "json-valid"
+          },
+          {
+            "kind": "nodeScriptPasses",
+            "script": "checks/verify-puzzle.mjs",
+            "timeoutMs": 5000,
+            "requiredOutput": [
+              {
+                "pattern": "PUZZLE OK",
+                "label": "grid verifies as solvable"
+              }
+            ]
+          },
+          {
+            "kind": "contains",
+            "file": "puzzle.json",
+            "pattern": "NORA|FELIX|IMANI|THEO",
+            "label": "a grandkid name made the grid"
+          },
+          {
+            "kind": "contains",
+            "file": "puzzle.json",
+            "pattern": "BISCUIT",
+            "label": "the dog made the grid"
+          }
+        ]
+      },
+      {
+        "path": "puzzle.html",
+        "kind": "html-page",
+        "minBytes": 2000,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "puzzle.html"
+          },
+          {
+            "kind": "jsParses",
+            "file": "puzzle.html"
+          },
+          {
+            "kind": "contains",
+            "file": "puzzle.html",
+            "pattern": "@page|@media\\s+print",
+            "flags": "i",
+            "label": "print CSS"
+          },
+          {
+            "kind": "contains",
+            "file": "puzzle.html",
+            "pattern": "Across",
+            "flags": "i",
+            "label": "across clue list"
+          },
+          {
+            "kind": "contains",
+            "file": "puzzle.html",
+            "pattern": "Down",
+            "flags": "i",
+            "label": "down clue list"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "puzzle.html",
+      "kind": "html"
+    },
+    "axes": [
+      {
+        "name": "solvability",
+        "description": "The grid interlocks and the clue numbering matches the grid — a solver could actually finish it."
+      },
+      {
+        "name": "personalization",
+        "description": "The names, the dog, and the running jokes from the family notes carry the puzzle; fillers stay in the background."
+      },
+      {
+        "name": "clue craft",
+        "description": "Clues are tuned to the solvers — in-jokes for the personal entries, honest difficulty for the fillers, help-sized for the youngest."
+      },
+      {
+        "name": "print readiness",
+        "description": "The page prints with pencil-sized squares and the solution on its own page, never beside the blank grid."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "verified interlocking grid",
+    "grounded personalization",
+    "solution out of sight"
+  ]
+}

package/data/craftbook-templates/cs/csv-transformer/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": "Reshape and convert tabular data from one schema to another: rename and reorder columns, split or merge fields, derive new columns, pivot/unpivot, change format (CSV<->JSON<->TSV), and filter rows.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/cs/csv-transformer/manifest.json

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

package/data/craftbook-templates/da/dashboard-spec/art.json

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "analyze-measure",
+  "accents": [
+    "muted indigo",
+    "ochre",
+    "sage"
+  ],
+  "sourceSummary": "Specify a dashboard from the questions it must answer, before anyone builds it — the artifact that prevents a chart-salad dashboard nobody uses.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/da/dashboard-spec/manifest.json

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

package/data/craftbook-templates/da/data-dictionary/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": "Document a dataset's schema as a clear, complete data dictionary so others can use it without guessing.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/da/data-dictionary/manifest.json

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