@bendyline/gilde 0.1.50 → 0.1.52

package/data/craftbook-templates/th/thumbnail-generator/versions/1.0.3/test.json

@@ -0,0 +1,103 @@
+{
+  "schemaVersion": 1,
+  "title": "Thumbnail Generator smoke eval",
+  "objective": "Self-contained smoke eval for the Thumbnail Generator craftbook using the media generic harness.",
+  "tags": [
+    "media"
+  ],
+  "prompt": "Our media files are all listd in source/media-index.csv. Can you put together the production plan for them as media-plan.json?",
+  "setup": {
+    "projectName": "Thumbnail Generator Eval",
+    "about": "Self-contained eval project for thumbnail-generator. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/media-plan.json.",
+    "missionObjectives": "Use the Thumbnail Generator craftbook/template, read the seeded local fixtures, and write media-plan.json without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Thumbnail Generator Eval Brief\n\nClient: Boreal Desk, a home-office accessories company.\nAudience: operations leads who need an artifact they can use this week.\n\nFixed source facts for grounding:\n- The returns desk pilot covered 18 SKUs.\n- Median first response improved from 18 hours to 6 hours.\n- Preventable refund leakage fell from 14.2% to 8.9%.\n- The top unresolved complaint is status silence after photo submission.\n- Required next actions are automated status emails, barcode-exception training, and a weekly Finance exception export.\n\nUse these facts when the task asks for prose, analysis, copy, UI content, or test data. Do not use live web services, real credentials, or current outside data.\n\nCraftbook under test: thumbnail-generator - Thumbnail Generator.\n"
+      },
+      {
+        "path": "source/media-index.csv",
+        "content": "filename,type,duration_or_size,notes\npilot-interview.wav,audio,00:02:15,mentions response time and status silence\nreturns-desk.png,image,1600x900,shows intake form and photo evidence step\nlaunch-clip.mp4,video,00:01:05,shows barcode exception handling\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Producer"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "media-plan.json is a valid JSON media-production manifest grounded in seeded fixture metadata.",
+    "deliverables": [
+      {
+        "path": "media-plan.json",
+        "kind": "json",
+        "minBytes": 700,
+        "checks": [
+          {
+            "kind": "sniff",
+            "file": "media-plan.json",
+            "sniff": "json-valid"
+          },
+          {
+            "kind": "contains",
+            "file": "media-plan.json",
+            "pattern": "pilot-interview\\.wav|returns-desk\\.png|launch-clip\\.mp4",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "media-plan.json",
+            "pattern": "outputs|assets|steps|cues|verification",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "media-plan.json",
+            "pattern": "accessibility|alt|caption|transcript|metadata",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "media-plan.json",
+      "kind": "json"
+    },
+    "axes": [
+      {
+        "name": "completeness",
+        "description": "The manifest covers sources, outputs, and processing steps end to end."
+      },
+      {
+        "name": "grounding",
+        "description": "Only seeded media fixtures are referenced, with faithful metadata."
+      },
+      {
+        "name": "accessibility",
+        "description": "Alt text, captions, or transcripts are planned wherever the class requires."
+      },
+      {
+        "name": "precision",
+        "description": "Timestamps, crops, and cues are specific enough to execute."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "media fixture handling",
+    "structured manifest",
+    "verification metadata"
+  ],
+  "extensions": {
+    "legacySimulators": [
+      {
+        "id": "thumbnail-generator-media-fixtures",
+        "kind": "data-source",
+        "status": "implemented",
+        "description": "Seeded local media index replacing real audio, video, image generation, and external media metadata services."
+      }
+    ]
+  }
+}

package/data/craftbook-templates/ti/tileset-batch/versions/1.0.2/test.json

@@ -31,9 +31,6 @@
     "worker": {
       "name": "Bram",
       "role": "Assetsmid"
-    },
-    "craftbookParams": {
-      "workPath": "tasks/eval"
     }
   },
   "mocks": [],

package/data/craftbook-templates/ti/tileset-batch/versions/1.0.3/craftbook.json

@@ -0,0 +1,321 @@
+{
+  "id": "tileset-batch",
+  "name": "Tileset Batch",
+  "description": "Produce a style-locked batch of tiles and account for every one: named to the convention, sized to spec, generated against the library's style anchor, and appended to the manifest with tags — an asset library a game engine can trust, not a folder of maybes. Locks the tile list and the naming convention FIRST, then generates the batch in the house style, then writes the manifest records and the batch summary. Use for tile batches, 'we need forest tiles', growing a game's asset library, style-consistent tilesets, and keeping the asset manifest honest.\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\nDeliverables marked \"artifact\" land in the project's artifacts drawer (`write_artifact` / `read_artifact`), not the shipped workspace — review output is not product source.\n\nPhases:\n\n1. Lock the batch (assetsmid) — tile list, naming convention, size spec, style anchor → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Generate the tiles (image-generator) — the batch, named to the convention, in the house style → gated on `assets/tiles` (image-set)\n3. Write the manifest records (data-analyst) — one record per new tile, appended, ids unique\n4. Write the batch summary (copywriter) — what was made, how it is named, what the library now holds → gated on artifact `{{workPath}}/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": [
+    "make a batch of tiles",
+    "we need more tiles for the game",
+    "tileset for the platformer",
+    "generate the tile batch",
+    "grow the asset library"
+  ],
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  },
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Lock the batch",
+      "description": "tile list, naming convention, size spec, style anchor",
+      "prompt": "Lock the batch before generating a tile. Step 1: read assets/manifest.json from the workspace — the library's existing records — and the style notes in assets/ (the palette, tile size, outline and shading rules that make the library one family). Step 2: write the tile list from the ask — every tile the batch needs, including the unglamorous edges and corners that make a set usable, at least eight. Step 3: lock the conventions — file names as assets/tiles/tile-<terrain>-<variant>.png, the size spec from the style notes, and the tags each tile will carry. Step 4: write an acceptance-criteria checklist ('every listed tile generated at spec size in the house style', 'every file named to the convention', 'every new tile appended to the manifest with id, file, size, and tags', 'the manifest stays valid JSON and lists only files that exist'). Call write_task_note with the tile list + checklist and write {{workPath}}/scope.md.\n\nThe deliverable `{{workPath}}/scope.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "assetsmid",
+      "advanceWhen": {
+        "file": "{{workPath}}/scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "scope",
+        "maxAttempts": 3
+      },
+      "next": "generate",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "artifact",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      }
+    },
+    {
+      "id": "generate",
+      "name": "Generate the tiles",
+      "description": "the batch, named to the convention, in the house style",
+      "prompt": "Generate the batch into assets/tiles/. Step 1: work the locked tile list one tile at a time through the project's image capabilities — every prompt built from the style anchor (palette, outline, shading) so the batch reads as one hand's work, saved under the locked naming convention. Step 2: keep the set complete — the edge and corner variants from the list matter more to a level builder than another hero tile. Step 3: after generating, re-list assets/tiles/ against the tile list and fill any gap before completing. Call write_task_note with the count generated and the names.",
+      "suggestedRole": "image-generator",
+      "advanceWhen": {
+        "file": "assets/tiles",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "fileCount",
+            "ext": [
+              "png",
+              "jpg",
+              "jpeg",
+              "svg",
+              "webp"
+            ],
+            "min": 3,
+            "dir": "assets/tiles"
+          },
+          {
+            "kind": "fileCount",
+            "ext": [
+              "png"
+            ],
+            "min": 8,
+            "dir": "assets/tiles"
+          }
+        ],
+        "onReject": "generate",
+        "maxAttempts": 3
+      },
+      "next": "manifest",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web"
+        ],
+        "outputMedium": "workspace",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      }
+    },
+    {
+      "id": "manifest",
+      "name": "Write the manifest records",
+      "description": "one record per new tile, appended, ids unique",
+      "prompt": "Account for every tile in assets/manifest.json. Step 1: append one record per new tile to the top-level JSON array, keeping the existing records untouched. Step 2: each record carries exactly these fields: \"id\" (unique, e.g. tile-grass-01), \"file\" (the workspace-relative path, e.g. assets/tiles/tile-grass-01.png), \"size\" (the pixel spec, e.g. 32x32), and \"tags\" (an array like [\"forest\", \"ground\"]) — plus \"seed\" and \"prompt\" where the generation gave you them, so a tile can be re-made in-style later. Step 3: re-read the whole file after writing — it must parse as JSON, ids must stay unique, and every recorded file must exist on disk; a manifest that lists a tile that is not there is worse than no manifest. Call write_task_note with the record count before and after.",
+      "suggestedRole": "data-analyst",
+      "consumes": [
+        {
+          "file": "assets/tiles"
+        }
+      ],
+      "next": "report",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "task-note"
+      }
+    },
+    {
+      "id": "report",
+      "name": "Write the batch summary",
+      "description": "what was made, how it is named, what the library now holds",
+      "prompt": "Write the batch summary at {{workPath}}/report.md. Step 1: the headline — how many tiles this batch added and what terrain they cover, in one plain sentence. Step 2: the batch list — each tile's id, file, and tags, one line each. Step 3: note the conventions used (naming, size, style anchor) so the next batch starts from the same page, and name anything from the ask that was skipped and why. Step 4: close with the library's new total. Keep it under a page. Write {{workPath}}/report.md and call write_task_note with the report path and the new total.\n\nThe deliverable `{{workPath}}/report.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "{{workPath}}/report.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/report.md",
+            "bytes": 600,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i",
+            "label": "at least one markdown heading",
+            "artifact": true
+          }
+        ],
+        "onReject": "report",
+        "maxAttempts": 4
+      },
+      "next": "evaluate",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "artifact",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      }
+    },
+    {
+      "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 assets/manifest.json, the assets/tiles/ listing, {{workPath}}/scope.md, and {{workPath}}/report.md and verify every criterion: every tile on the locked list exists at the convention name — the missing corner variant is the classic failure; every new tile has a manifest record with id, file, size, and tags, ids unique, and every recorded path resolves to a real file — check both directions; the batch reads as one style family against the anchor notes; and the report's counts match the manifest. Write PASS/FAIL per criterion; on any failure, name the tile or record and loop back to generate.\n\nThe deliverable lives in the project's artifacts drawer — open `{{workPath}}/report.md` with `read_artifact`, not `read_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: \"generate\" })` 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",
+      "consumes": [
+        {
+          "file": "{{workPath}}/report.md",
+          "artifact": true
+        }
+      ],
+      "next": "generate",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "task-note"
+      }
+    },
+    {
+      "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,
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "task-note"
+      }
+    }
+  ],
+  "version": "1.0.3",
+  "releasedAt": "2026-09-01T20:00:00Z",
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/ti/tileset-batch/versions/1.0.3/test.json

@@ -0,0 +1,159 @@
+{
+  "schemaVersion": 1,
+  "title": "Tileset Batch — forest tiles, accounted for",
+  "objective": "Measure whether the tileset-batch craftbook produces a style-locked batch of forest tiles named to the library convention and appends an honest manifest record for every one — ids unique, every recorded file real.",
+  "tags": [
+    "data"
+  ],
+  "prompt": "need a batch of forest tiles for the platformer — grass, dirt, water edges, that kind of thing. keep the manifst updated",
+  "setup": {
+    "projectName": "Foxglove Platformer Assets",
+    "about": "Asset foundry project. The library's records live at workspace/assets/manifest.json (a JSON array, one record per asset) and the style anchor at workspace/assets/style.md. Tiles land in workspace/assets/tiles; the batch summary goes to workspace/report.md.",
+    "missionObjectives": "An asset library a game engine can trust: tiles at spec size in the house style, named to the convention, every one recorded in the manifest and no record pointing at a file that is not there. No live services, no real credentials.",
+    "files": [
+      {
+        "path": "assets/style.md",
+        "content": "# Asset library style anchor\n\n- Tile size: 32x32 pixels, no partial tiles.\n- Palette: moss green #4c7a3f, loam brown #6b4a2e, slate gray #5a6472,\n  water blue #3f6d8e, highlight cream #e8dcb8.\n- Look: chunky 2px dark outlines (#22201c), flat interior shading, one\n  highlight edge top-left. No gradients, no anti-aliased edges.\n- Naming: assets/tiles/tile-<terrain>-<variant>.png (e.g. tile-grass-01,\n  tile-water-edge-n).\n- Every shipped asset gets a manifest record: id, file, size, tags —\n  plus seed and prompt when generation provides them.\n"
+      },
+      {
+        "path": "assets/manifest.json",
+        "content": "[\n  {\n    \"id\": \"tile-stone-01\",\n    \"file\": \"assets/tiles/tile-stone-01.png\",\n    \"size\": \"32x32\",\n    \"tags\": [\n      \"stone\",\n      \"ground\"\n    ]\n  },\n  {\n    \"id\": \"tile-stone-02\",\n    \"file\": \"assets/tiles/tile-stone-02.png\",\n    \"size\": \"32x32\",\n    \"tags\": [\n      \"stone\",\n      \"ground\",\n      \"variant\"\n    ]\n  }\n]\n"
+      },
+      {
+        "path": "assets/tiles/tile-stone-01.png",
+        "content": "placeholder tile image: stone ground\n"
+      },
+      {
+        "path": "assets/tiles/tile-stone-02.png",
+        "content": "placeholder tile image: stone ground variant\n"
+      }
+    ],
+    "worker": {
+      "name": "Bram",
+      "role": "Assetsmid"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "assets/tiles holds the forest batch named to the convention; assets/manifest.json accounts for every tile with unique ids and real paths; tasks/eval/report.md summarizes the batch.",
+    "checks": [
+      {
+        "kind": "fileCount",
+        "ext": [
+          "png"
+        ],
+        "min": 8,
+        "dir": "assets/tiles"
+      }
+    ],
+    "deliverables": [
+      {
+        "path": "assets/manifest.json",
+        "kind": "json",
+        "minBytes": 400,
+        "checks": [
+          {
+            "kind": "sniff",
+            "file": "assets/manifest.json",
+            "sniff": "json-valid"
+          },
+          {
+            "kind": "recordSchema",
+            "file": "assets/manifest.json",
+            "fields": [
+              {
+                "name": "id",
+                "type": "nonempty"
+              },
+              {
+                "name": "file",
+                "type": "nonempty"
+              },
+              {
+                "name": "size",
+                "required": false
+              },
+              {
+                "name": "tags",
+                "required": false
+              },
+              {
+                "name": "seed",
+                "required": false
+              },
+              {
+                "name": "prompt",
+                "required": false
+              }
+            ],
+            "minRows": 8,
+            "uniqueBy": "id"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "assets/manifest.json",
+            "pattern": "\"file\"\\s*:\\s*\"([^\"]+)\"",
+            "minCitations": 8,
+            "label": "every recorded file exists on disk"
+          },
+          {
+            "kind": "contains",
+            "file": "assets/manifest.json",
+            "pattern": "grass|dirt|water",
+            "flags": "i",
+            "label": "the asked-for terrain made the batch"
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/report.md",
+        "kind": "markdown-report",
+        "minBytes": 600,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "tile",
+            "flags": "i",
+            "label": "the batch is summarized"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/report.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "style consistency",
+        "description": "The batch reads as one hand's work against the style anchor — palette, outlines, and shading held across every tile."
+      },
+      {
+        "name": "naming discipline",
+        "description": "Every file follows tile-<terrain>-<variant>.png; the unglamorous edge and corner variants are there."
+      },
+      {
+        "name": "coverage",
+        "description": "The batch covers what was asked — grass, dirt, water edges — as a usable set, not eight hero tiles."
+      },
+      {
+        "name": "manifest quality",
+        "description": "Records are complete and honest: unique ids, real paths, useful tags, existing records untouched."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "manifest honesty",
+    "naming convention",
+    "style lock"
+  ]
+}

package/data/craftbook-templates/to/tone-rewrite/versions/1.0.2/test.json

@@ -19,9 +19,6 @@
     "worker": {
       "name": "Jules",
       "role": "Writer"
-    },
-    "craftbookParams": {
-      "workPath": "tasks/eval"
     }
   },
   "mocks": [],