crewly 1.20.439 → 1.20.440

package/config/skills/agent/core/search-chat/SKILL.md

@@ -67,3 +67,7 @@ Output: `{ "data": { "count": N, "hits": [ { "id", "time", "channelId", "channel
 - Try a shorter or different keyword when nothing comes back; CJK text is
   matched as written, without word splitting.
 - To read around a hit, search again with `--channel` and a one-day range.
+
+## What it does not search
+
+Replies a team member posts with `reply --work-item`, `--new-thread` or `--ticket` can go straight to Slack and are not stored in this chat history. The result carries a `note` saying so. A missing hit does **not** mean such a post failed: the `reply` call itself returns `slackChannelId` and `messageTs` as proof it landed. Ask the member for those, or read the Slack thread, before posting the answer again.

package/config/skills/agent/core/search-chat/execute.sh

@@ -65,4 +65,16 @@ if [ "${CREWLY_SKILL_DRY_RUN:-}" = "1" ]; then
   exit 0
 fi
 
-api_call GET "$ENDPOINT"
+# Posts a team member makes with `reply --work-item` / `--new-thread` go straight to
+# Slack and are not stored in the chat history this searches (CREW-877). Say so in
+# the output: an empty or partial result is not proof that such a post failed. The
+# reply itself returned the proof (slackChannelId + messageTs) to the member.
+NOTE="Not searched: replies a team member posts with 'reply --work-item', '--new-thread' or '--ticket' can go straight to Slack and are then not in this history. A missing hit does not mean such a post failed; ask the member for its messageTs (the reply returns it) or read the Slack thread."
+if ! RESP=$(api_call GET "$ENDPOINT"); then
+  exit 1
+fi
+if printf '%s' "$RESP" | jq -e 'type == "object"' >/dev/null 2>&1; then
+  printf '%s' "$RESP" | jq -c --arg note "$NOTE" '. + {note: $note}'
+else
+  printf '%s\n' "$RESP"
+fi

package/config/skills/agent/core/search-chat/execute.test.sh

@@ -20,5 +20,25 @@ assert_contains "missing --query is an error" "--query is required" "$(bash "$SC
 assert_contains "bad --limit is an error" "--limit must be a number" "$(bash "$SCRIPT_DIR/execute.sh" --query x --limit abc 2>&1 || true)"
 assert_contains "--help prints usage" "Usage:" "$(bash "$SCRIPT_DIR/execute.sh" --help)"
 
+# The result carries a note that work-item posts are not searched (CREW-877).
+unset CREWLY_SKILL_DRY_RUN
+PORT=18877
+python3 -u - <<'PY' >/dev/null 2>&1 &
+from http.server import BaseHTTPRequestHandler, HTTPServer
+class H(BaseHTTPRequestHandler):
+    def do_GET(self):
+        self.send_response(200); self.send_header('Content-Type', 'application/json'); self.end_headers()
+        self.wfile.write(b'{"success":true,"data":{"count":0,"hits":[]}}')
+    def log_message(self, *a, **k): pass
+HTTPServer(('127.0.0.1', 18877), H).serve_forever()
+PY
+STUB_PID=$!
+trap 'kill "$STUB_PID" >/dev/null 2>&1' EXIT
+for i in $(seq 1 30); do curl -s -o /dev/null -m 0.2 "http://127.0.0.1:${PORT}/" 2>/dev/null && break; sleep 0.1; done
+OUT=$(CREWLY_API_URL="http://127.0.0.1:${PORT}" bash "$SCRIPT_DIR/execute.sh" --query anything 2>/dev/null)
+assert_eq "result keeps its data" "0" "$(printf '%s' "$OUT" | jq -r '.data.count')"
+assert_contains "result says work-item posts are not searched" "reply --work-item" "$(printf '%s' "$OUT" | jq -r '.note')"
+assert_eq "output is one line" "1" "$(printf '%s\n' "$OUT" | wc -l | tr -d ' ')"
+
 echo "=== Results: $PASS passed, $FAIL failed ==="
 [ "$FAIL" -eq 0 ]

package/dist/backend/build-info.json

@@ -1,4 +1,4 @@
 {
-  "commit": "482ac2aedc409da8f790e36ed583ca81123e4ac2",
-  "builtAt": "2026-10-26T11:39:05.432Z"
+  "commit": "2972ea36bb1a5c6d904ef44da19cca160a3da99f",
+  "builtAt": "2026-10-26T12:03:10.159Z"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "crewly",
-  "version": "1.20.439",
+  "version": "1.20.440",
   "type": "module",
   "description": "Multi-agent orchestration platform for AI coding teams — coordinates Claude Code, Gemini CLI, and Codex agents with a real-time web dashboard",
   "workspaces": [