Yes. Both versions write to the same wp-reset_ option key namespace and create the same wp_wpr_snapshots table when snapshots are saved. Pro adds remote storage destinations as extra columns, which SleekView can chart alongside the local rows without any extra wiring.

Indirectly. The wp_wpr_snapshots table records the list of tables included in each snapshot, which signals which plugins added custom tables at snapshot time. Plugin lists themselves live inside the snapshot data, not on the row, so the chart layer reports counts rather than per-plugin names.

No. SleekView is a read-only dashboard layer. It queries the wp-reset option keys and wp_wpr_snapshots table but never calls the wp-reset action hooks that actually destroy data. All resets continue to run through the WP Reset UI or its WP-CLI commands.

Yes. SleekView views are capability-gated. A common setup limits WP Reset dashboards to a senior_qa or platform_engineer role and hides them from editors or contributors, so reset history and snapshot names stay scoped to the people who own the test environment.

Reads run against wp_options and the wp_wpr_snapshots table, both of which are small even on heavy QA installs. SleekView caches chart results between page loads so repeated dashboard views do not re-scan the option store on every refresh.

Each site renders its own dashboard out of the box. Cross-site aggregation requires a SleekView data source that joins wp-reset_history rows from multiple sites into a single table, usually backed by a custom collector or a shared analytics database.

Resets triggered through wp reset reset, wp reset delete and wp reset snapshots fire the same wp-reset- action hooks as the GUI, so they appear in wp-reset_history with the same shape. The chart layer cannot tell GUI from CLI on its own, but a separate trigger column can be added if your team annotates that on the hook.

Yes. The wp_wpr_snapshots data source supports CSV export from the table view, so QA leads can hand a row-level audit log to compliance reviewers without writing a single SQL query against the database.