@bendyline/gilde 0.1.50 → 0.1.52

package/data/craftbook-templates/br/broadcast-announcement/versions/1.0.3/craftbook.json

@@ -0,0 +1,219 @@
+{
+  "id": "broadcast-announcement",
+  "name": "Multi-Channel Broadcast Announcement",
+  "description": "Adapt a single announcement (launch, policy change, maintenance window, org news) into channel-tailored variants — email, Slack/Teams post, status-page note, and a short SMS/push — that carry one consistent core message at the right length and tone for each surface. Scopes the core message and the per-channel constraints FIRST (the single source of truth, the CTA, character/format limits and tone per channel, the must-include facts), then a copywriter writes every variant from that locked core so nothing contradicts across channels. Scoping the core before adapting is what keeps the facts, dates, and CTA identical everywhere while the voice fits each surface. Use for announcements, multi-channel comms, launch messaging, maintenance notices, and broadcasting one message everywhere.\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 message (planner) — lock the core message, CTA, and per-channel constraints → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Write the variants (copywriter) — adapt the core into channel-tailored variants → gated on `announcement.md` (markdown-doc)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "multi-channel announcement",
+    "broadcast a message",
+    "launch announcement",
+    "maintenance notice",
+    "announce this everywhere"
+  ],
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  },
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the message",
+      "description": "lock the core message, CTA, and per-channel constraints",
+      "prompt": "Define the announcement's single source of truth before writing variants. (1) Write the CORE message: the one thing being announced, the must-include facts (what, when/effective date, who's affected, why), and the single CTA. (2) Lock the channel list and each channel's constraints: email (subject + ~150 words, formal-friendly), Slack/Teams (~60 words, conversational, threaded details), status-page note (~40 words, neutral/factual), SMS/push (≤160 chars, urgent-but-calm, link only). (3) State the tone per channel and any compliance/do-not-say constraints. Write an acceptance-criteria checklist ('a variant exists for every channel', 'the core facts/dates/CTA are identical across all variants', 'each variant respects its length/format limit', 'each variant matches its channel tone', 'no variant contradicts another') plus the core message + per-channel constraint table to {{workPath}}/scope.md via write_task_note AND the produces path. No variants yet.\n\nThe deliverable `{{workPath}}/scope.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "planner",
+      "advanceWhen": {
+        "file": "{{workPath}}/scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "scope",
+        "maxAttempts": 3
+      },
+      "next": "write",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "artifact",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      }
+    },
+    {
+      "id": "write",
+      "name": "Write the variants",
+      "description": "adapt the core into channel-tailored variants",
+      "prompt": "Write announcement.md with one labeled section per channel, all derived from the locked core. (1) Email: a subject line plus a ~150-word body covering all must-include facts and the CTA, formal-friendly. (2) Slack/Teams: ~60 conversational words with the headline + CTA and a note that details follow. (3) Status-page: ~40 neutral, factual words stating what/when/impact. (4) SMS/push: ≤160 characters, the essential fact + CTA link, calm. Keep the facts, the effective date, and the CTA WORD-FOR-WORD consistent (where the medium allows) across every variant — only length and voice change. Stay within each length limit; count characters for SMS. Invent no facts beyond the core. On a loop-back fix only the flagged variants. Write the path and the per-channel lengths to notes via write_task_note.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "announcement.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "announcement.md",
+            "bytes": 500
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkContains",
+            "scope": "standard",
+            "inputs": {
+              "file": "announcement.md",
+              "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+              "flags": "i"
+            }
+          }
+        ],
+        "onReject": "write",
+        "maxAttempts": 4
+      },
+      "next": "evaluate",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web"
+        ],
+        "outputMedium": "workspace",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      }
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "QA announcement.md against the locked criteria. (1) Confirm a variant exists for every channel in scope. (2) Cross-check the core facts, the effective date, and the CTA across all variants — any contradiction or drifted date/CTA is FAIL. (3) Check each variant against its length/format limit (count the SMS characters, ~word counts for the others). (4) Read each for channel-appropriate tone. (5) Confirm no fact was invented beyond the locked core. Write PASS/FAIL per criterion with the specific variants at fault.\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": "announcement.md"
+        }
+      ],
+      "next": "write",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "task-note"
+      }
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
+      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
+      "suggestedRole": "developer",
+      "terminal": true,
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "task-note"
+      }
+    }
+  ],
+  "version": "1.0.3",
+  "releasedAt": "2026-09-01T20:00:00Z",
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/br/broadcast-announcement/versions/1.0.3/test.json

@@ -0,0 +1,103 @@
+{
+  "schemaVersion": 1,
+  "title": "Multi-channel announcement variants",
+  "objective": "Measure whether the broadcast-announcement craftbook locks a single source of truth before adapting channel-specific variants.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "In the `Broadcast Announcement Eval` project, read `source/message-brief.md` and write `announcement.md` with Email, Slack/Teams, Status page, and SMS/Push variants. Keep the effective date and CTA consistent across all variants. Do not include a restrictions, prohibited-words, or checklist section in the deliverable; silently omit any forbidden terms.",
+  "setup": {
+    "projectName": "Broadcast Announcement Eval",
+    "about": "Self-contained eval project for broadcast-announcement. The core message is in workspace/source/message-brief.md.",
+    "missionObjectives": "Create channel-tailored announcement variants with identical facts, date, CTA, and no contradictions.",
+    "files": [
+      {
+        "path": "source/message-brief.md",
+        "content": "# Core message\n\nAnnouncement: HarborCRM is launching guided returns intake for all Pro accounts.\nEffective date: July 15, 2026 at 09:00 Pacific.\nAudience: support leads and account admins.\nImpact: customers will submit order number, reason code, and photo evidence before an agent picks up the case.\nCTA: review the rollout checklist at https://status.boreal.example/returns.\nDo not say: no-cost, instant, guaranteed, or beta.\n"
+      }
+    ],
+    "worker": {
+      "name": "Eline",
+      "role": "Copywriter"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "workspace/announcement.md contains four channel variants with consistent core facts, date, CTA, and forbidden claims excluded.",
+    "deliverables": [
+      {
+        "path": "announcement.md",
+        "kind": "markdown-doc",
+        "minBytes": 1800,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "announcement.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "announcement.md",
+            "pattern": "Email|Slack|Teams|Status|SMS|Push",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "announcement.md",
+            "pattern": "July 15, 2026|09:00 Pacific",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "announcement.md",
+            "pattern": "https://status\\.boreal\\.example/returns",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "announcement.md",
+            "pattern": "guided returns intake|order number|reason code|photo evidence",
+            "flags": "i"
+          },
+          {
+            "kind": "notContains",
+            "file": "announcement.md",
+            "pattern": "no-cost|instant|guaranteed|beta",
+            "flags": "i",
+            "label": "forbidden launch claims must not appear anywhere, including restrictions, checklists, or meta notes"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "announcement.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": [
+    "single source of truth",
+    "channel adaptation",
+    "consistency checks"
+  ]
+}

package/data/craftbook-templates/br/browser-qa-audit/versions/2.0.5/test.json

@@ -23,10 +23,7 @@
         "content": "<!doctype html>\n<html lang=\"en\">\n<head>\n<meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width,initial-scale=1\">\n<title>Harbor Crew Signup</title>\n<style>\nbody{margin:0;background:#f6f7f8;color:#334;font:16px Arial,sans-serif}header{background:#10233f;color:#fff;padding:18px}.shell{width:980px;margin:32px auto;background:#fff;padding:24px}.muted{color:#c2c5ca}button,a,input{font:inherit}button:focus,a:focus,input:focus{outline:none}.nav{display:none}.card{border:1px solid #dde1e6;padding:20px}input{display:block;width:360px;padding:10px;margin:8px 0}.success{display:none;color:#16783b}a{color:#d97706}\n</style>\n</head>\n<body>\n<header><strong>Harbor Crew</strong> <span class=\"muted\">Shift updates without noise</span></header>\n<main class=\"shell\">\n<button id=\"menu\">Menu</button>\n<nav class=\"nav\"><a href=\"#signup\">Signup</a> <a href=\"missing-help.html\">Help</a></nav>\n<section class=\"card\" id=\"signup\">\n<h1>Join shift updates</h1>\n<p>One concise email before every assignment window.</p>\n<form id=\"signup-form\">\n<input id=\"email\" type=\"text\" placeholder=\"you@example.com\">\n<button type=\"submit\">Join</button>\n</form>\n<p class=\"success\" id=\"success\">Welcome aboard</p>\n</section>\n</main>\n<script>\nconsole.error('fixture-console-error: signup analytics failed');\ndocument.querySelector('#signup-form').addEventListener('submit',event=>{event.preventDefault();document.querySelector('#success').style.display='block'});\n</script>\n</body>\n</html>\n",
         "modelInput": false
       }
-    ],
-    "craftbookParams": {
-      "workPath": "tasks/eval"
-    }
+    ]
   },
   "mocks": [
     {