@bendyline/gilde 0.1.26 → 0.1.28

package/data/craftbook-templates/po/podcast-chaptering/versions/1.0.1/test.json

@@ -0,0 +1,103 @@
+{
+  "schemaVersion": 1,
+  "title": "Podcast Chapters & Show Notes smoke eval",
+  "objective": "Self-contained smoke eval for the Podcast Chapters & Show Notes craftbook using the media generic harness.",
+  "tags": [
+    "media"
+  ],
+  "prompt": "Our media files are all listd in source/media-index.csv. Can you put together the production plan for them as media-plan.json?",
+  "setup": {
+    "projectName": "Podcast Chapters & Show Notes Eval",
+    "about": "Self-contained eval project for podcast-chaptering. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/media-plan.json.",
+    "missionObjectives": "Use the Podcast Chapters & Show Notes craftbook/template, read the seeded local fixtures, and write media-plan.json without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Podcast Chapters & Show Notes 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: podcast-chaptering - Podcast Chapters & Show Notes.\n"
+      },
+      {
+        "path": "source/media-index.csv",
+        "content": "filename,type,duration_or_size,notes\npilot-interview.wav,audio,00:02:15,mentions response time and status silence\nreturns-desk.png,image,1600x900,shows intake form and photo evidence step\nlaunch-clip.mp4,video,00:01:05,shows barcode exception handling\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Producer"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "media-plan.json is a valid JSON media-production manifest grounded in seeded fixture metadata.",
+    "deliverables": [
+      {
+        "path": "media-plan.json",
+        "kind": "json",
+        "minBytes": 700,
+        "checks": [
+          {
+            "kind": "sniff",
+            "file": "media-plan.json",
+            "sniff": "json-valid"
+          },
+          {
+            "kind": "contains",
+            "file": "media-plan.json",
+            "pattern": "pilot-interview\\.wav|returns-desk\\.png|launch-clip\\.mp4",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "media-plan.json",
+            "pattern": "outputs|assets|steps|cues|verification",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "media-plan.json",
+            "pattern": "accessibility|alt|caption|transcript|metadata",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "media-plan.json",
+      "kind": "json"
+    },
+    "axes": [
+      {
+        "name": "completeness",
+        "description": "The manifest covers sources, outputs, and processing steps end to end."
+      },
+      {
+        "name": "grounding",
+        "description": "Only seeded media fixtures are referenced, with faithful metadata."
+      },
+      {
+        "name": "accessibility",
+        "description": "Alt text, captions, or transcripts are planned wherever the class requires."
+      },
+      {
+        "name": "precision",
+        "description": "Timestamps, crops, and cues are specific enough to execute."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "media fixture handling",
+    "structured manifest",
+    "verification metadata"
+  ],
+  "extensions": {
+    "legacySimulators": [
+      {
+        "id": "podcast-chaptering-media-fixtures",
+        "kind": "data-source",
+        "status": "implemented",
+        "description": "Seeded local media index replacing real audio, video, image generation, and external media metadata services."
+      }
+    ]
+  }
+}

package/data/craftbook-templates/po/portfolio-site/versions/1.0.1/craftbook.json

@@ -0,0 +1,151 @@
+{
+  "id": "portfolio-site",
+  "name": "Portfolio Site",
+  "description": "Build a personal or professional portfolio site that showcases projects, an about/bio, and contact links in a single polished page. Locks the content inventory — which projects, what bio, which links — first, then a clean gallery-style visual design, then builds responsive HTML with a project grid and real CSS. Scoping the content before designing prevents a small model from inventing fake projects or building a layout the real content does not fit; the portfolio's job is to present a finite set of real work cleanly.\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. Content scope (planner) — inventory projects, bio, links, sections → gated on artifact `notes/content-scope.md` (markdown-notes)\n2. Visual design (visual-designer) — gallery layout, project card, palette, type → gated on artifact `notes/visual-design.md` (markdown-notes)\n3. Build (developer) — implement index.html with the project grid → gated on `index.html` (html-marketing-site)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "content-scope",
+  "triggers": [
+    "portfolio site",
+    "personal website",
+    "showcase my work",
+    "developer portfolio",
+    "designer portfolio",
+    "build a portfolio"
+  ],
+  "steps": [
+    {
+      "id": "content-scope",
+      "name": "Content scope",
+      "description": "inventory projects, bio, links, sections",
+      "prompt": "Inventory the real content. (1) List the projects to feature (title, one-line description, role, link/repo, and whether an image exists) — use only what the user provided; if details are missing, leave placeholders the user must fill, do NOT fabricate. (2) Draft the bio focus (who, what they do, what they want). (3) List contact/social links to include. (4) Order the sections: hero/intro, project grid, about, contact. (5) Write an acceptance-criteria checklist of 5-8 items, e.g. 'every listed project has a card', 'the hero states name and role', 'an about section is present', 'contact links are present and clickable', 'responsive at 375px and 1280px', 'no fabricated projects'. Write to notes/content-scope.md and via write_task_note. No design or HTML yet.\n\nThe deliverable `notes/content-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": "notes/content-scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "notes/content-scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "notes/content-scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "content-scope",
+        "maxAttempts": 3
+      },
+      "next": "visual-design"
+    },
+    {
+      "id": "visual-design",
+      "name": "Visual design",
+      "description": "gallery layout, project card, palette, type",
+      "prompt": "Design the showcase look. (1) Pick a restrained palette (hex) and type pairing that lets the work shine, not the chrome. (2) Design the project card (image/placeholder, title, description, link) and how cards lay out in a responsive grid. (3) Lay out the hero/intro and the about/contact sections. (4) Specify hover/focus states for cards and links and the overall spacing rhythm. (5) Self-contained CSS, no external assets beyond any provided images. Write the visual spec to notes/visual-design.md and via write_task_note. No HTML yet.\n\nThe deliverable `notes/visual-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": "visual-designer",
+      "advanceWhen": {
+        "file": "notes/visual-design.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "notes/visual-design.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "notes/visual-design.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "visual-design",
+        "maxAttempts": 3
+      },
+      "next": "build"
+    },
+    {
+      "id": "build",
+      "name": "Build",
+      "description": "implement index.html with the project grid",
+      "prompt": "Implement index.html with inline CSS to the visual spec, using only the scoped content. (1) Palette as CSS variables and the chosen type. (2) Hero with name and role. (3) A responsive CSS-grid project gallery, one card per scoped project with its real (or placeholder) details and a clickable link. (4) About and contact sections with clickable links. (5) Responsive at 375px and 1280px; vanilla HTML/CSS, no CDN. Keep placeholders explicit where the user must supply content — never invent projects. On a loop-back, fix only the named gaps without regressing passing criteria. write_task_note the path and passing criteria.",
+      "suggestedRole": "developer",
+      "advanceWhen": {
+        "file": "index.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "index.html",
+            "bytes": 1200
+          },
+          {
+            "kind": "htmlLint",
+            "file": "index.html"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html"
+            }
+          },
+          {
+            "name": "checkCssMinBytes",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html",
+              "minBytes": 600
+            }
+          }
+        ],
+        "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 portfolio. Open/render index.html and resize to 375px and 1280px. Check EACH criterion from notes/content-scope.md and write PASS/FAIL with a reason: does every scoped project have a card, does the hero state name and role, is there an about section, are contact links present and clickable, is it responsive, and crucially are there ZERO fabricated projects? Any invented project or missing scoped project 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.1",
+  "releasedAt": "2026-08-14T00:00:00Z"
+}

package/data/craftbook-templates/po/portfolio-site/versions/1.0.1/test.json

@@ -0,0 +1,97 @@
+{
+  "schemaVersion": 1,
+  "title": "Portfolio Site smoke eval",
+  "objective": "Self-contained smoke eval for the Portfolio Site 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": "Portfolio Site Eval",
+    "about": "Self-contained eval project for portfolio-site. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/index.html.",
+    "missionObjectives": "Use the Portfolio Site 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": "# Portfolio Site 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: portfolio-site - Portfolio Site.\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"
+    }
+  },
+  "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/po/powerpoint-deck/versions/1.7.0/craftbook.json

@@ -0,0 +1,257 @@
+{
+  "id": "powerpoint-deck",
+  "name": "PowerPoint from Content",
+  "description": "Turn supplied content or a factual topic into a real, editable, source-grounded PowerPoint. A researcher first reads the exact named source or retrieves authoritative web sources and records a cited fact ledger. A planner locks a numbered slide outline. A copywriter writes deck.md with exactly one H1 per outline slide, while deterministic gates keep the slide count, titles, and order aligned. A reviewer checks factual traceability before a designer converts the Markdown to PPTX, previews every slide, and saves deck.pptx in artifacts.",
+  "entryStepId": "research",
+  "triggers": [
+    "make a powerpoint",
+    "create a pptx",
+    "powerpoint from this content",
+    "turn this into a presentation",
+    "build a slide deck file",
+    "export these slides to powerpoint"
+  ],
+  "toolsets": [
+    {
+      "toolsetId": "docblocks",
+      "sourceId": "bundled",
+      "autoAllow": true,
+      "reason": "convert deck.md directly to PPTX, preview slides, and save the finished PowerPoint without a prompt per call"
+    }
+  ],
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "outputPath": {
+        "type": "string",
+        "title": "Workspace output path",
+        "description": "Project-workspace-relative path for the finished PowerPoint.",
+        "default": "deck.pptx"
+      },
+      "sourcePath": {
+        "type": "string",
+        "title": "Source file",
+        "description": "Optional exact workspace-relative path to authoritative source content. Leave blank when the deck starts from a topic that needs web research.",
+        "default": ""
+      },
+      "topic": {
+        "type": "string",
+        "title": "Topic",
+        "description": "The factual topic or question the deck should address.",
+        "default": ""
+      },
+      "content": {
+        "type": "string",
+        "title": "Inline source brief",
+        "description": "Optional inline source material or factual brief for the deck.",
+        "default": ""
+      },
+      "audience": {
+        "type": "string",
+        "title": "Audience",
+        "description": "The people who will view the deck and the decision they need to make."
+      }
+    }
+  },
+  "steps": [
+    {
+      "id": "research",
+      "name": "Acquire and verify sources",
+      "description": "Read the exact supplied source or retrieve authoritative sources before outlining.",
+      "prompt": "Build the source packet before planning any slides. Exact source path: `{{sourcePath}}`. Topic: `{{topic}}`. Inline source brief: `{{content}}`. Audience: `{{audience}}`. 1. When `{{sourcePath}}` is non-empty, your FIRST source action is `read_file` on that exact path. Never replace a named source with a similarly named file. 2. Otherwise treat non-empty `{{content}}` as supplied source material and `{{topic}}` as the research question, but still perform real external source acquisition for factual grounding: use `web_search` when registered, otherwise `wikipedia_search`, then use `fetch_url` or browser automation to read the useful result. Prefer primary sources, official statistics, standards bodies, peer-reviewed work, or reputable institutional summaries. Do not treat model memory, the task prompt, or an invented URL as research. 3. Write `notes/sources.md` with: the invocation inputs and their boundary; a source table with title, resolvable URL or exact file path, authority/date, and intended use; a fact ledger where every number, quotation, and externally checkable claim carries `(source: URL-or-path)`; conflicts and uncertainties; and facts that must not be invented. Do not silently overwrite supplied facts with external claims—record conflicts explicitly. 4. Include at least one resolvable citation and call `write_task_note` with the sources used and any uncertainty. Do not draft the outline or deck yet.",
+      "suggestedRole": "researcher",
+      "advanceWhen": {
+        "file": "notes/sources.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "notes/sources.md",
+            "bytes": 500
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "notes/sources.md",
+            "minCitations": 1
+          },
+          {
+            "kind": "researchEvidence",
+            "sourcePath": "{{sourcePath}}",
+            "tools": [
+              "web_search",
+              "wikipedia_search",
+              "fetch_url",
+              "browser_navigate",
+              "run_playwright_script"
+            ],
+            "minSuccessful": 1
+          }
+        ],
+        "onReject": "research",
+        "maxAttempts": 3
+      },
+      "next": "outline"
+    },
+    {
+      "id": "outline",
+      "name": "Lock the slide outline",
+      "description": "Lock the audience, purpose, sequence, evidence, and one message per slide.",
+      "prompt": "Read `notes/sources.md` and plan the deck from its verified fact ledger. If `{{sourcePath}}` is non-empty, also read that exact source. 1. State the audience, occasion, and ONE takeaway. 2. Use exactly the slide count the user asked for; only when they gave none, draft 8-15 slides. Format every slide heading exactly as `## Slide N — Title`, numbered consecutively from 1. Under each heading write `Message:`, `Evidence:`, and `Visual:`. Every evidence line must point to a citation already recorded in `notes/sources.md`; mark unsupported ideas `UNVERIFIED` rather than filling gaps from memory. 3. Open with context, make the middle a coherent argument, and close with the ask or next step. Include a Sources slide in this locked outline when the audience needs visible references. 4. Write acceptance criteria: every numbered outline slide must become exactly one H1 in deck.md, with the same title and order; one idea per slide; no wall of text; claims remain traceable; visual preview passes; an artifact copy is retained; and the exact workspace file `{{outputPath}}` is delivered. Write only `notes/outline.md`, then call `write_task_note` with the exact slide count, takeaway, and requested output path. Do not write slide content or presentation code.",
+      "suggestedRole": "planner",
+      "advanceWhen": {
+        "file": "notes/outline.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "notes/outline.md",
+            "bytes": 500
+          },
+          {
+            "kind": "contains",
+            "file": "notes/outline.md",
+            "pattern": "(?:^|\\n)#{2,6}\\s+(?:Slide\\s+)?1(?:\\s*[.:\\-–—]\\s*|\\s+)\\S",
+            "flags": "i",
+            "label": "a numbered Slide 1 heading"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "notes/outline.md",
+            "minCitations": 1
+          }
+        ],
+        "onReject": "outline",
+        "maxAttempts": 3
+      },
+      "next": "write"
+    },
+    {
+      "id": "write",
+      "name": "Write the Markdown deck",
+      "description": "Write deck.md with exactly one matching H1 per locked outline slide.",
+      "prompt": "Read `notes/sources.md` and `notes/outline.md`, then write `deck.md` to the locked sequence. 1. For every `## Slide N — Title` in the outline, create exactly one `# Title` H1 in deck.md, preserving the title and order verbatim. Do not add, merge, drop, or reorder slides. Do not add `---` separators unless a visible horizontal rule is intended. Slides are split on H1: a deck whose slides are `##` converts to ONE slide, so never use `##` for a slide and never add a `# ` document title. 2. Under each H1, land that slide's one message with 3-6 short bullet phrases, a compact Markdown table, or a short quotation; never use paragraph walls. 3. Keep every factual claim traceable to `notes/sources.md`. Put concise `(source: URL-or-path)` citations next to load-bearing figures/claims. Use a Sources slide only when it is already in the locked outline; never add an unoutlined slide. Never invent a number, quotation, organization, or URL. 4. Bold the load-bearing figure or claim. 5. The final H1 must be the outline's ask or next-step slide. 6. On loop-back, repair only the mismatch or claim the gate/reviewer names. Call `write_task_note` with the path and H1 count. Do not create HTML, JavaScript, OOXML, or PPTX bytes.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "deck.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "deck.md",
+            "bytes": 700
+          },
+          {
+            "kind": "contains",
+            "file": "deck.md",
+            "pattern": "(?:^|\\n)#\\s+\\S",
+            "label": "at least one H1 slide heading"
+          },
+          {
+            "kind": "markdownHeadingsMatch",
+            "file": "deck.md",
+            "outlineFile": "notes/outline.md"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "deck.md",
+            "minCitations": 1
+          }
+        ],
+        "onReject": "write",
+        "maxAttempts": 4
+      },
+      "next": "review"
+    },
+    {
+      "id": "review",
+      "name": "Review narrative and grounding",
+      "description": "Verify slide parity, factual traceability, and presentation readiness before conversion.",
+      "prompt": "Read `notes/sources.md`, `notes/outline.md`, and `deck.md`. Write `notes/review.md` with PASS/FAIL for every criterion: (1) each numbered outline slide appears exactly once as an H1 with the same title and order; (2) the deck opens with context and closes with the locked ask; (3) each slide has one message and concise content; (4) every number, quote, and externally checkable claim maps to a real `(source: URL-or-path)` entry in the source packet; (5) no `UNVERIFIED` claim is presented as fact; (6) tables and visuals are purposeful and likely to fit. Cite `notes/sources.md`, `notes/outline.md`, and `deck.md` as `(source: path)` when recording evidence. Any failure must name the slide and exact repair. If every criterion passes, call `advance_task_step({ ref, stepId: \"review\", next: \"publish\" })`. If any criterion fails, call `advance_task_step({ ref, stepId: \"review\", next: \"write\" })`. Never publish a failed or ungrounded deck.",
+      "suggestedRole": "reviewer",
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "notes/review.md",
+            "bytes": 400
+          },
+          {
+            "kind": "contains",
+            "file": "notes/review.md",
+            "pattern": "PASS|FAIL",
+            "flags": "i",
+            "label": "explicit PASS/FAIL verdicts"
+          },
+          {
+            "kind": "markdownHeadingsMatch",
+            "file": "deck.md",
+            "outlineFile": "notes/outline.md"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "notes/review.md",
+            "minCitations": 3
+          }
+        ],
+        "onReject": "review",
+        "maxAttempts": 3
+      },
+      "next": "write"
+    },
+    {
+      "id": "publish",
+      "name": "Publish the PowerPoint",
+      "description": "Convert deck.md with DocBlocks, preview every slide, retain an artifact, and deliver {{outputPath}}.",
+      "prompt": "Publish the reviewed `deck.md` as a real editable PowerPoint with the pre-authorized DocBlocks tools. 1. Call `list_roots` and identify the read-enabled workspace root and write-enabled artifacts root. If there is no write root, report the blocker rather than substituting HTML. 2. Call `convert_document` ONCE for this approved revision with source `{ \"kind\": \"file\", \"rootId\": <workspace root id>, \"path\": \"deck.md\" }`, target `[{ \"format\": \"pptx\", \"fidelity\": \"editable-native\", \"slideBreak\": \"h1\", \"title\": <deck title> }]`, an audience-appropriate theme, and `autoTemplates: true`. 3. Call `preview_document` on the PPTX artifact URI and inspect every slide (paginate after 20): the preview slide count must equal the H1 count in deck.md; no overflow or tiny text; tables legible; hierarchy consistent. If QA fails, do not save a known-bad PPTX or silently remove content—record the exact slide and route back to write. 4. When preview passes, call `save_artifact` with destination `{ \"rootId\": <artifacts root id>, \"path\": \"{{outputPath}}\", \"ifExists\": \"error\" }`; on a loop-back, replace only with the current expectedSha256. 5. Call `copy_artifact_to_workspace` with source `\"{{outputPath}}\"` and dest `\"{{outputPath}}\"` so the user receives the exact requested workspace file without a text/binary round-trip. 6. Call `write_task_note` with the artifact path, workspace path, slide count, theme, and preview result. Do not hand-build an HTML deck or presentation XML.",
+      "suggestedRole": "designer",
+      "advanceWhen": {
+        "file": "{{outputPath}}",
+        "minBytes": 1
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{outputPath}}",
+            "bytes": 1000
+          }
+        ],
+        "onReject": "publish",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate the saved deck",
+      "description": "Review the PPTX against the locked source, outline, and visual criteria.",
+      "prompt": "Review `artifacts/{{outputPath}}` against `notes/sources.md`, `notes/outline.md`, and `notes/review.md`. Use `list_roots` to identify the artifacts root and `preview_document` with source `{ \"kind\": \"file\", \"rootId\": <artifacts root id>, \"path\": \"{{outputPath}}\" }`; inspect all slides. Confirm: it is a real PPTX; `workspace/{{outputPath}}` exists; the preview slide count equals the locked outline/H1 count; every outlined slide appears once and in order; source facts and citations remain visible or are represented by the outlined Sources slide; each slide has one message; text/tables fit; theme is consistent; the closing ask is present; and artifact/workspace copies represent the same approved revision. Write PASS/FAIL for every criterion. Every pass routes to `finish`; a content, grounding, density, or slide-structure failure routes to `write`; a conversion, theme, save, or copy failure with deck.md still approved routes to `publish`. Never route to finish while a criterion is unmet. After about three unproductive loops, stop with DONE_WITH_CONCERNS.",
+      "suggestedRole": "reviewer",
+      "next": "write"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All research, narrative, slide, and file checks passed.",
+      "prompt": "Every acceptance criterion passed. Call `write_task_note` with a short DONE summary naming `notes/sources.md`, `notes/outline.md`, and `deck.md` as the grounded source chain, `artifacts/{{outputPath}}` as the retained artifact, and `workspace/{{outputPath}}` as the user-facing deliverable, plus the slide count and confirmation that visual preview passed. Then report DONE.",
+      "suggestedRole": "designer",
+      "terminal": true
+    }
+  ],
+  "version": "1.7.0",
+  "releasedAt": "2026-08-06T00:00:00Z"
+}