<?php
/**
 * Background scan execution via WP-Cron.
 *
 * A full scan never runs as one request. miintg_schedule_scan()
 * creates a run row and schedules one wp_schedule_single_event per check,
 * staggered a few seconds apart. Each event calls exactly one check
 * (miintg_run_single_check()) and writes only its own detail
 * row, so a single request never does more than one check's work —
 * the scenario that risked PHP's max_execution_time on a cold manifest
 * cache is no longer possible, however many plugins or files a site has.
 *
 * @package MIINTG
 */

if ( ! defined( 'ABSPATH' ) ) {
	exit;
}

const MIINTG_CRON_HOOK = 'miintg_run_check';

add_action( MIINTG_CRON_HOOK, 'miintg_cron_run_check', 10, 2 );

/**
 * Creates a run and schedules its checks. Returns immediately — the
 * caller (admin AJAX handler or REST /scan) never waits on a check.
 *
 * @param array|null $checks  Subset of core,autoloaded,uploads,plugins,config,users.
 *                             Null/empty runs all six.
 * @param string     $trigger 'manual' | 'cron' | 'wp_cli' | 'rest'.
 * @param int|null   $user_id Triggering user id, if any.
 * @return int Run id.
 */
function miintg_schedule_scan( $checks = null, $trigger = 'manual', $user_id = null ) {
	$available = miintg_full_scan_available_checks();

	if ( empty( $checks ) ) {
		$checks = $available;
	} else {
		$checks = array_values( array_intersect( $available, $checks ) );
		if ( empty( $checks ) ) {
			$checks = $available;
		}
	}

	$run_id = miintg_db_create_run( $checks, $trigger, $user_id );

	foreach ( array_values( $checks ) as $i => $check ) {
		wp_schedule_single_event(
			time() + ( $i * 5 ),
			MIINTG_CRON_HOOK,
			array( $run_id, $check )
		);
	}

	// Nudges WP-Cron to fire on this request too, for sites with little
	// traffic between events. Harmless if it's already running.
	if ( ! defined( 'DOING_CRON' ) ) {
		spawn_cron();
	}

	return $run_id;
}

/**
 * WP-Cron callback: runs exactly one check and records it. Never lets
 * an exception escape (a bad plugin manifest fetch, a filesystem error)
 * without marking that check's row 'error' — otherwise a run could sit
 * "running" forever with the admin UI showing perpetual progress.
 *
 * @param int    $run_id Run id.
 * @param string $check  Check name.
 */
function miintg_cron_run_check( $run_id, $check ) {
	try {
		$result = miintg_run_single_check( $check );

		if ( null === $result ) {
			miintg_db_record_check( $run_id, $check, null, 'error' );
			return;
		}

		$status = empty( $result['ok'] ) ? 'error' : 'complete';
		miintg_db_record_check( $run_id, $check, $result, $status );
	} catch ( Throwable $e ) {
		miintg_db_record_check(
			$run_id,
			$check,
			array( 'ok' => false, 'error' => $e->getMessage() ),
			'error'
		);
	}
}

/**
 * Clears any scan-related cron events on deactivation so a stale event
 * doesn't fire after the plugin is off.
 */
function miintg_scanner_deactivate() {
	$timestamp = wp_next_scheduled( MIINTG_CRON_HOOK );
	while ( $timestamp ) {
		wp_unschedule_event( $timestamp, MIINTG_CRON_HOOK );
		$timestamp = wp_next_scheduled( MIINTG_CRON_HOOK );
	}
}