@bendyline/gilde 0.1.50 → 0.1.52

package/data/craftbook-templates/co/codemod-sweep/versions/1.0.1/test.json

@@ -0,0 +1,252 @@
+{
+  "schemaVersion": 1,
+  "title": "Repo-wide rename sweep with reconciled counts",
+  "objective": "The craftbook drives a complete mechanical rename of fetchUserData to loadUser across a small repo whose sites include a re-export and a template-literal log string, with a changelog legitimately excluded as history - verified mechanically by a residual scan, behavior probes on every site, and a green suite.",
+  "tags": [
+    "code",
+    "codemod",
+    "rename",
+    "tactical-fleet"
+  ],
+  "prompt": "Use the Codemod Sweep craftbook for this: rename fetchUserData to loadUser across the whole repo - the export, the re-export, every import and call site, and log strings that mention the old name. CHANGELOG.md is history and keeps the old name. The brief is in source/rename-brief.md. No behavior change.",
+  "setup": {
+    "projectName": "Profile Cards",
+    "about": "A tiny profile-rendering module with an in-memory user store. Tests run with `npm run test` (node --test).",
+    "files": [
+      {
+        "path": "package.json",
+        "content": "{\n  \"name\": \"profile-cards\",\n  \"private\": true,\n  \"version\": \"1.0.0\",\n  \"type\": \"module\",\n  \"scripts\": {\n    \"test\": \"node --test\"\n  }\n}\n"
+      },
+      {
+        "path": "src/api.js",
+        "content": "const USERS = new Map([\n  [1, { id: 1, name: 'Ada' }],\n  [2, { id: 2, name: 'Grace' }],\n]);\n\nexport function fetchUserData(id) {\n  const user = USERS.get(id);\n  if (!user) throw new Error(`no user ${id}`);\n  return { ...user };\n}\n"
+      },
+      {
+        "path": "src/index.js",
+        "content": "export { fetchUserData } from './api.js';\n"
+      },
+      {
+        "path": "src/log.js",
+        "content": "export const lines = [];\n\nexport function logLine(line) {\n  lines.push(line);\n}\n"
+      },
+      {
+        "path": "src/profile.js",
+        "content": "import { fetchUserData } from './api.js';\nimport { logLine } from './log.js';\n\nexport function profileSummary(id) {\n  const user = fetchUserData(id);\n  logLine(`fetchUserData resolved user ${user.id}`);\n  return `${user.name} (#${user.id})`;\n}\n"
+      },
+      {
+        "path": "tests/profile.test.mjs",
+        "content": "import assert from 'node:assert/strict';\nimport { test } from 'node:test';\nimport { fetchUserData } from '../src/index.js';\nimport { lines } from '../src/log.js';\nimport { profileSummary } from '../src/profile.js';\n\ntest('profileSummary renders the user line', () => {\n  assert.equal(profileSummary(1), 'Ada (#1)');\n});\n\ntest('profileSummary logs the lookup', () => {\n  profileSummary(2);\n  assert.ok(lines.some((line) => line.includes('resolved user 2')));\n});\n\ntest('the re-export serves the same function', () => {\n  assert.equal(fetchUserData(1).name, 'Ada');\n});\n"
+      },
+      {
+        "path": "CHANGELOG.md",
+        "content": "# Changelog\n\n## 1.2.0\n\n- fetchUserData now copies the record before returning it, so callers can\n  mutate the result safely.\n\n## 1.0.0\n\n- Initial release with fetchUserData and the profile summary renderer.\n"
+      },
+      {
+        "path": "source/rename-brief.md",
+        "content": "# Rename brief: fetchUserData -> loadUser\n\nThe function does not fetch anything remote any more, so the name misleads.\nRename `fetchUserData` to `loadUser` everywhere it appears: the export, the\nre-export, every import and call site, and log strings that mention the old\nname - the log lines should follow the rename too.\n\nDo not rewrite history: `CHANGELOG.md` keeps the old name, because it records\nwhat past releases were actually called.\n\nNo behavior change: same records returned, same summary strings, same number\nof log lines.\n"
+      },
+      {
+        "path": "tests/verify-sweep.mjs",
+        "content": "import assert from 'node:assert/strict';\nimport { execFileSync } from 'node:child_process';\nimport { readFileSync, readdirSync, statSync } from 'node:fs';\nimport { join, relative } from 'node:path';\nimport { pathToFileURL } from 'node:url';\n\nconst root = process.cwd();\n\n// 1) Residual scan: zero mentions of the old name outside the excluded\n//    history (CHANGELOG.md), the briefing material (source/), and\n//    harness-owned files.\nconst SKIP_FILES = new Set(['CHANGELOG.md', 'task-notes.md', 'task-graph.md', 'tests/verify-sweep.mjs']);\nconst SKIP_DIRS = new Set(['node_modules', 'source']);\nconst hits = [];\nfunction scan(dir) {\n  for (const entry of readdirSync(dir)) {\n    if (entry.startsWith('.')) continue;\n    const full = join(dir, entry);\n    const rel = relative(root, full).split('\\\\').join('/');\n    const stat = statSync(full);\n    if (stat.isDirectory()) {\n      if (SKIP_DIRS.has(entry)) continue;\n      scan(full);\n      continue;\n    }\n    if (SKIP_FILES.has(rel)) continue;\n    if (!/\\.(js|mjs|cjs|json|md|txt)$/.test(entry)) continue;\n    if (/\\bfetchUserData\\b/.test(readFileSync(full, 'utf8'))) hits.push(rel);\n  }\n}\nscan(root);\nassert.deepEqual(hits, [], `the old name survives outside the exclusions in: ${hits.join(', ')}`);\nconsole.log('CODEMOD_ORACLE residual scan clean');\n\n// 2) Every site behaves under the new name, including the tricky ones.\nconst api = await import(pathToFileURL(join(root, 'src/api.js')).href);\nassert.equal(typeof api.loadUser, 'function', 'src/api.js must export loadUser');\nassert.equal(api.fetchUserData, undefined, 'src/api.js still exports the old name');\nconst index = await import(pathToFileURL(join(root, 'src/index.js')).href);\nassert.equal(typeof index.loadUser, 'function', 'src/index.js must re-export loadUser');\nassert.equal(index.fetchUserData, undefined, 'src/index.js still re-exports the old name');\nassert.equal(index.loadUser(1).name, 'Ada', 'the re-exported loadUser must return the same records');\nconst { profileSummary } = await import(pathToFileURL(join(root, 'src/profile.js')).href);\nconst { lines } = await import(pathToFileURL(join(root, 'src/log.js')).href);\nassert.equal(profileSummary(1), 'Ada (#1)', 'profileSummary behavior must be unchanged');\nassert.ok(\n  lines.some((line) => line.includes('loadUser resolved user 1')),\n  'the log string must follow the rename',\n);\nassert.ok(\n  !lines.some((line) => line.includes('fetchUserData')),\n  'a log string still mentions the old name',\n);\nconsole.log('CODEMOD_ORACLE behavior ok');\n\n// 3) History kept: the excluded changelog still records the old name.\nassert.ok(\n  /\\bfetchUserData\\b/.test(readFileSync(join(root, 'CHANGELOG.md'), 'utf8')),\n  'CHANGELOG.md must keep the historical name',\n);\nconsole.log('CODEMOD_ORACLE history kept');\n\n// 4) The suite is green after the sweep, and the seeded test file survives.\nreadFileSync(join(root, 'tests/profile.test.mjs'));\nfunction runSuite(cwd) {\n  try {\n    execFileSync(process.execPath, ['--test'], { cwd, stdio: 'pipe', timeout: 30000 });\n    return 0;\n  } catch (err) {\n    return typeof err.status === 'number' ? err.status : 1;\n  }\n}\nassert.equal(runSuite(root), 0, 'the suite must be green after the sweep');\nconsole.log('CODEMOD_ORACLE suite green');\nconsole.log('CODEMOD_ORACLE done');\n",
+        "surface": "harness"
+      }
+    ],
+    "craftbookParams": {
+      "scope": "Rename fetchUserData to loadUser everywhere, including log strings that mention it; CHANGELOG.md keeps the historical name; no behavior change. See source/rename-brief.md."
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "Zero references to the old name remain outside the excluded changelog and brief, every site (including the re-export and the log string) behaves under the new name, the suite is green, and every fleet artifact exists with counts that reconcile.",
+    "deliverables": [
+      {
+        "path": "{{task.dir}}/sites.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 500,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "{{task.dir}}/sites.md",
+            "pattern": "^##\\s+Pattern[\\s\\S]*^##\\s+Sites found[\\s\\S]*^##\\s+Exclusions",
+            "flags": "im",
+            "label": "sites sections in order"
+          },
+          {
+            "kind": "contains",
+            "file": "{{task.dir}}/sites.md",
+            "pattern": "src/index\\.js",
+            "label": "found the re-export site"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "{{task.dir}}/sites.md",
+            "minCitations": 2,
+            "artifact": true
+          }
+        ]
+      },
+      {
+        "path": "{{task.dir}}/change-notes.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 500,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "{{task.dir}}/change-notes.md",
+            "pattern": "^##\\s+Sites changed[\\s\\S]*^##\\s+Files touched[\\s\\S]*^##\\s+Invariants held",
+            "flags": "im",
+            "label": "change-notes sections in order"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "{{task.dir}}/change-notes.md",
+            "minCitations": 2,
+            "artifact": true
+          }
+        ]
+      },
+      {
+        "path": "{{task.dir}}/verification.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 450,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "{{task.dir}}/verification.md",
+            "pattern": "^##\\s+Residual scan[\\s\\S]*^##\\s+Counts reconciled[\\s\\S]*^##\\s+Suite[\\s\\S]*^##\\s+Result",
+            "flags": "im",
+            "label": "verification sections in order"
+          }
+        ]
+      },
+      {
+        "path": "{{task.dir}}/review.md",
+        "kind": "markdown-report",
+        "artifact": true,
+        "minBytes": 400,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "{{task.dir}}/review.md",
+            "pattern": "Verdict:\\s*(?:PASS|REVISE)",
+            "flags": "i",
+            "label": "explicit reviewer verdict"
+          }
+        ]
+      }
+    ],
+    "checks": [
+      {
+        "kind": "notContains",
+        "file": "src/api.js",
+        "pattern": "\\bfetchUserData\\b",
+        "label": "the old name is gone from the definition site"
+      },
+      {
+        "kind": "notContains",
+        "file": "src/index.js",
+        "pattern": "\\bfetchUserData\\b",
+        "label": "the old name is gone from the re-export site"
+      },
+      {
+        "kind": "notContains",
+        "file": "src/profile.js",
+        "pattern": "\\bfetchUserData\\b",
+        "label": "the old name is gone from the call site and its log string"
+      },
+      {
+        "kind": "notContains",
+        "file": "tests/profile.test.mjs",
+        "pattern": "\\bfetchUserData\\b",
+        "label": "the old name is gone from the test call sites"
+      },
+      {
+        "kind": "contains",
+        "file": "CHANGELOG.md",
+        "pattern": "\\bfetchUserData\\b",
+        "label": "the excluded changelog keeps the historical name"
+      },
+      {
+        "kind": "sourceParses",
+        "file": "src/api.js"
+      },
+      {
+        "kind": "sourceParses",
+        "file": "src/profile.js"
+      },
+      {
+        "kind": "nodeRuns",
+        "file": "tests/profile.test.mjs"
+      },
+      {
+        "kind": "nodeScriptPasses",
+        "script": "tests/verify-sweep.mjs",
+        "timeoutMs": 60000,
+        "requiredOutput": [
+          {
+            "pattern": "CODEMOD_ORACLE residual scan clean",
+            "label": "zero un-excluded sites remain"
+          },
+          {
+            "pattern": "CODEMOD_ORACLE behavior ok",
+            "label": "every site behaves under the new name"
+          },
+          {
+            "pattern": "CODEMOD_ORACLE suite green",
+            "label": "suite green after the sweep"
+          }
+        ]
+      }
+    ],
+    "taskNotes": {
+      "minBytes": 120,
+      "checks": [
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "\\bDONE\\b[\\s\\S]*(npm\\s+run\\s+test|node\\s+--test)",
+          "flags": "i",
+          "label": "DONE note names the real test command"
+        }
+      ]
+    },
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    },
+    "unchangedFixtures": [
+      "CHANGELOG.md",
+      "source/rename-brief.md",
+      "package.json",
+      "src/log.js"
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "{{task.dir}}/verification.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "Enumeration completeness",
+        "description": "Every site was found by real searches before any edit - the definition, the re-export, the imports and call sites, and the log string - with the changelog excluded for a stated reason rather than missed."
+      },
+      {
+        "name": "Invariant discipline",
+        "description": "The change stayed mechanical: nothing changed beyond the declared rename, the excluded files are untouched, and behavior is identical."
+      },
+      {
+        "name": "Reconciled verification",
+        "description": "The residual re-scan is quoted with its result, the found/changed/excluded counts add up exactly, and the suite run backing the green claim is real."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "sweep completeness",
+    "count reconciliation",
+    "behavior invariants"
+  ]
+}

package/data/craftbook-templates/co/cohort-analysis/versions/1.0.3/craftbook.json

@@ -0,0 +1,277 @@
+{
+  "id": "cohort-analysis",
+  "name": "Cohort / Retention Analysis",
+  "description": "Analyze retention or behavior by cohort to reveal whether the product is getting stickier over time. Defines the cohort key, the activity event, and the retention window FIRST (so 'retained' has one unambiguous meaning), then builds the cohort/retention table and computes retention curves and trends as a data-analyst, then writes a readout on what the cohorts reveal. Use this for retention analysis, cohort tables, churn/stickiness analysis, a retention curve, or 'are newer users retaining better than older ones'.\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. Scope the cohorts (data-analyst) — lock the cohort key, activity event, and retention window → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Build the cohort table (data-analyst) — compute the retention matrix and curves → gated on `data/cohorts.json` (json)\n3. Write the readout (copywriter) — explain what the cohorts reveal about retention → gated on artifact `{{workPath}}/readout.md` (markdown-report)\n\nData output discipline:\n\n- `data/cohorts.json` must be valid JSON only: no Markdown fences, comments, formulas, or ratio strings.\n- Use stable keys such as `signup_week`, `total_users`, and `retention`.\n- Store retention rates as numeric decimals rounded consistently, for example `0.67`, not `\"2/3\"` or `\"66.7%\"`.\n- Distinguish observed zero retention from incomplete future periods: use `0` when the period is observed and no cohort users were active, and `null` when the period is outside the observed window.\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "cohort analysis",
+    "retention curve",
+    "are newer users retaining better",
+    "churn analysis",
+    "retention table"
+  ],
+  "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": "Scope the cohorts",
+      "description": "lock the cohort key, activity event, and retention window",
+      "prompt": "Define retention unambiguously before computing anything. Step 1: choose the cohort key — usually signup/first-activity period (weekly or monthly), and state the period. Step 2: define the ACTIVITY that counts as 'retained' (logged in, made a purchase, used core feature) and the unit (a user, an account). Step 3: define the retention window and periods (W0..W8, or M0..M6) and whether it's classic (active in period N) or rolling/unbounded. Step 4: state filters (exclude test accounts, a minimum-tenure cutoff so incomplete recent cohorts are flagged). Step 5: write an acceptance-criteria checklist ('cohort key and activity are precisely defined', 'retention table has cohorts as rows and periods as columns', 'period 0 is 100% by construction', 'incomplete recent cohorts are flagged', 'a trend across cohorts is reported'). Call write_task_note and write the definitions + checklist to {{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": "data-analyst",
+      "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": "analyze",
+      "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": "analyze",
+      "name": "Build the cohort table",
+      "description": "compute the retention matrix and curves",
+      "prompt": "Compute the cohort retention matrix from the defined rules. Step 1: assign each user/account to its cohort by the cohort key. Step 2: for each cohort and each retention period, compute the share of the cohort that performed the activity in that period; period 0 is 100% by construction. Step 3: build the triangular retention matrix (cohorts x periods), the cohort sizes, and the average retention curve across cohorts. Step 4: compute the trend — are later cohorts retaining better at the same period age than earlier ones? Step 5: flag cohorts too recent to have full data. Emit data/cohorts.json (matrix, sizes, average curve, trend) and call write_task_note with the headline retention numbers and the trend.",
+      "suggestedRole": "data-analyst",
+      "advanceWhen": {
+        "file": "data/cohorts.json",
+        "minBytes": 1,
+        "sniff": "json-valid"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "data/cohorts.json",
+            "bytes": 2
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkJsonValid",
+            "scope": "standard",
+            "inputs": {
+              "file": "data/cohorts.json"
+            }
+          }
+        ],
+        "onReject": "analyze",
+        "maxAttempts": 3
+      },
+      "next": "write",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "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": "write",
+      "name": "Write the readout",
+      "description": "explain what the cohorts reveal about retention",
+      "prompt": "Write the retention readout from the computed matrix — no invented figures. Step 1: lead with the headline: the typical W1/M1 retention and where the curve flattens (the 'sticky' floor). Step 2: present the retention table (cohorts as rows, periods as columns) and read it for the reader. Step 3: state the cross-cohort trend in plain language ('M1 retention improved from 22% to 31% over the last 6 cohorts'). Step 4: call out the best and worst cohorts and any inflection. Step 5: caveat the incomplete recent cohorts and suggest one next action. Write the readout to {{workPath}}/readout.md and call write_task_note with the path. On a loop-back, fix only the named gaps.\n\nThe deliverable `{{workPath}}/readout.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}}/readout.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/readout.md",
+            "bytes": 1500,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/readout.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i",
+            "label": "at least one markdown heading",
+            "artifact": true
+          }
+        ],
+        "onReject": "write",
+        "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": "Read {{workPath}}/readout.md and cross-check against {{workPath}}/scope.md and data/cohorts.json. Verify: the cohort key and activity are precisely defined and used; the retention table has cohorts as rows and periods as columns with period 0 = 100%; incomplete recent cohorts are flagged; and a cross-cohort trend is reported with numbers. Re-check the headline W1/M1 retention and the trend against the cohort data. Confirm no cohort's retention exceeds 100% or rises impossibly. Write PASS/FAIL per criterion; any FAIL loops back to write.\n\nThe deliverable lives in the project's artifacts drawer — open `{{workPath}}/readout.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: \"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": "{{workPath}}/readout.md",
+          "artifact": true
+        }
+      ],
+      "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": "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"
+}