<?php
/**
 * Fired when the plugin is uninstalled.
 *
 * Behavior (Feature 012 — preserve-by-default):
 *
 *   Reads the `acrossai_mcp_uninstall_delete_data` option (int 0/1, default 0).
 *   - 0 (default): preserves ALL plugin data on uninstall — no tables dropped,
 *     no options deleted, no scheduled hooks cleared. This matches the WP.org
 *     plugin guideline #5 (uninstall must not destroy data unless the operator
 *     explicitly opts in). This is a BEHAVIOR CHANGE from pre-Feature-012, where
 *     `acrossai_mcp_oauth_tokens` + `acrossai_mcp_oauth_audit` were dropped
 *     unconditionally.
 *   - 1 (destructive): drops every plugin-owned wp_acrossai_mcp_* table
 *     (including the orphaned pre-F040 OAuth tables — see F083 note below),
 *     deletes every `acrossai_mcp_*` option via LIKE-sweep (excluding the
 *     companion-owned `acrossai_mcp_connector_%` namespace), and clears the
 *     OAuth cleanup cron.
 *     Operators opt in via the "Delete all data on uninstall" checkbox on the
 *     MCP tab of the shared AcrossAI Settings page (see
 *     admin/Partials/SettingsMenu.php).
 *
 * @link       https://github.com/WPBoilerplate/acrossai-mcp-manager
 * @since      0.0.1
 *
 * @package    AcrossAI_MCP_Manager
 */

// If uninstall not called from WordPress, then exit.
if ( ! defined( 'WP_UNINSTALL_PLUGIN' ) ) {
	exit;
}

// Preserve-by-default gate. Operators opt into destructive teardown by
// ticking the "Delete all data on uninstall" checkbox on the MCP tab.
if ( 1 !== (int) get_option( 'acrossai_mcp_uninstall_delete_data', 0 ) ) {
	return;
}

global $wpdb;

// Drop all four plugin tables. Table names are derived from $wpdb->prefix +
// hardcoded stems (no user input reaches SQL). Uses the `%i` identifier
// placeholder (WordPress 6.2+) so $wpdb->prepare() escapes the table name
// safely and no phpcs:ignore is needed.
// Feature 015 — Access Control v2 (FR-012 / FR-013). Purge the plugin's
// namespace via the vendor RuleQuery BEFORE the raw DROP so BerlinDB
// invalidates its cache for the namespace. class_exists guards against the
// "vendor package uninstalled before this plugin" edge case (US5 scenario 3).
if ( class_exists( '\WPBoilerplate\AccessControl\Database\Rule\RuleQuery' ) ) {
	$rule_query = new \WPBoilerplate\AccessControl\Database\Rule\RuleQuery( 'mcp' );
	if ( method_exists( $rule_query, 'purge_namespace' ) ) {
		$rule_query->purge_namespace( 'acrossai-mcp-manager' );
	}
}

// Feature 040 moved OAuth ownership to the companion plugin. The companion
// (acrossai-pro) CREATES ITS OWN fresh tables under the
// `acrossai_pro_mcp_oauth_*` / `acrossai_pro_mcp_connector_approved_users`
// namespace — it never reads, migrates, renames, or drops the old names
// (verified: zero old-table-name references in its codebase; its
// uninstall.php drops only the `acrossai_pro_mcp_*` names). That leaves the
// four OLD-name tables (`wp_acrossai_mcp_oauth_clients`, `_oauth_tokens`,
// `_oauth_auth_codes`, `wp_acrossai_mcp_connector_approved_users`) created
// by pre-F040 builds of THIS plugin abandoned in place with no owner. F083
// restores them to this drop list as an idempotent safety net: `DROP TABLE
// IF EXISTS` no-ops on installs that never had them, and cannot collide
// with the companion's live data because the companion's table names
// differ. (The companion still OWNS the `acrossai_mcp_connector_%`
// *option* namespace — the LIKE-sweep exclusion below stays per A20.)
$tables = array(
	$wpdb->prefix . 'acrossai_mcp_servers',
	$wpdb->prefix . 'acrossai_mcp_cli_auth_logs',
	$wpdb->prefix . 'mcp_access_control',            // F015 AC rule table (TABLE_SLUG = 'mcp').
	$wpdb->prefix . 'acrossai_mcp_server_abilities', // F017 per-server ability overrides.
	$wpdb->prefix . 'acrossai_mcp_server_tools',     // F020 per-server tool selection.
	$wpdb->prefix . 'acrossai_mcp_servers_meta',     // F037 MCPServerMeta — per-server key/value settings (Embeds tab, etc).
	// F083 — orphans from pre-F040 builds (OAuth subsystem now lives in
	// acrossai-pro under different table names). See comment above.
	$wpdb->prefix . 'acrossai_mcp_oauth_clients',
	$wpdb->prefix . 'acrossai_mcp_oauth_tokens',
	$wpdb->prefix . 'acrossai_mcp_oauth_auth_codes',
	$wpdb->prefix . 'acrossai_mcp_connector_approved_users',
);
foreach ( $tables as $table ) {
	// phpcs:ignore WordPress.DB.DirectDatabaseQuery.DirectQuery, WordPress.DB.DirectDatabaseQuery.NoCaching, WordPress.DB.DirectDatabaseQuery.SchemaChange
	$wpdb->query( $wpdb->prepare( 'DROP TABLE IF EXISTS %i', $table ) );
}

// Feature 015 — delete the vendor-owned schema version option. The
// `acrossai_mcp_*` LIKE-sweep below does NOT match `wpb_ac_mcp_*`, so
// the vendor's version tracking option must be cleaned up explicitly.
delete_option( 'wpb_ac_mcp_db_version' );

// Delete every `acrossai_mcp_*` option EXCEPT `acrossai_mcp_connector_%`,
// which the companion plugin (acrossai-ai-connectors) now owns per Feature 040.
$options = $wpdb->get_col(
	// phpcs:ignore WordPress.DB.DirectDatabaseQuery.DirectQuery, WordPress.DB.DirectDatabaseQuery.NoCaching
	$wpdb->prepare(
		"SELECT option_name FROM {$wpdb->options} WHERE option_name LIKE %s AND option_name NOT LIKE %s",
		'acrossai_mcp_%',
		'acrossai_mcp_connector_%'
	)
);
if ( is_array( $options ) ) {
	foreach ( $options as $option_name ) {
		delete_option( $option_name );
	}
}