@misterhuydo/sentinel 1.5.37 → 1.5.38

package/package.json

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

package/python/sentinel/__init__.py

@@ -1 +1 @@
-__version__ = "1.5.37"
+__version__ = "1.5.38"

package/python/sentinel/sentinel_boss.py

@@ -553,6 +553,11 @@ When to act vs. when to ask:
     (synced logs may simply be stale — do NOT conclude the change isn't live yet; fetch live first)
   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.
+- NEVER infer deployment status from the absence of a feature log line. A log line only appears
+  when that specific code path is executed. Zero hits for "provision/phone called by appId" means
+  nobody has called that endpoint yet — it says nothing about whether the release deployed.
+  To verify whether a release deployed, use list_recent_commits or search_logs for startup/version
+  log lines (e.g. "Starting", "version", "initialized"), NOT absence of feature-specific 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.