crewly 1.20.192 → 1.20.193

package/config/skills/agent/core/report-status/execute.sh

@@ -9,7 +9,12 @@ print_usage() {
   cat <<'EOF_USAGE'
 Usage:
   # CLI flags (preferred — avoids shell escaping issues)
-  bash execute.sh --session dev-1 --status done --summary "Fixed the bug" --project /path/to/project
+  bash execute.sh --session dev-1 --status done --summary "Fixed the bug" --project /path/to/project \
+    --artifact src/fix.ts --command "npm test" --exit-code 0 --output-tail "42 passed"
+
+  # Could not finish: done with a blocked step is recorded as BLOCKED, not done
+  bash execute.sh --session dev-1 --status done --summary "Fix written, tests blocked" \
+    --blocked-step "npm test" --blocked-reason "test DB unreachable"
 
   # Summary from stdin (for multi-line or special characters)
   echo "Fixed the bug — it's working" | bash execute.sh --session dev-1 --status done --project /path
@@ -37,6 +42,18 @@ Options:
   --progress        Progress percentage (0-100, for structured format)
   --structured      Use structured StatusReport format (true/false)
   --json     | -j   Raw JSON payload (same as legacy)
+
+Evidence (status done — #873: "done" needs evidence):
+  --artifact <path>        A file the work produced (absolute, relative to the
+                           project/worktree, or an https URL). Must exist. Repeatable.
+  --command <cmd>          A command you ran. Follow it with --exit-code (required)
+  --exit-code <n>          and optionally --output-tail. Repeatable as a group.
+  --output-tail <text>     Last lines of that command's output.
+  --blocked-step <step>    You could not finish: the step that failed ...
+  --blocked-reason <why>   ... and why. The WorkItem is recorded as BLOCKED, not done.
+  --evidence <json>        Raw evidence array, e.g. '[{"type":"artifact","path":"/abs/f"}]'
+  A non-zero --exit-code or a missing artifact is rejected by the server. Without
+  any evidence, done is accepted this release with a warning; next release it is refused.
   --help     | -h   Show this help
 EOF_USAGE
 }
@@ -52,6 +69,28 @@ TASK_ID=""
 WORK_ITEM_ID=""
 PROGRESS=""
 STRUCTURED="false"
+# Evidence entries built from flags (#873), as a JSON array.
+FLAG_EVIDENCE='[]'
+BLOCKED_STEP=""
+BLOCKED_REASON=""
+EVIDENCE_ARG=""
+
+# add_evidence <jq-object-expression> [jq --arg pairs...]
+# Appends one entry to FLAG_EVIDENCE.
+add_evidence() {
+  local expr="$1"; shift
+  FLAG_EVIDENCE=$(printf '%s' "$FLAG_EVIDENCE" | jq -c "$@" ". + [${expr}]")
+}
+
+# set_last_command_field <field> <jq value expression> [jq --arg/--argjson pairs...]
+# Sets a field on the most recent --command entry; refuses when there is none.
+set_last_command_field() {
+  local field="$1" valexpr="$2" flag="$3"; shift 3
+  if [ "$(printf '%s' "$FLAG_EVIDENCE" | jq -r 'if length > 0 and .[-1].type == "command" then "yes" else "no" end')" != "yes" ]; then
+    error_exit "${flag} must follow --command <cmd>"
+  fi
+  FLAG_EVIDENCE=$(printf '%s' "$FLAG_EVIDENCE" | jq -c "$@" ".[-1].${field} = ${valexpr}")
+}
 
 # Detect legacy JSON argument as the first parameter
 if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
@@ -109,6 +148,35 @@ while [[ $# -gt 0 ]]; do
       INPUT_JSON="$2"
       shift 2
       ;;
+    --artifact)
+      add_evidence '{type: "artifact", path: $p}' --arg p "$2"
+      shift 2
+      ;;
+    --command)
+      add_evidence '{type: "command", command: $c}' --arg c "$2"
+      shift 2
+      ;;
+    --exit-code)
+      [[ "$2" =~ ^-?[0-9]+$ ]] || error_exit "--exit-code must be an integer (got \"$2\")"
+      set_last_command_field exitCode '($n | tonumber)' --exit-code --arg n "$2"
+      shift 2
+      ;;
+    --output-tail)
+      set_last_command_field outputTail '$t' --output-tail --arg t "$2"
+      shift 2
+      ;;
+    --blocked-step)
+      BLOCKED_STEP="$2"
+      shift 2
+      ;;
+    --blocked-reason)
+      BLOCKED_REASON="$2"
+      shift 2
+      ;;
+    --evidence)
+      EVIDENCE_ARG="$2"
+      shift 2
+      ;;
     --help|-h)
       print_usage
       exit 0
@@ -152,6 +220,7 @@ if [ -n "$INPUT_JSON" ]; then
   [ -z "$AGENT_ROLE" ] && AGENT_ROLE=$(printf '%s' "$INPUT" | jq -r '.role // .agentRole // empty')
   ARTIFACTS=$(printf '%s' "$INPUT" | jq -c '.artifacts // empty')
   BLOCKERS=$(printf '%s' "$INPUT" | jq -c '.blockers // empty')
+  [ -z "$EVIDENCE_ARG" ] && EVIDENCE_ARG=$(printf '%s' "$INPUT" | jq -c '.evidence // empty')
   USE_STRUCTURED=$(printf '%s' "$INPUT" | jq -r '.structured // "false"')
   [ "$USE_STRUCTURED" = "true" ] && STRUCTURED="true"
 else
@@ -159,6 +228,24 @@ else
   BLOCKERS=""
 fi
 
+# Assemble the evidence block (#873): --evidence / JSON `evidence` first, then
+# the entries from --artifact / --command / --blocked-step flags.
+if [ -n "$EVIDENCE_ARG" ]; then
+  if ! printf '%s' "$EVIDENCE_ARG" | jq -e 'type == "array"' >/dev/null 2>&1; then
+    error_exit "evidence must be a JSON array, e.g. '[{\"type\":\"artifact\",\"path\":\"/abs/file\"}]'"
+  fi
+else
+  EVIDENCE_ARG='[]'
+fi
+if [ -n "$BLOCKED_STEP" ] || [ -n "$BLOCKED_REASON" ]; then
+  [ -n "$BLOCKED_STEP" ] && [ -n "$BLOCKED_REASON" ] || error_exit "--blocked-step and --blocked-reason go together: name the step that failed and why"
+  add_evidence '{type: "blocked", step: $s, reason: $r}' --arg s "$BLOCKED_STEP" --arg r "$BLOCKED_REASON"
+fi
+if [ "$(printf '%s' "$FLAG_EVIDENCE" | jq '[.[] | select(.type == "command" and (has("exitCode") | not))] | length')" != "0" ]; then
+  error_exit "every --command needs --exit-code <n> after it: the exit code is the evidence"
+fi
+EVIDENCE=$(jq -cn --argjson a "$EVIDENCE_ARG" --argjson b "$FLAG_EVIDENCE" '$a + $b')
+
 require_param "sessionName (--session)" "$SESSION_NAME"
 require_param "status (--status)" "$STATUS"
 require_param "summary (--summary)" "$SUMMARY"
@@ -297,18 +384,31 @@ if [ "$STATUS" = "done" ]; then
     # `completeItem`). Prior shape `{summary}` 400'd with
     # `agentId is required` + `summary required in body.result`,
     # forcing every worker into a direct-curl workaround.
+    #
+    # #873: the evidence block goes in result.evidence. Omitted when empty
+    # (the server then warns this release, refuses the next).
     COMPLETE_BODY=$(jq -n \
       --arg agentId "$SESSION_NAME" \
       --arg summary "$SUMMARY" \
-      '{agentId: $agentId, result: {summary: $summary}}')
+      --argjson evidence "$EVIDENCE" \
+      '{agentId: $agentId, result: ({summary: $summary} + (if ($evidence | length) > 0 then {evidence: $evidence} else {} end))}')
     # No `|| true`. A swallowed failure here is the inverse of the bug above:
     # report-status would announce success while the WorkItem stayed open, and
     # that is equally invisible. Report what actually happened either way.
     if COMPLETE_RESULT=$(api_call POST "/task-pool/complete/${TARGET_WI_ID}" "$COMPLETE_BODY" 2>&1); then
       # Echo the resolved id even on the happy path. Silent-but-correct is how
       # this class hides — the caller must be able to see WHICH item closed.
-      jq -n --arg id "$TARGET_WI_ID" --arg how "$WI_RESOLUTION" \
-        '{completedWorkItem: $id, resolvedBy: $how}' >&2
+      # A `blocked` evidence entry is recorded as blocked, not done (#873);
+      # a completion without evidence carries the server's warning.
+      COMPLETE_WARNING=$(printf '%s' "$COMPLETE_RESULT" | jq -rs '(map(select(type == "object" and has("success"))) | last // {}) | .warning // empty' 2>/dev/null || true)
+      COMPLETE_RECORDED=$(printf '%s' "$COMPLETE_RESULT" | jq -rs '(map(select(type == "object" and has("success"))) | last // {}) | .recordedAs // empty' 2>/dev/null || true)
+      if [ "$COMPLETE_RECORDED" = "blocked" ]; then
+        jq -n --arg id "$TARGET_WI_ID" --arg how "$WI_RESOLUTION" \
+          '{workItem: $id, markedAs: "blocked", resolvedBy: $how, note: "blocked evidence: recorded as blocked, not done"}' >&2
+      else
+        jq -n --arg id "$TARGET_WI_ID" --arg how "$WI_RESOLUTION" --arg w "$COMPLETE_WARNING" \
+          '{completedWorkItem: $id, resolvedBy: $how} + (if $w != "" then {warning: $w} else {} end)' >&2
+      fi
     else
       jq -n --arg id "$TARGET_WI_ID" --arg err "$COMPLETE_RESULT" \
         '{warning: "status reported, but completing the WorkItem FAILED — it is still open", workItemId: $id, error: $err}' >&2

package/config/skills/agent/core/todo-add/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: To Do Add
-description: Add a task to one of the owner's Microsoft To Do lists — title, optional due date, note and importance (via the Microsoft grant held by Crewly Cloud).
-version: 1.0.0
+description: Add a task to one of the owner's Microsoft To Do lists — title, optional due date, note, importance and steps (checklist items) (via the Microsoft grant held by Crewly Cloud).
+version: 1.1.0
 category: productivity
 skillType: claude-skill
 assignableRoles:
@@ -18,6 +18,7 @@ triggers:
   - add a microsoft to do task
   - remind me in to do
   - create an outlook task
+  - add a task with steps
 tags:
   - microsoft
   - todo
@@ -35,8 +36,13 @@ execution:
 ```bash
 bash execute.sh --title "Buy milk"                     # default list ("Tasks")
 bash execute.sh --list Work --title "Send deck to Ann" --due 2026-10-01 --importance high --note "v3 is in Drive"
+bash execute.sh --list Groceries --title "Costco" --steps "Eggs,Milk,Bread"   # ONE task with three steps
 ```
 
+When the owner asks for items as **steps of one task** (a shopping run, a
+packing list), use `--steps` — do not put them in the note, and do not make
+one task per item unless he asked for separate tasks.
+
 | Flag | Meaning |
 |---|---|
 | `--title` | Task title (required) |
@@ -44,13 +50,21 @@ bash execute.sh --list Work --title "Send deck to Ann" --due 2026-10-01 --import
 | `--due` | Due date `YYYY-MM-DD` |
 | `--note` | Note shown under the task |
 | `--importance` | `low` \| `normal` \| `high` |
+| `--steps` | Comma-separated steps (checklist items), in order |
+| `--step` | One step; repeat it for more (for a step that contains a comma) |
 
 ## Output
 
 ```json
 {"success":true,"list":"Work","task":{"id":"AAMk…","title":"Send deck to Ann","status":"notStarted","importance":"high","due":"2026-10-01","note":"v3 is in Drive"}}
+{"success":true,"list":"Groceries","task":{"id":"AAMk…","title":"Costco","status":"notStarted","steps":[{"id":"…","title":"Eggs","checked":false},{"id":"…","title":"Milk","checked":false}]}}
 ```
 
+Steps are created after the task. If one fails, the task still exists and
+the answer lists it in `failedSteps` (`[{"step":"Milk","error":"…"}]`):
+add it with todo-update `--add-steps` — do **not** run todo-add again, that
+would make a second task.
+
 A list that does not exist is not created — make it with todo-lists
 `--create` first.
 

package/config/skills/agent/core/todo-add/execute.sh

@@ -7,6 +7,7 @@
 # Usage:
 #   bash execute.sh --title "Buy milk"                                  # default list
 #   bash execute.sh --list Work --title "Send deck to Ann" --due 2026-10-01 --importance high --note "v3 in Drive"
+#   bash execute.sh --list Groceries --title "Costco" --steps "Eggs,Milk,Bread"     # one task, three steps
 #   bash execute.sh '{"list":"Groceries","title":"Eggs"}'
 # =============================================================================
 set -euo pipefail
@@ -18,7 +19,8 @@ print_usage() {
 Usage:
   bash execute.sh --title "Buy milk"                                  # default list
   bash execute.sh --list Work --title "Send deck to Ann" --due 2026-10-01 --importance high --note "v3 in Drive"
-  bash execute.sh '{"list":"Groceries","title":"Eggs"}'
+  bash execute.sh --list Groceries --title "Costco" --steps "Eggs,Milk,Bread"     # one task, three steps
+  bash execute.sh '{"list":"Groceries","title":"Costco","steps":["Eggs","Milk"]}'
 
 Options:
   --title, -t    Task title (required)
@@ -26,6 +28,8 @@ Options:
   --due          Due date, YYYY-MM-DD
   --note         Note text shown under the task
   --importance   low | normal | high
+  --steps        Comma-separated steps (checklist items) to create on the task
+  --step         One step; repeat for more (use when a step contains a comma)
   --help | -h    Show this help
 EOF_USAGE
 }
@@ -38,6 +42,12 @@ fail_from() {
 
 uri() { jq -rn --arg v "$1" '$v|@uri'; }
 
+# Append step titles to a JSON array: $1 = array, $2 = text, $3 = "split" to
+# split the text on commas. Titles are trimmed; empty ones are dropped.
+add_steps() {
+  jq -c --arg v "$2" --arg mode "${3:-}" '. + (if $mode == "split" then ($v | split(",")) else [$v] end | map(gsub("^\\s+|\\s+$"; "")) | map(select(length > 0)))' <<<"$1"
+}
+
 # api_call may print a one-line warning to stderr (no CREWLY_SESSION_NAME);
 # the backend answer is always the last line. On failure print the mapped
 # failure JSON (fail_from) and return 1.
@@ -52,7 +62,7 @@ if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
   INPUT_JSON="$1"
   shift || true
 fi
-TITLE=""; LIST=""; DUE=""; NOTE=""; IMPORTANCE=""
+TITLE=""; LIST=""; DUE=""; NOTE=""; IMPORTANCE=""; STEPS='[]'
 while [[ $# -gt 0 ]]; do
   case "$1" in
     --title|-t)   [ $# -ge 2 ] || error_exit "--title requires a value";      TITLE="$2";      shift 2 ;;
@@ -60,6 +70,8 @@ while [[ $# -gt 0 ]]; do
     --due)        [ $# -ge 2 ] || error_exit "--due requires a value";        DUE="$2";        shift 2 ;;
     --note)       [ $# -ge 2 ] || error_exit "--note requires a value";       NOTE="$2";       shift 2 ;;
     --importance) [ $# -ge 2 ] || error_exit "--importance requires a value"; IMPORTANCE="$2"; shift 2 ;;
+    --steps)      [ $# -ge 2 ] || error_exit "--steps requires a value";      STEPS=$(add_steps "$STEPS" "$2" split); shift 2 ;;
+    --step)       [ $# -ge 2 ] || error_exit "--step requires a value";       STEPS=$(add_steps "$STEPS" "$2");       shift 2 ;;
     --help|-h)    print_usage; exit 0 ;;
     *) error_exit "Unknown option: $1" ;;
   esac
@@ -71,14 +83,18 @@ if [ -n "$INPUT_JSON" ]; then
   [ -z "$DUE" ]        && DUE=$(printf '%s' "$INPUT" | jq -r '.due // empty')
   [ -z "$NOTE" ]       && NOTE=$(printf '%s' "$INPUT" | jq -r '.note // empty')
   [ -z "$IMPORTANCE" ] && IMPORTANCE=$(printf '%s' "$INPUT" | jq -r '.importance // empty')
+  if [ "$STEPS" = '[]' ]; then
+    STEPS=$(printf '%s' "$INPUT" | jq -c '.steps // [] | if type == "string" then split(",") else map(tostring) end | map(gsub("^\\s+|\\s+$"; "")) | map(select(length > 0))')
+  fi
 fi
 [ -n "$TITLE" ] || error_exit "--title is required"
 if [ -n "$DUE" ] && ! [[ "$DUE" =~ ^[0-9]{4}-[0-9]{2}-[0-9]{2}$ ]]; then error_exit "--due must look like 2026-10-01"; fi
-BODY=$(jq -cn --arg title "$TITLE" --arg list "$LIST" --arg due "$DUE" --arg note "$NOTE" --arg imp "$IMPORTANCE" \
+BODY=$(jq -cn --arg title "$TITLE" --arg list "$LIST" --arg due "$DUE" --arg note "$NOTE" --arg imp "$IMPORTANCE" --argjson steps "$STEPS" \
   '{title: $title}
       + (if $list != "" then {list: $list} else {} end)
       + (if $due != "" then {due: $due} else {} end)
       + (if $note != "" then {note: $note} else {} end)
-      + (if $imp != "" then {importance: $imp} else {} end)')
+      + (if $imp != "" then {importance: $imp} else {} end)
+      + (if ($steps | length) > 0 then {steps: $steps} else {} end)')
 RESPONSE=$(call POST "/microsoft-todo/tasks" "$BODY") || { printf '%s\n' "$RESPONSE"; exit 1; }
-printf '%s' "$RESPONSE" | jq -c '{success: true, list: .data.list.name, task: .data.task}'
+printf '%s' "$RESPONSE" | jq -c '{success: true, list: .data.list.name, task: .data.task} + (if .data.failedSteps then {failedSteps: .data.failedSteps} else {} end)'

package/config/skills/agent/core/todo-add/execute.test.sh

@@ -33,6 +33,8 @@ class H(BaseHTTPRequestHandler):
             out = {'list': LIST, 'count': 1, 'tasks': [{'id': 'T1', 'title': 'Milk', 'status': 'notStarted', 'due': '2026-10-01'}]}
         elif path == '/api/microsoft-todo/tasks':
             out = {'list': LIST, 'task': {'id': 'T2', 'title': (data or {}).get('title'), 'status': 'notStarted'}}
+            if (data or {}).get('title') == 'partial':
+                out['failedSteps'] = [{'step': 'Milk', 'error': 'Forbidden: no'}]
         elif method == 'PATCH':
             out = {'list': LIST, 'task': {'id': path.rsplit('/', 1)[1], 'title': 'Milk', 'status': 'completed'}}
         elif method == 'DELETE':
@@ -69,6 +71,18 @@ run '{"list":"Groceries","title":"Eggs"}' >/dev/null
 check "json input" "$(last '.body')" '{"title":"Eggs","list":"Groceries"}'
 check "title required" "$(run_err --list Work | jq -r .error)" "--title is required"
 check "bad due" "$(run_err --title x --due tomorrow | jq -r .error)" "--due must look like 2026-10-01"
+run --title "Costco" --steps "Eggs, Milk,,Bread " >/dev/null
+check "steps: comma list, trimmed, empties dropped" "$(last '.body')" '{"title":"Costco","steps":["Eggs","Milk","Bread"]}'
+run --title "Costco" --step "Eggs, large" --step Milk >/dev/null
+check "steps: repeated --step keeps commas" "$(last '.body.steps')" '["Eggs, large","Milk"]'
+run '{"title":"Costco","steps":["Eggs","Milk"]}' >/dev/null
+check "steps: json array" "$(last '.body.steps')" '["Eggs","Milk"]'
+run '{"title":"Costco","steps":"Eggs,Milk"}' >/dev/null
+check "steps: json string" "$(last '.body.steps')" '["Eggs","Milk"]'
+run --title "Plain" --steps " , " >/dev/null
+check "steps: none left means no steps field" "$(last '.body')" '{"title":"Plain"}'
+OUT=$(run --title partial --steps "Eggs,Milk")
+check "steps: failed steps are reported" "$(printf '%s' "$OUT" | jq -c '[.success,.failedSteps]')" '[true,[{"step":"Milk","error":"Forbidden: no"}]]'
 OUT=$(run --title no-grant || true)
 check "not connected" "$(printf '%s' "$OUT" | jq -r .reason)" "not_connected"
 

package/config/skills/agent/core/todo-tasks/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: To Do Tasks
-description: List the tasks in one of the owner's Microsoft To Do lists — open tasks by default, --all to include completed ones (via the Microsoft grant held by Crewly Cloud). Read-only.
-version: 1.0.0
+description: List the tasks in one of the owner's Microsoft To Do lists — open tasks by default, --all to include completed ones, with each task's steps (via the Microsoft grant held by Crewly Cloud). Read-only.
+version: 1.1.0
 category: productivity
 skillType: claude-skill
 assignableRoles:
@@ -46,7 +46,8 @@ bash execute.sh --list Work --limit 20 # default 50, max 100
 ```
 
 `importance` appears only when not normal; `note` is plain text, cut at
-200 characters. `hasMore: true` means the list has more tasks than the
+200 characters. `steps` (checklist items, in To Do order, each with `id`,
+`title` and `checked`) appears only on tasks that have steps. `hasMore: true` means the list has more tasks than the
 limit. Use the task `id` with todo-update.
 
 ## Failures

package/config/skills/agent/core/todo-update/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: To Do Update
-description: Complete, reopen, retitle, re-date or delete a task in one of the owner's Microsoft To Do lists (via the Microsoft grant held by Crewly Cloud).
-version: 1.0.0
+description: Complete, reopen, retitle, re-date or delete a task — and add, tick, untick or remove its steps — in one of the owner's Microsoft To Do lists (via the Microsoft grant held by Crewly Cloud).
+version: 1.1.0
 category: productivity
 skillType: claude-skill
 assignableRoles:
@@ -38,8 +38,18 @@ bash execute.sh --list Work --task <id> --title "Send v4 deck" --due 2026-10-03
 bash execute.sh --list Work --task <id> --due none     # clear the due date
 bash execute.sh --list Work --task <id> --reopen
 bash execute.sh --list Work --task <id> --delete       # cannot be undone
+bash execute.sh --list Groceries --task <id> --add-steps "Butter,Ham"
+bash execute.sh --list Groceries --task <id> --check-steps "Eggs,Milk"    # tick steps
+bash execute.sh --list Groceries --task <id> --uncheck-steps Eggs         # untick
+bash execute.sh --list Groceries --task <id> --remove-steps Bread         # delete a step
 ```
 
+Steps are named by title (case-insensitive) or by step id from todo-tasks.
+`--add-step` / `--check-step` / `--uncheck-step` / `--remove-step` take one
+step each and can be repeated, for a step whose title contains a comma.
+Adding steps changes the existing task; it never creates a new one. A step
+name that matches nothing (or two steps) fails before anything is changed.
+
 `--task` is the id from todo-tasks. `--list` is the list the task is in
 (name or id; the default list when omitted). Changes can be combined in one
 call; `--delete` ignores the others.
@@ -48,6 +58,7 @@ call; `--delete` ignores the others.
 
 ```json
 {"success":true,"list":"Groceries","task":{"id":"AAMk…","title":"Milk","status":"completed","completedAt":"2026-09-23"}}
+{"success":true,"list":"Groceries","task":{"id":"AAMk…","title":"Costco","status":"notStarted","steps":[{"id":"…","title":"Eggs","checked":true},{"id":"…","title":"Butter","checked":false}]}}
 {"success":true,"deleted":true,"list":"Work","taskId":"AAMk…"}
 ```
 

package/config/skills/agent/core/todo-update/execute.sh

@@ -10,6 +10,7 @@
 #   bash execute.sh --list Work --task <taskId> --due none          # clear the due date
 #   bash execute.sh --list Work --task <taskId> --reopen
 #   bash execute.sh --list Work --task <taskId> --delete
+#   bash execute.sh --list Groceries --task <taskId> --add-steps "Butter,Ham" --check-steps "Eggs"
 #   bash execute.sh '{"list":"Work","task":"AAMk…","complete":true}'
 # =============================================================================
 set -euo pipefail
@@ -24,6 +25,7 @@ Usage:
   bash execute.sh --list Work --task <taskId> --due none          # clear the due date
   bash execute.sh --list Work --task <taskId> --reopen
   bash execute.sh --list Work --task <taskId> --delete
+  bash execute.sh --list Groceries --task <taskId> --add-steps "Butter,Ham" --check-steps "Eggs"
   bash execute.sh '{"list":"Work","task":"AAMk…","complete":true}'
 
 Options:
@@ -36,6 +38,12 @@ Options:
   --note         Replace the note
   --importance   low | normal | high
   --delete       Delete the task (cannot be undone)
+  --add-steps    Comma-separated steps to append to the task
+  --check-steps  Comma-separated steps to tick, by title (case-insensitive) or step id
+  --uncheck-steps  Comma-separated steps to untick, by title or id
+  --remove-steps Comma-separated steps to delete, by title or id
+  --add-step, --check-step, --uncheck-step, --remove-step
+                 One step each; repeat for more (use when a step contains a comma)
   --help | -h    Show this help
 EOF_USAGE
 }
@@ -48,6 +56,17 @@ fail_from() {
 
 uri() { jq -rn --arg v "$1" '$v|@uri'; }
 
+# Append step titles / ids to a JSON array: $1 = array, $2 = text, $3 =
+# "split" to split the text on commas. Trimmed; empty ones are dropped.
+add_steps() {
+  jq -c --arg v "$2" --arg mode "${3:-}" '. + (if $mode == "split" then ($v | split(",")) else [$v] end | map(gsub("^\\s+|\\s+$"; "")) | map(select(length > 0)))' <<<"$1"
+}
+
+# Step list from the JSON input: $1 = key; an array or a comma string.
+input_steps() {
+  printf '%s' "$INPUT" | jq -c --arg k "$1" '.[$k] // [] | if type == "string" then split(",") else map(tostring) end | map(gsub("^\\s+|\\s+$"; "")) | map(select(length > 0))'
+}
+
 # api_call may print a one-line warning to stderr (no CREWLY_SESSION_NAME);
 # the backend answer is always the last line. On failure print the mapped
 # failure JSON (fail_from) and return 1.
@@ -63,6 +82,7 @@ if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
   shift || true
 fi
 TASK=""; LIST=""; COMPLETE=""; TITLE=""; DUE=""; NOTE=""; IMPORTANCE=""; DELETE=""
+ADD_STEPS='[]'; CHECK_STEPS='[]'; UNCHECK_STEPS='[]'; REMOVE_STEPS='[]'
 while [[ $# -gt 0 ]]; do
   case "$1" in
     --task)       [ $# -ge 2 ] || error_exit "--task requires a value";       TASK="$2";       shift 2 ;;
@@ -74,6 +94,14 @@ while [[ $# -gt 0 ]]; do
     --note)       [ $# -ge 2 ] || error_exit "--note requires a value";       NOTE="$2";       shift 2 ;;
     --importance) [ $# -ge 2 ] || error_exit "--importance requires a value"; IMPORTANCE="$2"; shift 2 ;;
     --delete)     DELETE="1"; shift ;;
+    --add-steps)     [ $# -ge 2 ] || error_exit "--add-steps requires a value";     ADD_STEPS=$(add_steps "$ADD_STEPS" "$2" split);         shift 2 ;;
+    --add-step)      [ $# -ge 2 ] || error_exit "--add-step requires a value";      ADD_STEPS=$(add_steps "$ADD_STEPS" "$2");               shift 2 ;;
+    --check-steps)   [ $# -ge 2 ] || error_exit "--check-steps requires a value";   CHECK_STEPS=$(add_steps "$CHECK_STEPS" "$2" split);     shift 2 ;;
+    --check-step)    [ $# -ge 2 ] || error_exit "--check-step requires a value";    CHECK_STEPS=$(add_steps "$CHECK_STEPS" "$2");           shift 2 ;;
+    --uncheck-steps) [ $# -ge 2 ] || error_exit "--uncheck-steps requires a value"; UNCHECK_STEPS=$(add_steps "$UNCHECK_STEPS" "$2" split); shift 2 ;;
+    --uncheck-step)  [ $# -ge 2 ] || error_exit "--uncheck-step requires a value";  UNCHECK_STEPS=$(add_steps "$UNCHECK_STEPS" "$2");       shift 2 ;;
+    --remove-steps)  [ $# -ge 2 ] || error_exit "--remove-steps requires a value";  REMOVE_STEPS=$(add_steps "$REMOVE_STEPS" "$2" split);   shift 2 ;;
+    --remove-step)   [ $# -ge 2 ] || error_exit "--remove-step requires a value";   REMOVE_STEPS=$(add_steps "$REMOVE_STEPS" "$2");         shift 2 ;;
     --help|-h)    print_usage; exit 0 ;;
     *) error_exit "Unknown option: $1" ;;
   esac
@@ -88,6 +116,10 @@ if [ -n "$INPUT_JSON" ]; then
   [ -z "$NOTE" ]       && NOTE=$(printf '%s' "$INPUT" | jq -r '.note // empty')
   [ -z "$IMPORTANCE" ] && IMPORTANCE=$(printf '%s' "$INPUT" | jq -r '.importance // empty')
   [ -z "$DELETE" ]     && DELETE=$(printf '%s' "$INPUT" | jq -r 'if .delete == true then "1" else empty end')
+  [ "$ADD_STEPS" = '[]' ]     && ADD_STEPS=$(input_steps addSteps)
+  [ "$CHECK_STEPS" = '[]' ]   && CHECK_STEPS=$(input_steps checkSteps)
+  [ "$UNCHECK_STEPS" = '[]' ] && UNCHECK_STEPS=$(input_steps uncheckSteps)
+  [ "$REMOVE_STEPS" = '[]' ]  && REMOVE_STEPS=$(input_steps removeSteps)
 fi
 [ -n "$TASK" ] || error_exit "--task is required (ids come from todo-tasks)"
 if [ -n "$DELETE" ]; then
@@ -100,16 +132,22 @@ fi
 if [ -n "$DUE" ] && [ "$DUE" != "none" ] && ! [[ "$DUE" =~ ^[0-9]{4}-[0-9]{2}-[0-9]{2}$ ]]; then
   error_exit "--due must look like 2026-10-01, or none to clear it"
 fi
-if [ -z "$COMPLETE" ] && [ -z "$TITLE" ] && [ -z "$DUE" ] && [ -z "$NOTE" ] && [ -z "$IMPORTANCE" ]; then
-  error_exit "nothing to change: give --complete, --reopen, --title, --due, --note, --importance or --delete"
+STEP_CHANGES="${ADD_STEPS}${CHECK_STEPS}${UNCHECK_STEPS}${REMOVE_STEPS}"
+if [ -z "$COMPLETE" ] && [ -z "$TITLE" ] && [ -z "$DUE" ] && [ -z "$NOTE" ] && [ -z "$IMPORTANCE" ] && [ "$STEP_CHANGES" = '[][][][]' ]; then
+  error_exit "nothing to change: give --complete, --reopen, --title, --due, --note, --importance, a step change or --delete"
 fi
 BODY=$(jq -cn --arg list "$LIST" --arg complete "$COMPLETE" --arg title "$TITLE" --arg due "$DUE" --arg note "$NOTE" --arg imp "$IMPORTANCE" \
+  --argjson add "$ADD_STEPS" --argjson check "$CHECK_STEPS" --argjson uncheck "$UNCHECK_STEPS" --argjson remove "$REMOVE_STEPS" \
   '{}
       + (if $list != "" then {list: $list} else {} end)
       + (if $complete != "" then {complete: ($complete == "true")} else {} end)
       + (if $title != "" then {title: $title} else {} end)
       + (if $due == "none" then {due: null} elif $due != "" then {due: $due} else {} end)
       + (if $note != "" then {note: $note} else {} end)
-      + (if $imp != "" then {importance: $imp} else {} end)')
+      + (if $imp != "" then {importance: $imp} else {} end)
+      + (if ($add | length) > 0 then {addSteps: $add} else {} end)
+      + (if ($check | length) > 0 then {checkSteps: $check} else {} end)
+      + (if ($uncheck | length) > 0 then {uncheckSteps: $uncheck} else {} end)
+      + (if ($remove | length) > 0 then {removeSteps: $remove} else {} end)')
 RESPONSE=$(call PATCH "/microsoft-todo/tasks/$(uri "$TASK")" "$BODY") || { printf '%s\n' "$RESPONSE"; exit 1; }
 printf '%s' "$RESPONSE" | jq -c '{success: true, list: .data.list.name, task: .data.task}'

package/config/skills/agent/core/todo-update/execute.test.sh

@@ -75,6 +75,13 @@ check "json input" "$(last '[.path,.body]')" '["/api/microsoft-todo/tasks/T7",{"
 check "task required" "$(run_err --complete | jq -r .error)" "--task is required (ids come from todo-tasks)"
 check "nothing to change" "$(run_err --task T1 | jq -r .error | cut -c1-17)" "nothing to change"
 check "bad due" "$(run_err --task T1 --due 1/10 | jq -r .error)" "--due must look like 2026-10-01, or none to clear it"
+run --list Groceries --task T1 --add-steps "Butter, Ham" --check-steps Eggs --uncheck-step "Milk, oat" --remove-steps Bread >/dev/null
+check "steps: body" "$(last '[.method,.path,.body]')" '["PATCH","/api/microsoft-todo/tasks/T1",{"list":"Groceries","addSteps":["Butter","Ham"],"checkSteps":["Eggs"],"uncheckSteps":["Milk, oat"],"removeSteps":["Bread"]}]'
+run --task T1 --add-step Butter >/dev/null
+check "steps: a step change alone is a change" "$(last '.body')" '{"addSteps":["Butter"]}'
+run '{"task":"T1","checkSteps":["Eggs"],"removeSteps":"Bread,Ham"}' >/dev/null
+check "steps: json input" "$(last '.body')" '{"checkSteps":["Eggs"],"removeSteps":["Bread","Ham"]}'
+check "steps: blank is still nothing to change" "$(run_err --task T1 --add-steps ' , ' | jq -r .error | cut -c1-17)" "nothing to change"
 OUT=$(run --list no-grant --task T1 --complete || true)
 check "not connected" "$(printf '%s' "$OUT" | jq -r .reason)" "not_connected"
 

package/config/skills/marketplace-registry.ts

@@ -118,10 +118,10 @@ export const SKILL_FILE_EXCLUDES: ReadonlyArray<RegExp> = [/\.test\./, /^mock-/,
  * never installed.
  *
  * Deliberately FLAT: files in subdirectories (e.g. remotion-video/templates/)
- * are not listed. The shipped CLI writes each listed file without creating
- * parent directories, so a nested path would fail the whole install on every
- * CLI released so far. List them only after the CLI creates parent dirs AND
- * the older CLIs are no longer in use.
+ * are not listed. CLIs released before #800 write each listed file without
+ * creating parent directories, so a nested path fails the whole install on
+ * them. The installers create parent dirs since #800; list nested files only
+ * once the older CLIs are no longer in use.
  *
  * @param skillDir - Absolute skill directory
  * @returns File names relative to the skill directory

package/config/skills/orchestrator/complete-task/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: Complete Task
-description: Mark a task as complete in the task management system.
-version: 1.0.0
+description: Mark a WorkItem complete in the V3 task pool, with evidence.
+version: 1.1.0
 category: management
 skillType: claude-skill
 assignableRoles:
@@ -24,18 +24,25 @@ execution:
 
 # Complete Task
 
-Mark a task as complete in the task management system.
+Mark a WorkItem complete via `POST /api/task-pool/complete/:id`.
 
 ## Usage
 
 ```bash
-bash config/skills/orchestrator/complete-task/execute.sh '{"taskId":"task-123","result":"success"}'
+bash config/skills/orchestrator/complete-task/execute.sh '{"workItemId":"wi-123","summary":"Shipped the report","evidence":[{"type":"artifact","path":"/abs/path/report.md"},{"type":"command","command":"npm test","exitCode":0}]}'
 ```
 
 ## Parameters
 
-Pass the full JSON body as expected by `POST /api/task-management/complete`.
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `workItemId` (alias `taskId`) | Yes | The WorkItem to complete |
+| `summary` (alias `result`) | Yes | What was produced |
+| `evidence` | Yes* | Evidence array (#873): `{"type":"artifact","path":…}` (must exist, or an https URL), `{"type":"command","command":…,"exitCode":0,"outputTail":…}`, or `{"type":"blocked","step":…,"reason":…}` (records the item as blocked, not done). *Accepted without it this release with a `warning`; required from the next |
+| `output` | No | Structured output stored on the WorkItem before completion |
+| `agentId` / `sessionName` | No | Who completed it (defaults to `crewly-orc`) |
 
 ## Output
 
-JSON confirmation of task completion.
+The server's JSON response. A `warning` from the server (completion without
+evidence) is repeated on stderr.

package/config/skills/orchestrator/complete-task/execute.sh

@@ -6,7 +6,15 @@
 # on the WorkItem (replaces `<taskId>.output.json`) before completion.
 #
 # Input shape:
-#   { "workItemId": "abc-123", "summary": "...", "output"?: { ... } }
+#   { "workItemId": "abc-123", "summary": "...", "output"?: { ... },
+#     "evidence"?: [ {"type":"artifact","path":"..."} |
+#                    {"type":"command","command":"...","exitCode":0,"outputTail":"..."} |
+#                    {"type":"blocked","step":"...","reason":"..."} ] }
+#
+# `evidence` (#873) is sent as result.evidence. The server checks it: missing
+# artifacts and non-zero exit codes are refused, a `blocked` entry records the
+# item as blocked instead of done, and no evidence at all is accepted this
+# release with a `warning` (refused from the next).
 #
 # Backwards-compat: a `taskId` field is accepted as alias for `workItemId`.
 
@@ -26,6 +34,11 @@ OUTPUT=$(printf '%s' "$INPUT" | jq -c '.output // empty')
 # work — pass that session name instead).
 AGENT_ID=$(printf '%s' "$INPUT" | jq -r '.agentId // .sessionName // "crewly-orc"')
 
+EVIDENCE=$(printf '%s' "$INPUT" | jq -c '.evidence // empty')
+if [ -n "$EVIDENCE" ] && [ "$(printf '%s' "$EVIDENCE" | jq -r 'type')" != "array" ]; then
+  error_exit "evidence must be a JSON array, e.g. [{\"type\":\"artifact\",\"path\":\"/abs/file\"}]"
+fi
+
 require_param "workItemId" "$WORK_ITEM_ID"
 
 # Persist structured output on the WorkItem before completing, so that
@@ -47,6 +60,12 @@ fi
 COMPLETE_BODY=$(jq -n \
   --arg agentId "$AGENT_ID" \
   --arg summary "$SUMMARY" \
-  '{agentId: $agentId, result: {summary: $summary}}')
+  --argjson evidence "${EVIDENCE:-null}" \
+  '{agentId: $agentId, result: ({summary: $summary} + (if $evidence != null then {evidence: $evidence} else {} end))}')
 
-api_call POST "/task-pool/complete/${WORK_ITEM_ID}" "$COMPLETE_BODY"
+COMPLETE_RESPONSE=$(api_call POST "/task-pool/complete/${WORK_ITEM_ID}" "$COMPLETE_BODY")
+printf '%s\n' "$COMPLETE_RESPONSE"
+EVIDENCE_WARNING=$(printf '%s' "$COMPLETE_RESPONSE" | jq -r '.warning // empty' 2>/dev/null || true)
+if [ -n "$EVIDENCE_WARNING" ]; then
+  jq -n --arg w "$EVIDENCE_WARNING" '{warning: $w}' >&2
+fi

package/config/skills/orchestrator/delegate-task/execute.sh

@@ -255,13 +255,13 @@ if [ "$USE_STRUCTURED" = "true" ] && [ -n "$TITLE" ]; then
 
   [ -n "$CONTEXT" ] && TASK_MESSAGE="${TASK_MESSAGE}\n\nAdditional context: ${CONTEXT}"
   [ -n "$DEADLINE_HINT" ] && TASK_MESSAGE="${TASK_MESSAGE}\n\n**Deadline hint**: ${DEADLINE_HINT}"
-  TASK_MESSAGE="${TASK_MESSAGE}\n\n---\nWhen done, report back with report-status, passing the workItemId from your [CREWLY-DISPATCH] notice (or from get-my-tasks) so the right WorkItem is closed: bash ${CREWLY_ROOT}/config/skills/agent/core/report-status/execute.sh '{\"sessionName\":\"${TO}\",\"workItemId\":\"<your WorkItem id>\",\"status\":\"done\",\"summary\":\"<brief summary>\",\"projectPath\":\"${PROJECT_PATH}\"}'"
+  TASK_MESSAGE="${TASK_MESSAGE}\n\n---\nWhen done, report back with report-status, passing the workItemId from your [CREWLY-DISPATCH] notice (or from get-my-tasks) so the right WorkItem is closed: bash ${CREWLY_ROOT}/config/skills/agent/core/report-status/execute.sh '{\"sessionName\":\"${TO}\",\"workItemId\":\"<your WorkItem id>\",\"status\":\"done\",\"summary\":\"<brief summary>\",\"evidence\":[{\"type\":\"artifact\",\"path\":\"<file you produced>\"},{\"type\":\"command\",\"command\":\"<check you ran>\",\"exitCode\":0}],\"projectPath\":\"${PROJECT_PATH}\"}' — done needs evidence (files that exist, checks with exit code 0); if a step failed, send [{\"type\":\"blocked\",\"step\":\"<step>\",\"reason\":\"<why>\"}] instead, never done."
   TASK_MESSAGE="${TASK_MESSAGE}\n\nBefore reporting done, persist key findings using: bash ${CREWLY_ROOT}/config/skills/agent/core/remember/execute.sh '{\"agentId\":\"${TO}\",\"content\":\"<key findings>\",\"category\":\"pattern\",\"scope\":\"project\",\"projectPath\":\"${PROJECT_PATH}\"}'"
 else
   # Legacy free-text format (backwards compatible)
   TASK_MESSAGE="New task from orchestrator (priority: ${PRIORITY}):\n\n${TASK}"
   [ -n "$CONTEXT" ] && TASK_MESSAGE="${TASK_MESSAGE}\n\nContext: ${CONTEXT}"
-  TASK_MESSAGE="${TASK_MESSAGE}\n\nWhen done, report back with report-status, passing the workItemId from your [CREWLY-DISPATCH] notice (or from get-my-tasks) so the right WorkItem is closed: bash ${CREWLY_ROOT}/config/skills/agent/core/report-status/execute.sh '{\"sessionName\":\"${TO}\",\"workItemId\":\"<your WorkItem id>\",\"status\":\"done\",\"summary\":\"<brief summary>\",\"projectPath\":\"${PROJECT_PATH}\"}'"
+  TASK_MESSAGE="${TASK_MESSAGE}\n\nWhen done, report back with report-status, passing the workItemId from your [CREWLY-DISPATCH] notice (or from get-my-tasks) so the right WorkItem is closed: bash ${CREWLY_ROOT}/config/skills/agent/core/report-status/execute.sh '{\"sessionName\":\"${TO}\",\"workItemId\":\"<your WorkItem id>\",\"status\":\"done\",\"summary\":\"<brief summary>\",\"evidence\":[{\"type\":\"artifact\",\"path\":\"<file you produced>\"},{\"type\":\"command\",\"command\":\"<check you ran>\",\"exitCode\":0}],\"projectPath\":\"${PROJECT_PATH}\"}' — done needs evidence (files that exist, checks with exit code 0); if a step failed, send [{\"type\":\"blocked\",\"step\":\"<step>\",\"reason\":\"<why>\"}] instead, never done."
   TASK_MESSAGE="${TASK_MESSAGE}\n\nBefore reporting done, persist key findings using: bash ${CREWLY_ROOT}/config/skills/agent/core/remember/execute.sh '{\"agentId\":\"${TO}\",\"content\":\"<key findings>\",\"category\":\"pattern\",\"scope\":\"project\",\"projectPath\":\"${PROJECT_PATH}\"}'"
 fi