fix(02-agent-features): revise plans based on checker feedback

.planning/ROADMAP.md

@@ -47,13 +47,14 @@ Plans:
   3. The agent can invoke a registered tool (e.g., knowledge base search) and incorporate the result into its response
   4. When a configured escalation rule triggers (e.g., failed resolution attempts), the conversation and full context are handed off to a human with no information lost
   5. Every LLM call, tool invocation, and handoff event is recorded in an immutable audit trail queryable by tenant
-**Plans**: 4 plans
+**Plans**: 5 plans
 
 Plans:
 - [ ] 02-01: Conversational memory layer (Redis sliding window + pgvector long-term storage with HNSW index)
-- [ ] 02-02: Tool framework (registry, schema-validated execution, authorization enforcement, audit logging)
-- [ ] 02-03: WhatsApp adapter (Business Cloud API, per-tenant phone numbers, opt-in enforcement, Meta policy compliance)
+- [ ] 02-02: Tool framework (registry, schema-validated execution, audit logging) — split into audit+tools+wiring
+- [ ] 02-03: WhatsApp adapter (Business Cloud API, per-tenant phone numbers, media download, Meta policy compliance)
 - [ ] 02-04: Human escalation/handoff with full context transfer and audit trail
+- [ ] 02-05: Cross-channel media support and multimodal LLM interpretation (Slack file_share, image_url content blocks, channel-aware outbound routing)
 
 ### Phase 3: Operator Experience
 **Goal**: An operator can sign up, onboard their tenant through a web UI, connect their messaging channels, configure their AI employee, and manage their subscription — without touching config files or the command line
@@ -78,7 +79,7 @@ Phases execute in numeric order: 1 → 2 → 3
 | Phase | Plans Complete | Status | Completed |
 |-------|----------------|--------|-----------|
 | 1. Foundation | 4/4 | Complete    | 2026-03-23 |
-| 2. Agent Features | 0/4 | Not started | - |
+| 2. Agent Features | 0/5 | Not started | - |
 | 3. Operator Experience | 0/2 | Not started | - |
 
 ---