magpie-security-issue-deduplicate

<!-- 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 (example: <tracker>) <upstream> → value of `upstream_repo:` in <project-config>/project.md (example: <upstream>) <cve-tool> → CVE-tool adapter directory under `tools/` named by `cve_authority.tool` in <project-config>/project.md (example: cve-tool-vulnogram for the ASF default). Before running any bash command below, substitute these with the concrete values from the adopting project's <project-config>/project.md. --> # security-issue-deduplicate Merges two `<tracker>` tracking issues that describe the same underlying vulnerability. The output is a single tracker ("the **kept** issue") that carries every reporter's credit, every mailing-list thread, and every independent report's body, with the other tracker ("the **dropped** issue") closed and labelled `duplicate`. This is **one of the few places in the security workflow** where a piece of reporter-supplied content (the dropped issue's body) moves from one tracker to another. Since the target tracker is private to `<tracker>`, no confidentiality boundary is crossed, but the skill must still preserve every reporter's credit verbatim and surface the merge in a status ...