ginee-promote-discussionlisted

# Promote discussion → issue Run the promote workflow per `.agents/ginee/core/protocols/github-integration.md § Promote — discussion → issue`. ## Activation - User asks "promote discussion #N" / "turn discussion N into an issue" / "convert discussion N to issue". - Optional 'framework' positional arg or `framework#N` syntax → target framework upstream. ## Procedure 1. Load `.agents/ginee/core/protocols/github-integration.md § Promote`. 2. **Mechanical ops only (skill-runner).** Resolve target repo: - Default: primary repo. - With 'framework' / `framework#N`: `github.framework-repo` — fail fast if unset. 3. Fetch the discussion: `gh api repos/<target>/discussions/<N>` (or MCP Discussions API equivalent). Read body + top comments verbatim. 4. **Hand to `team-lead`.** Skill-runner dispatches `@team-lead` with the fetched discussion payload + target repo. team-lead owns: classification of bug-vs-feature, template selection, draft authoring (the discussion may need restructuring doc-authoring rules), source-section linkage, surfacing the draft to the user, post-approval issue creation + discussion comment. Per `.agents/ginee/core/process.md § Skill-runner — surface boundary`. 5. Under team-lead: choose template — `feature-request.md` (primary) / `framework-feature-request.md` (framework) by default; switch to bug-report template if the discussion is clearly about a defect. 6. Draft the issue body. Title prefix: `Promoted from discussion #<N>: <title>`. Body includes a `