@bendyline/gilde 0.1.50 → 0.1.52

package/data/craftbook-templates/ju/juice-pass/versions/1.0.3/craftbook.json

@@ -0,0 +1,228 @@
+{
+  "id": "juice-pass",
+  "name": "Juice Pass",
+  "description": "Make the game feel alive without breaking it: feedback on every player action — hit-flash, screenshake, sound hooks, particles, score pops — added with restraint and verified playable after every change. Locks the juice checklist FIRST — every player action gets visible feedback, effects stay tasteful, nothing regresses — then edits the game in place, re-checking that it still runs and still ends. Use for 'the game feels dead', game feel passes, adding screenshake and particles, polishing an arcade game, and making hits feel like hits.\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. Write the juice checklist (spellenmaker) — every player action listed with the feedback it deserves → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Add the juice (developer) — edit the game in place, one effect at a time, never breaking it → gated on `index.html` (html-game)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "give the game some juice",
+    "the game feels dead",
+    "add screenshake and particles",
+    "game feel pass",
+    "make the hits feel better"
+  ],
+  "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": "Write the juice checklist",
+      "description": "every player action listed with the feedback it deserves",
+      "prompt": "Read the game before touching it. Step 1: open index.html from the workspace and trace the play loop — every player action (move, shoot, hit, get hit, pick up, score, die, restart) and what feedback each currently gives; a working game with silent, flashless actions is exactly what this pass fixes. Step 2: write the juice checklist — for each action, the visible feedback it will get (flash, shake, particle burst, score pop, easing) and the sound hook where one fits. Step 3: lock the restraint rules — effects are short and purposeful, no strobing or seizure bait, the game's readability never drops, and nothing regresses: the game must still start, play, end, and restart exactly as before. Step 4: write an acceptance-criteria checklist ('every listed action has visible feedback', 'effects restrained and readable', 'the script still parses and the loop still runs', 'game over and restart still work'). Call write_task_note with the action count + 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": "spellenmaker",
+      "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": "implement",
+      "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": "implement",
+      "name": "Add the juice",
+      "description": "edit the game in place, one effect at a time, never breaking it",
+      "prompt": "Work through the checklist by editing index.html in place. Step 1: add the effects one action at a time — hit-flash on damage, a brief screenshake on impacts, particles where things break or land, a score pop when points arrive, sound hooks through the page's own audio where the checklist calls for them. Step 2: after each addition, re-read the script for errors — a juicy game that no longer runs is a failed pass, and the gate will send it back. Step 3: keep the restraint rules — short effects, no strobes, the player can always read the field. Step 4: play the loop end to end in your head against the code: start, action feedback, game over, restart — confirm nothing regressed. Call write_task_note with the effects added per action.",
+      "suggestedRole": "developer",
+      "advanceWhen": {
+        "file": "index.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "index.html",
+            "bytes": 6000
+          },
+          {
+            "kind": "htmlLint",
+            "file": "index.html"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlGame",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html"
+            }
+          },
+          {
+            "name": "checkJsParses",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html"
+            }
+          }
+        ],
+        "onReject": "implement",
+        "maxAttempts": 4
+      },
+      "next": "evaluate",
+      "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": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Open index.html beside {{workPath}}/scope.md and run the feel pass: walk every action on the checklist and confirm its feedback is actually wired in the code — a checklist row with no matching effect is a miss; check the restraint rules — effect durations short, nothing strobing, the field still readable; and verify nothing regressed — the script parses, the loop runs, game over still triggers, restart still resets cleanly including the score. Write PASS/FAIL per checklist row; on any failure, name the action or the regression and loop back to implement.\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: \"implement\" })` 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": "index.html"
+        }
+      ],
+      "next": "implement",
+      "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": "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/ju/juice-pass/versions/1.0.3/test.json

@@ -0,0 +1,116 @@
+{
+  "schemaVersion": 1,
+  "title": "Juice Pass — feedback on every action, nothing broken",
+  "objective": "Measure whether the juice-pass craftbook adds action feedback (flash, shake, particles, sound hooks) to a working but feedback-free canvas game while keeping it fully playable — the script still parses, the loop still runs, game over and restart still work.",
+  "tags": [
+    "html-game"
+  ],
+  "prompt": "the game works but feels kinda dead — can you give it some juice? screenshake, hit feedback, that sort of thign",
+  "setup": {
+    "projectName": "Meteor Lane Arcade",
+    "about": "Web arcade project. The game is workspace/index.html — a working canvas dodger with steering, score, game over, and restart, and no feedback effects at all. The juice pass edits it in place.",
+    "missionObjectives": "Every player action should get visible feedback, added with restraint — and the game must stay playable after every change. No live services, no real credentials.",
+    "files": [
+      {
+        "path": "index.html",
+        "content": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n<meta charset=\"utf-8\">\n<title>Meteor Lane</title>\n<style>\n  body { margin: 0; background: #0b0e1a; color: #dfe6ff; font-family: monospace;\n         display: flex; flex-direction: column; align-items: center; }\n  h1 { font-size: 18px; margin: 12px 0 4px; }\n  canvas { border: 1px solid #2a3355; background: #101528; }\n  p { font-size: 12px; color: #8a93b8; }\n</style>\n</head>\n<body>\n<h1>Meteor Lane</h1>\n<canvas id=\"game\" width=\"480\" height=\"600\"></canvas>\n<p>Arrow keys to steer. R to restart.</p>\n<script>\nvar canvas = document.getElementById('game');\nvar ctx = canvas.getContext('2d');\nvar W = canvas.width, H = canvas.height;\n\nvar ship, meteors, score, over, spawnTimer, keys = {};\n\nfunction reset() {\n  ship = { x: W / 2, y: H - 48, w: 26, h: 30, speed: 4.2 };\n  meteors = [];\n  score = 0;\n  over = false;\n  spawnTimer = 0;\n}\n\ndocument.addEventListener('keydown', function (e) {\n  keys[e.key] = true;\n  if (over && (e.key === 'r' || e.key === 'R')) reset();\n});\ndocument.addEventListener('keyup', function (e) { keys[e.key] = false; });\n\nfunction spawnMeteor() {\n  var r = 10 + Math.random() * 16;\n  meteors.push({ x: r + Math.random() * (W - 2 * r), y: -r, r: r, vy: 1.6 + Math.random() * 2.2 });\n}\n\nfunction update() {\n  if (over) return;\n  if (keys.ArrowLeft) ship.x -= ship.speed;\n  if (keys.ArrowRight) ship.x += ship.speed;\n  ship.x = Math.max(ship.w / 2, Math.min(W - ship.w / 2, ship.x));\n\n  spawnTimer -= 1;\n  if (spawnTimer <= 0) {\n    spawnMeteor();\n    spawnTimer = Math.max(18, 46 - Math.floor(score / 8));\n  }\n\n  for (var i = meteors.length - 1; i >= 0; i--) {\n    var m = meteors[i];\n    m.y += m.vy;\n    if (m.y - m.r > H) {\n      meteors.splice(i, 1);\n      score += 1;\n      continue;\n    }\n    var dx = Math.abs(m.x - ship.x), dy = Math.abs(m.y - ship.y);\n    if (dx < m.r + ship.w / 2 - 4 && dy < m.r + ship.h / 2 - 4) {\n      over = true;\n    }\n  }\n}\n\nfunction drawShip() {\n  ctx.fillStyle = '#9fd0ff';\n  ctx.beginPath();\n  ctx.moveTo(ship.x, ship.y - ship.h / 2);\n  ctx.lineTo(ship.x - ship.w / 2, ship.y + ship.h / 2);\n  ctx.lineTo(ship.x + ship.w / 2, ship.y + ship.h / 2);\n  ctx.closePath();\n  ctx.fill();\n}\n\nfunction draw() {\n  ctx.clearRect(0, 0, W, H);\n  drawShip();\n  ctx.fillStyle = '#b98a5e';\n  for (var i = 0; i < meteors.length; i++) {\n    var m = meteors[i];\n    ctx.beginPath();\n    ctx.arc(m.x, m.y, m.r, 0, Math.PI * 2);\n    ctx.fill();\n  }\n  ctx.fillStyle = '#dfe6ff';\n  ctx.font = '16px monospace';\n  ctx.fillText('Score: ' + score, 12, 24);\n  if (over) {\n    ctx.font = '28px monospace';\n    ctx.fillText('GAME OVER', W / 2 - 76, H / 2 - 10);\n    ctx.font = '14px monospace';\n    ctx.fillText('Press R to restart', W / 2 - 72, H / 2 + 16);\n  }\n}\n\nfunction loop() {\n  update();\n  draw();\n  requestAnimationFrame(loop);\n}\n\nreset();\nloop();\n</script>\n</body>\n</html>\n"
+      }
+    ],
+    "worker": {
+      "name": "Ties",
+      "role": "Game developer"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "index.html is still a working game and now carries restrained juice — flash, shake, particles, sound hooks — on player actions.",
+    "deliverables": [
+      {
+        "path": "index.html",
+        "kind": "html-game",
+        "minBytes": 1200,
+        "checks": [
+          {
+            "kind": "sniff",
+            "file": "index.html",
+            "sniff": "html-game"
+          },
+          {
+            "kind": "jsParses",
+            "file": "index.html"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "shake",
+            "flags": "i",
+            "label": "screenshake implementation present"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "particle|spark|burst|debris|explos",
+            "flags": "i",
+            "label": "particle system present"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "flash|pop|tint|blink|pulse|glow|fade|audio|sound",
+            "flags": "i",
+            "label": "hit/score feedback markers present"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "GAME OVER|game\\s*over",
+            "flags": "i",
+            "label": "the game still ends"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "restart|press r",
+            "flags": "i",
+            "label": "the game still restarts"
+          },
+          {
+            "kind": "judge",
+            "file": "index.html",
+            "rubric": "Player actions (dodging, scoring, getting hit, game over) produce visible feedback, and the effects are restrained — short, readable, no strobing or seizure bait; the original mechanics (steering, spawning, score, game over, restart) are intact.",
+            "label": "game feel with restraint"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "index.html",
+      "kind": "html"
+    },
+    "axes": [
+      {
+        "name": "game feel",
+        "description": "Hits flash, impacts shake, scores pop — actions feel like they land instead of silently mutating state."
+      },
+      {
+        "name": "restraint",
+        "description": "Effects are short and purposeful; the field stays readable and nothing strobes."
+      },
+      {
+        "name": "robustness",
+        "description": "The game still starts, plays, ends, and restarts exactly as before — no regression rode in with the juice."
+      },
+      {
+        "name": "performance",
+        "description": "Effects are lightweight — no unbounded particle arrays or leaked timers dragging the frame rate."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "action feedback",
+    "no regressions",
+    "restrained effects"
+  ]
+}

package/data/craftbook-templates/kn/knowledge-base-article/versions/1.0.2/test.json

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

package/data/craftbook-templates/kn/knowledge-base-article/versions/1.0.3/craftbook.json

@@ -0,0 +1,275 @@
+{
+  "id": "knowledge-base-article",
+  "name": "Knowledge Base Article",
+  "description": "Write a support knowledge-base article that lets a user solve their problem without contacting support: it first scopes the exact user problem, the search terms they would use, prerequisites, and the success outcome, then writes a task-oriented article with a clear title, a short overview, numbered steps with expected results, screenshots/placeholders where needed, and a troubleshooting section, then a review pass verifies accuracy and self-service completeness. Covers help center article, support documentation, how-to article, KB article, self-service docs, and product help. Scoping the precise problem and search terms before writing is the point: a small model that pins the one job-to-be-done writes a findable, followable article instead of a vague overview that leaves the user still stuck.\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. Article scope (planner) — lock the problem, search terms, prerequisites, and success outcome → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Write the article (copywriter) — write the task-oriented, self-service article → gated on `kb-article.md` (markdown-doc)\n3. Accuracy & completeness review (reviewer) — verify the article is accurate and lets a user self-serve → gated on `kb-article.md` (markdown-doc)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "write a knowledge base article",
+    "help center article",
+    "support how-to",
+    "kb article",
+    "self-service docs"
+  ],
+  "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": "Article scope",
+      "description": "lock the problem, search terms, prerequisites, and success outcome",
+      "prompt": "1) State the exact user PROBLEM the article solves, phrased as the user experiences it ('I can't log in after changing my email'). 2) List the search terms/keywords a stuck user would type, so the title and intro can match them. 3) List prerequisites (account type, permissions, plan, things they need before starting). 4) Define the SUCCESS outcome — how the user knows it worked. 5) Identify where a screenshot or example would prevent confusion. 6) Note common failure points for the troubleshooting section. Write an acceptance-criteria checklist (e.g. 'title matches likely search terms'; 'prerequisites stated up front'; 'numbered steps with one action each and expected results'; 'a troubleshooting section covers common failures'; 'ends with how to confirm success'; 'a user could self-serve without contacting support'). Use write_task_note for the scope + checklist, and write the same to the produces path. No article prose yet.\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": "planner",
+      "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": "write",
+      "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": "write",
+      "name": "Write the article",
+      "description": "write the task-oriented, self-service article",
+      "prompt": "Write the KB article from the scope. 1) Title: action- and search-oriented, matching the user's likely query. 2) Short overview (1-2 sentences): what this article helps them do and who it is for. 3) Prerequisites section. 4) Numbered step-by-step instructions: one action per step, in imperative voice, with the expected result after key steps and screenshot placeholders ('![screenshot: settings page](...)') where the scope flagged them. 5) A 'How to confirm it worked' line tied to the success outcome. 6) A 'Troubleshooting' section addressing the common failure points as a short Q&A. 7) Optional 'Related articles' links. Use scannable H2/H3 headings and a plain, reassuring support voice. Output GitHub-flavored markdown. Save to the produces path and note which checklist items pass.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "kb-article.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "kb-article.md",
+            "bytes": 500
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkContains",
+            "scope": "standard",
+            "inputs": {
+              "file": "kb-article.md",
+              "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+              "flags": "i"
+            }
+          }
+        ],
+        "onReject": "write",
+        "maxAttempts": 3
+      },
+      "next": "review",
+      "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"
+      }
+    },
+    {
+      "id": "review",
+      "name": "Accuracy & completeness review",
+      "description": "verify the article is accurate and lets a user self-serve",
+      "prompt": "Review and edit the article in place against the checklist. 1) Walk the steps as if you were the stuck user: are they complete, in order, and each a single clear action? Fix gaps and ambiguity. 2) Verify technical accuracy of every instruction and UI reference; flag anything you cannot confirm. 3) Confirm prerequisites are up front and the success check is present. 4) Confirm the troubleshooting section covers the likely failures. 5) Confirm the title matches search intent. The bar: could a real user solve this without contacting support? If not, fix what blocks them. Save the polished article to the produces path and note any criteria still unmet.",
+      "suggestedRole": "reviewer",
+      "advanceWhen": {
+        "file": "kb-article.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "kb-article.md",
+            "bytes": 500
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkContains",
+            "scope": "standard",
+            "inputs": {
+              "file": "kb-article.md",
+              "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+              "flags": "i"
+            }
+          }
+        ],
+        "onReject": "review",
+        "maxAttempts": 4
+      },
+      "next": "evaluate",
+      "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"
+      }
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Read kb-article.md against the scope and walk it as a stuck user. Check EACH criterion and write PASS/FAIL: (a) title matches the likely search terms; (b) prerequisites stated up front; (c) numbered steps, one action each, with expected results; (d) a troubleshooting section covers common failures; (e) a clear 'how to confirm success' step; (f) a real user could self-serve end to end without contacting support. An article that is a vague overview or leaves a step missing FAILS — loop back to write.\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: \"write\" })` 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": "kb-article.md"
+        }
+      ],
+      "next": "write",
+      "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": "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"
+}