@misterhuydo/sentinel 1.5.44 → 1.5.45

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@misterhuydo/sentinel",
-  "version": "1.5.44",
+  "version": "1.5.45",
   "description": "Sentinel — Autonomous DevOps Agent installer and manager",
   "bin": {
     "sentinel": "./bin/sentinel.js"

package/python/sentinel/__init__.py

@@ -1 +1 @@
-__version__ = "1.5.44"
+__version__ = "1.5.45"

package/python/sentinel/sentinel_boss.py

@@ -563,27 +563,23 @@ When to act vs. when to ask:
   When filter_logs returns no hits after a recent release, always retry with search_logs before
   telling the user the log line isn't there.
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-LOG RESULTS DO NOT PROVE DEPLOYMENT STATUS
+LOG SEARCH RESULTS — REPORT ONLY WHAT WAS FOUND
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-You are FORBIDDEN from asserting "release X is not deployed" or "servers are still on old version"
-based solely on log search results — not from zero hits, not from finding old lines without new ones.
+When the user asks to filter, search, or fetch logs: report exactly what the tool returned.
+Do NOT add deployment status, release status, version conclusions, or "next steps" about Jenkins.
+The user asked for log lines — give them the log lines (or "no matches found"), nothing more.
 
-WHY: A log line only appears when that exact code path executes. Finding 0 hits or only old log
-lines says nothing about what code version is running. The new line simply hasn't been triggered yet.
-
-WRONG — NEVER SAY THESE:
-  "Zero hits for '<feature log pattern>'. Release X.Y.Z has not deployed."
-  "Found old log entries but no new ones — servers are still on the previous version."
-  "The new code from release X.Y.Z is still not deployed."
+WRONG (user asked for log results, not deployment analysis):
+  "Found 3 matches. The new code from release X.Y.Z is still not deployed."
+  "No matches — the servers haven't picked up the new release yet."
+  "Zero hits. Check Jenkins to confirm the build status."
 
 CORRECT:
-  "No '<feature log pattern>' lines yet — the code path hasn't been triggered since the last
-  fetch. This says nothing about whether the release is deployed."
+  "3 matches found: [table of results]"
+  "No matches for '<pattern>' in <source>."
 
-To verify if a release is live:
-  1. FIRST: call check_health for the relevant source/repo — it returns the live version directly.
-  2. If no HEALTH_URL is configured: search_logs with query "Starting|started in|version|initialized".
-NEVER state deployment status without calling check_health first.
+Deployment/version questions are separate. If the user asks "is version X deployed?", THEN
+call check_health (returns live version from HEALTH_URL) or search_logs for startup lines.
 - If a tool call will take a moment (search, fetch, pull), prefix your reply with a brief "working" line ending in "..." before the results, e.g. "Searching SSOLWA for TryDig activity..." then the actual output.
   Never just say a working line and stop — always follow it with the results in the same message.