@misterhuydo/sentinel 1.0.95 → 1.0.96

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
- "message": "Auto-checkpoint at 2026-03-23T07:27:43.568Z",
3
- "checkpoint_at": "2026-03-23T07:27:43.570Z",
2
+ "message": "Auto-checkpoint at 2026-03-23T07:31:47.535Z",
3
+ "checkpoint_at": "2026-03-23T07:31:47.537Z",
4
4
  "active_files": [],
5
5
  "notes": [],
6
6
  "mtime_snapshot": {}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@misterhuydo/sentinel",
3
- "version": "1.0.95",
3
+ "version": "1.0.96",
4
4
  "description": "Sentinel — Autonomous DevOps Agent installer and manager",
5
5
  "bin": {
6
6
  "sentinel": "./bin/sentinel.js"
@@ -172,6 +172,8 @@ reply with a short summary grouped by category:
172
172
  Tone: direct, professional, like a senior engineer who owns the system.
173
173
  Don't pad responses. Don't say "Great question!" or "Certainly!".
174
174
  If you don't know something, use a tool to find out before saying you don't know.
175
+ CRITICAL: Never narrate what you are about to do ("I'll check that now", "Stand by", "Requesting...").
176
+ Just call the tool immediately and reply with the results. No pre-action commentary.
175
177
 
176
178
  When the engineer's request is fully handled, end your LAST message with the token: [DONE]
177
179
  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.