patchwork-os 0.2.0-alpha.2 → 0.2.0-alpha.21

package/templates/recipes/ctx-loop-test.yaml

@@ -0,0 +1,75 @@
+name: ctx-loop-test
+description: |
+  End-to-end test of the agent-read loop. An agent writes a decision trace with
+  ctxSaveTrace, then reads it back with ctxQueryTraces, and confirms the trace
+  appears in the result. Output lands in ~/.patchwork/inbox/ for manual inspection.
+  Run this after deploying a new bridge build to confirm the memory moat is live.
+
+  NOTE: requires --claude-driver subprocess and a running bridge with HTTP port
+  so the agent subprocess has MCP access. Running via `patchwork recipe run`
+  (local yamlRunner) will fail at Step 1 — the local claude -p subprocess has
+  no bridge MCP context. Trigger from the dashboard Recipes page instead.
+trigger:
+  type: manual
+steps:
+  - tool: git.log_since
+    since: 1h
+    into: recent_commits
+
+  - agent:
+      prompt: |
+        You are validating the Patchwork cross-session memory loop end-to-end.
+
+        RECENT COMMITS (context only):
+        {{recent_commits}}
+
+        Perform the following steps IN ORDER. Stop immediately if any step fails and
+        report the failure clearly in your output.
+
+        ## Step 1 — Write a trace
+        Call ctxSaveTrace with these exact values:
+          ref: "ctx-loop-test-{{date}}"
+          problem: "Validating that ctxSaveTrace persists traces readable by future sessions"
+          solution: "ctxSaveTrace writes to decision_traces.jsonl; ctxQueryTraces reads it back"
+          tags: ["loop-test", "dogfood"]
+
+        Record the returned `seq` number.
+
+        ## Step 2 — Read it back
+        Call ctxQueryTraces with:
+          traceType: "decision"
+          limit: 5
+
+        Check that the trace you just wrote (ref "ctx-loop-test-{{date}}") appears in
+        the results. If it does, the loop is confirmed closed.
+
+        ## Step 3 — Write your report
+        Output a markdown block in this exact format:
+
+        ```
+        # ctx-loop-test — {{date}} {{time}}
+
+        ## Result: PASS / FAIL
+
+        ### Step 1 — ctxSaveTrace
+        - seq: <returned seq>
+        - ref: ctx-loop-test-{{date}}
+        - Status: OK / ERROR: <message>
+
+        ### Step 2 — ctxQueryTraces
+        - Traces returned: <count>
+        - Test trace found: yes / no
+        - Status: OK / ERROR: <message>
+
+        ### Verdict
+        <one sentence summary>
+        ```
+
+        Output ONLY the markdown block. No preamble.
+      driver: claude-code
+      model: claude-haiku-4-5-20251001
+      into: report
+
+  - tool: file.write
+    path: ~/.patchwork/inbox/ctx-loop-test-{{date}}.md
+    content: "{{report}}\n"

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

@@ -0,0 +1,57 @@
+name: morning-brief-slack
+description: Daily morning brief combining calendar, GitHub PRs, and Linear issues — posted to Slack.
+trigger:
+  type: cron
+  at: "0 8 * * 1-5"
+steps:
+  - tool: github.list_prs
+    author: "@me"
+    max: 10
+    into: prs
+  - tool: linear.list_issues
+    assignee: "@me"
+    state: "started,unstarted"
+    max: 15
+    into: linear_issues
+  - tool: calendar.list_events
+    days_ahead: 1
+    max: 10
+    into: calendar
+  - agent:
+      prompt: |
+        You are a personal assistant writing a concise morning brief. Use ONLY the data provided below — do not call any tools or fetch additional information.
+
+        OPEN PULL REQUESTS (authored by me):
+        {{prs}}
+
+        LINEAR ISSUES (assigned to me, in progress or unstarted):
+        {{linear_issues}}
+
+        TODAY'S CALENDAR EVENTS:
+        {{calendar}}
+
+        Write a short morning brief for Slack. Rules:
+        - Plain text only. No markdown headers (no # or ## lines). No code blocks.
+        - Use emoji to start each section.
+        - Do NOT include a title or greeting line like "Morning Brief" or "Good morning" — start directly with the first section.
+
+        📅 *Calendar* — list today's meetings with time; write "No meetings today" if empty or error
+        🔀 *Pull Requests* — list open PRs needing attention; omit section entirely if empty
+        📋 *Linear* — list in-progress and unstarted issues by priority; omit section entirely if empty or error
+
+        Keep it under 15 lines. Be direct. Output only the brief, nothing else.
+      driver: claude-code
+      model: claude-haiku-4-5-20251001
+      into: brief
+  - tool: file.write
+    path: ~/.patchwork/inbox/morning-brief-{{date}}.md
+    content: |
+      # Morning brief — {{date}}
+
+      {{brief}}
+  - tool: slack.post_message
+    channel: all-massappealdesigns
+    text: |
+      *Morning Brief — {{date}}*
+
+      {{brief}}

package/templates/recipes/morning-brief.yaml

@@ -1,5 +1,5 @@
 name: morning-brief
-description: Daily morning brief combining unread emails, recent git activity, and open GitHub issues.
+description: Daily morning brief combining unread emails, calendar, recent git activity, and open GitHub issues.
 trigger:
   type: cron
   at: "0 8 * * 1-5"
@@ -19,6 +19,15 @@ steps:
     author: "@me"
     max: 10
     into: prs
+  - tool: linear.list_issues
+    assignee: "@me"
+    state: "started,unstarted"
+    max: 15
+    into: linear_issues
+  - tool: calendar.list_events
+    days_ahead: 1
+    max: 10
+    into: calendar
   - agent:
       prompt: |
         You are a personal assistant writing a concise morning brief. Use ONLY the data provided below — do not call any tools or fetch additional information.
@@ -37,15 +46,22 @@ steps:
         OPEN PULL REQUESTS (authored by me):
         {{prs}}
 
+        LINEAR ISSUES (assigned to me, in progress or unstarted):
+        {{linear_issues}}
+
+        TODAY'S CALENDAR EVENTS:
+        {{calendar}}
+
         Write a morning brief with these sections:
         1. **Email triage** — list emails needing action today (sender, subject, one-line summary)
         2. **FYI emails** — informational only, no action needed
-        3. **Code activity** — summarize the RECENT GIT COMMITS above; if the list is empty write "No commits in the last 24 hours"
-        4. **GitHub** — list open issues and PRs needing attention; omit this section entirely if both lists are empty
+        3. **Calendar** — list today's meetings with time and attendees; omit if calendar returned an error or no events
+        4. **Code activity** — summarize the RECENT GIT COMMITS above; if the list is empty write "No commits in the last 24 hours"
+        5. **GitHub** — list open issues and PRs needing attention; omit this section entirely if both lists are empty
+        6. **Linear** — list in-progress and unstarted issues by priority; omit this section entirely if the list is empty or returned an error
 
         Be concise. Skip newsletters and automated notifications.
-      driver: claude-code
-      model: claude-haiku-4-5-20251001
+      driver: gemini
       into: brief
   - tool: file.write
     path: ~/.patchwork/inbox/morning-brief-{{date}}.md

package/templates/recipes/sentry-to-linear.yaml

@@ -0,0 +1,77 @@
+name: sentry-to-linear
+description: |
+  Fetch a Sentry issue, enrich it with git blame, and create a triage-ready
+  Linear ticket. Requires both Sentry and Linear connectors connected.
+  Run ad-hoc or trigger via webhook / automation policy.
+
+# Example manual trigger:
+#   patchwork-os run-recipe sentry-to-linear --var SENTRY_ISSUE_ID=12345678
+#
+# Example automation trigger (add to ~/.patchwork/automation-policy.json):
+#   "onFileSave": { ... }  — or fire from a Sentry webhook handler
+
+trigger:
+  type: manual
+  vars:
+    - name: SENTRY_ISSUE_ID
+      description: "Sentry issue ID or URL (e.g. '12345678' or 'https://sentry.io/...')"
+      required: true
+    - name: LINEAR_TEAM_KEY
+      description: "Linear team key to create the issue in (e.g. 'ENG'). Defaults to first team."
+      required: false
+    - name: LINEAR_PRIORITY
+      description: "Linear priority: 1=urgent, 2=high, 3=medium, 4=low (default: 2)"
+      required: false
+      default: "2"
+
+steps:
+  - agent:
+      prompt: |
+        You are a triage assistant. Your job is to:
+        1. Fetch the Sentry issue using fetchSentryIssue with issueId "{{SENTRY_ISSUE_ID}}"
+        2. Create a Linear issue using createLinearIssue with the data you received
+
+        For the Linear issue:
+        - title: Use the Sentry issue title verbatim
+        - description: Write a structured Markdown body with these sections:
+            ## Error
+            (one-line error type + message from the Sentry title)
+
+            ## Stack trace
+            (the top 5 frames from the stackTrace field, formatted as a code block)
+
+            ## Suspect commit
+            (if topSuspect is present: sha, author, date, subject — otherwise write "No suspect commit identified")
+
+            ## Confidence
+            (the confidence field value + a one-sentence explanation of what it means)
+
+            ## Sentry link
+            (a link back to the Sentry issue — construct from the issueId: https://sentry.io/issues/{{SENTRY_ISSUE_ID}}/)
+
+        - teamKey: "{{LINEAR_TEAM_KEY}}" (pass as-is; if blank the tool picks the first team)
+        - priority: {{LINEAR_PRIORITY}} (as an integer)
+        - labelNames: ["bug"]
+
+        After creating the ticket, respond with ONLY a JSON object:
+        {
+          "sentryIssueId": "<the issueId from fetchSentryIssue>",
+          "sentryTitle": "<the title>",
+          "linearIdentifier": "<e.g. ENG-101>",
+          "linearUrl": "<the url from createLinearIssue>",
+          "confidence": "<high|medium|low>",
+          "suspectCommit": "<sha or null>"
+        }
+
+        If either tool returns an error (sentryConnected: false or linearConnected: false),
+        respond with the same JSON shape but set linearUrl to "" and add an "error" key
+        explaining which connector is not connected.
+      driver: claude-code
+      model: claude-haiku-4-5-20251001
+      into: result
+  - tool: file.write
+    path: ~/.patchwork/inbox/sentry-to-linear-{{date}}.md
+    content: |
+      # Sentry → Linear triage ({{date}})
+
+      {{result}}