karen plan P2: report, FAQ loop, chat summary, SLA escalation

[deepmasq]

Summary

• Use configured bot name in Karen captured thread scenario #21 Report improvements: Strip deal/pipeline sections from report schema (moved to Sales Bot). Collect task stats from kanban instead of hardcoding zeros. Add "nothing happened" variant when zero activity.
• Refactor Slack tests to remove global client #22 FAQ improvement loop: post_conversation expert saves escalated Q&A pairs to /support/wiki/{topic} via flexus_policy_document, building FAQ from real interactions. Added flexus_policy_document to post_conversation toolset.
• scenario improvements: move mcp to sep file, fix removing require_dev… #28 Old chat summarization: post_conversation stores a 1-2 sentence conversation summary in contact_details.last_conversation_summary for prior-context reference.
• discord 2 3 initial #29 SLA follow-up: Hourly scheduled task checks kanban for stale escalations (>2h without human response) and notifies operator. Prompt guidance added to KAREN_DEFAULT.
• Problem #30 Discord @mention: Skipped (already done).

Test plan

• Install Karen on staging, verify report runs without deal sections
• Trigger report with zero activity, confirm "nothing happened" message
• Complete a conversation with escalation, verify wiki entry created
• Verify contact_details.last_conversation_summary populated after post_conversation
• Wait for stale-escalation schedule to fire, confirm operator notification

🤖 Generated with Claude Code

[humbertoyusta]

For this we need to make the escalation first, but not sure if sending reminder to person each hour for each opened is a good idea

Also should send only if that person "claimed" or "took" the task, because if not, there can be many operators that could take it, and we either need to configure them somewhere in setup or similar