@bendyline/gilde 0.1.37 → 0.1.39

package/data/craftbook-templates/se/seo-meta-pack/versions/1.0.2/craftbook.json

@@ -0,0 +1,117 @@
+{
+  "id": "seo-meta-pack",
+  "name": "SEO Metadata Pack",
+  "description": "Generate a complete on-page SEO metadata pack for a set of pages: it first scopes each page's primary keyword and search intent and the length/format rules (title tag, meta description, Open Graph, Twitter card, slug), then writes optimized, unique metadata for every page that respects pixel/character limits and front-loads the keyword, producing a structured JSON file ready to drop into a CMS or templating layer. Covers SEO metadata, meta tags, title tags, meta descriptions, Open Graph tags, social cards, and on-page SEO. Scoping the keyword and limits per page before writing is the point: a small model that fixes the rules first produces unique, limit-respecting tags across the whole set, instead of duplicate titles and descriptions that get truncated in the SERP.\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. Metadata scope (planner) — lock per-page keyword/intent and the metadata field rules → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Write the metadata (copywriter) — write unique, limit-respecting metadata for every page → gated on `seo-meta.json` (json)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "write seo meta tags",
+    "generate meta descriptions",
+    "title tags for pages",
+    "open graph tags",
+    "seo metadata pack"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Metadata scope",
+      "description": "lock per-page keyword/intent and the metadata field rules",
+      "prompt": "1) List the pages in scope; for EACH, identify its primary keyword/phrase and search intent in one line. 2) Lock the field schema and limits: title tag (50-60 chars, keyword near front, brand suffix policy), meta description (140-155 chars, includes keyword + a soft CTA), URL slug (lowercase, hyphenated, keyword-based), Open Graph (og:title, og:description, og:type), and Twitter card (card type, title, description). 3) Set the duplicate policy: every title and description must be UNIQUE across pages. Write an acceptance-criteria checklist (e.g. 'every page has all fields'; 'titles 50-60 chars, descriptions 140-155 chars'; 'primary keyword present and front-loaded in title'; 'no duplicate titles or descriptions across pages'; 'slugs are valid kebab-case'; 'OG/Twitter fields populated'). Use write_task_note for the per-page keyword map + field rules + checklist, and write the same to the produces path. No metadata 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": "build"
+    },
+    {
+      "id": "build",
+      "name": "Write the metadata",
+      "description": "write unique, limit-respecting metadata for every page",
+      "prompt": "Write the metadata for EVERY page in scope to the locked schema. 1) For each page: a title tag (50-60 chars, primary keyword front-loaded, brand suffix per policy), a meta description (140-155 chars with the keyword and a soft CTA), a kebab-case slug, and the Open Graph + Twitter card fields. 2) Count characters for title and description and stay within range — do not exceed limits or they truncate in the SERP. 3) Ensure NO title and NO description is duplicated across pages. 4) Make each compelling and accurate to the page, not keyword-stuffed. 5) Output a single valid JSON array, one object per page: {\"page\", \"title\", \"titleChars\", \"metaDescription\", \"descChars\", \"slug\", \"og\": {\"title\",\"description\",\"type\"}, \"twitter\": {\"card\",\"title\",\"description\"}}. Save to the produces path and note the page count.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "seo-meta.json",
+        "minBytes": 1,
+        "sniff": "json-valid"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "seo-meta.json",
+            "bytes": 2
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkJsonValid",
+            "scope": "standard",
+            "inputs": {
+              "file": "seo-meta.json"
+            }
+          }
+        ],
+        "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": "Parse seo-meta.json (must be valid JSON) and grade against the checklist. Check EACH criterion and write PASS/FAIL: (a) every page in scope has an object with all fields populated; (b) titles are 50-60 chars and descriptions 140-155 chars (verify the char counts); (c) the primary keyword is present and front-loaded in each title; (d) no duplicate titles or descriptions across pages; (e) slugs are valid lowercase kebab-case; (f) OG and Twitter fields are populated. A pack with truncated, duplicate, or missing metadata FAILS — loop back to build and name the offending pages.\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": "seo-meta.json"
+        }
+      ],
+      "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/se/seo-meta-pack/versions/1.0.2/test.json

@@ -0,0 +1,100 @@
+{
+  "schemaVersion": 1,
+  "title": "SEO Metadata Pack smoke eval",
+  "objective": "Self-contained smoke eval for the SEO Metadata Pack 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": "SEO Metadata Pack Eval",
+    "about": "Self-contained eval project for seo-meta-pack. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/index.html.",
+    "missionObjectives": "Use the SEO Metadata Pack 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": "# SEO Metadata Pack 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: seo-meta-pack - SEO Metadata Pack.\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/so/social-digest/versions/1.0.1/craftbook.json

@@ -0,0 +1,140 @@
+{
+  "id": "social-digest",
+  "name": "Social Digest",
+  "description": "Read everything new on the synced social feeds since the lookback window opened, then compose a grounded morning digest: per-feed activity, notable mentions and replies, engagement movers, and 1-3 suggested next moves carrying one-click gezel-action blocks (fire the draft-social-post craftbook with a prefilled topic, or a reply task for a mention worth answering). Every number in the digest must trace to a synced record via the scan notes — no invented metrics. Runs happily with no connector bound: it reports from posts/index.json alone and names the missing corpus as a gap.",
+  "entryStepId": "scan",
+  "triggers": [
+    "social digest",
+    "what happened on our feeds",
+    "engagement digest",
+    "overnight social summary"
+  ],
+  "command": "social-digest",
+  "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}}"
+      },
+      "lookbackHours": {
+        "type": "integer",
+        "default": 24,
+        "description": "How many hours back to scan for new records. Default 24."
+      }
+    }
+  },
+  "runModes": {
+    "nightShift": "recommended",
+    "scheduled": "supported"
+  },
+  "connectors": [
+    {
+      "typeId": "bluesky-posts",
+      "optional": true,
+      "reason": "Read the synced Bluesky posts, mentions, and engagement counts the digest reports on."
+    },
+    {
+      "typeId": "x-posts",
+      "optional": true,
+      "reason": "Read the synced X posts, mentions, and engagement counts the digest reports on."
+    },
+    {
+      "typeId": "instagram-media",
+      "optional": true,
+      "reason": "Read the synced Instagram records so captions and comments show up in the digest."
+    }
+  ],
+  "steps": [
+    {
+      "id": "scan",
+      "name": "Scan the feeds",
+      "description": "Collect raw notes from every synced corpus record in the window — the only numbers the digest may cite.",
+      "suggestedRole": "omroeper",
+      "prompt": "You are collecting the raw material for the overnight social digest. Look back {{lookbackHours}} hours (if that value reads as a raw {{...}} placeholder, use the default: 24).\n\n1. Call `list_artifacts` on `data/` in the project artifacts. Each subfolder there is one synced feed corpus (Bluesky, X, Instagram, ...); its `_meta.json` names the feed and the last sync. If there is no `data/` folder, nothing is synced: still write the notes artifact, open it with the line \"no synced corpus this run\", record what `posts/index.json` says we published lately, and never invent feed activity.\n2. Read every record inside the window with `read_artifact` — records are markdown files with frontmatter under each corpus, organized newest-first by folder. Collect per feed: posts by us, mentions and replies (author handle plus a short verbatim quote), and each record's engagement counts (`likes`, `reposts`, `replies`) together with its `metrics_updated_at` stamp.\n3. Read `posts/index.json` in the workspace with `read_file` so the digest can match feed records to the posts we shipped.\n4. Write your raw notes to the artifact `{{workPath}}/reports/social-digest-notes.md` with `write_artifact`: one section per feed, and every count copied verbatim next to the record path it came from (for example `data/bluesky/posts/2026-08/2026-08-02-meet-the-makers.md`). These notes are the only source of numbers the digest step may cite.\n\nWhen the notes artifact is written, call `advance_task_step` to move to compose.",
+      "advanceWhen": {
+        "file": "{{workPath}}/reports/social-digest-notes.md",
+        "artifact": true,
+        "minBytes": 150
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/reports/social-digest-notes.md",
+            "bytes": 150,
+            "artifact": true
+          }
+        ],
+        "maxAttempts": 3
+      },
+      "next": "compose"
+    },
+    {
+      "id": "compose",
+      "name": "Compose the digest",
+      "description": "Write the morning digest from the scan notes, ending with 1-3 one-click actions.",
+      "suggestedRole": "omroeper",
+      "prompt": "Write the digest from `{{workPath}}/reports/social-digest-notes.md` (read it with `read_artifact` first). Every number you cite must appear in those notes — no other source of numbers is allowed.\n\nWrite the digest to the artifact `{{workPath}}/reports/social-digest-<today YYYY-MM-DD>.md` with `write_artifact` (use today's real date in the filename), then write the exact same content to `{{workPath}}/reports/social-digest-latest.md` — the stable path the completion gate reads. Write the latest file last. Sections, in order:\n\n- `## What happened on each feed` — one short block per synced feed; when a feed has no corpus or no new activity, say so in one line.\n- `## Notable mentions & replies` — who said what: name each author, quote them briefly, and say whether the mention deserves a reply.\n- `## Engagement movers` — which of our posts moved: compare the engagement counts and their `metrics_updated_at` stamps from the notes, and call out over- and under-performers. Never invent a number.\n- `## Suggested next moves` — 1-3 concrete suggestions. When a suggestion is directly actionable, follow it with a ```gezel-action fenced YAML block so the user can fire it with one click in the morning. Rules for these blocks: one block per action; flat YAML keys (only `params` nests one level); each block carries a unique, stable `id` slug that stays the same when tomorrow's digest repeats the suggestion; keep `title` short and `reason` to a sentence or two; never invent craftbook ids — the only craftbook you may reference is `draft-social-post`, which ships alongside this workflow. Two kinds:\n\nTo suggest drafting a post (prefill the topic):\n```gezel-action\nkind: fire-craftbook\nid: draft-<short-topic-slug>\ntitle: Draft a post about <thing>\nreason: <why, one sentence grounded in the notes>\ncraftbookId: draft-social-post\nparams:\n  topic: <the suggested topic>\n```\n\nTo suggest replying to a mention (a bespoke task with a concrete prompt):\n```gezel-action\nkind: create-task\nid: reply-<author-slug>\ntitle: Reply to <author>\nreason: <why this mention matters, one sentence>\nprompt: Read <record path> in the project artifacts and draft a reply in our voice for the user to approve. Do not post it.\nrole: omroeper\n```\n\nWhen both digest files are written, call `advance_task_step` to move to evaluate.",
+      "advanceWhen": {
+        "file": "{{workPath}}/reports/social-digest-latest.md",
+        "artifact": true,
+        "minBytes": 400,
+        "requireChange": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/reports/social-digest-latest.md",
+            "bytes": 400,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/reports/social-digest-latest.md",
+            "pattern": "```gezel-action",
+            "label": "digest carries at least one one-click action",
+            "artifact": true
+          },
+          {
+            "kind": "judge",
+            "file": "{{workPath}}/reports/social-digest-latest.md",
+            "rubric": "Every count or metric named in the digest appears verbatim in the scan notes; mentions name real authors from the notes; nothing is invented.",
+            "sourceFiles": [
+              "{{workPath}}/reports/social-digest-notes.md"
+            ],
+            "label": "no invented metrics",
+            "artifact": true
+          }
+        ],
+        "onReject": "compose",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the digest against every criterion. All pass — finish; any fail — loop back to compose with the named gaps.",
+      "suggestedRole": "reviewer",
+      "prompt": "Open `{{workPath}}/reports/social-digest-latest.md` and `{{workPath}}/reports/social-digest-notes.md` with `read_artifact` and grade the digest. Check EACH criterion and write PASS/FAIL with a one-line reason:\n\n1. Every number in the digest appears in the notes (spot-check at least three).\n2. Each feed present in the notes is covered — or its silence is stated in one line.\n3. Mentions name their authors and quote them accurately.\n4. The engagement-movers section compares real counts from the notes, not impressions.\n5. There are 1-3 suggested next moves, and every ```gezel-action block is valid flat YAML with `kind`, `id`, `title`, `reason`, and — for fire-craftbook — `craftbookId: draft-social-post` only.\n6. The digest is tight enough to read over coffee: no padding, no repeated sections.\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 task notes with `write_task_note`, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"compose\" })` to loop back. The compose step fixes exactly those gaps.\n\nNever route to finish while a criterion is unmet. After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "next": "compose"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "Stamp the summary note and stop.",
+      "suggestedRole": "omroeper",
+      "prompt": "Write a one-paragraph DONE summary with `write_task_note`: the digest artifact paths (the dated file and `{{workPath}}/reports/social-digest-latest.md`), the headline in one line, how many mentions deserve a reply, and how many one-click actions the digest carries. Report DONE.",
+      "terminal": true
+    }
+  ],
+  "version": "1.0.1",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/so/social-digest/versions/1.0.1/test.json

@@ -0,0 +1,169 @@
+{
+  "schemaVersion": 1,
+  "title": "Overnight digest grounded in a synced Bluesky corpus",
+  "objective": "Prove that social-digest reads the synced corpus records, names the people who mentioned us, reports engagement movers without inventing a number, and leaves one-click follow-up actions.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "Run the Social Digest craftbook for this project. Treat every synced record in the artifacts drawer as inside the digest window (the lookback parameter is set very wide for this eval). Write the digest artifact, ground every number in the synced records via your scan notes, name the people who mentioned us, and close with suggested next moves carrying at least one one-click gezel-action block.",
+  "setup": {
+    "projectName": "Social Digest Eval",
+    "about": "Overnight digest eval for a small furniture workshop's Bluesky presence. The artifacts drawer carries a synced corpus of the account's posts plus two mentions; the workspace carries the post index.",
+    "missionObjectives": "Produce the morning social digest as a real craftbook task: scan notes first, then the digest with per-feed activity, both mentions named and quoted, engagement movers compared from real counts, and 1-3 suggested next moves with gezel-action blocks referencing only the draft-social-post craftbook.",
+    "files": [
+      {
+        "path": "posts/index.json",
+        "content": "{\n  \"entries\": [\n    {\n      \"slug\": \"shop-refresh\",\n      \"folder\": \"posts/2026-07-20-shop-refresh\",\n      \"title\": \"The shop got a fresh coat\",\n      \"status\": \"published\",\n      \"platforms\": [\"bluesky\"],\n      \"created\": \"2026-07-20\"\n    },\n    {\n      \"slug\": \"meet-the-makers\",\n      \"folder\": \"posts/2026-08-01-meet-the-makers\",\n      \"title\": \"Meet the makers\",\n      \"status\": \"published\",\n      \"platforms\": [\"bluesky\"],\n      \"created\": \"2026-08-01\"\n    },\n    {\n      \"slug\": \"oak-bench-run\",\n      \"folder\": \"posts/2026-08-07-oak-bench-run\",\n      \"title\": \"A short run of oak benches\",\n      \"status\": \"published\",\n      \"platforms\": [\"bluesky\"],\n      \"created\": \"2026-08-07\"\n    }\n  ]\n}\n"
+      },
+      {
+        "path": "data/bluesky/_meta.json",
+        "surface": "artifact",
+        "content": "{\n  \"bindingId\": \"bluesky-workshop\",\n  \"typeId\": \"bluesky-posts\",\n  \"displayName\": \"Bluesky — @bankenbeitel.bsky.social\",\n  \"completeness\": \"window\",\n  \"lastSyncedAt\": \"2026-08-12T05:00:00Z\"\n}\n"
+      },
+      {
+        "path": "data/bluesky/posts/2026-07/2026-07-20-shop-refresh.md",
+        "surface": "artifact",
+        "content": "---\nrecord: post\nplatform: bluesky\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3kshop001\nauthor: bankenbeitel.bsky.social\ncreatedAt: 2026-07-20T09:05:00Z\nlikes: 14\nreposts: 2\nreplies: 1\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nThe shop got a fresh coat over the weekend. Same bench, better light. Come by and see.\n"
+      },
+      {
+        "path": "data/bluesky/posts/2026-07/2026-07-24-sharpening-night.md",
+        "surface": "artifact",
+        "content": "---\nrecord: post\nplatform: bluesky\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3ksharp01\nauthor: bankenbeitel.bsky.social\ncreatedAt: 2026-07-24T18:30:00Z\nlikes: 9\nreposts: 1\nreplies: 0\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nSharpening night. Every chisel in the rack gets its turn.\n"
+      },
+      {
+        "path": "data/bluesky/posts/2026-07/2026-07-27-glue-up.md",
+        "surface": "artifact",
+        "content": "---\nrecord: post\nplatform: bluesky\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3kglue001\nauthor: bankenbeitel.bsky.social\ncreatedAt: 2026-07-27T11:10:00Z\nlikes: 11\nreposts: 0\nreplies: 2\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nBig glue-up day. Twelve clamps, one tabletop, no room for lunch on the bench.\n"
+      },
+      {
+        "path": "data/bluesky/posts/2026-08/2026-08-01-meet-the-makers.md",
+        "surface": "artifact",
+        "content": "---\nrecord: post\nplatform: bluesky\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3kmake001\nauthor: bankenbeitel.bsky.social\ncreatedAt: 2026-08-01T10:00:00Z\nlikes: 63\nreposts: 19\nreplies: 8\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nMeet the makers: three of us, one bench, thirty years of chisels between us.\n"
+      },
+      {
+        "path": "data/bluesky/posts/2026-08/2026-08-04-workbench-tour.md",
+        "surface": "artifact",
+        "content": "---\nrecord: post\nplatform: bluesky\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3ktour001\nauthor: bankenbeitel.bsky.social\ncreatedAt: 2026-08-04T09:20:00Z\nlikes: 22\nreposts: 4\nreplies: 3\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nA thirty-second tour of the bench: shooting board, bench hooks, and the drawer of mystery screws.\n"
+      },
+      {
+        "path": "data/bluesky/posts/2026-08/2026-08-07-oak-bench-run.md",
+        "surface": "artifact",
+        "content": "---\nrecord: post\nplatform: bluesky\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3koak0001\nauthor: bankenbeitel.bsky.social\ncreatedAt: 2026-08-07T08:45:00Z\nlikes: 37\nreposts: 11\nreplies: 5\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nA short run of oak benches: six pieces, numbered and signed. First come, first seated.\n"
+      },
+      {
+        "path": "data/bluesky/posts/2026-08/2026-08-09-offcut-boxes.md",
+        "surface": "artifact",
+        "content": "---\nrecord: post\nplatform: bluesky\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3kbox0001\nauthor: bankenbeitel.bsky.social\ncreatedAt: 2026-08-09T16:00:00Z\nlikes: 8\nreposts: 0\nreplies: 1\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nOffcut boxes back in the window. Small wood, small prices.\n"
+      },
+      {
+        "path": "data/bluesky/posts/2026-08/2026-08-10-finish-test.md",
+        "surface": "artifact",
+        "content": "---\nrecord: post\nplatform: bluesky\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3kfin0001\nauthor: bankenbeitel.bsky.social\ncreatedAt: 2026-08-10T13:30:00Z\nlikes: 12\nreposts: 2\nreplies: 4\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nThree finishes on the same oak offcut: raw, oiled, soaped. Which would you take home?\n"
+      },
+      {
+        "path": "data/bluesky/posts/2026-08/2026-08-11-bench-dog.md",
+        "surface": "artifact",
+        "content": "---\nrecord: post\nplatform: bluesky\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3kdog0001\nauthor: bankenbeitel.bsky.social\ncreatedAt: 2026-08-11T09:00:00Z\nlikes: 5\nreposts: 0\nreplies: 0\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nNew bench dogs turned from leftover beech. The old ones earned their retirement.\n"
+      },
+      {
+        "path": "data/bluesky/mentions/2026-08/2026-08-10-meike-commission.md",
+        "surface": "artifact",
+        "content": "---\nrecord: mention\nplatform: bluesky\npostId: at://did:plc:meike/app.bsky.feed.post/3kmen0001\nauthor: meike.bsky.social\ninReplyTo: at://did:plc:bankenbeitel/app.bsky.feed.post/3kmake001\ncreatedAt: 2026-08-10T18:40:00Z\nlikes: 9\nreposts: 1\nreplies: 2\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nWent by the workshop after seeing this — walked out with a stool and a story. Do you take commissions for a matching bench?\n"
+      },
+      {
+        "path": "data/bluesky/mentions/2026-08/2026-08-11-stef-vandam-question.md",
+        "surface": "artifact",
+        "content": "---\nrecord: mention\nplatform: bluesky\npostId: at://did:plc:stefvandam/app.bsky.feed.post/3kmen0002\nauthor: stef-vandam.bsky.social\ninReplyTo: at://did:plc:bankenbeitel/app.bsky.feed.post/3kfin0001\ncreatedAt: 2026-08-11T20:15:00Z\nlikes: 3\nreposts: 0\nreplies: 1\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nSoaped, every time. Does the soap finish hold up on a kitchen table, or is that asking for water rings?\n"
+      }
+    ],
+    "craftbookParams": {
+      "lookbackHours": "87600",
+      "workPath": "tasks/eval"
+    },
+    "worker": {
+      "name": "Nora",
+      "role": "Omroeper"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The digest artifact exists at its stable path, names both mention authors, compares real engagement counts, and carries at least one gezel-action block; the scan notes artifact grounds every number.",
+    "checks": [
+      {
+        "kind": "minBytes",
+        "file": "tasks/eval/reports/social-digest-notes.md",
+        "bytes": 150,
+        "artifact": true
+      },
+      {
+        "kind": "minBytes",
+        "file": "tasks/eval/reports/social-digest-latest.md",
+        "bytes": 400,
+        "artifact": true
+      },
+      {
+        "kind": "contains",
+        "file": "tasks/eval/reports/social-digest-latest.md",
+        "pattern": "meike",
+        "flags": "i",
+        "label": "names the first mention author",
+        "artifact": true
+      },
+      {
+        "kind": "contains",
+        "file": "tasks/eval/reports/social-digest-latest.md",
+        "pattern": "stef-vandam|stef vandam",
+        "flags": "i",
+        "label": "names the second mention author",
+        "artifact": true
+      },
+      {
+        "kind": "contains",
+        "file": "tasks/eval/reports/social-digest-latest.md",
+        "pattern": "```gezel-action",
+        "label": "carries at least one one-click action",
+        "artifact": true
+      },
+      {
+        "kind": "contains",
+        "file": "tasks/eval/reports/social-digest-latest.md",
+        "pattern": "meet-the-makers|Meet the makers",
+        "label": "the standout post shows up in the digest",
+        "artifact": true
+      }
+    ],
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    },
+    "unchangedFixtures": [
+      "posts/index.json"
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/reports/social-digest-latest.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "grounding",
+        "description": "Every count in the digest appears in the seeded records; mentions are quoted accurately and attributed to meike.bsky.social and stef-vandam.bsky.social."
+      },
+      {
+        "name": "structure",
+        "description": "The four sections are present and each does its job: per-feed activity, mention triage, engagement movers compared from real counts, and suggested next moves."
+      },
+      {
+        "name": "actionability",
+        "description": "The gezel-action blocks are valid flat YAML with stable id slugs, reference only draft-social-post, and the suggestions follow from the evidence (e.g. people-first posts outperforming)."
+      }
+    ],
+    "contextNote": "The digest is an artifacts-drawer report; the lookback parameter was set very wide so all seeded records fall inside the window."
+  },
+  "qualityFocus": [
+    "every metric traceable to a synced record",
+    "mention triage names authors and quotes them",
+    "one-click actions valid and never inventing craftbook ids"
+  ]
+}