crewly 1.20.194 → 1.20.195

package/config/skills/agent/core/experiment-card/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: Experiment Card
 description: Attach an experiment to an optimisation ticket — hypothesis ("change X → metric Y from a to b"), a Search Console or GA4 metric (via seo-ops), an observation window (default 14 days). Crewly captures the baseline when the change ships, measures it when the window ends, labels it worked / didn't / inconclusive, resolves your prediction, writes the wiki experiment log and tells the owner.
-version: 1.0.0
+version: 1.1.0
 category: analysis
 skillType: claude-skill
 assignableRoles:
@@ -41,7 +41,10 @@ Crewly does the rest:
 
 1. **Ship** — when the linked ticket reaches `done` (or you run `ship`), the
    windows are fixed and the **baseline** is fetched right away: the
-   `windowDays` days that had settled before the ship day.
+   `windowDays` days that had settled before the ship day. The ship time is
+   the ticket's move to `done` in its log. If you link a ticket that is
+   already done and its log has no done time, `create` asks for
+   `--shipped-at` (when the change went live).
 2. **Wait** — the observation window is the `windowDays` days after the ship
    day. Nothing to do; don't re-check it by hand.
 3. **Measure** — once those days have settled (Search Console +3 days, GA4
@@ -76,8 +79,10 @@ bash execute.sh create --hypothesis "3-field inquiry form → submissions from 8
 - gsc measures: `clicks`, `impressions`, `ctr`, `position` (lower is better;
   direction defaults to `decrease`). Filters: `--page URL`, `--query Q`,
   `--page-match` / `--query-match exact|contains`.
-- ga4 measures: `sessions` (Organic Search unless `--channel all`) and
-  `events` (`--event NAME`). Filter: `--page /landing-path`.
+- ga4 measures: `sessions` (Organic Search unless `--channel all`),
+  `events` (`--event NAME`) and `conversions` (GA4 key events; `--event NAME`
+  for one of them). Filter: `--page /landing-path` (a full URL is reduced to
+  its path; the query string is dropped).
 - `--window-days` 7–90, whole weeks preferred (default 14).
 - One experiment per change: two changes on the same page in one window
   can't be told apart.
@@ -93,4 +98,4 @@ bash execute.sh cancel --id EXP-3 --reason "change reverted"
 ```
 
 If a fetch keeps failing (credentials, property access) the owner is told
-once with the error; it keeps retrying.
+once with the error; after 6 failures in a row it retries once a day.

package/config/skills/agent/core/experiment-card/execute.sh

@@ -10,7 +10,7 @@
 #                          [--page P] [--page-match exact|contains] [--query Q] [--query-match exact|contains]
 #                          [--event NAME] [--channel all] [--label "…"] [--title "…"]
 #                          [--from A] [--to B] [--direction increase|decrease] [--window-days 14]
-#                          [--confidence 0.6] [--project P --ticket ID | --tkt TKT-12]
+#                          [--confidence 0.6] [--project P --ticket ID | --tkt TKT-12] [--shipped-at ISO]
 #   bash execute.sh ship    --id EXP-3 [--shipped-at ISO]
 #   bash execute.sh show    --id EXP-3
 #   bash execute.sh list    [--status planned|running|done|cancelled] [--ticket ID]
@@ -28,8 +28,9 @@ Usage:
   bash execute.sh create --hypothesis "change X → metric Y from a to b" --source gsc|ga4 --measure M
                          --config /abs/path/seo-ops.config.json [filters] [--from A] [--to B]
                          [--window-days 14] [--confidence 0.6] [--project P --ticket ID | --tkt TKT-12]
+                         [--shipped-at ISO]   (required when the ticket is already done but has no recorded done time)
       gsc measures: clicks impressions ctr position   (filters: --page URL --query Q, --page-match/--query-match exact|contains)
-      ga4 measures: sessions events                   (filters: --page /path, --event NAME, --channel all)
+      ga4 measures: sessions events conversions       (filters: --page /path, --event NAME, --channel all)
   bash execute.sh ship    --id EXP-3 [--shipped-at ISO]   The change is live (automatic when the ticket is done)
   bash execute.sh show    --id EXP-3                      Card, baseline, result and timeline
   bash execute.sh list    [--status S] [--ticket ID]
@@ -51,7 +52,7 @@ if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
   STATUS=$(printf '%s' "$J" | jq -r '.status // empty')
   REASON=$(printf '%s' "$J" | jq -r '.reason // empty')
   TICKET=$(printf '%s' "$J" | jq -r 'if (.ticket|type) == "string" then .ticket else empty end')
-  JSON_BODY=$(printf '%s' "$J" | jq -c 'del(.action, .id, .shippedAt, .status, .reason)')
+  JSON_BODY=$(printf '%s' "$J" | jq -c 'del(.action, .id, .status, .reason)')
 fi
 if [[ -z "$ACTION" && $# -gt 0 && ${1:0:1} != '-' ]]; then ACTION="$1"; shift; fi
 
@@ -116,6 +117,7 @@ case "$ACTION" in
            elif $tic != "" then {ticket: {kind: "project", project: $proj, id: $tic}}
            else {} end)')
     fi
+    if [ -n "$SHIPPED_AT" ]; then BODY=$(printf '%s' "$BODY" | jq -c --arg at "$SHIPPED_AT" '. + {shippedAt: $at}'); fi
     api_call POST "/experiments" "$BODY" | jq "{success, experiment: (.data | ${CARD})}"
     ;;
   ship)

package/config/skills/agent/core/experiment-card/execute.test.sh

@@ -64,6 +64,12 @@ check "create ga4: body" "$(last '.body | tostring')" '{"hypothesis":"Shorter fo
 run '{"action":"create","hypothesis":"J","metric":{"source":"gsc","measure":"ctr","config":"/c.json"}}' >/dev/null
 check "create json: body" "$(last '.body | tostring')" '{"hypothesis":"J","metric":{"source":"gsc","measure":"ctr","config":"/c.json"}}'
 
+# --- create on an already-done ticket with an explicit ship time ---
+run create --hypothesis "Late card" --source gsc --measure clicks --config /c.json --project ce --ticket T-9 --shipped-at 2026-10-01T10:00:00Z >/dev/null
+check "create shipped-at: body" "$(last '.body.shippedAt')" "2026-10-01T10:00:00Z"
+run '{"action":"create","hypothesis":"J","metric":{"source":"gsc","measure":"ctr","config":"/c.json"},"shippedAt":"2026-10-01T10:00:00Z"}' >/dev/null
+check "create json shipped-at: body" "$(last '.body.shippedAt')" "2026-10-01T10:00:00Z"
+
 # --- missing params / a ticket without its project ---
 check "create: missing" "$(run_err create --hypothesis h --source gsc --measure clicks | grep -c 'config')" "1"
 check "create: ticket w/o project" "$(run_err create --hypothesis h --source gsc --measure clicks --config /c --ticket T-1 | grep -c 'needs --project')" "1"

package/config/skills/agent/desktop-app-control/execute.sh

@@ -32,6 +32,9 @@ set -euo pipefail
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 LOG_DIR="${HOME}/.crewly/logs"
 LOG_FILE="${LOG_DIR}/desktop-app-control.log"
+# Where `scan` looks for installed apps. Overridable so the scan can be
+# exercised against a fixture directory on machines without /Applications.
+APPLICATIONS_DIR="${CREWLY_APPLICATIONS_DIR:-/Applications}"
 
 # Ensure log directory exists
 mkdir -p "$LOG_DIR"
@@ -108,7 +111,7 @@ do_scan() {
   }
 
   # Scan for Electron apps by checking framework directory
-  for app_dir in /Applications/*.app; do
+  for app_dir in "$APPLICATIONS_DIR"/*.app; do
     [ ! -d "$app_dir" ] && continue
     if [ -d "$app_dir/Contents/Frameworks/Electron Framework.framework" ]; then
       local app_name
@@ -138,7 +141,7 @@ do_scan() {
   local browser port
   while IFS='|' read -r browser port; do
     [ -z "$browser" ] && continue
-    if [ -d "/Applications/$browser.app" ]; then
+    if [ -d "$APPLICATIONS_DIR/$browser.app" ]; then
       local running="false"
       if pgrep -f "$browser" > /dev/null 2>&1; then
         running="true"

package/config/skills/orchestrator/send-message/execute.sh

@@ -5,10 +5,27 @@ set -euo pipefail
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 source "${SCRIPT_DIR}/../_common/lib.sh"
 
-INPUT=$(read_json_input "${1:-}")
+# CLI flags (--session/--to, --message, --force) are accepted too: the Gemini
+# safe-call guide shows the flag form.
+if [ "${1:-}" != "" ] && [ "${1#--}" != "${1}" ]; then
+  FLAG_SESSION=""; FLAG_MESSAGE=""; FLAG_FORCE=""
+  while [ $# -gt 0 ]; do
+    case "$1" in
+      --session|--sessionName|--to) FLAG_SESSION="${2:-}"; shift 2 ;;
+      --message) FLAG_MESSAGE="${2:-}"; shift 2 ;;
+      --force) FLAG_FORCE="true"; shift ;;
+      *) error_exit "Unknown option: $1" ;;
+    esac
+  done
+  INPUT=$(jq -n --arg s "$FLAG_SESSION" --arg m "$FLAG_MESSAGE" --arg f "$FLAG_FORCE" \
+    '{sessionName: $s, message: $m} + (if $f == "true" then {force: true} else {} end)')
+else
+  INPUT=$(read_json_input "${1:-}")
+fi
 [ -z "$INPUT" ] && error_exit "Usage: execute.sh '{\"sessionName\":\"agent-session\",\"message\":\"hello\"}' or echo '{...}' | execute.sh"
 
-SESSION_NAME=$(printf '%s' "$INPUT" | jq -r '.sessionName // empty')
+# `to` is accepted as an alias for `sessionName` (older prompt examples used it).
+SESSION_NAME=$(printf '%s' "$INPUT" | jq -r '.sessionName // .to // empty')
 MESSAGE=$(printf '%s' "$INPUT" | jq -r '.message // empty')
 FORCE=$(printf '%s' "$INPUT" | jq -r '.force // empty')
 require_param "sessionName" "$SESSION_NAME"

package/config/skills/orchestrator/send-message/execute.test.sh

@@ -0,0 +1,80 @@
+#!/bin/bash
+# Tests for the orchestrator send-message skill.
+#
+# Guards the input forms the orchestrator prompt teaches: JSON with
+# `sessionName` (canonical), JSON with `to` (older examples), and the CLI
+# flag form from the Gemini safe-call guide. `curl` is stubbed on PATH, so
+# every case runs offline and records the real request the skill issues.
+set -uo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PASS=0
+FAIL=0
+
+check() {
+  local name="$1" needle="$2" haystack="$3"
+  if printf '%s' "$haystack" | grep -qF -- "$needle"; then
+    PASS=$((PASS + 1)); echo "  ✓ ${name}"
+  else
+    FAIL=$((FAIL + 1)); echo "  ✗ ${name}"; echo "    expected to contain: ${needle}"; echo "    actual: ${haystack}"
+  fi
+}
+
+STUB_DIR="$(mktemp -d)"
+cat > "$STUB_DIR/curl" << 'STUB_EOF'
+#!/bin/bash
+URL=""; BODY=""
+while [ $# -gt 0 ]; do
+  case "$1" in
+    -d) BODY="$2"; shift 2 ;;
+    -X|-H|-w) shift 2 ;;
+    -s) shift ;;
+    *) URL="$1"; shift ;;
+  esac
+done
+printf '%s %s\n' "$URL" "$(printf '%s' "$BODY" | tr -d '\n ')" >> "$CURL_LOG"
+printf '{"success":true}\n200'
+STUB_EOF
+chmod +x "$STUB_DIR/curl"
+export PATH="$STUB_DIR:$PATH" CREWLY_API_URL="http://stub.invalid" CREWLY_SESSION_NAME="crewly-orc"
+
+# Runs the skill; sets OUT (stdout+stderr) and REQ (requests sent).
+run() {
+  CURL_LOG="$(mktemp)"; export CURL_LOG
+  OUT="$(bash "$SCRIPT_DIR/execute.sh" "$@" </dev/null 2>&1)" || true
+  REQ="$(cat "$CURL_LOG")"; rm -f "$CURL_LOG"
+}
+
+echo "=== orchestrator send-message tests ==="
+
+run '{"sessionName":"dev-1","message":"hi"}'
+check "sessionName JSON reaches /deliver for that session" "http://stub.invalid/api/terminal/dev-1/deliver" "$REQ"
+check "readiness-aware delivery by default" '"waitForReady":true' "$REQ"
+
+run '{"to":"dev-2","message":"hi"}'
+check "'to' is accepted as an alias for sessionName" "/api/terminal/dev-2/deliver" "$REQ"
+
+run --to dev-3 --message "hello there"
+check "--to/--message flags work" "/api/terminal/dev-3/deliver" "$REQ"
+check "flag message is sent" '"message":"hellothere"' "$REQ"
+
+run --session dev-4 --message hi --force
+check "--session and --force flags work" "/api/terminal/dev-4/deliver" "$REQ"
+check "--force sends force:true" '"force":true' "$REQ"
+
+run '{"message":"no target"}'
+check "missing session is reported" "sessionName" "$OUT"
+# (lib.sh sends a skill-start heartbeat; what must not happen is a delivery.)
+if printf '%s' "$REQ" | grep -q "/deliver"; then
+  FAIL=$((FAIL + 1)); echo "  ✗ missing session must not deliver anything"
+else
+  PASS=$((PASS + 1)); echo "  ✓ missing session delivers nothing"
+fi
+
+run --bogus x
+check "unknown flag is refused" "Unknown option: --bogus" "$OUT"
+
+rm -rf "$STUB_DIR"
+echo ""
+echo "=== Results: ${PASS} passed, ${FAIL} failed ==="
+[ "$FAIL" -eq 0 ]

package/config/skills/registry.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 2,
-  "lastUpdated": "2026-10-02T23:58:51.779Z",
+  "lastUpdated": "2026-10-03T01:12:43.309Z",
   "cdnBaseUrl": "https://raw.githubusercontent.com/stevehuang0115/crewly/main",
   "source": "github",
   "items": [
@@ -1412,7 +1412,7 @@
       "name": "SEO Ops",
       "description": "Search Console-driven SEO operations for any site: query patterns (low-CTR top-3, near-miss 4-20, rising queries, keyword cannibalization), per-URL report cards, pre-publish SEO/AEO checks, a gated programmatic-page queue, and a live-diff gate that stops agents from removing things from live pages. Use when auditing organic search, deciding what to rewrite, or before changing a live page. For writing posts use seo-blog-writer instead.",
       "author": "Crewly",
-      "version": "1.1.0",
+      "version": "1.2.0",
       "category": "development",
       "tags": [
         "seo",
@@ -1425,12 +1425,12 @@
       "downloads": 0,
       "rating": 0,
       "createdAt": "2026-09-29T01:43:29.904Z",
-      "updatedAt": "2026-10-02T23:58:51.779Z",
+      "updatedAt": "2026-10-03T01:12:43.309Z",
       "source": "config/skills/agent/marketplace/seo-ops",
       "assets": {
         "archive": "config/skills/agent/marketplace/seo-ops",
         "checksum": "",
-        "sizeBytes": 122232
+        "sizeBytes": 149452
       },
       "metadata": {
         "skillType": "claude-skill",
@@ -1448,7 +1448,8 @@
           "pre-publish seo check",
           "programmatic seo pages",
           "live page diff",
-          "experiment metric"
+          "experiment metric",
+          "url inspection"
         ],
         "files": [
           "execute.sh",

package/config/skills/team-leader/signal-digest/SKILL.md

@@ -0,0 +1,110 @@
+---
+name: Signal Digest
+description: "Daily signal digest for a site you own as team lead: GA4 traffic and key events, Search Console opportunities (low-CTR top-3, near-miss 4-20, rising, cannibalization), the site's inbound mail and broken pages / JS errors, minus what was already tried — turned into 3-5 ranked actions the owner answers Do / Skip on one Slack card. Do opens an experiment ticket."
+version: 1.1.0
+category: productivity
+skillType: claude-skill
+assignableRoles:
+  - team-leader
+triggers:
+  - daily signal digest
+  - daily signals
+  - what should we try on the site
+  - site opportunities
+tags:
+  - seo
+  - analytics
+  - experiments
+  - owner-decisions
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 180000
+---
+
+# Signal Digest (team lead)
+
+One run per site per day (#987, `specs/2026-10-03-signal-digest.md`):
+
+1. **collect** — gathers the signals and drafts actions.
+2. **you decide** — keep the 3–5 actions most worth the owner's tap, rewrite them in plain words,
+   add your own (e.g. a question the inbox keeps asking → an FAQ section).
+3. **propose** — the owner gets **one card**: each action with **Do** / **Skip**.
+   - **Do** opens an experiment ticket in the site's project and, when the action names an
+     `experiment` metric, an **experiment card** (#986) linked to it: the baseline is captured when
+     the ticket is done and the result is measured after 14 days, automatically. You get a
+     `[SIGNAL DIGEST]` message with both ids. Ship it and close the ticket.
+   - **Skip** keeps that action off your list for 30 days. A Do keeps it off for 90.
+   - Unanswered actions are replaced by your next digest (you may propose them again).
+
+## Setup (once per site)
+
+The config is the site's **seo-ops** config plus a `signalDigest` section — copy
+`signal-digest.config.example.json`. Google access is seo-ops's service account
+(`SEO_OPS_GOOGLE_CREDENTIALS`, read-only: Search Console user + GA4 Viewer).
+
+| `signalDigest` key | Meaning |
+|---|---|
+| `site` | Site name on the card and in the history (default: host of `siteUrl`) |
+| `project` | Project the Do tickets go into (name or id). Without it a Do opens no ticket |
+| `days` | Window, compared with the window before it (default 7) |
+| `ga4.conversionEvents` | Key events that count as conversions (default: all key events) |
+| `inbox.query` / `.account` / `.max` | Gmail search for the site's inbound requests (Google connector) |
+| `errors.checkSitemap` / `.maxUrls` | Fetch up to N sitemap pages and report the ones not answering 200 (default on, 60) |
+| `errors.url` or `errors.command` | JS errors as JSON: `[{"message","count","url"}]` or `{"errors":[…]}` |
+| `experimentLog` | Extra Markdown experiment log; a draft whose query/page it mentions is dropped (experiment cards are always checked) |
+| `thresholds` | `ga4DropPct` (20), `ga4MinPrevSessions` (50), `ga4MinPrevKeyEvents` (5) |
+
+Daily run: `bash execute.sh schedule --config <file> [--cron "0 8 * * *"] [--timezone America/New_York]`
+prints the cron task; hand it to the orchestrator to create with `create-cron`.
+
+## Commands
+
+```bash
+bash execute.sh collect --config ce.signal.json            # JSON: signals, alreadyTried, candidates
+bash execute.sh propose --config ce.signal.json --actions actions.json
+```
+
+`collect` prints `sources` (ok / not configured / error: why), the signals (`ga4`, `gsc`,
+`inbox`, `errors`), `alreadyTried` (dropped drafts and why: the owner's earlier Do / Skip, an
+experiment card on the same query or page, or the experiment log), `pendingOnOwner` and up to 10
+`candidates`, best first. GA4 respects seo-ops' `ga4HostName`. The sitemap check takes a different
+slice of `errors.maxUrls` pages each day, so the whole sitemap is covered over a few days.
+
+`collect` also reports the source statuses to Crewly (`sourceReport` in the output). The owner is
+told **once** when a source starts failing and once when it works again; the digest card shows
+each source's status. So never post about a failing source yourself. Exit `1` when no source
+could be examined: stop there and do not propose from nothing.
+
+`--actions` is a JSON array (file or inline) of 3–5 actions, best first:
+
+```json
+[{"key":"gsc:low-ctr:h1b visa fee","source":"gsc",
+  "signal":"'h1b visa fee' ranks #2 with 4% CTR on 900 impressions (7 days)",
+  "proposal":"Rewrite the title and description of /h1b-fee to answer the fee question",
+  "expectedEffect":"CTR 4% → ~16%: about +100 clicks a week",
+  "effort":"S — 1 h","metric":"GSC CTR for 'h1b visa fee'",
+  "experiment":{"source":"gsc","measure":"ctr","query":"h1b visa fee","page":"https://visa.careerengine.us/h1b-fee"}}]
+```
+
+- `key` is the action's identity across days. Keep the draft's key when you keep its action;
+  for your own, use `<source>:<kind>:<subject>`.
+- `source`: `ga4` | `gsc` | `inbox` | `errors` | `other`.
+- Lengths: signal ≤ 400, proposal ≤ 200, expectedEffect ≤ 240, effort ≤ 60 characters.
+- `experiment` (optional, keep the draft's): the seo-ops metric that measures it —
+  `source` gsc (`clicks` / `impressions` / `ctr` / `position`, filters `query`, `page`) or
+  ga4 (`sessions` / `events`, `event`, `channel`). Leave it out for fixes that move no metric
+  (a broken page, a JS error).
+
+`propose` answers `{"success":true,"digestId":"SD-4","card":"posted"}`. A `409` lists actions
+the owner already decided — replace them and propose again. One card a day: while today's
+digest (the last 20 hours) still has open actions, proposing the same actions returns it and
+different ones get a `409` — do not post a second card.
+
+## Rules
+
+- Never propose what `alreadyTried` lists, and never more than 5 actions.
+- Each action states signal → proposal → expected effect → effort, with a number when there is one.
+- This skill only reads Google and Gmail; it never changes the site.

package/config/skills/team-leader/signal-digest/execute.sh

@@ -0,0 +1,173 @@
+#!/bin/bash
+# =============================================================================
+# signal-digest — a site's daily signals → 3–5 actions → one owner card (#987)
+#
+#   collect   GA4 + Search Console + the site inbox + broken pages / JS errors,
+#             minus what was already tried; prints JSON with draft actions.
+#             Reports each source's status to Crewly, which tells the owner
+#             once when a source starts or stops failing.
+#   propose   send 3–5 actions; the owner gets one Slack card with Do / Skip
+#             per action (Do opens an experiment ticket in the site's project).
+#   schedule  print the daily cron task for the orchestrator to create.
+#
+# Usage:
+#   bash execute.sh collect  --config site.signal.json [--days 7]
+#   bash execute.sh propose  --config site.signal.json --actions actions.json
+#   bash execute.sh schedule --config site.signal.json [--cron "0 8 * * *"] [--timezone America/New_York]
+#   bash execute.sh '{"command":"collect","config":"site.signal.json"}'
+# =============================================================================
+set -euo pipefail
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "${SCRIPT_DIR}/../_common/lib.sh"
+
+DEFAULT_CRON="0 8 * * *"
+DEFAULT_TIMEZONE="America/New_York"
+
+print_usage() {
+  cat <<'EOF_USAGE'
+Usage:
+  bash execute.sh collect  --config site.signal.json [--days 7]
+  bash execute.sh propose  --config site.signal.json --actions actions.json   (file, or inline JSON)
+  bash execute.sh schedule --config site.signal.json [--cron "0 8 * * *"] [--timezone America/New_York]
+  bash execute.sh '{"command":"collect","config":"site.signal.json"}'
+
+The config is the site's seo-ops config plus a "signalDigest" section
+(see signal-digest.config.example.json).
+EOF_USAGE
+}
+
+COMMAND=""; CONFIG=""; DAYS=""; ACTIONS=""; CRON=""; TIMEZONE=""
+if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
+  INPUT=$(read_json_input "$1")
+  shift || true
+  COMMAND=$(printf '%s' "$INPUT" | jq -r '.command // empty')
+  CONFIG=$(printf '%s' "$INPUT" | jq -r '.config // empty')
+  DAYS=$(printf '%s' "$INPUT" | jq -r '.days // empty')
+  ACTIONS=$(printf '%s' "$INPUT" | jq -r 'if .actions == null then empty elif (.actions | type) == "string" then .actions else (.actions | tojson) end')
+  CRON=$(printf '%s' "$INPUT" | jq -r '.cron // empty')
+  TIMEZONE=$(printf '%s' "$INPUT" | jq -r '.timezone // empty')
+elif [[ $# -gt 0 && ${1:0:1} != '-' ]]; then
+  COMMAND="$1"
+  shift
+fi
+while [[ $# -gt 0 ]]; do
+  case "$1" in
+    --config|-c)  [ $# -ge 2 ] || error_exit "--config requires a value";   CONFIG="$2";   shift 2 ;;
+    --days)       [ $# -ge 2 ] || error_exit "--days requires a value";     DAYS="$2";     shift 2 ;;
+    --actions)    [ $# -ge 2 ] || error_exit "--actions requires a value";  ACTIONS="$2";  shift 2 ;;
+    --cron)       [ $# -ge 2 ] || error_exit "--cron requires a value";     CRON="$2";     shift 2 ;;
+    --timezone)   [ $# -ge 2 ] || error_exit "--timezone requires a value"; TIMEZONE="$2"; shift 2 ;;
+    --help|-h)    print_usage; exit 0 ;;
+    *) error_exit "Unknown option: $1" ;;
+  esac
+done
+[ -n "$COMMAND" ] || { print_usage; exit 1; }
+require_param "config (--config)" "$CONFIG"
+[ -f "$CONFIG" ] || error_exit "Config file not found: $CONFIG"
+jq -e 'type == "object"' "$CONFIG" >/dev/null 2>&1 || error_exit "Config file $CONFIG is not a JSON object"
+
+# The site name: signalDigest.site, else the host of siteUrl.
+SITE=$(jq -r '.signalDigest.site // ((.siteUrl // "") | sub("^[a-zA-Z]+://"; "") | sub("/.*$"; ""))' "$CONFIG")
+[ -n "$SITE" ] || error_exit "Config needs signalDigest.site (or siteUrl) to name the site"
+PROJECT=$(jq -r '.signalDigest.project // empty' "$CONFIG")
+uri() { jq -rn --arg v "$1" '$v|@uri'; }
+
+# api_call may print a one-line warning to stderr; the answer is the last line.
+call() {
+  local out
+  out=$(api_call "$@" 2>&1) || { printf '%s\n' "$out" | tail -n 1; return 1; }
+  printf '%s\n' "$out" | tail -n 1
+}
+
+case "$COMMAND" in
+  collect)
+    command -v python3 >/dev/null 2>&1 || error_exit "python3 (>= 3.8) is required"
+    WORK=$(mktemp -d)
+    trap 'rm -rf "$WORK"' EXIT
+    ARGS=(collect --config "$CONFIG")
+    [ -n "$DAYS" ] && ARGS+=(--days "$DAYS")
+    # History: what the owner already chose Do / Skip on for this site.
+    if HISTORY=$(call GET "/signal-digests/history?site=$(uri "$SITE")"); then
+      printf '%s' "$HISTORY" > "$WORK/history.json"
+      ARGS+=(--history "$WORK/history.json")
+    else
+      echo "{\"warning\":\"could not read the site history from Crewly; already-decided actions are not filtered out\"}" >&2
+    fi
+    # Experiment cards (#986): drafts their query / page already covers are dropped.
+    if EXPERIMENTS=$(call GET "/experiments"); then
+      printf '%s' "$EXPERIMENTS" > "$WORK/experiments.json"
+      ARGS+=(--experiments "$WORK/experiments.json")
+    else
+      echo "{\"warning\":\"could not read the experiment cards from Crewly; drafts they cover are not filtered out\"}" >&2
+    fi
+    # Inbox: the site's inbound requests (signalDigest.inbox.query), via Gmail.
+    INBOX_QUERY=$(jq -r '.signalDigest.inbox.query // empty' "$CONFIG")
+    if [ -n "$INBOX_QUERY" ]; then
+      INBOX_ACCOUNT=$(jq -r '.signalDigest.inbox.account // empty' "$CONFIG")
+      INBOX_MAX=$(jq -r '.signalDigest.inbox.max // 20' "$CONFIG")
+      [ -n "$INBOX_ACCOUNT" ] && export CREWLY_GOOGLE_ACCOUNT="$INBOX_ACCOUNT"
+      if INBOX=$(call GET "/google/gmail/search?q=$(uri "$INBOX_QUERY")&max=$(uri "$INBOX_MAX")"); then
+        printf '%s' "$INBOX" | jq -c '{query: .data.query, count: .data.count, messages: [.data.messages[]? | {from, subject, date, snippet}]}' > "$WORK/inbox.json"
+      else
+        printf '%s' "$INBOX" | jq -c '{success: false, reason: (.details.error // .error // "unknown"), message: (.details.message // .message // "")}' > "$WORK/inbox.json" 2>/dev/null \
+          || jq -n '{success: false, reason: "unreadable answer"}' > "$WORK/inbox.json"
+      fi
+      ARGS+=(--inbox "$WORK/inbox.json")
+    fi
+    set +e
+    RESULT=$(python3 "$SCRIPT_DIR/signal_digest.py" "${ARGS[@]}")
+    CODE=$?
+    set -e
+    [ -n "$RESULT" ] || exit "$CODE"
+    # Source status → Crewly. The owner hears once when a source starts or
+    # stops failing; nothing is posted on the days nothing changes.
+    REPORT='{"sent":false}'
+    SOURCES=$(printf '%s' "$RESULT" | jq -c '.sources // empty' 2>/dev/null || true)
+    if [ -n "$SOURCES" ]; then
+      BODY=$(jq -cn --arg site "$SITE" --argjson sources "$SOURCES" '{site: $site, sources: $sources}')
+      if ANSWER=$(call POST "/signal-digests/sources" "$BODY"); then
+        REPORT=$(printf '%s' "$ANSWER" | jq -c '{sent: true, started: (.data.started // []), stopped: (.data.stopped // []), ownerTold: (.data.notified // false)}' 2>/dev/null || echo '{"sent":true}')
+      else
+        echo "{\"warning\":\"could not report the source status to Crewly; the owner is not told about source failures\"}" >&2
+      fi
+    fi
+    printf '%s' "$RESULT" | jq --argjson report "$REPORT" '. + {sourceReport: $report}' 2>/dev/null || printf '%s\n' "$RESULT"
+    exit "$CODE"
+    ;;
+
+  propose)
+    require_param "actions (--actions)" "$ACTIONS"
+    if [ -f "$ACTIONS" ]; then ACTIONS_JSON=$(cat "$ACTIONS"); else ACTIONS_JSON="$ACTIONS"; fi
+    ITEMS=$(printf '%s' "$ACTIONS_JSON" | jq -c 'if type == "array" then . elif type == "object" and (.items | type) == "array" then .items elif type == "object" and (.actions | type) == "array" then .actions else error("expected an array of actions") end' 2>/dev/null) \
+      || error_exit "--actions must be a JSON array of actions (or {\"items\": [...]}), as a file or inline"
+    # The absolute config lets a Do create the action's experiment card (#986).
+    CONFIG_ABS="$(cd "$(dirname "$CONFIG")" && pwd)/$(basename "$CONFIG")"
+    BODY=$(jq -cn --arg site "$SITE" --arg project "$PROJECT" --arg config "$CONFIG_ABS" --argjson items "$ITEMS" \
+      '{site: $site, config: $config, items: [$items[] | {key, source, signal, proposal, expectedEffect, effort}
+          + (if .metric then {metric} else {} end) + (if .experiment then {experiment} else {} end)]}
+        + (if $project != "" then {project: $project} else {} end)')
+    if ! RESPONSE=$(call POST "/signal-digests" "$BODY"); then
+      printf '%s' "$RESPONSE" | jq -c '{success: false, error: (.details.error // .error // .details // "unknown")}' 2>/dev/null || jq -n --arg r "$RESPONSE" '{success: false, error: $r}'
+      exit 1
+    fi
+    printf '%s' "$RESPONSE" | jq -c '{success: true, digestId: .data.id, site: .data.site, actions: (.data.items | length)}
+      + (if .data.card then {card: "posted"} else {card: "not posted", postError: .data.postError} end)'
+    ;;
+
+  schedule)
+    # Cron tasks are created by the orchestrator (or the owner), not by a lead:
+    # print the exact create-cron call to hand over.
+    [ -n "${CREWLY_SESSION_NAME:-}" ] || error_exit "CREWLY_SESSION_NAME is not set: run this from your agent session"
+    TEAM_ID=$(resolve_team_id) || error_exit "Could not find the team of ${CREWLY_SESSION_NAME}"
+    CONFIG_ABS="$(cd "$(dirname "$CONFIG")" && pwd)/$(basename "$CONFIG")"
+    TASK="Daily signal digest for ${SITE}: run \`bash ${SCRIPT_DIR}/execute.sh collect --config ${CONFIG_ABS}\`, pick the 3-5 actions most worth the owner's tap (rewrite the drafts as needed), then run \`bash ${SCRIPT_DIR}/execute.sh propose --config ${CONFIG_ABS} --actions <file>\`. If no source could be examined, stop there: the owner is told once when a source starts or stops failing, so post nothing about it."
+    CRON_JSON=$(jq -cn --arg cron "${CRON:-$DEFAULT_CRON}" --arg tz "${TIMEZONE:-$DEFAULT_TIMEZONE}" --arg agent "$CREWLY_SESSION_NAME" --arg team "$TEAM_ID" --arg task "$TASK" \
+      '{cronExpression: $cron, timezone: $tz, targetAgent: $agent, targetTeamId: $team, taskDescription: $task}')
+    jq -cn --argjson cron "$CRON_JSON" '{success: true, createCron: $cron,
+      next: "Cron tasks are created by the orchestrator: send it this createCron object and ask it to run create-cron with it (or the owner can add it under Schedules)."}'
+    ;;
+
+  *)
+    error_exit "Unknown command: ${COMMAND} (collect | propose | schedule)"
+    ;;
+esac