=== CoderVex Site Guardian – Update Monitoring & Error Diagnostics ===
Contributors: codervex
Tags: update monitor, error diagnostics, site health, monitoring, debugging
Requires at least: 6.6
Tested up to: 7.1
Requires PHP: 8.1
Stable tag: 1.3.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Track WordPress updates, investigate observed errors, monitor site health, and review local alerts and reports.

== Description ==

CoderVex Site Guardian – Update Monitoring & Error Diagnostics gives administrators a local, evidence-focused view of update activity, diagnostic findings, and WordPress scheduling health.

= Update Safety =

Record WordPress core, plugin, and theme updates observed while the plugin is active. Version details are displayed when WordPress makes them available. When a valid scan exists before an update and another scan completes afterward, Site Guardian records a factual comparison. A comparison indicates timing and changed findings; it does not prove that an update caused a problem and it does not perform rollback.

= WP Doctor =

Review persisted health findings and supported local PHP diagnostic events with observed conditions, timestamps, evidence, diagnostic limitations, and safe troubleshooting guidance. Possible causes are hypotheses based on available evidence, not confirmed root causes. WP Doctor never applies an automatic repair.

= Local Monitoring =

Review WP-Cron configuration, scheduled health-scan status, recorded diagnostic and update activity, and cached results from administrator-triggered WordPress core integrity checks. Core integrity uses official WordPress checksums when available and never restores files automatically.

= Health and reporting tools =

Run read-only health checks, review the stored Health Score and score coverage, open immutable scan history, inspect local alerts, view persisted report trends, export protected CSV data, and control scheduling and bounded retention from Settings.

== Important Limitations ==

* Site Guardian does not automatically repair findings or roll back WordPress updates.
* PHP diagnostic coverage is limited to supported events WordPress exposes while the plugin is active, including recovery events, shutdown fatal errors, and doing-it-wrong notices. Absence of a recorded event does not prove that no PHP error occurred.
* Local WP-Cron monitoring depends on activity inside this WordPress installation. It is not independent external uptime monitoring and cannot verify availability while the site or server is unreachable.
* The Free plugin has no remote monitoring service, cloud dashboard, external uptime checks, SSL or domain-expiry monitoring, synthetic form tests, email-delivery tests, or checkout monitoring.

The Free plugin operates independently. A separate optional add-on may extend documented APIs, but no existing Free feature requires it.

== Installation ==

1. Upload the `codervex-site-guardian` directory to `/wp-content/plugins/`, or install the release ZIP through Plugins > Add New.
2. Activate CoderVex Site Guardian.
3. Open Site Guardian in the WordPress administration menu.
4. Run a manual Health Scan to establish the first local baseline.

== Frequently Asked Questions ==

= Does the plugin send diagnostic data elsewhere? =

No diagnostic events, scan evidence, reports, or settings are sent to CoderVex or another monitoring service.

= Does it make any external requests? =

Only two bounded WordPress-related checks can make requests: the REST API health check requests this site's own WordPress REST endpoint, and an administrator-triggered core integrity check requests official checksums from `api.wordpress.org`. The checksum request sends the installed WordPress version and locale required by that service. It does not send stored diagnostics or the site URL.

= What diagnostic information is stored? =

The plugin stores bounded, redacted event summaries, relative component paths, timestamps, occurrence counts, and supported plugin or theme associations. It does not intentionally store raw stack traces, request bodies, cookies, credentials, or authorization headers.

= Does WP Doctor confirm root causes? =

No. Guidance is based on observed evidence and clearly states its limitations. Possible causes are diagnostic hypotheses.

= Can Site Guardian automatically repair a problem or roll back an update? =

No. Health checks and diagnostic guidance are read-only. Update Safety records observed updates and scan comparisons but does not restore files, repair configuration, or perform rollback.

= Is Local Monitoring an uptime-monitoring service? =

No. It reports locally persisted WordPress information such as WP-Cron scheduling, scheduled scans, diagnostic activity, update activity, and administrator-triggered core integrity results. It cannot independently check the site from an external location.

= Does WP Doctor capture every PHP error? =

No. Observation coverage is limited to supported events exposed to WordPress while Site Guardian is active. Private server logs may contain events that the plugin cannot observe.

= What happens on deactivation or uninstall? =

Deactivation clears scheduled hooks but preserves settings and historical data. Uninstall also preserves data unless an administrator previously enabled the explicit "Delete all plugin data on uninstall" setting.

= Does the Free plugin require the Pro add-on? =

No. All existing functionality remains in Free. The optional add-on skeleton contains no paid features, remote services, licensing, or payment code.

== Privacy ==

Site Guardian stores its scan, diagnostic, update, alert, report, schedule, and settings data in the site's WordPress database. Access is restricted to users with the plugin management capability. CSV exports exclude raw diagnostic evidence and apply spreadsheet-formula protection. Retention cleanup is opt-in and bounded. Diagnostic screens identify their observation coverage and limitations.

== Changelog ==

= 1.3.0 =
* Added the local monitoring overview and administrator-triggered WordPress core integrity checks.
* Added settings, site-time scheduled scans, reports, protected CSV exports, and opt-in retention.
* Added a privacy-conscious extension API and independent Pro add-on architecture.
* Improved diagnostic redaction, report validation, and release documentation.

= 1.2.0 =
* Added privacy-safe diagnostic event grouping, WordPress update tracking and scan comparison, and persistent local alerts.

= 1.1.2 =
* Added context-aware memory assessment, check-specific diagnostic guidance, and score-consistency validation.

= 1.1.1 =
* Refined diagnostic details, score transparency, local HTTPS handling, memory evidence, and immutable historical views.

= 1.1.0 =
* Added persisted read-only health scans, transparent scoring, scan history, dashboard summaries, and WP Doctor findings.

= 1.0.0 =
* Added the initial WordPress administration foundation.
