docs: add Phase 6 — Web Chat interface for AI Employees

.planning/ROADMAP.md

@@ -114,7 +114,7 @@ Plans:
 ## Progress
 
 **Execution Order:**
-Phases execute in numeric order: 1 -> 2 -> 3 -> 4 -> 5
+Phases execute in numeric order: 1 -> 2 -> 3 -> 4 -> 5 -> 6
 
 | Phase | Plans Complete | Status | Completed |
 |-------|----------------|--------|-----------|
@@ -123,6 +123,7 @@ Phases execute in numeric order: 1 -> 2 -> 3 -> 4 -> 5
 | 3. Operator Experience | 5/5 | Complete    | 2026-03-24 |
 | 4. RBAC | 3/3 | Complete    | 2026-03-24 |
 | 5. Employee Design | 4/4 | Complete    | 2026-03-25 |
+| 6. Web Chat | 0/0 | Not started | - |
 
 ---
 
@@ -130,6 +131,21 @@ Phases execute in numeric order: 1 -> 2 -> 3 -> 4 -> 5
 
 **LLM-03 conflict resolved:** BYO API keys confirmed in v1 scope per user decision during Phase 3 context gathering. Implemented via Fernet encryption in Phase 3.
 
+### Phase 6: Web Chat
+**Goal**: Users can chat with AI Employees directly in the portal through a real-time web chat interface — no external messaging platform required
+**Depends on**: Phase 5
+**Requirements**: CHAT-01, CHAT-02, CHAT-03, CHAT-04, CHAT-05
+**Success Criteria** (what must be TRUE):
+  1. A user can open a chat window with any AI Employee and have a real-time conversation within the portal
+  2. The chat interface supports the full agent pipeline — memory, tools, escalation, and media (same capabilities as Slack/WhatsApp)
+  3. Conversation history persists and is visible when the user returns to the chat
+  4. The chat respects RBAC — users can only chat with agents belonging to tenants they have access to
+  5. The chat interface feels responsive — typing indicators, message streaming or fast response display
+**Plans**: 0 plans
+
+Plans:
+- [ ] TBD (run /gsd:plan-phase 6 to break down)
+
 ---
 *Roadmap created: 2026-03-23*
 *Coverage: 25/25 v1 requirements + 6 RBAC requirements + 5 Employee Design requirements mapped*