@misterhuydo/sentinel 1.2.0 → 1.2.1

package/.cairn/session.json

@@ -1,6 +1,6 @@
 {
-  "message": "Auto-checkpoint at 2026-03-23T09:22:14.601Z",
-  "checkpoint_at": "2026-03-23T09:22:14.603Z",
+  "message": "Auto-checkpoint at 2026-03-23T09:27:13.974Z",
+  "checkpoint_at": "2026-03-23T09:27:13.976Z",
   "active_files": [],
   "notes": [],
   "mtime_snapshot": {}

package/package.json

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

package/python/sentinel/sentinel_boss.py

@@ -201,12 +201,12 @@ Issue identification — before calling create_issue:
    - Attachments: summarise any files/screenshots the user shared.
    - Support URL: note any ticket/doc/link the user mentioned.
    - Identity: always captured automatically from the Slack session.
-3. ALWAYS populate the `findings` field with evidence from this session:
+3. Populate `findings` with curated evidence — only when relevant and concise:
    - If you ran search_logs, tail_log, ask_codebase, or get_status before creating the issue,
-     include the relevant results (log excerpts, error counts, timestamps, stack traces, etc.).
-   - The fix engine reads only the issue file — it has no access to the conversation.
-     Everything it needs to understand and fix the problem must be in the file.
-   - A `description` with no evidence forces the fix engine to guess. Always attach what you found.
+     summarise only the findings directly related to this specific issue.
+   - Do NOT paste raw tool output. Summarise: which services, how often, key pattern, 1-3 example lines.
+   - If the search returned nothing relevant, or the issue is purely user-described with no log evidence, leave `findings` empty.
+   - The fix engine reads only the issue file. Give it signal, not noise — 500 words max.
 4. Before calling the tool, confirm with the user in natural language:
    e.g. "I'll create an issue for project *1881* — here's what I have: [summary]. Look right?"
    Wait for their confirmation before proceeding.
@@ -276,11 +276,11 @@ _TOOLS = [
                 "findings": {
                     "type": "string",
                     "description": (
-                        "Evidence gathered during this session: log excerpts, search results, "
-                        "stack traces, error counts, timestamps — anything from tool calls that "
-                        "is relevant to the issue. Include this whenever you ran search_logs, "
-                        "tail_log, ask_codebase, or get_status before creating the issue. "
-                        "The fix engine reads the issue file and needs this context to act."
+                        "A concise, curated summary of evidence directly relevant to this issue — "
+                        "NOT raw tool output. Include only what the fix engine needs: "
+                        "key error patterns, affected services, approximate frequency/timestamps, "
+                        "and 1-3 representative log lines. Omit unrelated results. "
+                        "Keep under 500 words. Leave empty if no tool results are relevant."
                     ),
                 },
             },