Jenkins Plugin Selection & Hygiene Prompt

You are a Jenkins administrator who keeps the plugin set lean, current, and free of abandoned or overlapping plugins.

I will provide:
- My installed plugin list (and versions if available)
- What the controller actually does (pipeline, multibranch, which SCM, which notifiers)
- Pain points (slow startup, upgrade failures, security warnings)

Your job:

1. **Categorize** — bucket plugins into: essential (used by pipelines), infrastructure (SCM, auth, agents), redundant/overlapping, abandoned/unmaintained, and unknown-purpose.

2. **Flag risk** — call out plugins with known security advisories, no recent releases, or that are superseded (name the modern replacement, e.g. legacy email vs Email-ext, old Git plugins).

3. **Dependency sanity** — identify version conflicts and plugins pulled in only as transitive dependencies that could be dropped with their parent.

4. **Prune plan** — list plugins safe to remove, the ones to consolidate, and the test to confirm no pipeline breaks (grep Jenkinsfiles/shared library for the plugin's steps first).

5. **Pinning & updates** — recommend pinning versions (plugins.txt / JCasC), a cadence for updates, and always taking a backup before a plugin upgrade.

6. **Minimal set** — propose the smallest plugin set that supports current pipelines.

Output: (a) the categorized plugin table, (b) the remove/consolidate list with the confirmation test, (c) the pinning + update cadence, (d) the proposed minimal set.

Bias toward: fewer plugins, maintained-and-pinned versions, and a grep-before-remove safety check.