Can GIMP automatically disable plugins that fail to load after a version upgrade?

Goal

Keep GIMP usable after a major version upgrade when third‑party plugins may no longer be compatible.

Constraints and uncertainty

• GIMP scans the user and system plug‑in directories at startup, records each plugin’s menu entry, and loads them on demand via the procedural database.
• While the plugin API is version‑agnostic, binary compatibility is not guaranteed between major releases, so a plugin built for GIMP 2.10 may fail to load or misbehave in GIMP 3.0.
• GIMP logs load‑time errors to the console but does not automatically disable a plugin that fails, leaving broken menu items until the user removes them manually.
• There is no built‑in compatibility checker or rollback mechanism; users must test each plugin individually after an upgrade.

Open questions

1. Which plugin metadata (e.g., embedded version tag, build information) could GIMP reliably read to decide whether to load a plugin after an upgrade?
2. Does GIMP expose any hook or signal that an external script could use to disable a plugin after a load failure is detected?
3. Would a safe‑mode that bypasses the plug‑in folder after a configurable number of consecutive load failures be a viable recovery strategy?