# M7tawa Impact Monitor — Older Changelog

Older release history moved from readme.txt to keep the WordPress.org readme concise.

= 2.7.0 =
* Added read-only Residue Monitor after extension deletion.
* Reports observed and likely leftover tables, options, transients, cron hooks, roles, post meta keys, and user meta keys.
* Added post-removal residue panel to Lifecycle Timeline with confidence labels and manual Recheck Residue.
* No residue is deleted or modified automatically.

= 2.6.0 =
* Add two primary admin tabs: Impact Monitor (default) and How it works.
* Add Update Watch with a dedicated pre-update snapshot when WordPress provides update context.
* Compare Before update → After update for Version, Current Impact Score, Autoload, Options, Cron hooks, REST routes, and Database tables.
* Show a clear delta for each update metric and explain the measurable changes caused around that update event.
* Flag batch-update attribution limits instead of overstating certainty.
* Preserve Lifecycle Timeline, measured-first profiles, Impact Score history, and all v2.5.0 monitoring behavior.

= 2.5.0 =
* Added per-extension Lifecycle Timeline with install, activation, reactivation, update, deactivation, and deletion events.
* Added lifecycle summary with Current Score, Peak Score, event count, first monitored, and last monitored dates.
* Added lifecycle event filtering and version-before/version-after display.
* Added lifecycle links to extension profiles and retained history for removed extensions.
* Added monitoring for plugin installation and successful deletion events.

= 2.4.0 =
* Added measured-impact-first as the default extension profile order so scored extensions appear before partial, observed-only, and baseline-only profiles.
* Added a measured-extension summary and new Recently observed sort option.
* Replaced the technical version-2 explanation with a benefit-focused How it works banner in a dismissible gold panel.
* Saved the help-banner visibility per administrator and added a Show help banner again control.
* Changed successful baseline and history actions to one-time green flash notices that disappear after navigation or interaction.
* Replaced the plain Observed/Detected sentence with a colored confidence guide.
* Simplified the Impact Score explanation and moved secondary details into a collapsible How scoring works control.
* Kept monitoring and scoring logic read-only and unchanged.

= 2.3.0 =
* Added Current and Peak Impact Score so the present measured footprint is clearly separated from the highest observed score.
* Added per-extension score history and a Rising, Falling, Stable, or New history trend indicator.
* Added visible Observed or Partial confidence badges beside profile scores.
* Added Top impact contributors using the transparent Database, Runtime, WordPress Integration, and Footprint Breadth components.
* Added Attention Flags for measurable items worth reviewing, including frequent cron schedules, elevated known autoload, large attributed database footprint, many tables, and many options.
* Added signed Event Impact Delta to score transitions.
* Added dedicated before/after update comparison and a notable-change notice when an update shifts Impact Score by 10 points or more.
* Kept all scoring explanatory and read-only; no action is taken automatically.

= 2.2.0 =
* Added a transparent 0–100 Impact Score with Low, Moderate, High, and Very High technical-impact levels.
* Added score breakdowns for Database, Runtime, WordPress Integration, and Footprint Breadth.
* Added score confidence: activation-observed profiles receive observed confidence; incomplete histories are labeled Partial; baseline-only extensions remain unscored.
* Added before/after Impact Score transitions to observed events and updates.
* Added impact-level filtering and highest/lowest score sorting.
* Added metadata for added/removed options and cron recurrence intervals to improve scoring without storing option values.
* Excluded WordPress's active_plugins option from inflating extension impact scores.
* Added explanatory guidance while keeping all actions read-only and manual.

= 2.1.0 =
* Added search, status filters, monitoring-state filters, and 12-item pagination for extension impact profiles.
* Organized detailed event evidence into collapsible categories for database, cron, content types, REST API, options, roles, and autoload.
* Improved option metadata comparisons with clearer before-and-after size and autoload-state presentation.
* Kept monitoring logic and read-only behavior unchanged.

= 2.0.0 =
* Added detailed change lists for tables, cron hooks, post types, taxonomies, and REST routes.
* Added metadata-only option tracking for added, removed, resized, and autoload-state changes.
* Added role and capability difference tracking.
* Added extension impact profiles for all installed extensions.
* Added version transition details for monitored events when available.
* Added version 2 baseline schema detection while preserving v1.x history.
* Removed bundled local language files; repository translations can be handled by WordPress.org.

= 1.0.2 =
* Removed the discouraged manual load_plugin_textdomain() call.
* Improved extension-name resolution.

= 1.0.1 =
* Renamed to M7tawa Impact Monitor and changed the slug to m7tawa-impact-monitor.
* Added friendly extension names and clearer confidence labels.
* Strengthened nonce handling and corrected database-query handling.

= 1.0.0 =
* Initial test release.
