<?php
/**
 * The services free's boot hands the Pro add-on.
 *
 * @package ActivityLog404
 */

namespace ActivityLog404;

defined( 'ABSPATH' ) || exit;

/**
 * Everything the Pro add-on's boot needs from free's boot, handed over on the
 * `ops404_activity_log_booted` action. A value object, not a service locator:
 * the add-on receives exactly these four, constructed once by
 * `Plugin::boot()`, and never reaches back into free for anything else.
 *
 * Three of the four are closures rather than objects, and that is this
 * plugin's shape rather than a preference. Every free class the add-on needs
 * -- `ActivityLog`, `EventLogger`, `Database` -- is entirely static; there is
 * no instance to hand over, and manufacturing one purely to carry static
 * calls would be indirection that lies about how free works. A closure
 * bound at free's own boot says exactly what it is: the one call the add-on
 * is allowed to make, already resolved against free's own classes.
 *
 * The fourth, `$table`, is a plain string because the two Pro surfaces that
 * need the log at scale -- the monthly archive's month-range SELECT and its
 * row deletion -- are bulk SQL that no paged `get_events()` reader can
 * express. Handing over the resolved, `$wpdb->prefix`-ed name keeps the add-on
 * from re-deriving it (and from getting the prefix wrong on multisite).
 *
 * Public promoted properties, NOT `readonly`: the plugin's PHP floor is 8.0.
 */
final class ProServices {

	/**
	 * @param \Closure(array<string, mixed>): array<int, array<string, mixed>>                  $query    One page of events; `ActivityLog::get_events()`'s arguments and row shape verbatim.
	 * @param string                                                                           $table    The prefixed activity-log table name.
	 * @param \Closure(): array{retention_days: int, store_full_ips: bool, ip_source: string}   $settings The free plugin's effective settings, read fresh on every call.
	 * @param \Closure(string, string, string|null, int|null, array<string, mixed>|null, int|null=): void $log Write an event to the log; `EventLogger::log()`'s parameters. The sixth, who acted, was added (optional) by the login-alerts slice.
	 */
	public function __construct(
		public \Closure $query,
		public string $table,
		public \Closure $settings,
		public \Closure $log
	) {
	}
}