Context:
The manage_issue_comment MCP tool was previously enriched in PR #10287 to return {commentId, url, createdAt}. This unlocked the A2A Comment-ID Hand-off Protocol, drastically reducing token fetch costs during multi-cycle PR reviews. The equivalent extension for manage_discussion_comment was explicitly deferred as out-of-scope in that PR.
The Problem:
Agents utilizing GitHub Discussions (via the ideation-sandbox skill) for architectural swarm coordination cannot perform the standard A2A commentId hand-off. When an agent invokes manage_discussion_comment (action: create), the tool does not return the commentId. The agent must either manually re-fetch and scan the discussion thread to find their ID, or skip the hand-off protocol entirely, which breaks swarm efficiency.
The Architectural Reality:
The manage_discussion_comment tool's handler in the github-workflow MCP server natively executes a GraphQL mutation to create the comment. It currently discards or fails to parse the returned node ID from the mutation payload.
The Fix:
Symmetrically extend the manage_discussion_comment tool's create action to capture the GraphQL response and map it to the {message, commentId, url, createdAt} shape, mirroring the pattern established by manage_issue_comment.
Acceptance Criteria:
Out of Scope:
- Building selectors into the discussion-fetch tool (
get_discussion_conversation, etc.) is out of scope. This ticket is strictly for the creation-side payload enrichment.
Origin Session ID:
88a6ed3a-b1b9-461a-aaf3-7c9984bd12e7
Context: The
manage_issue_commentMCP tool was previously enriched in PR #10287 to return{commentId, url, createdAt}. This unlocked the A2A Comment-ID Hand-off Protocol, drastically reducing token fetch costs during multi-cycle PR reviews. The equivalent extension formanage_discussion_commentwas explicitly deferred as out-of-scope in that PR.The Problem: Agents utilizing GitHub Discussions (via the
ideation-sandboxskill) for architectural swarm coordination cannot perform the standard A2A commentId hand-off. When an agent invokesmanage_discussion_comment(action:create), the tool does not return thecommentId. The agent must either manually re-fetch and scan the discussion thread to find their ID, or skip the hand-off protocol entirely, which breaks swarm efficiency.The Architectural Reality: The
manage_discussion_commenttool's handler in thegithub-workflowMCP server natively executes a GraphQL mutation to create the comment. It currently discards or fails to parse the returned node ID from the mutation payload.The Fix: Symmetrically extend the
manage_discussion_commenttool'screateaction to capture the GraphQL response and map it to the{message, commentId, url, createdAt}shape, mirroring the pattern established bymanage_issue_comment.Acceptance Criteria:
manage_discussion_commentactioncreatereturns a payload includingcommentIdupon success.Out of Scope:
get_discussion_conversation, etc.) is out of scope. This ticket is strictly for the creation-side payload enrichment.Origin Session ID:
88a6ed3a-b1b9-461a-aaf3-7c9984bd12e7