@bendyline/gilde 0.1.21 → 0.1.22

package/data/craftbook-templates/re/reception-report/manifest.json

@@ -0,0 +1,21 @@
+{
+  "schemaVersion": 1,
+  "kind": "craftbook-template",
+  "id": "reception-report",
+  "role": "maintenance-review",
+  "name": "Reception Report",
+  "description": "The weekly reception review for your social posting. Reconciles published posts with their live feed records (stamping the corpus reference onto any post that lost track of its live copy), builds a per-post engagement ledger of likes, reposts, and replies, compares each post against your account's recent baseline, and reports what landed, what did not, and what to post next — closing with a single one-click action that seeds the next draft from the strongest theme. Covers social media analytics, post performance review, engagement reporting, cadence tracking, Bluesky and X and Instagram metrics, and honest small-sample reading of your feeds. No connected feed? It still writes the ledger from what the workspace knows and names the gap.",
+  "tags": [
+    "social",
+    "analytics",
+    "engagement",
+    "report",
+    "weekly"
+  ],
+  "maintainer": {
+    "name": "Gezel"
+  },
+  "license": "MIT",
+  "yankedVersions": [],
+  "workflow": "build-loop"
+}

package/data/craftbook-templates/re/reception-report/versions/1.0.0/craftbook.json

@@ -0,0 +1,170 @@
+{
+  "id": "reception-report",
+  "name": "Reception Report",
+  "description": "Weekly review of how the posting landed: reconcile published posts with their live synced records (stamp corpusRef where it is missing), build a per-post engagement ledger, analyze each post against the account's recent baseline, then write the reception report — scoreboard, three findings, three recommendations, and exactly one one-click action seeding the next draft-social-post run with the strongest theme. Every metric must trace to the ledger, and the ledger to a synced record. Runs gracefully with no connector bound: the ledger then carries what the workspace knows, with metric cells marked as unknown.",
+  "entryStepId": "reconcile",
+  "triggers": [
+    "reception report",
+    "how did our posts do",
+    "social performance review",
+    "weekly social report"
+  ],
+  "command": "reception-report",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "lookbackDays": {
+        "type": "integer",
+        "default": 7,
+        "description": "How many days of posting the review covers. Default 7."
+      }
+    }
+  },
+  "runModes": {
+    "scheduled": "recommended",
+    "nightShift": "supported"
+  },
+  "connectors": [
+    {
+      "typeId": "bluesky-posts",
+      "optional": true,
+      "reason": "Match published posts to their live Bluesky records and read the engagement counts the ledger reports."
+    },
+    {
+      "typeId": "x-posts",
+      "optional": true,
+      "reason": "Match published posts to their live X records and read the engagement counts the ledger reports."
+    },
+    {
+      "typeId": "instagram-media",
+      "optional": true,
+      "reason": "Read the synced Instagram records so caption performance can join the ledger."
+    }
+  ],
+  "steps": [
+    {
+      "id": "reconcile",
+      "name": "Reconcile posts with live records",
+      "description": "Stamp missing corpusRef links and build the engagement ledger from the synced records.",
+      "suggestedRole": "omroeper",
+      "prompt": "You are reconciling our published posts with their live feed records, looking back {{lookbackDays}} days (if that value reads as a raw {{...}} placeholder, use the default: 7).\n\n1. Read `posts/index.json` with `read_file`, then each listed post folder's `post.md` and every file under its `variants/`. Collect every variant whose `status` is `published` or `scheduled`.\n2. For each collected variant MISSING a `corpusRef` in its frontmatter: find its live record in the project artifacts under `data/` (`list_artifacts`, then `read_artifact`) by matching the variant's `postId` or `permalink` against the record frontmatter — fall back to matching the opening text. When found, stamp it: call `record_publication` if it is in your function schema; otherwise edit the variant file with `write_file`, adding `corpusRef: <artifacts-relative record path>` (and `publishedAt` from the record when the variant lacks it). Leave variants that already carry `corpusRef` untouched.\n3. If there is no `data/` corpus at all, note \"no synced corpus — reconciliation skipped\" and still write the ledger from what the workspace knows, with unknown metric cells marked `-`.\n4. Write the artifact `reports/reception-ledger.md` with `write_artifact`: a markdown table, one row per published or scheduled variant, columns `Post` (slug), `Platform`, `Live record` (the corpusRef path or `-`), `Likes`, `Reposts`, `Replies`, `Metrics as of` (the record's `metrics_updated_at`). Copy every count verbatim from its record; use `-` where unknown. Below the table, add one line per reconciliation you performed this run.\n\nWhen the ledger artifact is written, call `advance_task_step` to move to analyze.",
+      "advanceWhen": {
+        "file": "reports/reception-ledger.md",
+        "artifact": true,
+        "minBytes": 150
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "reports/reception-ledger.md",
+            "bytes": 150,
+            "artifact": true
+          }
+        ],
+        "maxAttempts": 3
+      },
+      "next": "analyze"
+    },
+    {
+      "id": "analyze",
+      "name": "Analyze reception",
+      "description": "Read the ledger and work out what over- and under-performed against the account's own baseline.",
+      "suggestedRole": "omroeper",
+      "prompt": "Read `reports/reception-ledger.md` with `read_artifact`. Every number in your analysis must come from that ledger — cite the post slug next to each figure; no other source of numbers is allowed.\n\nWrite the artifact `reports/reception-analysis.md` with `write_artifact`:\n\n- `## Per-post` — each post against the account's recent baseline. The median of the ledger's like/repost/reply counts is a fine baseline; name the baseline you used.\n- `## What worked, what did not` — formats, themes, or posting times that over- or under-performed, each claim tied to specific ledger rows.\n- `## Cadence` — posts shipped in the window versus the project's cadence target when the mission or voice guide states one; when none is stated, say so and suggest a target.\n\nBe honest about small samples: with only a handful of posts, call patterns \"early signals\", never conclusions. When the analysis artifact is written, call `advance_task_step` to move to report.",
+      "advanceWhen": {
+        "file": "reports/reception-analysis.md",
+        "artifact": true,
+        "minBytes": 300
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "reports/reception-analysis.md",
+            "bytes": 300,
+            "artifact": true
+          },
+          {
+            "kind": "judge",
+            "file": "reports/reception-analysis.md",
+            "rubric": "Every metric named in the analysis appears in the ledger; baselines are computed from ledger rows, not invented; claims cite post slugs.",
+            "sourceFiles": [
+              "reports/reception-ledger.md"
+            ],
+            "label": "no metric absent from the ledger",
+            "artifact": true
+          }
+        ],
+        "onReject": "analyze",
+        "maxAttempts": 3
+      },
+      "next": "report"
+    },
+    {
+      "id": "report",
+      "name": "Write the reception report",
+      "description": "Scoreboard, three findings, three recommendations, and exactly one one-click next-post action.",
+      "suggestedRole": "omroeper",
+      "prompt": "Assemble the reception report from `reports/reception-ledger.md` and `reports/reception-analysis.md` (read both with `read_artifact`). Cite no number that is not in the ledger.\n\nWrite the report to the artifact `reports/reception-report-<today YYYY-MM-DD>.md` with `write_artifact` (use today's real date in the filename), then write the exact same content to `reports/reception-report-latest.md` — the stable path the completion gate reads. Write the latest file last. Structure:\n\n- `## Scoreboard` — the ledger table trimmed to `Post`, `Platform`, `Likes`, `Reposts`, `Replies`.\n- `## Findings` — exactly 3, each one sentence plus one line of supporting evidence from the ledger or analysis.\n- `## Recommendations` — exactly 3, each concrete enough to act on this week.\n- `## Next post` — one paragraph naming the strongest theme to post about next, followed by EXACTLY ONE ```gezel-action fenced YAML block. Rules for the block: flat YAML keys (only `params` nests one level); a unique `id` slug that stays stable across weekly runs unless the theme changes; short `title`; one-sentence `reason`; never invent craftbook ids — reference only `draft-social-post`, which ships alongside this workflow:\n\n```gezel-action\nkind: fire-craftbook\nid: next-post-<theme-slug>\ntitle: Draft the next post\nreason: <the strongest theme, grounded in the findings>\ncraftbookId: draft-social-post\nparams:\n  topic: <the suggested topic>\n```\n\nWhen both report files are written, call `advance_task_step` to move to evaluate.",
+      "advanceWhen": {
+        "file": "reports/reception-report-latest.md",
+        "artifact": true,
+        "minBytes": 400,
+        "requireChange": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "reports/reception-report-latest.md",
+            "bytes": 400,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "reports/reception-report-latest.md",
+            "pattern": "```gezel-action",
+            "label": "report carries the one-click next-post action",
+            "artifact": true
+          },
+          {
+            "kind": "judge",
+            "file": "reports/reception-report-latest.md",
+            "rubric": "Every metric in the report appears in the ledger; the findings follow from the analysis; there is exactly one gezel-action block and it references craftbookId draft-social-post with a topic grounded in the findings.",
+            "sourceFiles": [
+              "reports/reception-ledger.md",
+              "reports/reception-analysis.md"
+            ],
+            "label": "grounded scoreboard and single action",
+            "artifact": true
+          }
+        ],
+        "onReject": "report",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the report against every criterion. All pass — finish; any fail — loop back to report with the named gaps.",
+      "suggestedRole": "reviewer",
+      "prompt": "Open `reports/reception-report-latest.md`, `reports/reception-analysis.md`, and `reports/reception-ledger.md` with `read_artifact` and grade the report. Check EACH criterion and write PASS/FAIL with a one-line reason:\n\n1. The scoreboard covers every ledger row (no post silently dropped).\n2. Every number in the report traces to the ledger (spot-check at least three).\n3. There are exactly 3 findings, each with evidence.\n4. There are exactly 3 recommendations, each actionable this week.\n5. There is exactly one ```gezel-action block, it is valid flat YAML, and its `craftbookId` is `draft-social-post` with a `params.topic` seeded from the strongest theme.\n6. Small samples are read honestly — early signals, not sweeping conclusions.\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: \"report\" })` to loop back. The report 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": "report"
+    },
+    {
+      "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 report artifact paths (the dated file and `reports/reception-report-latest.md`), the top finding in one line, how many posts were reconciled this run, and the recommended next topic. Report DONE.",
+      "terminal": true
+    }
+  ],
+  "version": "1.0.0",
+  "releasedAt": "2026-08-12T00:00:00Z"
+}

package/data/craftbook-templates/re/reception-report/versions/1.0.0/test.json

@@ -0,0 +1,168 @@
+{
+  "schemaVersion": 1,
+  "title": "Weekly reception review with a reconciliation gap",
+  "objective": "Prove that reception-report stamps the missing corpusRef onto a published post, builds a ledger covering every published post, and writes a grounded report with exactly one next-post action.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "Run the Reception Report craftbook for this project. Treat every synced record in the artifacts drawer as inside the review window (the lookback parameter is set very wide for this eval). One published post — returns-faq — is missing its corpusRef; reconcile it against the synced records, build the reception ledger covering all three published posts, and write the weekly reception report with its single one-click next-post action.",
+  "setup": {
+    "projectName": "Reception Report Eval",
+    "about": "Weekly reception review eval for a small furniture workshop's Bluesky presence. Three published posts sit in the workspace posts tree — one missing its corpusRef — and their live records with engagement counts sit in the artifacts drawer.",
+    "missionObjectives": "Reconcile posts/2026-08-08-returns-faq/variants/bluesky.md with its live record (stamp corpusRef), build reports/reception-ledger.md covering summer-sale, behind-the-scenes, and returns-faq with verbatim counts, analyze against the account baseline, and write the reception report with exactly one gezel-action block firing draft-social-post.",
+    "files": [
+      {
+        "path": "posts/index.json",
+        "content": "{\n  \"entries\": [\n    {\n      \"slug\": \"summer-sale\",\n      \"folder\": \"posts/2026-07-28-summer-sale\",\n      \"title\": \"Summer sale on seconds\",\n      \"status\": \"published\",\n      \"platforms\": [\"bluesky\"],\n      \"created\": \"2026-07-28\"\n    },\n    {\n      \"slug\": \"behind-the-scenes\",\n      \"folder\": \"posts/2026-08-03-behind-the-scenes\",\n      \"title\": \"Behind the scenes at the bench\",\n      \"status\": \"published\",\n      \"platforms\": [\"bluesky\"],\n      \"created\": \"2026-08-03\"\n    },\n    {\n      \"slug\": \"returns-faq\",\n      \"folder\": \"posts/2026-08-08-returns-faq\",\n      \"title\": \"Your returns questions, answered\",\n      \"status\": \"published\",\n      \"platforms\": [\"bluesky\"],\n      \"created\": \"2026-08-08\"\n    }\n  ]\n}\n"
+      },
+      {
+        "path": "posts/2026-07-28-summer-sale/post.md",
+        "content": "---\nstatus: published\ntitle: Summer sale on seconds\nslug: summer-sale\nplatforms: [bluesky]\ncreated: 2026-07-28\ntags: [sale]\n---\nSeconds shelf is full: benches and boxes with honest scars, priced to leave. Ends Sunday.\n"
+      },
+      {
+        "path": "posts/2026-07-28-summer-sale/variants/bluesky.md",
+        "content": "---\nplatform: bluesky\ncharCount: 96\nstatus: published\npublishedAt: 2026-07-28T09:00:00Z\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3ksale001\npermalink: https://bsky.app/profile/bankenbeitel.bsky.social/post/3ksale001\ncorpusRef: data/bluesky/posts/2026-07/2026-07-28-summer-sale.md\n---\nSeconds shelf is full: benches and boxes with honest scars, priced to leave. Ends Sunday.\n"
+      },
+      {
+        "path": "posts/2026-08-03-behind-the-scenes/post.md",
+        "content": "---\nstatus: published\ntitle: Behind the scenes at the bench\nslug: behind-the-scenes\nplatforms: [bluesky]\ncreated: 2026-08-03\ntags: [workshop]\n---\nWhat a Tuesday actually looks like here: glue squeeze-out, sharpening breaks, and the radio arguing with itself.\n"
+      },
+      {
+        "path": "posts/2026-08-03-behind-the-scenes/variants/bluesky.md",
+        "content": "---\nplatform: bluesky\ncharCount: 113\nstatus: published\npublishedAt: 2026-08-03T10:30:00Z\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3kbts0001\npermalink: https://bsky.app/profile/bankenbeitel.bsky.social/post/3kbts0001\ncorpusRef: data/bluesky/posts/2026-08/2026-08-03-behind-the-scenes.md\n---\nWhat a Tuesday actually looks like here: glue squeeze-out, sharpening breaks, and the radio arguing with itself.\n"
+      },
+      {
+        "path": "posts/2026-08-08-returns-faq/post.md",
+        "content": "---\nstatus: published\ntitle: Your returns questions, answered\nslug: returns-faq\nplatforms: [bluesky]\ncreated: 2026-08-08\ntags: [returns]\n---\nYour returns questions, answered: what the new desk takes back, how long it takes, and what needs no receipt.\n"
+      },
+      {
+        "path": "posts/2026-08-08-returns-faq/variants/bluesky.md",
+        "content": "---\nplatform: bluesky\ncharCount: 109\nstatus: published\npublishedAt: 2026-08-08T09:15:00Z\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3kfaq0001\npermalink: https://bsky.app/profile/bankenbeitel.bsky.social/post/3kfaq0001\n---\nYour returns questions, answered: what the new desk takes back, how long it takes, and what needs no receipt.\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-28-summer-sale.md",
+        "surface": "artifact",
+        "content": "---\nrecord: post\nplatform: bluesky\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3ksale001\npermalink: https://bsky.app/profile/bankenbeitel.bsky.social/post/3ksale001\nauthor: bankenbeitel.bsky.social\ncreatedAt: 2026-07-28T09:00:00Z\nlikes: 18\nreposts: 3\nreplies: 2\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nSeconds shelf is full: benches and boxes with honest scars, priced to leave. Ends Sunday.\n"
+      },
+      {
+        "path": "data/bluesky/posts/2026-08/2026-08-03-behind-the-scenes.md",
+        "surface": "artifact",
+        "content": "---\nrecord: post\nplatform: bluesky\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3kbts0001\npermalink: https://bsky.app/profile/bankenbeitel.bsky.social/post/3kbts0001\nauthor: bankenbeitel.bsky.social\ncreatedAt: 2026-08-03T10:30:00Z\nlikes: 57\nreposts: 21\nreplies: 9\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nWhat a Tuesday actually looks like here: glue squeeze-out, sharpening breaks, and the radio arguing with itself.\n"
+      },
+      {
+        "path": "data/bluesky/posts/2026-08/2026-08-08-returns-faq.md",
+        "surface": "artifact",
+        "content": "---\nrecord: post\nplatform: bluesky\npostId: at://did:plc:bankenbeitel/app.bsky.feed.post/3kfaq0001\npermalink: https://bsky.app/profile/bankenbeitel.bsky.social/post/3kfaq0001\nauthor: bankenbeitel.bsky.social\ncreatedAt: 2026-08-08T09:15:00Z\nlikes: 24\nreposts: 6\nreplies: 11\nmetrics_updated_at: 2026-08-12T05:00:00Z\n---\nYour returns questions, answered: what the new desk takes back, how long it takes, and what needs no receipt.\n"
+      }
+    ],
+    "craftbookParams": {
+      "lookbackDays": "3650"
+    },
+    "worker": {
+      "name": "Sten",
+      "role": "Omroeper"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The returns-faq variant gained its corpusRef, the ledger covers all three published posts with verbatim counts, and the reception report at its stable path carries exactly one gezel-action block firing draft-social-post.",
+    "checks": [
+      {
+        "kind": "contains",
+        "file": "posts/2026-08-08-returns-faq/variants/bluesky.md",
+        "pattern": "corpusRef:",
+        "label": "the missing corpusRef was reconciled"
+      },
+      {
+        "kind": "minBytes",
+        "file": "reports/reception-ledger.md",
+        "bytes": 150,
+        "artifact": true
+      },
+      {
+        "kind": "contains",
+        "file": "reports/reception-ledger.md",
+        "pattern": "summer-sale",
+        "label": "ledger covers summer-sale",
+        "artifact": true
+      },
+      {
+        "kind": "contains",
+        "file": "reports/reception-ledger.md",
+        "pattern": "behind-the-scenes",
+        "label": "ledger covers behind-the-scenes",
+        "artifact": true
+      },
+      {
+        "kind": "contains",
+        "file": "reports/reception-ledger.md",
+        "pattern": "returns-faq",
+        "label": "ledger covers returns-faq",
+        "artifact": true
+      },
+      {
+        "kind": "minBytes",
+        "file": "reports/reception-report-latest.md",
+        "bytes": 400,
+        "artifact": true
+      },
+      {
+        "kind": "contains",
+        "file": "reports/reception-report-latest.md",
+        "pattern": "```gezel-action",
+        "label": "report carries the next-post action",
+        "artifact": true
+      },
+      {
+        "kind": "contains",
+        "file": "reports/reception-report-latest.md",
+        "pattern": "craftbookId: draft-social-post",
+        "label": "the action fires draft-social-post",
+        "artifact": true
+      }
+    ],
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    },
+    "unchangedFixtures": [
+      "posts/index.json",
+      "posts/2026-07-28-summer-sale/post.md",
+      "posts/2026-07-28-summer-sale/variants/bluesky.md",
+      "posts/2026-08-03-behind-the-scenes/post.md",
+      "posts/2026-08-03-behind-the-scenes/variants/bluesky.md",
+      "posts/2026-08-08-returns-faq/post.md"
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "reports/reception-report-latest.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "grounding",
+        "description": "No metric appears in the report that is absent from the ledger; the ledger counts match the seeded records verbatim (18/3/2, 57/21/9, 24/6/11)."
+      },
+      {
+        "name": "insight",
+        "description": "The findings read the data honestly: behind-the-scenes over-performed, returns-faq drew reply-heavy engagement, and small-sample caveats are stated."
+      },
+      {
+        "name": "actionability",
+        "description": "Exactly one gezel-action block, valid flat YAML with a stable id, firing draft-social-post with a topic seeded from the strongest theme."
+      }
+    ],
+    "contextNote": "Only the returns-faq bluesky variant should gain frontmatter this run; the other seeded post files stay byte-identical. The report is an artifacts-drawer file."
+  },
+  "qualityFocus": [
+    "reconciliation touches only the variant missing corpusRef",
+    "ledger counts copied verbatim from records",
+    "exactly one next-post action, never inventing craftbook ids"
+  ]
+}

package/data/craftbook-templates/so/social-digest/manifest.json

@@ -0,0 +1,21 @@
+{
+  "schemaVersion": 1,
+  "kind": "craftbook-template",
+  "id": "social-digest",
+  "role": "maintenance-review",
+  "name": "Social Digest",
+  "description": "The overnight read of your social feeds. Scans the synced Bluesky, X, and Instagram corpus records since the last look plus your own post index, then leaves a morning digest: what happened on each feed, notable mentions and replies with the people who wrote them, which posts moved on likes, reposts, and replies, and suggested next moves — each carrying a one-click action to draft the follow-up post or a reply task. Covers social media monitoring, engagement tracking, mention triage, and a nightly social summary grounded entirely in real synced records. No connected feed? It still runs, reports what the workspace knows, and names the gap instead of inventing activity.",
+  "tags": [
+    "social",
+    "digest",
+    "engagement",
+    "night-shift",
+    "analytics"
+  ],
+  "maintainer": {
+    "name": "Gezel"
+  },
+  "license": "MIT",
+  "yankedVersions": [],
+  "workflow": "build-loop"
+}

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

@@ -0,0 +1,133 @@
+{
+  "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": {
+      "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 `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": "reports/social-digest-notes.md",
+        "artifact": true,
+        "minBytes": 150
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "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 `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 `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 `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": "reports/social-digest-latest.md",
+        "artifact": true,
+        "minBytes": 400,
+        "requireChange": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "reports/social-digest-latest.md",
+            "bytes": 400,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "reports/social-digest-latest.md",
+            "pattern": "```gezel-action",
+            "label": "digest carries at least one one-click action",
+            "artifact": true
+          },
+          {
+            "kind": "judge",
+            "file": "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": [
+              "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 `reports/social-digest-latest.md` and `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 `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.0",
+  "releasedAt": "2026-08-12T00:00:00Z"
+}