=== SSF SiteCare ===
Contributors: ssfllc
Tags: site health, maintenance, diagnostics, reports
Requires at least: 6.6
Tested up to: 6.6
Requires PHP: 8.1
Stable tag: 0.1.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Read-only local WordPress configuration reports and private JSON snapshots without API keys, passwords or remote connections.

== Description ==

SSF SiteCare helps an administrator review selected local configuration facts and export a small, structured snapshot. It complements WordPress Site Health with a focused format for manual agency reporting. Free works without AI, paid features, an external account or a hosted service.

* Administrator-only Tools page and authenticated JSON download.
* WordPress/PHP versions, configured HTTPS URL flag and hostname consistency.
* Search visibility setting, debug/display-error flags, PHP upload/memory limits and cron summary.
* Cached plugin/theme update counts with source check timestamps; missing information remains unknown.
* Plugin names, versions and active-state inventory.
* No passwords, account emails, absolute paths, database access details, customer records or cron arguments in its export.

This is a read-only configuration report, not a security scan, backup tool, mail test, uptime monitor, SEO score or repair engine. Configured HTTPS is the saved URL scheme, not a certificate/availability test. Cached update information can be stale. SSF plugin installation alone never proves operational success. Backup restores, mail delivery and uptime remain unknown.

The separate SSF SiteCare Pro add-on provides a private dashboard for manually imported snapshots, source timestamps, stale warnings, retained history, differences and CSV export. It does not remotely connect to or control sites. Premium implementation is not included in Free.

== Installation ==

1. Upload and activate the ssf-sitecare folder or ZIP.
2. As an administrator, open Tools → SSF SiteCare.
3. Review the report and its limits. Download JSON only when you want a point-in-time copy.
4. Review the exported site URL/name and software inventory before sharing it with anyone.

== Frequently Asked Questions ==

= Does it contact my websites, SSF or another API? =
No. This plugin reads local WordPress configuration and cached update transients. It makes no remote requests, sends no email, and collects no telemetry. WordPress itself retains its ordinary update behaviour.

= Is an unknown update count zero? =
No. Missing cache data is exported as null/unknown. A known zero comes only from an available cached update response. The report does not force a fresh update check.

= Does it repair HTTPS, scan malware or prove a successful backup? =
No. It reports the configured URL scheme and selected settings. Use appropriate operational checks for actual TLS, restore tests, mail receipt, uptime and security.

= What does it store? =
Free stores no report history. A downloaded JSON is a file under your control. The separate Pro add-on stores only manually imported, validated snapshots on the hub site. Neither package has a remote-management endpoint or credential store.

== Privacy ==

The private report includes public site URL/name, versions, selected flags/limits and installed plugin names/versions. It excludes login credentials, account emails, private records, database credentials and absolute paths. Do not publish administrative diagnostics publicly. There is no telemetry, AI processing, tracking, automatic email or service signup.

== Changelog ==

= 0.1.0 =
* Initial read-only local report and authenticated JSON export.
