magpie-report-framework-issue

<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Placeholder convention (see AGENTS.md#placeholder-convention-used-in-skill-files): <project-config> → adopting project's `.apache-magpie/` directory <tracker> → value of `tracker_repo:` in <project-config>/project.md <upstream> → value of `upstream_repo:` in <project-config>/project.md <framework> → `.apache-magpie/apache-magpie` in adopters; `.` in the framework standalone framework repo → where framework issues are filed. Default `apache/magpie`; override with `framework_repo` in `.apache-magpie-overrides/report-framework-issue.md`. --> # report-framework-issue Turn a problem an adopter hits **while using Magpie itself** into a clean, public-safe GitHub issue on the framework repo (`apache/magpie`). The adopter is running the framework against pre-disclosure CVE content on a private tracker, so the whole point of this skill — and the reason it is modelled on a redact-then-file flow rather than a bare `gh issue create` — is the **mandatory public-disclosure scrub** in Step 2. The destination is a public repo; anything that leaks the adopter's tracker, an embargoed CVE, private-list traffic, or another ASF project's vulnerability is a disclosure incident, not a cosmetic slip. The skill gathers the problem *from the user* (a description plus whatever error text...