=== Plugin Removal Impact Analysis ===
Tags: plugin audit, plugin dependencies, shortcodes, database cleanup, site health
Requires at least: 6.4
Tested up to: 7.0
Stable tag: 1.0.1
Requires PHP: 7.4
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

See what may break, stop, be deleted, or remain before removing a WordPress plugin.

== Description ==

Plugin Removal Impact Analysis answers one question:

**What exactly will break or be left behind if I remove this plugin?**

Choose an installed plugin and run a read-only scan. The result starts with a simple **Impact Meter from 1 to 10**, a plain-language answer, and a short recommendation.

* **Green (1–3):** low detected impact.
* **Yellow (4–6):** review or cleanup is needed.
* **Red (7–10):** higher-priority potential impact was detected.

Each finding stays concise. Open **What this means** to see what could be affected, what the artifact is, what remains after removal, what to do, and how confident the scanner is. Stored-data evidence also explains each artifact type and whether cleanup is necessary.

The scan can inspect:

* Blocks and shortcodes stored in posts, pages, templates, reusable blocks, page-builder data, and core widget content.
* Legacy widgets, custom post types, taxonomies, scheduled cron events, and Action Scheduler jobs.
* REST routes, AJAX actions, block patterns, block variations, and outbound service calls detected in source.
* Plugin options, transients, metadata, roles, upload folders, and custom database tables.
* Declared plugin dependencies and matching references in active theme, must-use plugin, drop-in, and plugin code.
* Uninstall cleanup code to distinguish data that may be deleted from data likely to remain.

The plugin never deactivates, deletes, edits, or replaces anything. It does not send scanned site data to an external service.

This is an evidence-based analysis, not a guarantee. Dynamically generated, encrypted, remote, or unusual server-side code can hide dependencies. Large scans are deliberately bounded and clearly marked when coverage is incomplete.

== Installation ==

1. Upload the `plugin-removal-impact-analysis` folder to `/wp-content/plugins/`, or install the ZIP through **Plugins > Add New > Upload Plugin**.
2. Activate **Plugin Removal Impact Analysis**.
3. Open **Tools > Plugin Impact**.
4. Choose a plugin and click **Scan impact**.

A **Removal impact** link is also added beside each installed plugin.

== Frequently Asked Questions ==

= Does this plugin deactivate or delete anything? =

No. The scan is read-only. It does not modify the selected plugin, site content, settings, schedules, files, or database tables.

= Does a green score guarantee removal is safe? =

No scanner can guarantee that. Green means no meaningful impact was detected in the areas successfully inspected. Review the coverage and limits before removal, and take a backup first.

= What is the difference between deactivation and deletion? =

Deactivation stops a plugin from running. Deletion can also execute the plugin's uninstall cleanup code. The report separates operational breakage, possible deletion, and leftovers.

= Why can a scan be yellow when no direct breakage was found? =

Yellow can mean the scan found review items, leftovers, endpoints, scheduled work, or incomplete coverage. The top answer explains which one applies.

= Does it support multisite? =

It runs on the current site. If the selected plugin is network-active, the report warns that other sites in the network must also be checked.

= Does it scan plugin source code? =

Yes, within strict file-count and file-size limits. Vendor, node_modules, test, language, and cache directories are excluded to reduce noise and resource use. This limitation is shown in scan coverage when applicable.

= Where is scan data stored? =

Temporary progress is stored locally as expiring WordPress transients. The current administrator's latest report is stored in user metadata so the result can be reopened. Uninstalling this analyzer removes its temporary state and reports only.

== Changelog ==

= 1.0.1 =
* Reduced the title and result typography for a calmer WordPress admin presentation.
* Reframed red results as higher-priority potential impact rather than guaranteed failure.
* Added plain-language explanations of what could be affected, what each artifact is, what remains after removal, and how to handle cleanup safely.
* Added item-level descriptions and cautious cleanup notes for stored data.
* Added confidence context to every built-in finding.
* Improved top-answer and recommendation language while preserving the core removal question.

= 1.0.0 =
* Initial public release.
* Added the 1–10 Impact Meter and red/yellow/green result model.
* Added resumable, cancellable, read-only scanning.
* Added content, operations, data, dependency, active-code, and uninstall-impact analysis.
* Added bounded-scan warnings, coverage details, keyboard support, responsive layouts, and reduced-motion support.
