From ef1179839d662f073e4e0195e0f1c63beae94cb2 Mon Sep 17 00:00:00 2001
From: shokollm <270575765+shokollm@users.noreply.github.com>
Date: Mon, 30 Mar 2026 23:00:34 +0000
Subject: [PATCH] docs(phase3): update status and add testing plan

---
 docs/kugetsu-architecture.md |  4 ++--
 docs/kugetsu-chat.md         |  2 +-
 docs/phase3a-setup.md        | 41 ++++++++++++++++++++++++++++++++++++
 3 files changed, 44 insertions(+), 3 deletions(-)

diff --git a/docs/kugetsu-architecture.md b/docs/kugetsu-architecture.md
index ddcc21e..027d5d5 100644
--- a/docs/kugetsu-architecture.md
+++ b/docs/kugetsu-architecture.md
@@ -326,7 +326,7 @@ When a Coding Agent starts, it:
 | Phase 1 | ✅ Complete | SSH + Tailscale remote access |
 | Phase 1b | ✅ Complete | Tailscale VPN setup |
 | Phase 2 | 📋 Planned | API Interface |
-| Phase 3 | 📋 Planned | Chat Integration (Telegram) |
+| Phase 3 | 🔄 In Progress | Chat Integration (Telegram) |
 | Phase 4 | 📋 Planned | Web Dashboard |
 
 ### 6.2 Current Implementation
@@ -344,7 +344,7 @@ When a Coding Agent starts, it:
 | Parallel capacity | How many Coding Agents can run simultaneously on one machine? | Pending |
 | Session management | Does kugetsu properly manage opencode sessions? | ✅ Working |
 | Remote access | Does SSH + Tailscale enable remote work? | ✅ Working |
-| Chat interface | Can Hermes bridge Telegram for mobile UX? | Planned (Phase 3) |
+| Chat interface | Can Hermes bridge Telegram for mobile UX? | Phase 3a Testing |
 
 ### 6.4 Success Criteria
 
diff --git a/docs/kugetsu-chat.md b/docs/kugetsu-chat.md
index c6ca50e..40092f5 100644
--- a/docs/kugetsu-chat.md
+++ b/docs/kugetsu-chat.md
@@ -1,6 +1,6 @@
 # Kugetsu Chat Architecture (Phase 3)
 
-**Status:** Planned (Not Yet Implemented)  
+**Status:** Phase 3a Implemented (Testing in Progress)  
 **Related Issue:** #19
 
 ## Overview
diff --git a/docs/phase3a-setup.md b/docs/phase3a-setup.md
index a03618f..61013ad 100644
--- a/docs/phase3a-setup.md
+++ b/docs/phase3a-setup.md
@@ -151,6 +151,47 @@ kugetsu init
 └── kugetsu-helper            # CLI helper script
 ```
 
+## Testing Plan (Manual)
+
+### Test 1: Casual Conversation
+**Objective:** Verify Hermes handles small talk directly without delegation
+
+| Step | Action | Expected Result |
+|------|--------|-----------------|
+| 1 | Send `hi` to @your_bot_username | Bot responds with greeting |
+| 2 | Send `how are you?` | Bot responds naturally |
+
+### Test 2: Task Delegation
+**Objective:** Verify Hermes delegates task to PM Agent via `kugetsu-helper`
+
+| Step | Action | Expected Result |
+|------|--------|-----------------|
+| 1 | Send `status?` to bot | Bot routes to PM, PM responds |
+| 2 | Send `fix issue #5` to bot | PM agent receives task via opencode |
+| 3 | Send `Work on issue #35` to bot | PM agent creates branch, worktree, PR |
+
+### Test 3: Error Handling
+**Objective:** Verify graceful error handling
+
+| Step | Action | Expected Result |
+|------|--------|-----------------|
+| 1 | Send `status?` with PM agent stopped | Bot says "PM agent not available" |
+| 2 | Send `status?` before `kugetsu init` | Bot says "kugetsu not initialized" |
+
+### Debugging
+
+If delegation fails:
+```bash
+# Check Hermes logs
+hermes gateway logs
+
+# Check PM agent is running
+kugetsu-helper check-status
+
+# Check kugetsu-helper directly
+~/.local/bin/kugetsu-helper delegate-to-pm "test"
+```
+
 ## Security Notes
 
 - Never commit `~/.kugetsu/` or SOUL files to version control