npm - @bendyline/gilde - Versions diffs - 0.1.37 → 0.1.39 - Mend

@bendyline/gilde 0.1.37 → 0.1.39

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (551) hide show

package/data/craftbook-templates/pu/puzzle-pack-layout/versions/1.0.2/test.json ADDED Viewed

@@ -0,0 +1,126 @@
+{
+  "schemaVersion": 1,
+  "title": "Lay Out the Puzzle Pack — shelf to printable booklet",
+  "objective": "Measure whether the puzzle-pack-layout craftbook binds the seeded puzzles/ shelf into one print-ready pack with a cover, a page per puzzle, and the solutions gathered at the back.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "can you put this months three puzzles into one printable pack? solutions at the back, seperate pages",
+  "setup": {
+    "projectName": "Loon Lake Puzzle Almanac",
+    "about": "Puzzle almanac project for the Halloran family. Finished puzzles live on the workspace/puzzles shelf as data plus a rendered page each; packs go under workspace/pack.",
+    "missionObjectives": "The pack must include every chosen shelf puzzle, one per page, with solutions sectioned at the back. Everything is grounded in the shelf files — no live services, no real credentials.",
+    "files": [
+      {
+        "path": "puzzles/loon-lake-crossword.json",
+        "content": "{\n  \"title\": \"Loon Lake Crossword\",\n  \"kind\": \"crossword\",\n  \"size\": { \"rows\": 5, \"cols\": 5 },\n  \"grid\": [\"CANOE\", \"A....\", \"BAIT.\", \"I....\", \"NORA.\"],\n  \"entries\": [\n    { \"number\": 1, \"answer\": \"CANOE\", \"row\": 0, \"col\": 0, \"direction\": \"across\", \"clue\": \"What tipped over in 2019, twice\" },\n    { \"number\": 1, \"answer\": \"CABIN\", \"row\": 0, \"col\": 0, \"direction\": \"down\", \"clue\": \"Where the summer happens\" },\n    { \"number\": 2, \"answer\": \"BAIT\", \"row\": 2, \"col\": 0, \"direction\": \"across\", \"clue\": \"What Grandpa forgets to buy\" },\n    { \"number\": 3, \"answer\": \"NORA\", \"row\": 4, \"col\": 0, \"direction\": \"across\", \"clue\": \"Reigning flashlight-tag champion\" }\n  ],\n  \"solution\": \"grid as printed above\"\n}\n"
+      },
+      {
+        "path": "puzzles/loon-lake-crossword.html",
+        "content": "<!doctype html>\n<html><head><meta charset=\"utf-8\"><title>Loon Lake Crossword</title><style>td{width:2em;height:2em;border:1px solid #333;text-align:center}</style></head>\n<body><h1>Loon Lake Crossword</h1><table></table><p>Across: 1. What tipped over in 2019, twice; 2. What Grandpa forgets to buy; 3. Reigning flashlight-tag champion. Down: 1. Where the summer happens.</p></body></html>\n"
+      },
+      {
+        "path": "puzzles/garden-birds-word-search.json",
+        "content": "{\n  \"title\": \"Garden Birds Word Search\",\n  \"kind\": \"word-search\",\n  \"size\": { \"rows\": 8, \"cols\": 8 },\n  \"grid\": [\"WRENXQZC\", \"WARBLERH\", \"FINCHAAI\", \"XNUTHATC\", \"ROBINPZK\", \"JAYQWERA\", \"SISKINQD\", \"CHICKADE\"],\n  \"words\": [\"WREN\", \"WARBLER\", \"FINCH\", \"ROBIN\", \"JAY\", \"SISKIN\"],\n  \"solution\": \"words run left to right on their rows\"\n}\n"
+      },
+      {
+        "path": "puzzles/garden-birds-word-search.html",
+        "content": "<!doctype html>\n<html><head><meta charset=\"utf-8\"><title>Garden Birds Word Search</title><style>td{width:1.6em;height:1.6em;text-align:center;font-family:monospace}</style></head>\n<body><h1>Garden Birds Word Search</h1><table></table><p>Find: WREN, WARBLER, FINCH, ROBIN, JAY, SISKIN.</p></body></html>\n"
+      },
+      {
+        "path": "puzzles/porch-sudoku.json",
+        "content": "{\n  \"title\": \"Porch Sudoku\",\n  \"kind\": \"sudoku-4x4\",\n  \"size\": { \"rows\": 4, \"cols\": 4 },\n  \"grid\": [\"1..4\", \"..2.\", \".3..\", \"4..1\"],\n  \"solution\": [\"1234\", \"3421\", \"2313\", \"4132\"],\n  \"note\": \"gentle one for the porch after dinner\"\n}\n"
+      },
+      {
+        "path": "puzzles/porch-sudoku.html",
+        "content": "<!doctype html>\n<html><head><meta charset=\"utf-8\"><title>Porch Sudoku</title><style>td{width:2em;height:2em;border:1px solid #333;text-align:center}</style></head>\n<body><h1>Porch Sudoku</h1><table></table><p>Fill each row, column, and box with 1 through 4.</p></body></html>\n"
+      }
+    ],
+    "worker": {
+      "name": "Marnix",
+      "role": "Designer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "pack/pack.html is a print-ready booklet: cover with contents, one page per shelf puzzle, and all solutions gathered in a back section.",
+    "deliverables": [
+      {
+        "path": "pack/pack.html",
+        "kind": "html-page",
+        "minBytes": 3000,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "pack/pack.html"
+          },
+          {
+            "kind": "contains",
+            "file": "pack/pack.html",
+            "pattern": "@page|page-break|break-after|break-before",
+            "flags": "i",
+            "label": "page-break CSS"
+          },
+          {
+            "kind": "contains",
+            "file": "pack/pack.html",
+            "pattern": "Loon Lake",
+            "label": "crossword included"
+          },
+          {
+            "kind": "contains",
+            "file": "pack/pack.html",
+            "pattern": "Garden Birds",
+            "label": "word search included"
+          },
+          {
+            "kind": "contains",
+            "file": "pack/pack.html",
+            "pattern": "Porch Sudoku|Sudoku",
+            "label": "sudoku included"
+          },
+          {
+            "kind": "contains",
+            "file": "pack/pack.html",
+            "pattern": "solutions?",
+            "flags": "i",
+            "label": "solutions section present"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "pack/pack.html",
+      "kind": "html"
+    },
+    "axes": [
+      {
+        "name": "layout quality",
+        "description": "Grids and clues are re-laid properly for paper — pencil-sized squares, readable clue lists, a real cover."
+      },
+      {
+        "name": "completeness",
+        "description": "All three shelf puzzles appear under their own titles; none dropped or duplicated."
+      },
+      {
+        "name": "print readiness",
+        "description": "Page breaks put one puzzle per page and keep every solution in the back section, never beside its puzzle."
+      },
+      {
+        "name": "delight",
+        "description": "The pack feels like a thing a family would fight over at the kitchen table."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "shelf completeness",
+    "solutions at the back",
+    "print-ready booklet"
+  ]
+}

package/data/craftbook-templates/pw/pwa-offline/versions/1.0.2/craftbook.json ADDED Viewed

@@ -0,0 +1,167 @@
+{
+  "id": "pwa-offline",
+  "name": "Installable Offline PWA",
+  "description": "Build an installable Progressive Web App that works offline — an HTML app shell, a web app manifest, and a service worker that caches the shell so it loads with no network. Scopes the app's one job and the offline strategy first, designs the app shell, then implements the manifest, registration, and a cache-first service worker. PWAs fail at installability and the service-worker caching contract, so the scope phase locks the cached asset list and the offline behavior before coding, keeping a small model from shipping a manifest that fails the install criteria or a service worker that never caches.\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 (planner) — the app's job + offline strategy + cached assets → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. App shell design (designer) — shell layout, theme colors, offline indicator → gated on artifact `{{workPath}}/design.md` (markdown-notes)\n3. Build (developer) — index.html + manifest + service worker → gated on `index.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": [
+    "pwa",
+    "progressive web app",
+    "offline web app",
+    "installable app",
+    "service worker app",
+    "add to home screen app"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope",
+      "description": "the app's job + offline strategy + cached assets",
+      "prompt": "Scope the PWA. (1) State the app's one job in a sentence (e.g. 'a checklist that works offline'). (2) List the app-shell assets to precache (index.html, the CSS/JS, icons) for offline load. (3) Choose the caching strategy (cache-first for the shell) and what happens for uncached requests. (4) Define the manifest essentials: name, short_name, start_url, display 'standalone', theme/background color, and at least a 192 and 512 icon. (5) Write an acceptance-criteria checklist of 5-8 items, e.g. 'a web app manifest is linked with required fields', 'a service worker registers', 'the SW precaches the shell on install', 'the app loads offline after first visit (cache-first)', 'icons are referenced', 'no console errors'. Write to {{workPath}}/scope.md and via write_task_note. No code 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": "design"
+    },
+    {
+      "id": "design",
+      "name": "App shell design",
+      "description": "shell layout, theme colors, offline indicator",
+      "prompt": "Design the app shell. (1) Lay out the minimal shell UI for the app's one job and pick a palette (hex) including the theme/background colors used in the manifest. (2) Specify an online/offline indicator so the user knows their state. (3) Keep the shell light so it caches small and loads instantly. (4) Note the icon look. Write the shell spec to {{workPath}}/design.md and via write_task_note. No code yet.\n\nThe deliverable `{{workPath}}/design.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": "designer",
+      "advanceWhen": {
+        "file": "{{workPath}}/design.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/design.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/design.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "design",
+        "maxAttempts": 3
+      },
+      "next": "build"
+    },
+    {
+      "id": "build",
+      "name": "Build",
+      "description": "index.html + manifest + service worker",
+      "prompt": "Build the PWA to the scope and shell spec. (1) Write index.html as the app shell with the app's UI; link the web app manifest and add theme-color meta. (2) Write manifest.webmanifest (or manifest.json) with name, short_name, start_url, display standalone, theme/background colors, and 192/512 icon entries. (3) In index.html, register the service worker on load (navigator.serviceWorker.register). (4) Write sw.js that on 'install' precaches the shell asset list into a named cache, and on 'fetch' serves cache-first falling back to network. (5) Show the online/offline indicator. On a loop-back, fix only the named gaps. write_task_note the file paths and passing criteria.",
+      "suggestedRole": "developer",
+      "advanceWhen": {
+        "file": "index.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "index.html",
+            "bytes": 600
+          },
+          {
+            "kind": "htmlLint",
+            "file": "index.html"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "serviceWorker\\.register",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "sw.js",
+            "pattern": "addEventListener\\(['\"]install",
+            "flags": "i"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html"
+            }
+          }
+        ],
+        "onReject": "build",
+        "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": "Evaluate the PWA. Read index.html, the manifest, and sw.js. Check EACH criterion from {{workPath}}/scope.md and write PASS/FAIL with a reason: is a manifest linked with name/start_url/display-standalone/theme-color and 192+512 icons, does index.html call serviceWorker.register, does sw.js cache the shell on the install event, does fetch serve cache-first (so a second load works offline), are icons referenced, zero console errors? If a browser/DevTools is available, simulate offline and reload to confirm it still loads. A service worker that never caches the shell is a FAIL — loop back to build.\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: \"build\" })` 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": "build"
+    },
+    {
+      "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.2",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "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}}"
+      }
+    }
+  },
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/pw/pwa-offline/versions/1.0.2/test.json ADDED Viewed

@@ -0,0 +1,100 @@
+{
+  "schemaVersion": 1,
+  "title": "Installable Offline PWA smoke eval",
+  "objective": "Self-contained smoke eval for the Installable Offline PWA craftbook using the html-page generic harness.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "Can you biuld us a little page for this? The content notes are in source/page-content.md. Save it as index.html — one file, nothing fancy needed on our end.",
+  "setup": {
+    "projectName": "Installable Offline PWA Eval",
+    "about": "Self-contained eval project for pwa-offline. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/index.html.",
+    "missionObjectives": "Use the Installable Offline PWA craftbook/template, read the seeded local fixtures, and write index.html without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Installable Offline PWA 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: pwa-offline - Installable Offline PWA.\n"
+      },
+      {
+        "path": "source/page-content.md",
+        "content": "# Boreal Desk Support Board\n\nBuild content around a support operations board. Required labels: Open issues, Status silence, Response time, Refund leakage, Next action. Required metric text: 18 hours to 6 hours and 14.2% to 8.9%.\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Developer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "index.html is a source-grounded self-contained HTML page/tool.",
+    "deliverables": [
+      {
+        "path": "index.html",
+        "kind": "html-page",
+        "minBytes": 3000,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "index.html"
+          },
+          {
+            "kind": "jsParses",
+            "file": "index.html"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "Boreal|Support Board|returns",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "18\\s*hours|6\\s*hours|14\\.2%|8\\.9%",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "button|input|filter|tab|card|section|nav",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "index.html",
+      "kind": "html"
+    },
+    "axes": [
+      {
+        "name": "structure",
+        "description": "Layout and hierarchy fit the content; sections are scannable and coherent."
+      },
+      {
+        "name": "grounding",
+        "description": "Seeded source content is used faithfully — no invented facts or dropped requirements."
+      },
+      {
+        "name": "interactivity",
+        "description": "Controls and states the page claims to offer actually work."
+      },
+      {
+        "name": "polish",
+        "description": "Styling is intentional and responsive rather than unstyled or broken."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "self-contained UI",
+    "source grounding",
+    "responsive structure"
+  ]
+}

package/data/craftbook-templates/qu/quarterly-summary/versions/1.0.2/craftbook.json ADDED Viewed

@@ -0,0 +1,152 @@
+{
+  "id": "quarterly-summary",
+  "name": "Quarterly Shoebox Summary",
+  "description": "Close the quarter the way your accountant wishes everyone did: totals by category computed from the ledger entries themselves, the missing-documentation list naming each entry that lacks its paperwork, and the estimated-payment reminder in plain words. Locks the target quarter and the checks FIRST, then reconciles the numbers, then writes the summary — twenty minutes, four times a year, instead of an April archaeology dig. Use for quarterly tax summaries, 'how did the quarter shake out', estimated payment prep, and shoebox quarter closes.\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 quarter (data-analyst) — target quarter, checks, what the summary must report → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Reconcile the quarter (data-analyst) — category totals from the entries, missing docs, prior-quarter deltas → gated on artifact `{{workPath}}/reconcile.md` (markdown-notes)\n3. Write the quarter summary (copywriter) — category table, missing-doc list, one next-quarter action → 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": [
+    "quarterly shoebox summary",
+    "how did the quarter shake out",
+    "close the tax quarter",
+    "quarterly expense summary",
+    "estimated payment prep"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the quarter",
+      "description": "target quarter, checks, what the summary must report",
+      "prompt": "Define the close before computing anything. Step 1: read ledger.json from the workspace and lock the target quarter (default: the most recently ended calendar quarter) and the prior quarter as the comparison baseline. Step 2: define the checks — entries in the quarter with no category or a category that fits badly, entries with no source document behind them, and amounts that look like typos against their category's usual range. Step 3: define what the summary must report — totals by category computed from the entries, the missing-documentation list naming each entry that lacks its source, the delta versus the prior quarter, and a plain-words estimated-payment reminder. Step 4: write an acceptance-criteria checklist ('every quarter entry counted exactly once', 'totals computed from the entries, never estimated', 'every entry without a source document named', 'one concrete next-quarter action', 'no figure in the summary that is not derivable from the ledger'). Call write_task_note with the quarter + checks + checklist and write {{workPath}}/scope.md. No totals 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": "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": "reconcile"
+    },
+    {
+      "id": "reconcile",
+      "name": "Reconcile the quarter",
+      "description": "category totals from the entries, missing docs, prior-quarter deltas",
+      "prompt": "Reconcile the quarter against the locked checks. Step 1: list every entry in the target quarter and total them by category directly from the amounts — show the per-category arithmetic in your notes so the summary phase inherits checkable numbers. Step 2: sweep for the problem entries — no category, no source document, amounts that look off — and list each one with what is missing. Step 3: compute the prior-quarter comparison per category and flag the big movers. Step 4: note anything that affects the estimated payment — a quarter well above or below the last one deserves a plain-words caution. Step 5: write the structured findings to {{workPath}}/reconcile.md and call write_task_note with the quarter total, the biggest mover, and the missing-documentation count.\n\nThe deliverable `{{workPath}}/reconcile.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}}/reconcile.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/reconcile.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/reconcile.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "reconcile",
+        "maxAttempts": 3
+      },
+      "next": "report"
+    },
+    {
+      "id": "report",
+      "name": "Write the quarter summary",
+      "description": "category table, missing-doc list, one next-quarter action",
+      "prompt": "Write the quarter summary from the reconciliation. Step 1: open with the headline — the quarter's total spend in one plain sentence. Step 2: give the category table — one row per category with its total, computed from the entries, under Category and Total columns. Step 3: list the missing-documentation entries by date and vendor so finding the paperwork is a checklist, not a hunt. Step 4: give the prior-quarter comparison in a line or two, and the estimated-payment reminder in words a non-accountant acts on. Step 5: close with ONE concrete action for next quarter. Keep it calm and factual. Write {{workPath}}/report.md and call write_task_note with the report path and the quarter 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": 1500,
+            "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"
+    },
+    {
+      "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 {{workPath}}/report.md and {{workPath}}/reconcile.md and verify every criterion from {{workPath}}/scope.md: every entry in the quarter is counted exactly once (re-add one category yourself to check), the category table's totals trace to the entries, every entry lacking a source document appears in the missing-documentation list, the prior-quarter comparison is present, the estimated-payment reminder is in plain words, and exactly one next-quarter action is named. Write PASS/FAIL per criterion; on any failure, name the gap and loop back to report.\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: \"report\" })` 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": "report"
+    },
+    {
+      "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.2",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "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}}"
+      }
+    }
+  },
+  "minGezelVersion": "1.26233"
+}