Reference the manage_discussion tool in ideation-sandbox §3

Context

@neo-gpt surfaced this as a non-blocking follow-up while reviewing PR #11750 (the implementation of #10138 — the new manage_discussion MCP tool). The tool ships an action: 'update_body' operation that updates a GitHub Discussion body in place via the updateDiscussion GraphQL mutation.

ideation-sandbox-workflow.md §3 "Author's Note Convention (The #10119 Annotation Pattern)" already instructs agents to "edit the [Discussion] body directly (like a force-push)" for post-publication corrections — but it predates manage_discussion and names no mechanism. An agent following §3 today must either rediscover the raw gh api graphql updateDiscussion workaround (the exact friction #10138 was filed to remove) or fall back to correction comments.

The Problem

§3 is correct guidance with a missing tool reference. The body-canonical correction pattern it describes is now backed by a first-class MCP tool, but the workflow doc does not connect the two. Result: manage_discussion is discoverable from the github-workflow MCP tool list and learn/agentos/GitHubWorkflow.md §4.5, but NOT from the ideation-sandbox workflow that is the primary consumer of body-canonical corrections. A new agent doing a #10119-style annotation pass has no pointer from the workflow it is actually running — so the MX loop that #10138 closed stays half-open at the ideation-sandbox surface.

The Architectural Reality

• Doc: .agents/skills/ideation-sandbox/references/ideation-sandbox-workflow.md §3 (lines ~26-29) — "Author's Note Convention (The #10119 Annotation Pattern)".
• Tool: manage_discussion (action: 'update_body', params discussion_number + body) — github-workflow MCP server; service method DiscussionService.manageDiscussion; documented in learn/agentos/GitHubWorkflow.md §4.5.
• This is an Atlas-only change: §3 lives in the references/ payload (the World Atlas), not the top-level ideation-sandbox/SKILL.md router (the Map). No router bloat — Progressive Disclosure preserved (ticket-create §1b Meta-Skill Sweep satisfied).

The Fix

In ideation-sandbox-workflow.md §3, add a brief clause naming manage_discussion({action: 'update_body', discussion_number, body}) as the MCP tool that performs the "edit the body directly" step. One clause — enhance the existing §3 in place; do not add a new section.

Acceptance Criteria

• ideation-sandbox-workflow.md §3 references the manage_discussion tool (action: 'update_body') as the mechanism for its "edit the body directly" instruction.
• The change is confined to §3 of the references/ payload — the top-level ideation-sandbox/SKILL.md router is untouched (Progressive Disclosure / Map-vs-Atlas preserved).
• No new section is added; the existing §3 is enhanced in place — net substrate change is a single clause.

Out of Scope

• Any change to the manage_discussion tool itself (shipped via #10138 / PR #11750).
• Broader rewrite of §3's Author's Note Convention — only the missing tool reference is in scope.
• Documenting manage_discussion elsewhere — GitHubWorkflow.md §4.5 already covers the tool surface.

Gating Condition

Begins after PR #11750 (#10138) merges — the manage_discussion tool must exist in the codebase before the workflow doc references it. filing ≠ starting.

Related

• Surfaced in: PR #11750 cross-family review by @neo-gpt (the #10138 implementation review).
• Tool ticket: #10138 (manage_discussion MCP tool).
• Pattern origin: Discussion #10119 — the body-annotation correction pattern §3 is named after.

Origin Session ID

ff79d594-1c1e-4181-ad9b-3d9150547699

Handoff Retrieval Hints

• query_raw_memories({query: 'manage_discussion ideation-sandbox author note convention pointer'})
• Exact anchors: ideation-sandbox-workflow.md §3; learn/agentos/GitHubWorkflow.md §4.5.