patchwork-os 1.2.0-beta.2.canary.743 → 1.2.0-beta.2.canary.744

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchwork-os",
-  "version": "1.2.0-beta.2.canary.743",
+  "version": "1.2.0-beta.2.canary.744",
   "description": "Your personal AI runtime, local-first. Patchwork OS gives any AI model a consistent set of tools, YAML recipes, a delegation policy with approval queue, and a durable trace memory — all on your machine, all under your policy.",
   "type": "module",
   "main": "dist/index.js",

package/templates/recipes/daily-status.yaml

@@ -7,6 +7,24 @@ description: Every morning at 08:00, summarize yesterday's commits + today's cal
 allowWrites:
   - file.write
 
+# Run-level completion contract. Every step can report ok and the run can still
+# finish `done` having produced no `brief` — an agent that narrates instead of
+# answering, or a driver that returns empty, leaves the key unset and the step
+# after it writes a heading with nothing under it. That is this recipe's real
+# failure mode and it is silent.
+#
+# Checked AFTER the last step; it does NOT change the run's status. A violation
+# is recorded as `assertionFailures` on the run and counted by `patchwork halts`
+# under `completion contract failed`. So the run still writes whatever it
+# produced — this reports, it does not roll back.
+#
+# Asserts only the daily status it exists to write: the upstream fetch steps are
+# allowed to come back empty (no commits today, an empty calendar), and turning
+# a quiet day into a halt would be a contract that cries wolf.
+expect:
+  outputs:
+    - brief
+
 trigger:
   type: cron
   at: "0 8 * * *"

package/templates/recipes/morning-brief-slack.yaml

@@ -8,6 +8,24 @@ allowWrites:
   - file.write
   - slack.post_message
 
+# Run-level completion contract. Every step can report ok and the run can still
+# finish `done` having produced no `brief` — an agent that narrates instead of
+# answering, or a driver that returns empty, leaves the key unset and the step
+# after it writes a heading with nothing under it. That is this recipe's real
+# failure mode and it is silent.
+#
+# Checked AFTER the last step; it does NOT change the run's status. A violation
+# is recorded as `assertionFailures` on the run and counted by `patchwork halts`
+# under `completion contract failed`. So the run still writes whatever it
+# produced — this reports, it does not roll back.
+#
+# Asserts only the brief it posts to Slack: the upstream fetch steps are
+# allowed to come back empty (no commits today, an empty calendar), and turning
+# a quiet day into a halt would be a contract that cries wolf.
+expect:
+  outputs:
+    - brief
+
 trigger:
   type: cron
   at: "0 8 * * 1-5"

package/templates/recipes/release-notes.yaml

@@ -6,6 +6,24 @@ name: release-notes
 description: After a commit lands, draft a changelog entry from the new commits into the inbox.
 allowWrites:
   - file.write
+# Run-level completion contract. Every step can report ok and the run can still
+# finish `done` having produced no `notes` — an agent that narrates instead of
+# answering, or a driver that returns empty, leaves the key unset and the step
+# after it writes a heading with nothing under it. That is this recipe's real
+# failure mode and it is silent.
+#
+# Checked AFTER the last step; it does NOT change the run's status. A violation
+# is recorded as `assertionFailures` on the run and counted by `patchwork halts`
+# under `completion contract failed`. So the run still writes whatever it
+# produced — this reports, it does not roll back.
+#
+# Asserts only the release notes it drafts: the upstream fetch steps are
+# allowed to come back empty (no commits today, an empty calendar), and turning
+# a quiet day into a halt would be a contract that cries wolf.
+expect:
+  outputs:
+    - notes
+
 trigger:
   type: git_hook
   event: post-commit