=== TaxoCommerce System Check ===
Contributors: davidperezmartorell
Tags: diagnostics, security, performance, maintenance, monitoring
Requires at least: 6.2
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 0.2.15
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Server, WordPress and plugin diagnostics with administrator-controlled reports and local checks.

== Description ==

TaxoCommerce System Check provides a standalone administration entry for diagnostics, and can integrate its menu with TaxoCommerce Core when installed.

* WordPress, PHP and hosting/system status screens.
* Plugin validation and local PHP checks.
* Optional HTTP URL audit of site content, when started explicitly by an administrator.
* On-demand diagnostic reports and optional administrator-configured notification emails.
* Dedicated bounded processing for longer URL checks. Neither external GitHub runners nor artificial traffic generation are necessary.
* Historical administration URLs are kept for compatibility.

Some historical diagnostic callbacks are reused when the old TaxoCommerce SEO plugin is still present. Standalone behavior must be tested with the old plugin disabled before publication.

== Installation ==

1. Install and activate TaxoCommerce System Check.
2. Open System Check in WordPress administration (or the Core submenu if Core is installed).
3. Run a system or plugin check and review the findings.
4. Start URL audits or enable scheduled email reports only when you intend to use them.

== Privacy ==

System diagnostics can include server configuration, URLs and error details. Treat exported results as potentially sensitive. No diagnostic report should be sent to a developer automatically: optional email reports must be explicitly enabled and target an address chosen by the site administrator. HTTP checks make requests to the site's specified URLs and must be used within hosting limits.

== Changelog ==

= 0.2.15 =
* Pestaña homogénea «Autocheck» y descarga JSON del último informe, por usuario y sitio, con control de permisos y nonce.

= 0.2.14 =
* Cabecera administrativa unificada de TaxoCommerce con nombre, icono y versión.
* Estilos propios sin Core, funciones y permisos intactos.


= 0.2.13 =
* Bind both Action Scheduler table identifiers using %i when retrieving the highest-volume pending action group.
* Add source-regression checks to prevent restoring interpolated SQL and synchronize the standalone Auto Test version.
* Preserve live diagnostics and all existing historical callbacks; production publication requires separate approval.

= 0.2.12 =
* Fix remaining Plugin Check SQL preparation findings by binding canonical table identifiers and preserving bound user values in billing, semantic checks, health scans and external images.
* Document narrowly scoped live database diagnostics without introducing stale caches or changing public legacy SEO APIs.
* Add regression assertions and validate installable ZIP with WordPress Plugin Check before release.


= 0.2.11 =
* Prepare the canonical table identifiers in all eight MySQL EXPLAIN diagnostics with the WordPress 6.2+ %i placeholder.
* Extend offline SQL and malformed-input safety tests to PHP 7.4 and PHP 8.4; ignore array-valued HTTP audit filters and actions without changing valid requests or legacy public APIs.
* This patch does not claim to resolve all remaining WordPress Plugin Check warnings; the compatibility and direct-database warnings continue to be tracked in GitHub issue #1958.


= 0.2.9 =
* Refresh WordPress.org metadata for the standalone System Check package.
* Confirm current gettext calls use the standalone text domain and Action Scheduler table identifiers use prepared `%i` placeholders.

= 0.2.8 =
* Standalone system and plugin diagnostics with compatibility routes.
* Local PHP checks and optional bounded HTTP URL audits.
* Administrator-controlled reports and notifications.

== Historical origins (monolith; not standalone releases) ==
* Legacy origin: server diagnostics, plugin validation and HTTP/URL checks existed under TaxoCommerce SEO administration; the monolith's release numbers are not standalone System Check versions.
* The old validation panel mixed site status, plugin-specific checks and URL/HTTP observations; its historical outputs were not automatically proof that newer modules had passed.
* During modularisation System Check was isolated from SEO_SYSTEM_* globals and constants to prevent collisions with the still-installed monolith.
* Standalone diagnostics distinguished the active plugin modules from installed but inactive extensions and retained administrator-controlled bounded scans and reports.
* Later WordPress.org work corrected text-domain usage and prepared SQL identifiers; the historical original checker remained distinct from each plugin's own Auto Test.
