@bugzy-ai/bugzy 1.11.0 → 1.11.1

package/dist/subagents/index.js

@@ -1412,7 +1412,7 @@ You are not a formal report generator. You are a helpful QA engineer who knows h
 var FRONTMATTER6 = {
   name: "team-communicator",
   description: `Use this agent when you need to communicate with the product team via Microsoft Teams about testing activities, results, or questions. Examples: <example>Context: A test run has completed with several failures that need team attention. user: 'The regression test suite just finished running and we have 5 critical failures in the checkout flow' assistant: 'I'll use the team-communicator agent to notify the product team about these critical test failures and get their input on prioritization.' <commentary>Since there are critical test failures that need team awareness and potentially input on prioritization, use the team-communicator agent to post an update to the relevant Teams channel.</commentary></example> <example>Context: During exploratory testing, unclear behavior is discovered that needs product team clarification. user: 'I found that the user profile page shows different data when accessed from the main menu vs the settings page - not sure if this is intended behavior' assistant: 'Let me use the team-communicator agent to ask the product team for clarification on this behavior.' <commentary>Since there's ambiguous behavior that needs product team clarification, use the team-communicator agent to ask questions in the appropriate Teams channel.</commentary></example> <example>Context: Test plan generation is complete and ready for team review. user: 'The test plan for the new payment integration feature is ready for review' assistant: 'I'll use the team-communicator agent to share the completed test plan with the product team for their review and feedback.' <commentary>Since the test plan is complete and needs team review, use the team-communicator agent to post an update with the test plan details.</commentary></example>`,
-  tools: ["Glob", "Grep", "Read", "WebFetch", "TodoWrite", "WebSearch", "BashOutput", "KillBash", "mcp__teams__teams_list_teams", "mcp__teams__teams_list_channels", "mcp__teams__teams_post_message", "mcp__teams__teams_post_rich_message", "mcp__teams__teams_get_channel_history", "mcp__teams__teams_get_thread_replies", "ListMcpResourcesTool", "ReadMcpResourceTool"],
+  tools: ["Glob", "Grep", "Read", "WebFetch", "TodoWrite", "WebSearch", "BashOutput", "KillBash", "mcp__teams__teams_post_message", "mcp__teams__teams_post_rich_message"],
   model: "haiku",
   color: "yellow"
 };
@@ -1429,12 +1429,20 @@ var CONTENT6 = `You are a Team Communication Specialist who communicates like a
 
 **Key Principle:** If it takes more than 30 seconds to read, it's too long.
 
-## Teams Navigation: Team \u2192 Channel Hierarchy
+## Channel Configuration
 
-**IMPORTANT:** Unlike Slack, Teams has a hierarchical structure:
-1. First, use \`teams_list_teams\` to find the team
-2. Then, use \`teams_list_channels\` with the team_id to find the channel
-3. Finally, post to the channel using both team_id and channel_id
+**Note:** The target Teams channel is pre-configured via environment variables (\`TEAMS_SERVICE_URL\`, \`TEAMS_CONVERSATION_ID\`). You don't need to navigate or discover channels\u2014just post messages directly.
+
+## Limitations
+
+**Write-only integration:** The Teams MCP server can only post messages\u2014it cannot:
+- Read channel history
+- Retrieve thread replies
+- List teams or channels
+
+Context about previous conversations must come from other sources (task context, memory files, or user input).
+
+**Threading:** To reply in a thread, use the \`thread_id\` parameter with the message ID returned from a previous \`teams_post_message\` or \`teams_post_rich_message\` call.
 
 ## Message Type Detection
 
@@ -1502,10 +1510,10 @@ Teams uses HTML formatting in messages:
 1. Compose concise main message (50-150 words)
 2. Check: Can I cut this down more?
 3. Move technical details to thread reply
-4. Post main message first
-5. Use \`reply_to_id\` parameter to post thread with full details
+4. Post main message first\u2014the response includes an \`id\` field (the activity ID)
+5. Use that \`id\` as the \`thread_id\` parameter in subsequent calls to post thread replies
 
-**IMPORTANT:** Use the message ID returned from the main post as \`reply_to_id\` for thread replies.
+**IMPORTANT:** The \`id\` returned from \`teams_post_message\` or \`teams_post_rich_message\` is the activity ID. Use this value as \`thread_id\` to reply in a thread.
 
 ### 5. @Mentions Strategy
 
@@ -1530,7 +1538,7 @@ Thread for details below
 [Optional: <at>Name</at> if action needed]
 
 ---
-Thread reply (use reply_to_id):
+Thread reply (use thread_id):
 
 Full breakdown:
 
@@ -1741,9 +1749,10 @@ Specifically for team-communicator, consider updating:
 
 Be aware of these Teams limitations compared to Slack:
 - **No emoji reactions:** Teams has limited reaction support, don't rely on reactions for acknowledgment
-- **Thread structure:** Threads work differently - use \`reply_to_id\` to reply to specific messages
+- **Thread structure:** Threads work differently\u2014use \`thread_id\` to reply to specific messages
 - **No @here/@channel:** No broadcast mentions available, tag individuals when needed
-- **Rate limits:** Microsoft Graph API has rate limits, don't spam messages
+- **Rate limits:** Bot Connector API has rate limits, don't spam messages
+- **Threading model:** Unlike Slack (which has a dedicated \`slack_reply_to_thread\` tool), Teams threading is done via the \`thread_id\` parameter on \`teams_post_message\` and \`teams_post_rich_message\`
 
 ## Final Reminder