=== PHM Health Monitor ===
Contributors: maor40
Tags: performance, plugins, speed, diagnostics, monitoring
Requires at least: 5.8
Tested up to: 6.9
Requires PHP: 7.4
Stable tag: 1.1.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Find which plugins impact your WordPress frontend performance. One click, clear results, exportable reports.

== Description ==

PHM Health Monitor (PHM) runs a controlled frontend scan and attributes timing, assets, and (when available) database signals to active plugins. Results are shown in Tools -> PHM - Plugin Benchmark with scores, trends, and a Markdown export for support tickets.

**Highlights**

* One-click scan from the WordPress admin
* Per-plugin timing and asset footprint (CSS/JS)
* Category-aware diagnostics with benchmark context (built-in + optional external dataset)
* Stability and trend signals where history exists
* Optional daily scheduled scans when allowed by your plan
* Clear Cache integrations with safe fallbacks (plan limits apply on Free)

**Important**

* Metrics depend on the page URL scanned, active theme, caching, and hosting. Run more than one scan before major decisions.
* A “partial” scan means some hooks or data could not be fully captured; PHM explains the reason when possible and keeps the last good scan when applicable.
* PHM includes cloud-connected features for plan validation, usage counters, license management, and support-center sync.
* Core scan analysis is performed in your WordPress admin. Some service-dependent flows require PHM Cloud availability.

== Installation ==

1. Upload the plugin folder to /wp-content/plugins/phm-health-monitor/ or install the ZIP from Plugins -> Add New.
2. Activate PHM Health Monitor through the Plugins menu.
3. Open Tools -> PHM - Plugin Benchmark and click Scan Now.

Optional: place `data/plugin_benchmarks.json` for extended external benchmark coverage (see `data/plugin_benchmarks.example.json`).

== Frequently Asked Questions ==

= Does this replace a full APM or server profiler? =

No. PHM focuses on practical WordPress plugin attribution for a single frontend request path, not full infrastructure tracing.

= Will this slow down my site? =

Scans run from the admin and use a short loopback-style measurement. Do not run scans continuously on production during peak traffic.

= What data leaves my site? =

Plan validation and related cloud features use your configured PHM cloud session. Review your privacy policy and the in-plugin notices for details.

== External Services ==

PHM uses external services for specific cloud features.

1. PHM Cloud API (`https://api.pluginhealthmonitor.com/v1`)
* Purpose: site enrollment, plan validation, usage counters, and support ticket sync.
* Data sent can include: site URL, plugin version, WordPress/PHP versions, scan usage counters, support request payloads, and related account/site identifiers.

2. PHM Website / Customer Portal (`https://pluginhealthmonitor.com`)
* Purpose: account management, customer portal access, and billing-related flows.

3. Paddle (`https://paddle.com`)
* Purpose: payment processing and subscription management for paid plans.
* Paddle acts as Merchant of Record for purchases.

Service legal documents:
* Terms of Service: `https://pluginhealthmonitor.com/terms`
* Privacy Policy: `https://pluginhealthmonitor.com/privacy`
* Refund Policy: `https://pluginhealthmonitor.com/refund`

== Screenshots ==

1. Dashboard summary with scan actions and environment context.
2. Per-plugin results with expandable details and export.

== Changelog ==

= 1.1.0 =
* Rebased release package from the production 1.0.11 build and finalized as 1.1.0.
* Refreshed release metadata and distribution ZIP naming for WordPress upload flow.

= 1.0.11 =
* Sync production-hardening: partial scan reason metadata, smart scan retry, dynamic hook wrap cap filter, and last-good-scan preservation.
* Admin UX: expanded tooltips, timing trend indicators, and clearer partial scan messaging.
* QA helpers: LocalWP PowerShell scripts (`qa-localwp.ps1`, log collection, multi-site deploy).
* Remove stray debug file logging paths from core admin flows.

= 1.0.10 =
* Cloud enrollment and heartbeat reliability improvements.
* Benchmark-calibrated analysis and query attribution groundwork.

== Upgrade Notice ==

= 1.1.0 =
This release repackages the latest production-ready build under version 1.1.0 for clean upgrades and distribution.
