=== Autonomous Recovery & Safe Updates ===
Contributors: dhruvalbhansali
Tags: recovery, rollback, updates, maintenance, monitoring
Requires at least: 6.0
Tested up to: 6.8
Requires PHP: 7.4
Stable tag: 0.1.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Reduce the risk of broken updates by preparing rollback points, logging incidents, and keeping recovery tools available.

== Description ==

Autonomous Recovery & Safe Updates helps site owners reduce downtime from plugin and theme failures.

Included in the WordPress plugin:

* Snapshot-based rollback preparation
* File-aware change tracking and rollback support
* Built-in file manager for browsing, editing, and rolling back recent file changes
* Safer one-by-one plugin auto updates
* Recovery-focused activity logging
* A WordPress-side incident ledger with exports
* Recovery diagnostics and incident reporting tools
* Optional SaaS connection for remote orchestration

External SaaS communication is opt-in. No site registration or health telemetry is sent until the site owner explicitly enables it in the plugin settings.

== Installation ==

1. Upload the plugin to `/wp-content/plugins/`.
2. Activate it from the `Plugins` screen.
3. Open the `Recovery` menu in wp-admin.
4. Review local recovery settings.
5. If you want to use the external SaaS service, enter the endpoint and explicitly enable the SaaS opt-in checkbox.

== Frequently Asked Questions ==

= Does this plugin require the external SaaS service? =

No. The WordPress plugin can still manage local snapshots, rollback history, incident visibility, and diagnostics without the SaaS service.

= Where does the file manager fit in? =

The file manager belongs to the same recovery suite and works with the local recovery engine so edited files can be snapshotted, compared, and rolled back before broader plugin or theme action is needed.

= Does the plugin send data automatically? =

No. External SaaS communication is disabled by default and requires explicit opt-in from the site owner.

= What happens if SaaS credits run out? =

Nothing on the site is blocked. Local recovery, file snapshots, and rollback continue to work. SaaS credits only affect optional remote orchestration and hosted services.

= What happens during plugin auto updates? =

The plugin updates one plugin at a time, checks the site after each update, and keeps rollback information available if something goes wrong.

== Changelog ==

= 0.1.0 =

* Initial public release
* Snapshot and rollback groundwork
* Incident logging and incident ledger
* Safer plugin auto-update workflow
* Optional SaaS connectivity with explicit opt-in
