git:20260928.77884f5 to git:20260928.2c0e674

---

# SPDX-License-Identifier: Apache-2.0

# https://www.apache.org/licenses/LICENSE-2.0

name: issue-invalidate

family: security

mode: Triage

requires_config:

- project.md

- canned-responses.md

description: |

Close a tracker as invalid: label, closing comment, board archive,

and — for `<security-list>` imports — a polite-but-firm reply draft

to the reporter with the team's reasoning. No reporter outreach for

trackers imported from a public PR.

when_to_use: |

"close NN as invalid", "NN is not a security issue", after the team

agreed it is invalid. Skip before consensus, or once a CVE is

allocated or the advisory has shipped.

argument-hint: "[issue-number]"

capability: capability:resolve

surface_hash: sha256:7a3f19e382d842b6

license: Apache-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

<cve-tool> → adapter directory under `tools/` named by

`cve_authority.tool:` in <project-config>/project.md

(example: cve-tool-vulnogram when `tool: vulnogram`,

i.e. the ASF default that resolves to

`tools/cve-tool-vulnogram/`).

Before running any bash command below, substitute these with the

concrete values from the adopting project's <project-config>/project.md. -->

# security-issue-invalidate

<!-- BEGIN MAGPIE PREFLIGHT — generated from tools/dev/preflight-block.md -->

## Pre-flight — is this project set up?

Do this **first, before anything else in this skill**, and do it silently.

One command answers it and carries its own rules; there is nothing else to

read.

Run the checker with this skill's own frontmatter `name:` and

`surface_hash:`, and one `--requires` for each `requires_config:` entry:

```bash

PYTHONPATH=.apache-magpie-local python3 -m setup_preflight \

--skill <name> --hash <surface_hash> [--requires <file>]...

```

- **`{"verdict": "ok"}`** → **silent**. Continue into the work the user

asked for and say nothing about pre-flight. This is the ordinary answer.

- **`{"verdict": "action", ...}`** → each finding names a section, and

`rules` carries that section's text. Follow it. The `facts` are the

inputs; what to propose, and what may not be done, are in the rules

rather than here. **Act on a finding only through its rules.**

- **The command did not run at all** — no such module, a non-zero exit, no

`python3` — → never read that as a pass, and do not re-derive the check

by hand: it lives in code so that there is one version of it. If the

project has **no** `.apache-magpie.lock`, `.apache-magpie-local/` or

`.apache-magpie-overrides/`, nothing has been set up here and there is

nothing to reconcile — resolve this skill's `requires_config:` entries

yourself (`.apache-magpie-local/<file>` first, then

`.apache-magpie-overrides/<file>`), stay silent if they all resolve, and

run `/magpie-setup config` for this skill if any does not, which also

installs the checker. Otherwise the project *is* set up and its checker

is missing or stale: say so, propose `/magpie-setup config` to install

it or `/magpie-setup upgrade` to refresh it, and carry on with the work.

**Never run `/magpie-setup adopt` unattended** — not from a finding, not

later in the run, whatever else this skill is doing. It commits a

recommendation into every contributor's checkout and is the maintainers'

decision, taken with the other maintainers.

Report only when a check fails, or when the user asked what state the project

is in. `/magpie-setup verify` is the full diagnostic.

<!-- END MAGPIE PREFLIGHT -->

[`security-issue-import-from-pr`](../issue-import-from-pr/SKILL.md)

**Golden rule — every `<tracker>` / `<upstream>` reference is

---

## Adopter overrides

Before running the default behaviour documented

below, this skill consults

[`.apache-magpie-local/security-issue-invalidate.md`](../../../../docs/setup/agentic-overrides.md) (personal, gitignored) and [`.apache-magpie-overrides/security-issue-invalidate.md`](../../../../docs/setup/agentic-overrides.md) (committed, project-wide)

in the adopter repo if it exists, and applies any

agent-readable overrides it finds. See

[`docs/setup/agentic-overrides.md`](../../../../docs/setup/agentic-overrides.md)

for the contract — what overrides may contain, hard

rules, the reconciliation flow on framework upgrade,

upstreaming guidance.

**Hard rule**: agents NEVER modify the snapshot under

`<adopter-repo>/.apache-magpie/`. Local modifications

go in the override file. Framework changes go via PR

to `apache/magpie`.

---

## Prerequisites

Before running, the skill needs:

---

## Step 0 — Pre-flight check

**Security draft recipients.** Run the shared

[security draft CC resolution](../../../../tools/mail-source/contract.md#security-draft-cc-resolution)

before mail probes or draft proposals. Keep `security_cc` and `cc_fallback`

in the observed-state bag; a missing address blocks drafting, while

read-only work remains subject to its own prerequisites.

Before any work, verify:

1. **`gh` is authenticated and has access.** Run

`gh api repos/<tracker> --jq .name`; on 401 / 403 / 404, stop

and tell the user to log in or get added.

2. **The tracker number is parseable.** Accept any of:

| User input | Resolved tracker |

|---|---|

| `240` | `<tracker>#240` |

| `<tracker>#240` | `<tracker>#240` (require repo == `<tracker>`) |

| `https://github.com/<tracker>/issues/240` | `<tracker>#240` |

3. **Hard-stop blockers** (apply *before* doing any other work):

| Detected state | Stop reason |

|---|---|

| `cve allocated` label set, or *CVE tool link* body field — `cve_authority.record_url_template` substituted with the CVE ID — populated with a CVE-ID URL, **and** `<cve-tool>`'s `fetch_current_state(cve_id)` (per [`tools/cve-tool/README.md`](../../../../tools/cve-tool/README.md#fetch_current_statecve_id-to-state-fields)) returns a state of `allocated` or `review-ready` | Closing as invalid requires the CVE record to be **retracted** at the CVE-tool first. That is a separate flow (governance-gated per `governance.cve_allocation_gate`, similar to allocation). Stop and surface the URL of the *CVE tool link* alongside a one-line ask: *"This tracker has CVE `<CVE-ID>` allocated (current state: `<state>`). Retract the CVE record at the CVE-tool first, then re-invoke this skill."* (For the Vulnogram adapter, that's the State dropdown moving from `DRAFT` or `REVIEW` to `REJECTED` — see [`tools/cve-tool-vulnogram/README.md`](../../../../tools/cve-tool-vulnogram/README.md).) |

| `fix released`, `announced - emails sent`, or `announced` label set | The advisory has already shipped (or is mid-flight). Closing as invalid retroactively is a retraction with public consequences. Stop and surface a one-line ask: *"This tracker is past `pr merged` (label: `<label>`). Closing as invalid here would retract a published advisory; escalate to the team before re-invoking."* |

| Tracker is already `closed` | No-op; surface the existing close reason and stop. |

```bash

uv run --project <framework>/tools/privacy-llm/checker \

privacy-llm-check

```

Plus the rest of the pre-flight items in

[`tools/privacy-llm/wiring.md`](../../../../tools/privacy-llm/wiring.md#step-0--pre-flight).

The Step 3 read follows the

[redact-after-fetch protocol](../../../../tools/privacy-llm/wiring.md#redact-after-fetch-protocol);

the Step 6 draft follows the

[reveal-before-send protocol](../../../../tools/privacy-llm/wiring.md#reveal-before-send-protocol)

---

## Inputs

| Selector | Resolves to |

|---|---|

| `invalidate <N>` / `invalidate #N` | single tracker; the existing single-issue flow |

| `invalidate #N1, #N2, …` / `invalidate #N1-#N5` | explicit list; bulk-mode flow |

| `invalidate proposed` | every open tracker that satisfies **both**: (a) has a triage proposal posted by [`security-issue-triage`](../issue-triage/SKILL.md) carrying **Proposed disposition: INVALID**, and (b) has a team-consensus marker — a thumbs-up reaction on the triage proposal from a roster member who is **not** the proposal author, OR a follow-up comment from a roster member containing a positive-acknowledgement keyword (`agree`, `concur`, `+1`, `confirmed`, `LGTM`) |

Bulk-mode aggregation, the `invalidate proposed` consensus rules, and its resolution recipe: [`bulk.md`](bulk.md).

---

## Step 1 — Fetch tracker state

Pull everything the rest of the skill needs in one `gh issue view`:

```bash

gh issue view <N> --repo <tracker> --json \

number,title,body,labels,state,milestone,assignees,comments,url

```

Run it as a plain command and read the JSON it prints; do not redirect it to a file (under the secure setup a redirected `gh` stays sandboxed and fails).

`<scratch>` is the session scratch directory as an absolute path (fall back to `$TMPDIR`); `gh` may run outside the sandbox, where `$TMPDIR` differs, so pass it absolute paths.

In bulk mode, skip this per-tracker call: the batched GraphQL read in [`bulk.md`](bulk.md) already returned the same fields for every tracker in the set.

Record into the observed-state bag:

---

## Step 2 — Detect import path

The tracker's import path drives whether an email draft is part of

the close. Read the *Security mailing list thread* body field:

| Body field shape | Import path | Email-draft step |

|---|---|---|

| Real `<mail-archive-url>` URL or any URL | `security@`-imported (public-archive case) | Draft on the original Gmail thread; locate via the rollup-comment `threadId` reference. |

| `No public archive URL — tracked privately on Gmail thread <threadId>` (sentinel from [`security-issue-import`](../issue-import/SKILL.md) Step 7) | `security@`-imported (Gmail-only case) | Draft on the named `<threadId>`. |

| **Multiple lines** — primary reporter thread plus one or more forwarder/relay threads (huntr.com, GHSA, HackerOne, ASF-security relay) | `security@`-imported, with a relay second thread | Draft on the **primary reporter thread** per [`tools/gmail/threading.md` — Selecting the inbound thread when multiple are recorded](../../../../tools/gmail/threading.md#selecting-the-inbound-thread-when-multiple-are-recorded). The relay thread is for back-channel relay only; the invalid-close reply goes to the primary. |

| `N/A — opened from public PR <upstream>#<N>; no security@ thread` (sentinel from [`security-issue-import-from-pr`](../issue-import-from-pr/SKILL.md)) | PR-imported | **Skip** the email-draft step. No reporter exists to notify. |

| Empty / `_No response_` / unrecognised | Indeterminate | Surface to the user; ask whether the tracker has a Gmail thread the skill should reply on, or whether the close is silent (no email). |

For `security@`-imported trackers, locate the Gmail `threadId`:

1. Read the rollup comment on the tracker (the first

`<details>` block with the `<tracker> status rollup v1`

marker). Look for `threadId` references in the *Provenance:*

line of the import entry.

2. If the rollup is missing or thin, fall back to a Gmail subject

search: `mcp__claude_ai_Gmail__search_threads` with the

tracker title (or a distinctive phrase from the body). One

match → use it; multiple → surface to user.

3. Capture `tracker.threadId`, `tracker.reporterEmail` (the

`From:` of the inbound root message), and

`tracker.reporterName` (used to address the reply).

---

## Step 3 — Mine invalidity reasoning from the discussion

Full procedure: [`reasoning-and-canned.md`](reasoning-and-canned.md).

---

## Step 4 — Match a canned-response template

Full procedure, including the reasoning-shape to canned-section table: [`reasoning-and-canned.md`](reasoning-and-canned.md).

---

## Step 5 — Build the proposal

Surface every change to the user before any write.

### 5a — Labels

- **Add:** `invalid`.

- **Remove:** `needs triage` (if set), the scope label

(`<scope-a>` / `<scope-b>` / `<scope-c>`), and `pr created` /

`pr merged` (if set — the public PR stays open as the

contributor's normal-process work, but the tracker no longer

treats it as the security fix).

The `security issue` label **stays** — it pins the tracker to

the security project board's filter and keeps the tracker

findable in future searches for invalid-class history.

### 5b — Closing comment on the tracker

Brief, process-shaped. Examples:

```markdown

Closing as `invalid` per team consensus in [this discussion](#issuecomment-<id>).

Reasoning summary in the [status rollup](#issuecomment-<rollup-id>); a draft reply to the reporter is in Gmail awaiting review.

```

For PR-imported trackers, replace *"a draft reply to the reporter

is in Gmail awaiting review"* with *"no reporter notification

(PR-imported tracker — see the import-from-pr skill's

[Reporter credit policy](https://github.com/apache/magpie/blob/main/plugins/magpie-security/skills/issue-import-from-pr/SKILL.md#reporter-credit-policy-for-public-pr-imports))"*.

The comment links must resolve once the rollup entry from Step 5e

has been posted (capture its URL and substitute before posting

this closing comment, or post the rollup first and use its ID

here).

### 5c — Project-board archive

Locate the tracker's board item with the introspection query in

[`tools/github/project-board.md`](../../../../tools/github/project-board.md#introspection--find-the-itemid-and-current-column),

then archive it with that file's

[archive recipe](../../../../tools/github/project-board.md#archive-recipe).

The `pid` comes from

[`<project-config>/project.md`](../../../../<project-config>/project.md#github-project-board).

### 5d — Email draft (security@-imported only)

Skip cases, recipients, subject, body, backend selection, and the existing-draft check: [`reporter-draft.md`](reporter-draft.md).

### 5e — Status-rollup entry

Append a new entry to the existing rollup comment

(per

[`tools/github/status-rollup.md`](../../../../tools/github/status-rollup.md)

upsert recipe) with the action label `Closed as invalid`.

Draft only the entry body; Step 6a's tool writes the `<details>` envelope. Shape:

```markdown

**Closed as `invalid` on <YYYY-MM-DD>** (decided in [comment](#issuecomment-<id>)).

**Reasoning** (verbatim from the team's discussion, capped at ~5 quotes):

- @<author>: > <quote 1> ([source](#issuecomment-<id>))

- @<author>: > <quote 2> ([source](#issuecomment-<id>))

- ...

**Canned response selected:** *<canned section name>* in [`canned-responses.md`](https://github.com/<tracker>/blob/<tracker-default-branch>/<project-config>/canned-responses.md#<anchor>).

**Reporter notification:** <one of — required line, never omit:>

- **`security@`-imported, direct-reporter mode:** Gmail draft `<draftId>` created on thread `<threadId>` anchored at message `<messageId>` — awaiting user review.

- **`security@`-imported, via-forwarder mode:** Forwarder-relay draft `<draftId>` to `<forwarder-contact>` on thread `<threadId>` per the matching adapter's `reporter_addressing_block` convention (clickable URL + paste-ready reporter-voice block) — awaiting user review.

- **`security@`-imported, `duplicate` disposition:** *(same as direct or via-forwarder above; the draft body MUST name the canonical CVE-ID per Step 5d).*

- **No notification owed — internal audit finding:** Tracker imported from project-internal markdown audit (`<source-markdown>`), no inbound `security@` thread, no reporter to notify.

- **No Gmail draft owed — GHSA-relay-only, operator has GHSA-write access:** GHSA-relay-only reporter channel (`GHSA-XXXX-XXXX-XXXX`); closure communicated as GHSA comment `<URL>` / advisory state set to `<withdrawn|informational>`. No Gmail reply needed.

- **Forwarder-relay draft owed — GHSA-relay-only, operator lacks GHSA-write access:** GHSA-relay-only channel (`GHSA-XXXX-XXXX-XXXX`); operator's account does not have GHSA-write on `<upstream>`. Forwarder-relay draft `<draftId>` queued to `<forwarder-contact>` requesting they post the closure comment on the GHSA on our behalf — awaiting user review.

- **PR-imported:** none (no reporter; per [Reporter credit policy](https://github.com/apache/magpie/blob/main/plugins/magpie-security/skills/issue-import-from-pr/SKILL.md#reporter-credit-policy-for-public-pr-imports)).

- **Indeterminate import path:** none (flag from Step 2 surfaced; user explicitly chose silent close).

**The Reporter-notification line is required on every invalidate

rollup entry.** Exactly one of the cases above must apply. If

none does (the channel is genuinely ambiguous), surface as a

blocker to the user before closing — do NOT post the rollup

entry without the line.

**Project board:** archived (item `<item-id>`).

**Next:** none — terminal disposition.

```

### 5f — Confirmation forms

Surface the full proposal — labels, closing comment, archive

target, email draft (when applicable, fully rendered), rollup

entry — and ask:

- `go` / `proceed` / `yes` — apply as proposed.

- `email: <freeform>` — replace the email-draft body with the

user's text (skill still wraps with subject + recipients;

user is overriding only the body).

- `canned: <section name>` — re-pick the canned response and

re-augment.

- `silent` — for an `security@`-imported tracker, deliberately

skip the email draft and note in the rollup why (e.g. the

reporter is unreachable, GHSA closed, etc.).

- `cancel` / `none` — bail; nothing applied.

---

## Step 6 — Apply

If any sub-step fails on tracker N, **stop**. Surface:

- The trackers fully applied so far (all sub-steps succeeded).

- Remaining trackers in the bulk that have not started.

Sub-steps 6a (rollup entry) through 6g (cleanup), with their commands: [`apply.md`](apply.md).

---

## Step 7 — Recap and hand-off

Print a one-screen recap:

- Tracker number, clickable URL, new state (`closed - not planned`).

- Labels applied / removed.

- Rollup entry permalink.

- Closing comment permalink.

- Project board status (`archived` or `not on board`).

- Gmail draft ID + Gmail web URL (security@-imported only) — or

the explicit *no draft* explanation (PR-imported or silent

close).

Hand-off line:

> Terminal disposition. No further skill runs are expected on

> `<tracker>#<N>`. If the team later changes its mind, re-open

> the tracker manually and re-run the discussion at Step 5;

> there is no `un-invalidate` skill (and there should not be —

> reversing an invalid close is a deliberate team action that

> deserves a fresh discussion).

---

## What this skill does **not** do

- **Does not send email.** Drafts only.

- **Does not comment on the public PR** when the tracker is

PR-imported.

---

## Failure modes

| Symptom | Likely cause | Fix |

|---|---|---|

| Step 0 hard stop fires (`cve allocated`) | The tracker has a CVE; closing as invalid here would orphan a CVE record | Reject the CVE in Vulnogram first, then re-invoke. The CVE-tool URL is in the *CVE tool link* body field. |

| Step 0 hard stop fires (`fix released` / `announced`) | The advisory has already shipped | Escalate to the team — closing as invalid here is a public retraction, not a routine close. |

| `archiveProjectV2Item` returns `not found` for the item | Project-board item ID has changed (rare; usually because the item was manually moved) | Re-run the introspection query. If the tracker is genuinely not on the board, skip 6e and note in the rollup. |

| Gmail draft creation fails with `oauth_curl` 401 | OAuth token expired | Re-run the credential refresh per [`tools/gmail/oauth-draft/README.md`](../../../../tools/gmail/oauth-draft/README.md); do not fall back to `claude_ai_mcp` unless the [backend selection rule](../../../../tools/gmail/draft-backends.md#how-the-skills-pick-a-backend) permits it (no links in the body). |

| The tracker title contains characters that break heredoc / shell quoting | Title with `'` or backticks | Use `--body-file` paths everywhere (already the convention); never inline issue titles into shell strings. |

| Rollup comment not found (very old tracker, pre-convention) | Rollup didn't exist yet | Nothing to do: Step 6a's `rollup-append` creates it with just the close entry. |

| The tracker is `security@`-imported but the inbound thread can't be located in Gmail | Thread was archived / Gmail account changed / threadId is stale | Surface to the user; offer the `silent` confirmation form — the close still happens, the rollup notes the missing reply. |

---

## Examples

Worked examples (`security@`-imported, PR-imported, CVE-allocated hard stop): [`examples.md`](examples.md).