@misterhuydo/sentinel 1.1.9 → 1.2.0

package/.cairn/.hint-lock

@@ -1 +1 @@
-2026-03-23T08:53:23.129Z
+2026-03-23T09:25:27.661Z

package/.cairn/session.json

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

package/package.json

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

package/python/sentinel/sentinel_boss.py

@@ -201,12 +201,18 @@ 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. Before calling the tool, confirm with the user in natural language:
+3. ALWAYS populate the `findings` field with evidence from this session:
+   - 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.
+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.
    EXCEPTION: if the user's message already contains a clear project + unambiguous description,
    skip the confirmation and create immediately — don't ask when nothing is unclear.
-4. After creating, tell them the issue was queued and Sentinel will pick it up on the next poll.
+5. After creating, tell them the issue was queued and Sentinel will pick it up on the next poll.
 
 When the engineer's request is fully handled, end your LAST message with the token: [DONE]
 IMPORTANT: Always write your actual reply text FIRST, then append [DONE] at the end. Example: "Hello! I'm Sentinel. [DONE]". Never output [DONE] as your only content.
@@ -267,6 +273,16 @@ _TOOLS = [
                     "type": "string",
                     "description": "Summary of any files/screenshots the user attached",
                 },
+                "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."
+                    ),
+                },
             },
             "required": ["description"],
         },
@@ -949,6 +965,7 @@ async def _run_tool(name: str, inputs: dict, cfg_loader, store, slack_client=Non
 
         support_url          = inputs.get("support_url", "").strip()
         attachments_summary  = inputs.get("attachments_summary", "").strip()
+        findings             = inputs.get("findings", "").strip()
 
         issues_dir = project_dir / "issues"
         issues_dir.mkdir(exist_ok=True)
@@ -966,6 +983,8 @@ async def _run_tool(name: str, inputs: dict, cfg_loader, store, slack_client=Non
         lines.append(f"SUBMITTED_AT: {datetime.now(timezone.utc).isoformat()}")
         lines.append("")
         lines.append(description)
+        if findings:
+            lines.append(f"\nEVIDENCE (gathered by Sentinel Boss):\n{findings}")
         if attachments_summary:
             lines.append(f"\nATTACHMENTS:\n{attachments_summary}")
         content = "\n".join(lines)