perf(security): decide and render the five import skills as code, and read tracker fields through one normaliser

.github/labeler.yml

@@ -564,6 +564,7 @@ substrate:analytics:
               - 'tools/dashboard-generator/**'
               - 'tools/pr-management/**'
               - 'tools/preflight-audit/**'
+              - 'tools/security-management/**'
               - 'tools/security-tracker-stats-dashboard/**'
               - 'tools/skill-token-count/**'
               - 'tools/spec-inventory/**'

docs/labels-and-capabilities.md

@@ -357,6 +357,7 @@ or a contract-free mix of substrates (e.g. `tools/spec-inventory` is
 | [`tools/vetted-ops`](../tools/vetted-ops/) | `substrate:sandbox` | Fixed, policy-scoped forge operations — a closed catalogue whose parameters can never become commands or flags, so one `allow` entry replaces the wildcard Layer 3 `ask` rules |
 | [`tools/contributor-metrics`](../tools/contributor-metrics/) | `substrate:analytics` | Deterministic contributor activity counts, per-area shares and automated-work weighting for the contributor-growth skills |
 | [`tools/pr-management`](../tools/pr-management/) | `substrate:analytics` | Deterministic core of the `pr-management` skills: classifies a saved PR sweep (pre-filters, decision table, stale sweeps), guards each mutation on fresh reads, renders every contributor-facing body, and builds the whole PR-backlog dashboard |
+| [`tools/security-management`](../tools/security-management/) | `substrate:analytics` | Deterministic core of the `security-*` skills: the Step 1 pre-filter, batched `threadId` dedup, forwarder pre-screen, the sanitised tracker body, rollup entry, rejections-ledger record and fix-already-public reply, the receipt-draft matrix, the confirmation-reply grammar and the recap; runs nothing. Used by `security-issue-import` Steps 0–8 `security-issue-import-from-pr` Steps 0–8 (PR reference, scope detection, milestone check, duplicate query, body, labels, rollup, recap), `security-issue-import-from-md` Steps 0–6 (findings parser, keyword, body, rollup, proposal, recap), `security-issue-import-via-forwarder` Steps 0–3 (preflight, adapter detection, credit kind, routing) and `security-issue-import-from-scan` Steps C–F (bucket rule, report, decision, scrub) |
 | [`tools/preflight-audit`](../tools/preflight-audit/) | `substrate:analytics` | Dry-run the bulk-mode pre-flight classifier; measure skip-rate before / after any rule edit in the security-issue-sync skill |
 | [`tools/privacy-llm`](../tools/privacy-llm/) | `substrate:privacy` | Privacy-LLM PII-scrubbing gate |
 | [`tools/probe-templates`](../tools/probe-templates/) | `substrate:sandbox` | Sandbox-doctor probe templates |

docs/vendor-neutrality.md

@@ -614,7 +614,7 @@ Organization scope (declared, orthogonal to vendor): ASF = 16, agnostic = 64.
 
 **LLM / agent-integration neutrality**
 
-**Agent harness: 33/33 substrate tools run under any harness unchanged (100%).** Substrate tools are Magpie's own machinery; each declares the agent harness it integrates with (`**Harness:**`), or `agnostic`. A tool is neutral when it is harness-agnostic or supports two or more harnesses; *coupled* when it targets a single harness.
+**Agent harness: 34/34 substrate tools run under any harness unchanged (100%).** Substrate tools are Magpie's own machinery; each declares the agent harness it integrates with (`**Harness:**`), or `agnostic`. A tool is neutral when it is harness-agnostic or supports two or more harnesses; *coupled* when it targets a single harness.
 
 | Substrate tool | Substrate | Harness support | Verdict |
 |---|---|---|---|
@@ -638,6 +638,7 @@ Organization scope (declared, orthogonal to vendor): ASF = 16, agnostic = 64.
 | `release-verify` | release | any | ✅ agnostic |
 | `reproducible-archive` | release | any | ✅ agnostic |
 | `sandbox-lint` | sandbox | Claude Code, Codex, Cursor, Gemini CLI, Grok, Kiro, OpenCode | ✅ portable |
+| `security-management` | analytics | any | ✅ agnostic |
 | `security-tracker-stats-dashboard` | analytics | any | ✅ agnostic |
 | `setup-preflight` | setup | any | ✅ agnostic |
 | `skill-and-tool-validator` | framework-dev | any | ✅ agnostic |
@@ -663,7 +664,7 @@ Harness → substrate tools it supports:
 - **Junie** (1): `agent-guard`
 - **Kiro** (3): `agent-guard`, `sandbox-lint`, `spec-loop`
 - **OpenCode** (3): `agent-guard`, `sandbox-lint`, `spec-loop`
-- **any harness** (30): `adversarial-review`, `agent-isolation`, `container-gateway`, `contributor-metrics`, `dashboard-generator`, `dev`, `egress-gateway`, `maven-artifact-verify`, `permission-audit`, `pilot-report-validator`, `pr-management`, `preflight-audit`, `privacy-llm`, `probe-templates`, `release-config`, `release-management`, `release-verify`, `reproducible-archive`, `security-tracker-stats-dashboard`, `setup-preflight`, `skill-and-tool-validator`, `skill-evals`, `skill-reconciler-diff`, `skill-token-count`, `spec-inventory`, `spec-status-index`, `spec-validator`, `symlink-lint`, `vendor-neutrality-score`, `vetted-ops`
+- **any harness** (31): `adversarial-review`, `agent-isolation`, `container-gateway`, `contributor-metrics`, `dashboard-generator`, `dev`, `egress-gateway`, `maven-artifact-verify`, `permission-audit`, `pilot-report-validator`, `pr-management`, `preflight-audit`, `privacy-llm`, `probe-templates`, `release-config`, `release-management`, `release-verify`, `reproducible-archive`, `security-management`, `security-tracker-stats-dashboard`, `setup-preflight`, `skill-and-tool-validator`, `skill-evals`, `skill-reconciler-diff`, `skill-token-count`, `spec-inventory`, `spec-status-index`, `spec-validator`, `symlink-lint`, `vendor-neutrality-score`, `vetted-ops`
 
 **Model endpoint: neutral by construction — 4 default-approved endpoint classes across independent trust domains, plus adopter opt-in.** From the [`privacy-llm` registry](../tools/privacy-llm/models.md): the framework keys approval on *endpoint identity*, not on who hosts the model, so no single LLM vendor is privileged.
 

plugins/magpie-security/skills/cve-allocate/SKILL.md

@@ -21,7 +21,7 @@ argument-hint: "[issue-number] [CVE-YYYY-NNNNN]"
 capability: capability:resolve
 surface_hash: sha256:25c2286c4e159c66
 license: Apache-2.0
-measured_tokens: 7638
+measured_tokens: 7679
 ---
 
 <!-- Placeholder convention (see AGENTS.md#placeholder-convention-used-in-skill-files):
@@ -420,8 +420,8 @@ partial failures stay legible:
    (`uv run --project ~/.claude/magpie/vetted-ops vetted-op-tracker --caller security-cve-allocate rollup-append <N> "CVE allocated (<CVE-YYYY-NNNNN>)" <scratch>/rollup-entry-<N>.md`)
    — appends the entry to the tracker's rollup, creating the rollup if none exists yet.
    `<scratch>` is the session scratch directory as an absolute path (fall back to `$TMPDIR`); the entry point runs outside the sandbox, where `$TMPDIR` differs, so pass it absolute paths.
-4. `uv run --project <framework>/<cve-tool>/generate-cve-json generate-cve-json <N> --attach`
-   — embeds the CVE JSON in the body.
+4. `uv run --project <framework>/<cve-tool>/generate-cve-json generate-cve-json <N> --attach --report-json <scratch>/cve-report-<N>.json`
+   — embeds the CVE JSON in the body; a report with any non-empty array goes through the [CVE JSON fallback](../issue-sync/outcomes/cve-json-fallback.md).
 5. Create draft on the original thread (reporter notification, if
    applicable) via the project's configured drafting backend — see
    [`tools/gmail/draft-backends.md`](../../../../tools/gmail/draft-backends.md).

plugins/magpie-security/skills/cve-allocate/tracker-updates.md

@@ -43,9 +43,10 @@ user to confirm. Numbered items:
 4. **Regenerate the CVE JSON attachment** in the tracker body by
    running the adapter's `generate-cve-json` sub-tool:
    ```bash
-   uv run --project <framework>/<cve-tool>/generate-cve-json generate-cve-json <N> --attach
+   uv run --project <framework>/<cve-tool>/generate-cve-json generate-cve-json <N> --attach --report-json <scratch>/cve-report-<N>.json
    ```
    This is how the CVE record first gets seeded with the allocated ID.
+   Any non-empty `normalisation_changes`, `missing_required` or `needs_decision` in the report goes through [`security-issue-sync`'s CVE JSON fallback](../issue-sync/outcomes/cve-json-fallback.md).
    The remediation-developer credit (if any) comes from the *Remediation developer* body field,
    which `security-issue-sync` fills from the linked PR's author the first time *PR with the fix* is set
    (editable by hand thereafter); no CLI flag needed.

plugins/magpie-security/skills/issue-deduplicate/SKILL.md

@@ -25,7 +25,7 @@ argument-hint: "[kept-issue] [duplicate-issue]"
 capability: capability:resolve
 surface_hash: sha256:3c9f502b802d2037
 license: Apache-2.0
-measured_tokens: 6261
+measured_tokens: 6312
 ---
 
 <!-- Placeholder convention (see AGENTS.md#placeholder-convention-used-in-skill-files):
@@ -374,8 +374,9 @@ After confirmation, apply **sequentially** (never in parallel):
    (GitHub's `duplicate` close-reason is not exposed by `gh` on
    all versions; `not planned` combined with the `duplicate` label
    carries the same signal)
-6. `uv run --project <framework>/tools/<cve-tool>/generate-cve-json generate-cve-json <keep> --attach`
-   — remediation-developer credits come from the *Remediation developer* body field
+6. `uv run --project <framework>/tools/<cve-tool>/generate-cve-json generate-cve-json <keep> --attach --report-json <scratch>/cve-report-<keep>.json`
+   — a report with any non-empty array (a merge can leave a field twice) goes through the [CVE JSON fallback](../issue-sync/outcomes/cve-json-fallback.md);
+   remediation-developer credits come from the *Remediation developer* body field
    (populated by `security-issue-sync` from the linked PR's author); no CLI flag needed.
    The regen output is the kept tracker's canonical JSON record.
    When the kept tracker already carries an allocated CVE ID, feed the record into