patchwork-os 0.2.0-alpha.9 → 0.2.0-beta.1

package/scripts/start-all.sh

@@ -53,6 +53,7 @@ VPS=""
 FULL_MODE=""
 NO_DASHBOARD=""
 DASHBOARD_PORT="3200"
+BRIDGE_PORT_FLAG=""
 AUTOMATION_POLICY=""
 CLAUDE_DRIVER="subprocess"
 BRIDGE_READY_TIMEOUT="${BRIDGE_READY_TIMEOUT:-30}"
@@ -71,6 +72,7 @@ while [[ $# -gt 0 ]]; do
     --full)              FULL_MODE="--full"; shift ;;
     --no-dashboard)      NO_DASHBOARD=1; shift ;;
     --dashboard-port)    DASHBOARD_PORT="$2"; shift 2 ;;
+    --bridge-port)       BRIDGE_PORT_FLAG="--port $2"; shift 2 ;;
     --automation-policy) AUTOMATION_POLICY="$2"; shift 2 ;;
     --claude-driver)     CLAUDE_DRIVER="$2"; shift 2 ;;
     *)                   echo "Unknown option: $1" >&2; exit 1 ;;
@@ -147,7 +149,7 @@ if [[ -z "${TMUX:-}" ]]; then
   fi
   # Create session detached, re-run this script inside it, then attach
   tmux new-session -d -s "$SESSION" -x 200 -y 50
-  tmux send-keys -t "$SESSION" "\"$SCRIPT_PATH\" --workspace \"$WORKSPACE\"$([ -n "$NTFY_TOPIC" ] && echo " --notify \"$NTFY_TOPIC\"")$([ -n "$IDE_NAME" ] && echo " --ide \"$IDE_NAME\"")$([ -n "$VPS" ] && echo " --vps \"$VPS\"")$([ -n "$FULL_MODE" ] && echo " --full")" Enter
+  tmux send-keys -t "$SESSION" "\"$SCRIPT_PATH\" --workspace \"$WORKSPACE\"$([ -n "$NTFY_TOPIC" ] && echo " --notify \"$NTFY_TOPIC\"")$([ -n "$IDE_NAME" ] && echo " --ide \"$IDE_NAME\"")$([ -n "$VPS" ] && echo " --vps \"$VPS\"")$([ -n "$FULL_MODE" ] && echo " --full")$([ -n "$BRIDGE_PORT_FLAG" ] && echo " ${BRIDGE_PORT_FLAG/--port /--bridge-port }")" Enter
   exec tmux attach -t "$SESSION"
 fi
 
@@ -213,7 +215,7 @@ if [[ -f "$BRIDGE_DIR/src/index.ts" ]]; then
 else
   BRIDGE_BIN="node dist/index.js"
 fi
-BRIDGE_CMD="cd $(printf '%q' "$BRIDGE_DIR") && $BRIDGE_BIN --workspace $(printf '%q' "$WORKSPACE")${BRIDGE_IDE_FLAGS:+ $BRIDGE_IDE_FLAGS}${FULL_MODE:+ $FULL_MODE}${BRIDGE_AUTOMATION_FLAGS:+ $BRIDGE_AUTOMATION_FLAGS}"
+BRIDGE_CMD="cd $(printf '%q' "$BRIDGE_DIR") && $BRIDGE_BIN --workspace $(printf '%q' "$WORKSPACE")${BRIDGE_IDE_FLAGS:+ $BRIDGE_IDE_FLAGS}${FULL_MODE:+ $FULL_MODE}${BRIDGE_AUTOMATION_FLAGS:+ $BRIDGE_AUTOMATION_FLAGS}${BRIDGE_PORT_FLAG:+ $BRIDGE_PORT_FLAG}"
 # Derive a short display name for the Claude session from the workspace directory name.
 # This appears in Claude Code's session list, making multi-workspace tmux setups identifiable.
 WS_BASENAME=$(basename "$WORKSPACE")
@@ -379,10 +381,39 @@ tmux send-keys -t "${SESSION}:0.3" "$REMOTE_CMD" Enter
 # Pane 4: Dashboard (only if not --no-dashboard and dashboard dir exists)
 DASHBOARD_DIR="$BRIDGE_DIR/dashboard"
 if [[ -z "$NO_DASHBOARD" ]] && [[ -d "$DASHBOARD_DIR" ]]; then
+  # First-run guard: missing node_modules silently breaks `npm run dev` with
+  # an unhelpful error in pane 4. Surface a concrete remediation step in the
+  # orchestrator pane so the user knows what to do.
+  if [[ ! -d "$DASHBOARD_DIR/node_modules" ]]; then
+    echo "" >&2
+    echo "Error: dashboard/node_modules not found." >&2
+    echo "Run: cd $(printf '%q' "$DASHBOARD_DIR") && npm install" >&2
+    echo "Then re-run start-all (or pass --no-dashboard to skip)." >&2
+    exit 1
+  fi
   BRIDGE_PORT=$(basename "$LOCK_FILE" .lock)
-  DASHBOARD_CMD="cd $(printf '%q' "$DASHBOARD_DIR") && PATCHWORK_BRIDGE_PORT=${BRIDGE_PORT} npm run dev"
+  # Call `next dev -p` directly. `npm run dev` hardcodes `-p 3200`, so
+  # `--dashboard-port` previously only changed the printed URL while
+  # Next.js stayed on 3200. Bypassing the npm script makes the flag
+  # actually configure the dev server end-to-end.
+  DASHBOARD_CMD="cd $(printf '%q' "$DASHBOARD_DIR") && PATCHWORK_BRIDGE_PORT=${BRIDGE_PORT} npx next dev -p ${DASHBOARD_PORT}"
   notify "Starting dashboard on http://localhost:${DASHBOARD_PORT}"
   tmux send-keys -t "${SESSION}:0.4" "$DASHBOARD_CMD" Enter
+  # Poll the dashboard port until Next.js answers, then open the browser.
+  # Replaces a fixed 8s sleep that opened a not-yet-ready page on slow
+  # machines and added unnecessary delay on fast ones. Times out at 60s.
+  (
+    for _ in $(seq 1 60); do
+      if curl -sS -o /dev/null --max-time 1 \
+          "http://localhost:${DASHBOARD_PORT}/" 2>/dev/null; then
+        open "http://localhost:${DASHBOARD_PORT}" 2>/dev/null || \
+          xdg-open "http://localhost:${DASHBOARD_PORT}" 2>/dev/null || true
+        exit 0
+      fi
+      sleep 1
+    done
+    notify "Dashboard didn't respond on port ${DASHBOARD_PORT} within 60s — open it manually."
+  ) &
 fi
 
 # Pane 5: SSH reverse tunnel (only if --vps was set)

package/templates/automation-policies/recipe-authoring.json

@@ -0,0 +1,25 @@
+{
+  "_comment": "recipe-authoring — runs preflight automatically when a .yaml recipe file is saved. Closes the authoring inner loop: edit → save → instant validation feedback via Claude task.",
+  "_usage": "Copy to automation-policy.json. Requires --automation --automation-policy <path> --claude-driver subprocess",
+
+  "automationSystemPrompt": "Recipe lint bot. ≤10 lines. No preamble. List issues with file:line if available. End with 'Recipe OK' when clean.",
+
+  "onRecipeSave": {
+    "enabled": true,
+    "cooldownMs": 10000
+  },
+
+  "onFileSave": {
+    "enabled": false,
+    "_comment": "Disabled — onRecipeSave handles .yaml files. Enable this for non-recipe YAML if needed.",
+    "patterns": ["**/*.yaml", "**/*.yml"],
+    "cooldownMs": 10000,
+    "prompt": "{{file}} saved. getDiagnostics → report issues ≤5 lines."
+  },
+
+  "onGitCommit": {
+    "enabled": true,
+    "cooldownMs": 15000,
+    "prompt": "Committed recipes on {{branch}}: {{files}}\nFor each modified .yaml file: run preflight and report any issues. If all pass, reply 'All recipes OK'."
+  }
+}

package/templates/automation-policy.example.json

@@ -20,6 +20,12 @@
     "cooldownMs": 10000
   },
 
+  "onRecipeSave": {
+    "enabled": false,
+    "_comment": "Fires when any .yaml/.yml file is saved. No prompt needed — default runs patchwork recipe preflight and reports issues. Enable when authoring recipes.",
+    "cooldownMs": 10000
+  },
+
   "onDiagnosticsError": {
     "enabled": true,
     "minSeverity": "error",

package/templates/co.patchwork-os.bridge.plist

@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
+  "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+  <key>Label</key>
+  <string>co.patchwork-os.bridge</string>
+  <key>ProgramArguments</key>
+  <array>
+    <string>__BINARY_PATH__</string>
+    <string>--claude-driver</string>
+    <string>subprocess</string>
+  </array>
+  <key>RunAtLoad</key>
+  <true/>
+  <key>KeepAlive</key>
+  <true/>
+  <key>StandardOutPath</key>
+  <string>__HOME__/Library/Logs/patchwork-os/bridge.log</string>
+  <key>StandardErrorPath</key>
+  <string>__HOME__/Library/Logs/patchwork-os/bridge.err</string>
+  <key>EnvironmentVariables</key>
+  <dict>
+    <key>HOME</key>
+    <string>__HOME__</string>
+    <key>PATH</key>
+    <string>/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin</string>
+  </dict>
+  <key>WorkingDirectory</key>
+  <string>__HOME__</string>
+  <key>ThrottleInterval</key>
+  <integer>30</integer>
+</dict>
+</plist>

package/templates/policies/README.md

@@ -0,0 +1,72 @@
+# Delegation policy templates
+
+Five starter delegation policies for common personas. Each file is a partial
+`~/.patchwork/config.json` you can copy or merge into your own config.
+
+> A delegation policy answers three questions: *what may my AI do without
+> asking, what needs approval, and what is forbidden?* See the strategic
+> plan §1.2 for the framing.
+
+## Personas
+
+| File | Mode | Push | When to pick |
+|---|---|---|---|
+| [`conservative.json`](conservative.json) | `all` | yes | First-time users, sensitive personal data, learning what your AI actually does. |
+| [`developer.json`](developer.json) | `high` | no | Solo engineer at workstation. Dashboard-only oversight is enough. |
+| [`headless-ci.json`](headless-ci.json) | `off` | no | Build agents, schedulers, CI runners. **No human in the loop** — pair with disabled write recipes. |
+| [`regulated-industry.json`](regulated-industry.json) | `all` | yes | Medicine, law, journalism, finance, gov. Includes managed-settings pointer for compliance-team override. |
+| [`personal-assistant.json`](personal-assistant.json) | `high` | yes | Non-developer life automation. Inbox, calendar, smart home — approve from phone. |
+
+## How to apply
+
+### Fresh install
+
+Copy the file into place:
+
+```sh
+cp templates/policies/developer.json ~/.patchwork/config.json
+```
+
+Then add your driver/model (run `patchwork init` for guided setup, or edit
+`config.json` to add `model`, `driver`, `apiKeys`, `localEndpoint`, etc.).
+
+### Already configured
+
+Merge with `jq` (drops the `_persona` / `_summary` documentation fields):
+
+```sh
+jq -s '.[0] * (.[1] | with_entries(select(.key | startswith("_") | not)))' \
+   ~/.patchwork/config.json templates/policies/developer.json \
+   > ~/.patchwork/config.json.new \
+&& mv ~/.patchwork/config.json.new ~/.patchwork/config.json
+```
+
+### Restart
+
+```sh
+patchwork stop
+patchwork start
+```
+
+Restart Claude Code too — the `PreToolUse` hook reads bridge state at session
+start.
+
+## Verify
+
+Open the dashboard at `http://localhost:3000/settings`. The **Delegation
+policy** card should reflect your chosen mode. Trigger a tool call and watch
+`/approvals` — the detail page shows *why* a call was gated (matched rule +
+risk tier).
+
+## Key fields
+
+- `approvalGate` — `"off" | "high" | "all"`. Coarse gate for `PreToolUse`
+  routing.
+- `dashboard.requireApproval` — `["low" | "medium" | "high"]`. Which risk
+  tiers require human approval inside the dashboard queue.
+- `dashboard.pushNotifications` — send approval requests to your phone.
+- `enableTimeOfDayAnomaly` — opt-in heuristic 10. Flags calls happening
+  outside your typical activity window. Off by default.
+- `managedSettingsPath` — admin-controlled overrides, highest precedence.
+  Users cannot override fields set there.
+- `recipes.disabled` — opt out of specific recipes by name.

package/templates/policies/conservative.json

@@ -0,0 +1,14 @@
+{
+  "_persona": "conservative",
+  "_summary": "Gate every tool call. Notify on phone. Maximum oversight. Best for first-time users, sensitive personal data, or while learning what your AI actually does.",
+  "_usage": "Copy fields into ~/.patchwork/config.json (or merge with `jq`). Restart the bridge and Claude Code.",
+
+  "approvalGate": "all",
+  "enableTimeOfDayAnomaly": true,
+
+  "dashboard": {
+    "port": 3000,
+    "requireApproval": ["low", "medium", "high"],
+    "pushNotifications": true
+  }
+}

package/templates/policies/developer.json

@@ -0,0 +1,14 @@
+{
+  "_persona": "developer",
+  "_summary": "Gate high-risk tool calls only. No phone push (dashboard is enough — you're already at your machine). Time-of-day anomaly on. Sensible default for solo engineers running Patchwork on their workstation.",
+  "_usage": "Copy fields into ~/.patchwork/config.json (or merge with `jq`). Restart the bridge and Claude Code.",
+
+  "approvalGate": "high",
+  "enableTimeOfDayAnomaly": true,
+
+  "dashboard": {
+    "port": 3000,
+    "requireApproval": ["high"],
+    "pushNotifications": false
+  }
+}

package/templates/policies/headless-ci.json

@@ -0,0 +1,24 @@
+{
+  "_persona": "headless-ci",
+  "_summary": "No human in the loop. Approval gate off. Disable recipes that touch external systems with side effects. For build agents, scheduled jobs, and CI runners that must not block waiting for a phone tap.",
+  "_warning": "Off-mode means *every* tool call passes. Use only when (a) the underlying recipes are auditable and (b) the runner has narrowly-scoped credentials. Pair with managedSettingsPath if running on shared infra.",
+  "_usage": "Copy fields into ~/.patchwork/config.json (or merge with `jq`). Restart the bridge.",
+
+  "approvalGate": "off",
+  "enableTimeOfDayAnomaly": false,
+
+  "dashboard": {
+    "port": 3000,
+    "requireApproval": [],
+    "pushNotifications": false
+  },
+
+  "recipes": {
+    "disabled": [
+      "send-email",
+      "send-slack",
+      "github-create-pr",
+      "linear-create-issue"
+    ]
+  }
+}

package/templates/policies/personal-assistant.json

@@ -0,0 +1,15 @@
+{
+  "_persona": "personal-assistant",
+  "_summary": "Friendly default for non-developer use cases — life automation, inbox triage, journal prompts, household ops. Gate high-risk only, push to phone so you can approve while away from your machine.",
+  "_targets": "people who want their AI to act on email, calendar, smart home, and notes without watching the dashboard.",
+  "_usage": "Copy fields into ~/.patchwork/config.json (or merge with `jq`). Restart the bridge.",
+
+  "approvalGate": "high",
+  "enableTimeOfDayAnomaly": true,
+
+  "dashboard": {
+    "port": 3000,
+    "requireApproval": ["high"],
+    "pushNotifications": true
+  }
+}

package/templates/policies/regulated-industry.json

@@ -0,0 +1,18 @@
+{
+  "_persona": "regulated-industry",
+  "_summary": "Maximum oversight + audit posture. Gate everything, push to phone, time-of-day anomaly on, point at a managed settings file that your compliance team controls (highest precedence — users cannot override).",
+  "_targets": "medicine, law, journalism, finance, gov, security work — anywhere you need a paper trail for every AI-initiated action.",
+  "_usage": "Copy fields into ~/.patchwork/config.json. Have your compliance team produce the managed settings file at /etc/patchwork/managed-settings.json (or anywhere admin-writable, user-readable). Restart the bridge and Claude Code.",
+  "_audit_note": "Decision traces are persisted under ~/.patchwork/traces/ — exportable via `patchwork traces export --encrypt`.",
+
+  "approvalGate": "all",
+  "enableTimeOfDayAnomaly": true,
+
+  "dashboard": {
+    "port": 3000,
+    "requireApproval": ["low", "medium", "high"],
+    "pushNotifications": true
+  },
+
+  "managedSettingsPath": "/etc/patchwork/managed-settings.json"
+}

package/templates/recipes/approval-queue-ui-test.yaml

@@ -0,0 +1,205 @@
+# yaml-language-server: $schema=https://raw.githubusercontent.com/patchworkos/recipes/main/schema/recipe.v1.json
+apiVersion: patchwork.sh/v1
+name: approval-queue-ui-test
+description: |
+  End-to-end UI test for the dashboard Approval queue page. Drives a real
+  browser via the Playwright MCP server to exercise every button on
+  /approvals, verifies the expected side effects (network calls, clipboard
+  writes, DOM state, keyboard shortcuts), and writes a PASS/FAIL report to
+  ~/.patchwork/inbox/.
+
+  Coverage:
+    Header — DecisionsTabs (Pending / Suggested / History), Sync inbox
+    Risk filters — All / Low / Medium / High chips
+    Card body — params toggle (▸/▾), Copy JSON, Approve (E), Reject (X),
+                Edit & approve (clipboard), Open in terminal (clipboard)
+    Selection — per-card checkbox, Select all, batch Approve, batch Reject
+    Empty state — Clear filter (filtered) and Clear filter (session banner)
+    Suggestions card — Copy allow rule, Dismiss (×), Clear all patterns
+    Keyboard — J / K (focus), E / X (decide)
+
+  PREREQUISITES
+    1. Bridge running with --claude-driver subprocess so the agent has MCP
+       access to the Playwright server.
+    2. Dashboard reachable at DASHBOARD_URL (defaults to localhost:3000;
+       Patchwork's Next.js dev typically mounts under /dashboard, so the
+       page at $DASHBOARD_URL/approvals must respond 200).
+    3. approvalGate must be "all" or "high" — if "off", every POST
+       /approvals auto-allows ({decision:"allow",reason:"gate_off"}) and
+       the queue stays empty. The agent toggles it on at the start of the
+       run and restores it at the end.
+    4. Seeded pending approvals — the agent creates them via POST
+       /api/bridge/approvals with nohup+disown durability (so the curl
+       process survives shell exit; see seeding step). Default TTL is
+       5 min, so all UI work must finish before re-seeding.
+    5. Trigger from the dashboard Recipes page (NOT `patchwork recipe run`)
+       — the local subprocess shell has no MCP context.
+
+  IMPLEMENTATION NOTES (learned from 2026-05-07 dogfood)
+    - Click via mcp__playwright__browser_click (real Playwright clicks),
+      NOT browser_evaluate(.click()) — Chromium's clipboard.writeText
+      requires "transient activation" which programmatic clicks don't
+      provide. Edit & approve / Open in terminal silently fail otherwise.
+    - Same goes for checkboxes — programmatic input.click() doesn't
+      always trigger React's onChange synthetic event reliably.
+    - Use the URL ?session= param to force the session-banner branch;
+      no need to find a real session.
+    - Use the "Low (0)" filter to hit the empty-state branch deterministically
+      (without rejecting cards mid-test).
+trigger:
+  type: manual
+  vars:
+    - name: DASHBOARD_URL
+      description: "Base URL where the dashboard is reachable from the agent's browser"
+      required: false
+      default: "http://localhost:3000"
+steps:
+  - id: drive_browser
+    agent:
+      driver: claude-code
+      model: claude-haiku-4-5-20251001
+      prompt: |
+        You are running an end-to-end UI test of the Patchwork Approval
+        queue page. Use the Playwright MCP tools (mcp__playwright__*) to
+        drive a real browser. Do not skip steps. If a tool call errors,
+        record the failure and continue — every checkpoint must be
+        attempted so the report is complete.
+
+        BASE_URL: {{DASHBOARD_URL}}
+        TARGET:   {{DASHBOARD_URL}}/approvals
+
+        Use mcp__playwright__browser_snapshot between actions to confirm
+        DOM state. Use mcp__playwright__browser_evaluate to read
+        navigator.clipboard.readText() (after granting clipboard-read
+        permission via browser_evaluate of the appropriate Permissions
+        API call) to verify clipboard-writing buttons.
+
+        ## Checklist — record PASS / FAIL + a one-line note for each
+
+        ### A. Page load + tabs (DecisionsTabs)
+        A1. browser_navigate to TARGET. Snapshot. Confirm h1 contains
+            "Approval queue".
+        A2. Click the "Suggested" tab. Confirm URL becomes /suggestions.
+        A3. browser_navigate_back. Confirm URL returns to /approvals.
+        A4. Click the "History" tab. Confirm URL becomes /decisions.
+        A5. browser_navigate_back to /approvals.
+
+        ### B. Header controls
+        B1. Click "Sync inbox". Use browser_network_requests to confirm a
+            GET request to /api/bridge/approvals fired within 2s.
+
+        ### C. Risk filter chips (All / Low / Medium / High)
+        For each label in [All, Low, Medium, High]:
+          C{n}. Click the filter chip with text starting with that label.
+                Confirm aria-pressed="true" on the clicked chip and
+                aria-pressed="false" on the others. Confirm the URL
+                ?risk= param matches (or is absent for "All").
+
+        ### D. Per-card controls — pick the FIRST visible approval card
+        Skip section D with a clear note if the queue is empty.
+        D1. Click the card's "Full params" toggle (▸). Confirm it
+            switches to ▾ and the params JSON region expands.
+        D2. Click "Copy JSON". Read clipboard; confirm it parses as JSON
+            and equals the card's params.
+        D3. Click "Edit & approve". Read clipboard; confirm it starts
+            with "patchwork approve --edit ".
+        D4. Click "› Open in terminal". Read clipboard; confirm it
+            starts with "patchwork approve " (no --edit).
+        D5. Note the card's callId, then click the per-card checkbox.
+            Confirm the checkbox is checked and the BatchActionBar
+            renders with "1 selected".
+        D6. Uncheck the same checkbox. Confirm BatchActionBar disappears.
+
+        ### E. Select-all + batch (only if filtered.length > 1)
+        Skip with a note if there are fewer than 2 cards.
+        E1. Click "Select all". Confirm every visible card checkbox is
+            checked.
+        E2. Confirm BatchActionBar shows "Approve selected (N)" and
+            "Reject selected (N)" with N === visible card count.
+        E3. Do NOT click batch Approve / Reject in this run — they fire
+            real POSTs and would mutate state. Just record that the
+            buttons render and are not disabled.
+        E4. Uncheck "Select all". Confirm all card checkboxes clear.
+
+        ### F. Empty-state "Clear filter"
+        F1. Click the "High" risk filter. If the resulting list is empty,
+            confirm the EmptyState renders with a "Clear filter" button.
+            Click it; confirm the filter resets to All.
+            If the High filter still has cards, record SKIP with reason.
+
+        ### G. Keyboard shortcuts
+        G1. Press "j" via browser_press_key. Confirm focus advances to
+            the next card (outline: 2px solid var(--accent) on the
+            second card).
+        G2. Press "k". Confirm focus returns to the first card.
+        G3. Do NOT press E or X — they fire real decisions. Record only
+            that the keyboard hint row renders KeyChip pills for J, K,
+            E, X, ⌘K.
+
+        ### H. Suggestions card (best-effort)
+        H1. Scroll to bottom. If "Pattern suggestions" card is visible
+            (depends on local approval history, may not exist), click
+            "Copy allow rule" on the first row and confirm clipboard
+            contains JSON like {"allow":["<toolName>"]}. Otherwise
+            record SKIP: "no suggestions in queue".
+
+        ### I. Session-filter banner
+        I1. browser_navigate to {{DASHBOARD_URL}}/approvals?session=test1234.
+            Confirm the info banner renders with text containing
+            "Showing approvals for session". Click the banner's
+            "Clear filter" link; confirm URL becomes /approvals.
+
+        ## Final step — write the report
+        Output ONLY the markdown block below, nothing else:
+
+        ```
+        # approval-queue-ui-test — {{date}} {{time}}
+
+        Base URL: {{DASHBOARD_URL}}
+        Browser: <user-agent from snapshot>
+
+        ## Result: PASS / FAIL  (FAIL if any checkpoint failed)
+
+        ### A. Page load + tabs
+        - A1 ... A5 — PASS / FAIL / SKIP — <note>
+
+        ### B. Header controls
+        - B1 — ...
+
+        ### C. Risk filters
+        - All — ...
+        - Low — ...
+        - Medium — ...
+        - High — ...
+
+        ### D. Per-card controls
+        - D1 ... D6 — ...
+
+        ### E. Select-all + batch
+        - E1 ... E4 — ...
+
+        ### F. Empty-state Clear filter
+        - F1 — ...
+
+        ### G. Keyboard shortcuts
+        - G1 ... G3 — ...
+
+        ### H. Suggestions card
+        - H1 — ...
+
+        ### I. Session-filter banner
+        - I1 — ...
+
+        ### Failures
+        <bullet list of every FAIL with the full error / screenshot ref;
+         "none" if clean>
+
+        ### Verdict
+        <one sentence>
+        ```
+      into: report
+
+  - id: write_report
+    tool: file.write
+    path: ~/.patchwork/inbox/approval-queue-ui-test-{{date}}.md
+    content: "{{report}}\n"

package/templates/recipes/lint-on-save.yaml

@@ -9,5 +9,4 @@ steps:
     into: diags
   - tool: file.append
     path: ~/.patchwork/inbox/lint.md
-    content: "- {{time}}  {{file}} — {{diags.errors}} errors, {{diags.warnings}} warnings\n"
-    when: "{{diags.errors}} > 0 || {{diags.warnings}} > 0"
+    content: "- {{time}}  {{file}} — {{diags}}\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

@@ -61,8 +61,8 @@ steps:
         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
+      # Use claude (not gemini) — Gemini free tier hits daily quota mid-recipe
+      driver: claude
       into: brief
   - tool: file.write
     path: ~/.patchwork/inbox/morning-brief-{{date}}.md

package/templates/recipes/project-health-check.yaml

@@ -0,0 +1,50 @@
+# yaml-language-server: $schema=https://raw.githubusercontent.com/patchworkos/recipes/main/schema/recipe.v1.json
+apiVersion: patchwork.sh/v1
+name: project-health-check
+description: Fetch git activity, open issues, and diagnostics in parallel, then write a health summary.
+trigger:
+  type: manual
+maxConcurrency: 4
+steps:
+  - id: gather
+    parallel:
+      - id: commits
+        tool: git.log_since
+        since: 24h
+      - id: issues
+        tool: github.list_issues
+        assignee: "@me"
+        max: 20
+      - id: prs
+        tool: github.list_prs
+        author: "@me"
+        max: 10
+  - id: summarize
+    agent:
+      prompt: |
+        Write a concise project health summary using ONLY the data below.
+
+        RECENT COMMITS (last 24h):
+        {{commits}}
+
+        OPEN ISSUES (assigned to me):
+        {{issues}}
+
+        OPEN PULL REQUESTS:
+        {{prs}}
+
+        Sections:
+        1. **Activity** — what shipped or changed in the last 24 hours
+        2. **Issues** — issues needing attention today; omit if empty
+        3. **PRs** — PRs waiting on review or action; omit if empty
+        4. **Health** — one-sentence overall assessment (on track / needs attention / blocked)
+      driver: claude
+    awaits: [gather]
+  - id: write
+    tool: file.write
+    path: ~/.patchwork/inbox/health-{{date}}.md
+    content: |
+      # Project health — {{date}}
+
+      {{summarize}}
+    awaits: [summarize]