docs: Add RCA for Timmy Telegram unresponsiveness

- Investigation findings
- SSH connection failed to Mac (100.124.176.28)
- Ezra also down (disconnected)
- Root cause hypotheses and required actions

Refs: #186

rcas/RCA-196-timmy-telegram-down.md

@@ -0,0 +1,122 @@
+# RCA: Timmy Unresponsive on Telegram
+
+**Status:** INVESTIGATING  
+**Severity:** P0  
+**Reported:** 2026-03-31  
+**Investigator:** Allegro  
+
+---
+
+## Summary
+
+Timmy is unresponsive through Telegram. Investigation reveals:
+1. **Timmy's Mac is unreachable** via SSH (100.124.176.28 - Connection timed out)
+2. **Timmy was never successfully woken** with Kimi fallback (pending from #186)
+3. **Ezra (same network) is also down** - Gateway disconnected
+
+---
+
+## Timeline
+
+| Time | Event |
+|------|-------|
+| 2026-03-31 ~06:00 | Ezra successfully woken with Kimi primary |
+| 2026-03-31 ~18:00 | Timmy wake-up attempted but failed (Mac unreachable) |
+| 2026-03-31 ~18:47 | `/tmp/timmy-wake-up.md` created for manual deployment |
+| 2026-03-31 ~21:00 | **REPORTED:** Timmy unresponsive on Telegram |
+| 2026-03-31 ~21:30 | Investigation started - SSH to Mac failed |
+
+---
+
+## Investigation Findings
+
+### 1. SSH Access Failed
+```
+ssh timmy@100.124.176.28
+Result: Connection timed out
+```
+**Impact:** Cannot remotely diagnose or fix Timmy
+
+### 2. Timmy's Configuration Status
+| Component | Status | Notes |
+|-----------|--------|-------|
+| HERMES_HOME | Unknown | Expected: `~/.timmy` on Mac |
+| Config (Kimi) | Unknown | Should have been updated per #186 |
+| API Key | Unknown | KIMI_API_KEY deployment status unclear |
+| Gateway Process | Unknown | Cannot verify without SSH |
+| Telegram Token | Unknown | May be expired/invalid |
+
+### 3. Related System Status
+| Wizard | Status | Last Known |
+|--------|--------|------------|
+| Allegro | ✅ Operational | Current session active |
+| Ezra | ❌ DOWN | Gateway disconnected ~06:09 |
+| Timmy | ❌ UNRESPONSIVE | Never confirmed operational |
+| Allegro-Primus | ⚠️ IDLE | Running but no output |
+
+---
+
+## Root Cause Analysis
+
+### Primary Hypothesis: Network/Mac Issue
+**Confidence:** High (70%)
+
+Timmy's Mac (100.124.176.28) is not accepting SSH connections. Possible causes:
+1. **Mac is offline/asleep** - Power management, network disconnect
+2. **IP address changed** - DHCP reassignment
+3. **Firewall blocking** - SSH port closed
+4. **VPN/network routing** - Not on expected network
+
+### Secondary Hypothesis: Never Deployed
+**Confidence:** Medium (25%)
+
+Timmy may never have been successfully migrated to Kimi:
+1. Wake-up documentation created but not executed
+2. No confirmation of Mac-side deployment
+3. Original Anthropic quota likely exhausted
+
+### Tertiary Hypothesis: Token/Auth Issue
+**Confidence:** Low (5%)
+
+If Timmy IS running but not responding:
+1. Telegram bot token expired
+2. Kimi API key invalid
+3. Hermes config corruption
+
+---
+
+## Required Actions
+
+### Immediate (User Required)
+- [ ] **Verify Mac status** - Is it powered on and connected?
+- [ ] **Check current IP** - Has 100.124.176.28 changed?
+- [ ] **Execute wake-up script** - Run commands from `/tmp/timmy-wake-up.md`
+
+### If Mac is Accessible
+- [ ] SSH into Mac
+- [ ] Check `~/.timmy/` directory exists
+- [ ] Verify `config.yaml` has Kimi primary
+- [ ] Confirm `KIMI_API_KEY` in `.env`
+- [ ] Check gateway process: `ps aux | grep gateway`
+- [ ] Review logs: `tail ~/.timmy/logs/gateway.log`
+
+### Alternative: Deploy to VPS
+If Mac continues to be unreachable:
+- [ ] Create Timmy profile on VPS (like Ezra)
+- [ ] Deploy to `/root/wizards/timmy/home`
+- [ ] Use same Kimi config as Ezra
+- [ ] Assign new Telegram bot token
+
+---
+
+## References
+
+- Issue #186: [P0] Add kimi-coding fallback for Timmy and Ezra
+- Wake-up guide: `/tmp/timmy-wake-up.md`
+- Ezra working config: `/root/wizards/ezra/home/config.yaml`
+
+---
+
+*RCA compiled by: Allegro*  
+*Date: 2026-03-31*  
+*Next Update: Pending user input on Mac status*