<?php
/**
 * Commerce Link Builder uninstall handler.
 *
 * This file is executed by WordPress when the plugin is deleted from the
 * Plugins screen. It MUST only be reached via the WordPress uninstall
 * lifecycle; direct access is blocked by the WP_UNINSTALL_PLUGIN guard.
 *
 * Real uninstall logic (table drops, option cleanup, scheduled event
 * removal, credential wipe, etc.) will be added in a later slice when
 * the corresponding subsystems land. See:
 *   - specifications/database-schema.md
 *   - specifications/security-and-compliance.md
 *   - architecture-decision-records/0021-adopt-custom-sync-jobs-table-over-action-scheduler.md
 *
 * Until then this file intentionally performs no destructive action so
 * that accidental deletion during Phase 0 / Phase 1 does not strand data.
 *
 * @package CommerceLinkBuilder
 */

declare(strict_types=1);

// Exit if not called from the WordPress uninstall lifecycle.
if ( ! defined( 'WP_UNINSTALL_PLUGIN' ) ) {
	exit;
}

// Extra belt-and-braces guard: ABSPATH must also be defined in a real
// WordPress context. Without it we refuse to proceed.
if ( ! defined( 'ABSPATH' ) ) {
	exit;
}

/*
 * Intentionally empty.
 *
 * Populated in a dedicated slice once the following are decided and
 * implemented:
 *   - clb_* option / transient keys to delete
 *   - clb_* custom tables to drop (gated by an explicit "purge on uninstall"
 *     site option; default is to preserve data)
 *   - clb_* cron / scheduled jobs to unschedule
 *   - stored credentials / secrets to wipe
 *   - multisite iteration (switch_to_blog loop) when network-activated
 */
