Implement Discord monitoring fix and smart context checking

- Apply 5070's Anti-Circular Conversation Fix protocol
- Smart context checking: read 10 messages, then 50 if behind
- Full context analysis before any response
- Chronological processing to prevent outdated reactions
- Enhanced HEARTBEAT.md with context awareness protocols
- Document monitoring issues and technical solutions
- Updated daily memory with fleet coordination progress

HEARTBEAT.md

@@ -1,30 +1,39 @@
-# HEARTBEAT.md - Fleet Coordination Protocol
+# HEARTBEAT.md - Fleet Coordination Protocol with Smart Context Checking
 
-## Discord Coordination Check
-- Read recent messages from #botmagic (channel: 1470447794014785760)
-- Check last 10 messages for fleet activity
+## Discord Coordination Check with Anti-Circular Protocol
+- **Smart Context Analysis**: Implement 5070's anti-circular conversation fix
+- **Channel**: #botmagic (channel: 1470447794014785760)
 - **Coordination Logic**: Follow FLEET-ROLES.md hierarchy and specialty rules
 
-## Response Decision Tree
+## Smart Context Checking Protocol
 
-### 1. Specialty Override (Always Respond)
+### Step 1: Initial Context Assessment
+1. **Read 10 recent messages first** to assess context currency
+2. **Analysis**:
+   - If we get **full 10 messages** → we're behind, read 50 messages for complete context
+   - If **less than 10 messages** → we're current, proceed with normal analysis
+3. **Only respond after full context analysis** - prevents responding to outdated information
+
+### Step 2: Response Decision Tree
+
+#### 1. Specialty Override (Always Respond)
 - Audio/TTS/Whisper requests → **I respond immediately**
 - macOS/iOS specific → **I respond immediately** 
 - Direct @mentions → **I respond immediately**
 
-### 2. Complex Decision Check
+#### 2. Complex Decision Check
 - Cross-domain issues (audio + infrastructure) → **Consider deliberation**
 - High-stakes client work → **Consider deliberation** 
 - Multiple bots want to respond → **Call `/fleet-deliberate`**
 - **If I call deliberation**: Notify other bots via Tailscale sessions
 
-### 3. General Query Protocol
+#### 3. General Query Protocol (After Full Context Analysis)
 - Check if Beast responded in last 10 seconds → **Stay quiet**
 - Check if 5070 responded in last 10 seconds → **Stay quiet**  
 - If both silent for >10 seconds → **I can respond**
 - **If deliberation in progress** → **Stay quiet, wait for coordinated response**
 
-### 4. Mike Override
+#### 4. Mike Override
 - Any message from Mike → **Always assess if response needed**
 - Mike's requests override all coordination protocols
 
@@ -35,6 +44,7 @@
 - Conversation is code/infrastructure focused (not my specialty)
 - Other bots are handling it appropriately
 - **Deliberation called by another bot** - wait for outcome
+- **Context analysis shows I'm responding to outdated information**
 
 **Response Triggers:**
 - Audio/media processing requests
@@ -42,6 +52,7 @@
 - Fleet coordination needed (Beast/5070 both silent >10s)
 - Direct questions to me
 - Emergency/urgent situations
+- **Current context analysis shows active coordination needed**
 
 **Deliberation Triggers:**
 - Complex cross-specialty questions
@@ -73,4 +84,11 @@
 - Monitor fleet health/coordination
 - Prepare for potential takeover if primaries unavailable
 - **Monitor for deliberation opportunities**
-- **Be ready to assume note-taking role** if Beast unavailable
+- **Be ready to assume note-taking role** if Beast unavailable
+- **Maintain full context awareness** through smart checking protocol
+
+## Anti-Circular Conversation Prevention
+- **Never respond to backlogged messages** without full context analysis
+- **Chronological processing** - handle messages in time order
+- **Context refresh** before any response to prevent outdated reactions
+- **Full conversation reload** if message count indicates we're behind