@bendyline/gilde 0.1.38 → 0.1.40

package/data/craftbook-templates/ch/changelog-cut/versions/1.0.2/craftbook.json

@@ -0,0 +1,125 @@
+{
+  "id": "changelog-cut",
+  "name": "Changelog Cut",
+  "description": "Cut a new versioned section into a Keep a Changelog / CHANGELOG.md style file for a release — moving entries out of the Unreleased section into a dated, semver-stamped version block under the standard Added / Changed / Deprecated / Removed / Fixed / Security headings, with a fresh empty Unreleased section left behind. A developer gathers the unreleased entries and reconciles them against actual merged changes before a copywriter normalizes them into terse, consistent changelog lines and stamps the version block. Use this whenever you 'cut a release', 'update the changelog', or roll the Unreleased section into a tagged version while keeping the file append-only and machine-comparable.\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. Gather unreleased entries (developer) — reconcile the Unreleased section against actual merged changes → gated on artifact `{{workPath}}/gather.md` (markdown-notes)\n2. Cut the version block (copywriter) — normalize entries and stamp the dated version section → gated on `CHANGELOG.md` (markdown-doc)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "gather",
+  "triggers": [
+    "cut a changelog",
+    "update CHANGELOG.md",
+    "roll unreleased into a version",
+    "stamp the changelog for v1.4",
+    "keep a changelog release"
+  ],
+  "steps": [
+    {
+      "id": "gather",
+      "name": "Gather unreleased entries",
+      "description": "reconcile the Unreleased section against actual merged changes",
+      "prompt": "1. Locate the changelog file (CHANGELOG.md or similar) and read its existing format — Keep a Changelog headings (Added, Changed, Deprecated, Removed, Fixed, Security) are the default; match whatever the file already uses. 2. Read the current Unreleased section and reconcile it against the real merged changes since the last version block (git log / merged PRs) — add anything user-facing that is missing, and remove or merge duplicates. 3. Determine the new version number per semver: bump MAJOR for breaking changes, MINOR for new backward-compatible features, PATCH for fixes only; note the reasoning. 4. Map each entry to the correct heading (Removed and Security are not Changed). 5. Good looks like: a reconciled, categorized list of every unreleased user-facing change, the chosen version number with a one-line semver justification, and the release date. Write an acceptance-criteria checklist ('version follows semver given the change set', 'every entry sits under the correct standard heading', 'Unreleased reconciles with merged changes', 'existing version blocks untouched') plus the inventory to the notes file via write_task_note AND to {{workPath}}/gather.md.\n\nThe deliverable `{{workPath}}/gather.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": "developer",
+      "advanceWhen": {
+        "file": "{{workPath}}/gather.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/gather.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/gather.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "gather",
+        "maxAttempts": 3
+      },
+      "next": "write"
+    },
+    {
+      "id": "write",
+      "name": "Cut the version block",
+      "description": "normalize entries and stamp the dated version section",
+      "prompt": "1. Open {{workPath}}/gather.md and rewrite the changelog so the reconciled entries form a new version block headed '## [VERSION] - YYYY-MM-DD' inserted directly above the previous version block. 2. Under that block, emit only the non-empty standard headings, each with terse, parallel one-line bullets in the imperative ('Add…', 'Fix…') — one change per bullet, no implementation chatter. 3. Leave a fresh, empty '## [Unreleased]' section at the top with the standard heading placeholders. 4. Do NOT alter any pre-existing version block, the file header, or the comparison-link footer except to add the new version's link if the file uses them. 5. Preserve issue/PR references if the file's convention includes them. 6. Good looks like: a clean, append-only CHANGELOG.md where the new dated version block is correct semver, Unreleased is empty, and the file still parses as Keep a Changelog. Write the updated changelog to CHANGELOG.md.\n\nBefore working, open the artifact input `{{workPath}}/gather.md` with `read_artifact`; do not look for it in the workspace.",
+      "suggestedRole": "copywriter",
+      "consumes": [
+        {
+          "file": "{{workPath}}/gather.md",
+          "artifact": true
+        }
+      ],
+      "advanceWhen": {
+        "file": "CHANGELOG.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "CHANGELOG.md",
+            "bytes": 500
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkContains",
+            "scope": "standard",
+            "inputs": {
+              "file": "CHANGELOG.md",
+              "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+              "flags": "i"
+            }
+          }
+        ],
+        "onReject": "write",
+        "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 CHANGELOG.md and check it against the acceptance criteria in {{workPath}}/gather.md, PASS/FAIL each. Confirm: (a) a new '## [VERSION] - DATE' block exists with a valid date and a semver-correct version for the change set; (b) every gathered entry appears once under the correct standard heading and empty headings are omitted; (c) a fresh empty Unreleased section sits at the top; (d) all previous version blocks and the file header/footer are unchanged; (e) bullets are terse and parallel with one change each; (f) the file still reads as a valid Keep a Changelog document. Any FAIL routes back to the write phase.\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": "CHANGELOG.md"
+        }
+      ],
+      "next": "write"
+    },
+    {
+      "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/ch/changelog-cut/versions/1.0.2/test.json

@@ -0,0 +1,109 @@
+{
+  "schemaVersion": 1,
+  "title": "Cut Unreleased changelog into dated version block",
+  "objective": "Measure whether the changelog-cut craftbook preserves the existing file while moving user-facing Unreleased entries into a semver block.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "In the `Changelog Cut Eval` project, read the existing `CHANGELOG.md` and `source/merged-prs.md`, then cut release 2.4.0 dated 2026-06-28. Leave a fresh empty Unreleased section, move user-facing entries into the correct standard headings, preserve PR references, and do not include internal-only chores.",
+  "setup": {
+    "projectName": "Changelog Cut Eval",
+    "about": "Self-contained eval project for changelog-cut. Existing changelog and merged PR inventory are seeded in the workspace.",
+    "missionObjectives": "Update CHANGELOG.md append-only style for version 2.4.0 while preserving previous blocks and excluding internal-only noise.",
+    "files": [
+      {
+        "path": "CHANGELOG.md",
+        "content": "# Changelog\n\n## [Unreleased]\n\n### Added\n- Add saved invoice filters for finance teams (#812).\n- Add webhook retry visibility in the admin panel (#817).\n\n### Fixed\n- Fix duplicate customer merge suggestions after CSV import (#829).\n\n### Security\n- Rotate default API key salt for new installs (#836).\n\n### Changed\n- Internal reducer file rename in billing package (#831).\n\n## [2.3.1] - 2026-05-14\n\n### Fixed\n- Fix invoice PDF currency rounding (#801).\n"
+      },
+      {
+        "path": "source/merged-prs.md",
+        "content": "# Merged PRs since 2.3.1\n\n- #812 user-facing feature: saved invoice filters.\n- #817 user-facing improvement: webhook retry queue shows next retry time.\n- #829 user-facing fix: duplicate customer merge suggestions.\n- #831 internal-only: reducer file rename, do not publish.\n- #836 security: rotate default API key salt for new installs.\n"
+      }
+    ],
+    "worker": {
+      "name": "Hanne",
+      "role": "Release Writer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "workspace/CHANGELOG.md contains a new 2.4.0 block with user-facing entries, fresh Unreleased, previous block preserved, and internal-only PRs excluded.",
+    "deliverables": [
+      {
+        "path": "CHANGELOG.md",
+        "kind": "markdown-doc",
+        "minBytes": 1200,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "## \\[Unreleased\\]",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "## \\[2\\.4\\.0\\] - 2026-06-28",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "Added|Fixed|Security",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "#812|#817|#829|#836",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "## \\[2\\.3\\.1\\] - 2026-05-14",
+            "flags": "i"
+          },
+          {
+            "kind": "notContains",
+            "file": "CHANGELOG.md",
+            "pattern": "reducer file rename|#831",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "CHANGELOG.md",
+      "kind": "markdown"
+    },
+    "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": [
+    "append-only changelog edit",
+    "semver heading",
+    "de-noising"
+  ]
+}

package/data/craftbook-templates/ch/changelog-writeup/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "changelog-writeup",
   "role": "general",
+  "category": "code-release",
   "name": "Human-Readable Changelog",
   "description": "Turn raw commit/PR history into a human-readable changelog that users actually understand: a developer first gathers and triages the merged changes since the last release into user-facing buckets (Added, Changed, Fixed, Deprecated, Removed, Security), filtering out noise like internal refactors, then a copywriter rewrites each entry in plain, benefit-oriented language with breaking changes called out. Covers changelog, release notes, what's new, version notes, and Keep a Changelog format. Gathering and triaging before writing is the point: a small model that first separates user-facing changes from internal churn avoids the changelog that lists 'bump deps' next to a breaking API change with equal weight.",
   "tags": [

package/data/craftbook-templates/ch/changelog-writeup/versions/1.0.2/craftbook.json

@@ -0,0 +1,119 @@
+{
+  "id": "changelog-writeup",
+  "name": "Human-Readable Changelog",
+  "description": "Turn raw commit/PR history into a human-readable changelog that users actually understand: a developer first gathers and triages the merged changes since the last release into user-facing buckets (Added, Changed, Fixed, Deprecated, Removed, Security), filtering out noise like internal refactors, then a copywriter rewrites each entry in plain, benefit-oriented language with breaking changes called out. Covers changelog, release notes, what's new, version notes, and Keep a Changelog format. Gathering and triaging before writing is the point: a small model that first separates user-facing changes from internal churn avoids the changelog that lists 'bump deps' next to a breaking API change with equal weight.\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. Gather & triage changes (developer) — collect merged changes and bucket the user-facing ones → gated on artifact `{{workPath}}/gather.md` (markdown-notes)\n2. Write the changelog (copywriter) — rewrite entries in plain, user-facing language → gated on `CHANGELOG.md` (markdown-doc)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "gather",
+  "triggers": [
+    "write a changelog",
+    "generate release notes",
+    "whats new writeup",
+    "changelog from commits",
+    "version notes"
+  ],
+  "steps": [
+    {
+      "id": "gather",
+      "name": "Gather & triage changes",
+      "description": "collect merged changes and bucket the user-facing ones",
+      "prompt": "1) Determine the version range (since the last tag/release). 2) Collect the merged commits/PRs in that range (use git log or the available VCS tools). 3) Triage each into a Keep-a-Changelog bucket: Added, Changed, Deprecated, Removed, Fixed, Security — or DROP if it is internal-only (refactors, test/CI tweaks, dependency bumps with no user impact). 4) Flag BREAKING changes explicitly and note any required migration step. 5) For each kept change, jot the raw description and the PR/commit reference. Write an acceptance-criteria checklist (e.g. 'every user-facing change is captured'; 'internal noise is excluded'; 'changes are bucketed correctly'; 'breaking changes flagged with migration notes'; 'version and date present'). Use write_task_note for the triaged change list + checklist, and write the same to the produces path. No prose changelog yet.\n\nThe deliverable `{{workPath}}/gather.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": "developer",
+      "advanceWhen": {
+        "file": "{{workPath}}/gather.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/gather.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/gather.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "gather",
+        "maxAttempts": 3
+      },
+      "next": "write"
+    },
+    {
+      "id": "write",
+      "name": "Write the changelog",
+      "description": "rewrite entries in plain, user-facing language",
+      "prompt": "Write the changelog from the triaged list in Keep a Changelog style. 1) Header: '## [version] - YYYY-MM-DD'. 2) Group entries under the standard H3 buckets (Added/Changed/Deprecated/Removed/Fixed/Security) — include only non-empty buckets. 3) Rewrite each entry as one plain sentence focused on what the USER can now do or what changed for them, not the implementation ('Added dark mode toggle in settings', not 'Implemented theme state reducer'). 4) Put BREAKING CHANGES in a prominent callout at the top with migration instructions. 5) Keep entries terse and parallel in structure; link PRs/issues if available. Output GitHub-flavored markdown. Save to the produces path and note bucket counts.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "CHANGELOG.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "CHANGELOG.md",
+            "bytes": 500
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkContains",
+            "scope": "standard",
+            "inputs": {
+              "file": "CHANGELOG.md",
+              "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+              "flags": "i"
+            }
+          }
+        ],
+        "onReject": "write",
+        "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": "Read CHANGELOG.md against the triaged list. Check EACH criterion and write PASS/FAIL: (a) every user-facing change from the triage is present; (b) internal noise (refactors, dep bumps, CI) is excluded; (c) entries are in the correct buckets; (d) breaking changes are prominently flagged with migration notes; (e) entries are in plain, user-focused language; (f) version header and date present. A changelog that dumps raw commit messages or buries a breaking change FAILS — loop back to write.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"write\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "consumes": [
+        {
+          "file": "CHANGELOG.md"
+        }
+      ],
+      "next": "write"
+    },
+    {
+      "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/ch/changelog-writeup/versions/1.0.2/test.json

@@ -0,0 +1,132 @@
+{
+  "schemaVersion": 1,
+  "title": "User-facing changelog from seeded release notes",
+  "objective": "Measure whether the changelog-writeup craftbook filters internal noise, buckets user-facing changes, and calls out breaking changes.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "In the `Changelog Writeup Eval` project, read `source/merged-changes.md` and write `CHANGELOG.md` for version 2.4.0 dated 2026-06-27. Include user-facing Added, Changed, Fixed, and Security buckets as appropriate, exclude internal-only noise, and put the breaking API change in a prominent migration note.",
+  "setup": {
+    "projectName": "Changelog Writeup Eval",
+    "about": "Self-contained eval project for the changelog-writeup craftbook. Source changes are in workspace/source/merged-changes.md.",
+    "missionObjectives": "Produce a plain-language Keep a Changelog style CHANGELOG.md from seeded merged changes, excluding internal noise and highlighting breaking changes.",
+    "files": [
+      {
+        "path": "source/merged-changes.md",
+        "content": "# Merged Changes Since 2.3.0\n\n- PR #418 Added CSV export for filtered inventory reports.\n- PR #421 Changed webhook payload field `customerId` to `customer_id`; breaking for existing integrations.\n- PR #424 Fixed duplicate shipment status emails when labels were regenerated.\n- PR #425 Security: tightened SAML certificate expiry validation.\n- PR #426 Internal: refactored reducer names; no user-facing change.\n- PR #427 CI: upgraded lint runner.\n"
+      }
+    ],
+    "worker": {
+      "name": "Maud",
+      "role": "Writer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "workspace/CHANGELOG.md has version/date, buckets, user-facing entries, breaking migration note, and excludes internal noise.",
+    "deliverables": [
+      {
+        "path": "CHANGELOG.md",
+        "kind": "markdown-doc",
+        "minBytes": 1200,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "2\\.4\\.0|2026-06-27"
+          },
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "Added",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "Changed",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "Fixed",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "Security",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "CSV export|inventory reports",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "customerId|customer_id|migration|breaking",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "CHANGELOG.md",
+            "pattern": "duplicate shipment status emails|SAML",
+            "flags": "i"
+          },
+          {
+            "kind": "notContains",
+            "file": "CHANGELOG.md",
+            "pattern": "reducer|lint runner|CI:",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "CHANGELOG.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "safety",
+        "description": "Dry-run posture is explicit: no real credentials, clear stop-before-side-effect boundary."
+      },
+      {
+        "name": "mapping",
+        "description": "Fake endpoints/commands are mapped completely to the workflow steps."
+      },
+      {
+        "name": "signals",
+        "description": "Success, failure, retry, and abort conditions are all defined."
+      },
+      {
+        "name": "containment",
+        "description": "The plan cannot accidentally reach a real service from a mock context."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "triage before writing",
+    "breaking change visibility",
+    "plain user language"
+  ],
+  "extensions": {
+    "legacySimulators": [
+      {
+        "id": "changelog-writeup-fake-service-fixture",
+        "kind": "data-source",
+        "status": "implemented",
+        "description": "Seeded local fake service contract replacing live CLIs, HTTP APIs, credentials, and side effects."
+      }
+    ]
+  }
+}

package/data/craftbook-templates/ch/chapter-narration-run/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "chapter-narration-run",
   "role": "general",
+  "category": "media",
   "name": "Narrate a Chapter",
   "description": "Take one chapter from manuscript to narrated audio, deliberately: a narration script with pronunciations and pauses marked before anything renders, the audio driven through the project's narration capabilities with a run log, and a listen-check against the text — no skipped paragraphs, no mangled names. Locks the chapter and the style sheet FIRST (voice, pace, every proper noun's pronunciation), then preps the script, then renders, then checks coverage. Use for narrating a chapter, audiobook recording runs, text-to-speech passes, and 'read chapter two aloud'.",
   "tags": [