sticky-note-cli 2.6.3 → 2.6.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sticky-note-cli",
-  "version": "2.6.3",
+  "version": "2.6.5",
   "description": "Human-to-human handoff for AI coding assistants. Git-backed shared memory for Claude Code and Copilot CLI.",
   "license": "MIT",
   "bin": {

package/templates/CLAUDE.md

@@ -186,6 +186,27 @@ after. A raw `git checkout` or `git switch` will fail if sticky-note
 files have uncommitted changes. The alias `git sw <branch>` also works
 if set up by `npx sticky-note init`.
 
+### ⚠️ Overlap warnings (CRITICAL — always surface these)
+
+Sticky-note hooks detect when your files overlap with other teammates'
+open or stuck threads. When you see `[STICKY-NOTE] ⚠️ OVERLAP DETECTED`
+in your injected context, you **MUST** start your response with this
+exact banner format before doing ANYTHING else:
+
+```
+⚠️ Overlap detected: [user] is working on [files] — [narrative summary]
+   Status: [STUCK/OPEN] | Resume: npx sticky-note resume [id]
+```
+
+Rules:
+- This banner MUST be the **very first thing** in your response
+- Do NOT bury it at the end or in a footnote
+- Do NOT rephrase it as "Also noted..." or "By the way..."
+- Then continue with the user's actual request normally
+
+This pattern exists to prevent two teammates from wasting hours on the
+same problem. Treat it like a system alert, not optional context.
+
 ### `[STICKY-NOTE]` tags
 
 All sticky-note hooks prefix their output with `[STICKY-NOTE]`. When you

package/templates/copilot-instructions.md

@@ -164,6 +164,34 @@ after. A raw `git checkout` or `git switch` will fail if sticky-note
 files have uncommitted changes. The alias `git sw <branch>` also works
 if set up by `npx sticky-note init`.
 
+### ⚠️ Overlap warnings (CRITICAL — always surface these)
+
+Sticky-note hooks detect when your files overlap with other teammates'
+open or stuck threads. When you see `[STICKY-NOTE] ⚠️ OVERLAP DETECTED`
+in your injected context, you **MUST** start your response with this
+exact banner format before doing ANYTHING else:
+
+```
+⚠️ Overlap detected: [user] is working on [files] — [narrative summary]
+   Status: [STUCK/OPEN] | Resume: npx sticky-note resume [id]
+```
+
+Example:
+```
+⚠️ Overlap detected: alice is working on session-start.js, cli.js — fixing auth token refresh
+   Status: STUCK (tried retry logic, tokens expire mid-request) | Resume: npx sticky-note resume demo-ali
+```
+
+Rules:
+- This banner MUST be the **very first thing** in your response
+- Show it BEFORE your thinking indicators (◐, ●, etc.)
+- Do NOT bury it at the end or in a footnote
+- Do NOT rephrase it as "Also noted..." or "By the way..."
+- Then continue with the user's actual request normally
+
+This pattern exists to prevent two teammates from wasting hours on the
+same problem. Treat it like a system alert, not optional context.
+
 ### `[STICKY-NOTE]` tags
 
 All sticky-note hooks prefix their output with `[STICKY-NOTE]`. When you

package/templates/hooks/inject-context.js

@@ -150,7 +150,8 @@ function detectAndFormatOverlaps(threads, currentUser) {
   });
 
   const lines = [
-    "## [STICKY-NOTE] ⚠️ OVERLAP DETECTED\n",
+    "## [STICKY-NOTE] ⚠️ OVERLAP DETECTED — TELL THE USER IMMEDIATELY\n",
+    "**IMPORTANT: You MUST surface this warning to the user before doing anything else.**\n",
     "Someone else is working on files you're touching:\n",
   ];
   for (const { thread, overlap } of warnings) {

package/templates/hooks/session-start.js

@@ -354,7 +354,8 @@ function formatOverlapWarnings(threads, currentUser, memory) {
   if (warnings.length === 0 && claims.length === 0) return "";
 
   const lines = [
-    "## [STICKY-NOTE] ⚠️ OVERLAP DETECTED\n",
+    "## [STICKY-NOTE] ⚠️ OVERLAP DETECTED — TELL THE USER IMMEDIATELY\n",
+    "**IMPORTANT: You MUST surface this warning to the user before doing anything else.**\n",
     "Someone else is working on files you're touching:\n",
   ];