[plan] Fix discussion intelligence visibility path for DeepReport

[github-actions]

Context

From DeepReport Intelligence Briefing 2026-03-17: Both repo-level and org-level discussion listing queries returned empty results in the DeepReport run, despite discussions being present. This significantly limits the intelligence coverage of DeepReport since discussions are a primary data source for trend analysis.

Objective

Diagnose and fix the discussion-listing access path used by the DeepReport workflow so it reliably returns discussion data for both repository and organization scopes.

Approach

1. Review the DeepReport workflow (deep-report.md or similar) to find the discussion-listing step
2. Identify the MCP tool call or API query used for discussion reads
3. Test the query in isolation using gh aw mcp inspect or the MCP inspector
4. Check for:
   • Incorrect repository/org scope configuration
   • Missing toolset permissions (e.g., discussions toolset not enabled)
   • API pagination or empty-result handling bugs
5. Apply a fix and verify discussions are returned in a test run

Files to Review

• .github/workflows/deep-report.md (or equivalent workflow file)
• pkg/workflow/ — toolset/permission compilation logic
• MCP tool configuration for GitHub discussion access

Acceptance Criteria

• DeepReport can list discussions at both repo and org scope
• Fix is verified by a test run showing non-empty discussion data
• Root cause is documented in the PR description

Generated by Plan Command for issue #discussion #21411 · ◷

• expires on Mar 19, 2026, 11:45 PM UTC