v2.4.31

Fixed

• Aggregator: ServerRegistry::is_config_server() read Config::load_config('full'), but the aggregator plugin registers aggregator_servers in the extended option schema (newspack-event-aggregator.php), which causes load_config('full') to overlay the WP option event_logger_aggregator_servers onto the file defaults. Every WP-managed server therefore appeared as a "config-file server," tripping the immutability guards in remove() and update() — Remove produced a generic 500 "Failed to delete server." in the admin UI, and update() silently stripped all fields except enabled. Switched to Config::load_config_defaults() so only file-defined servers are flagged. Added a regression test that reproduces the schema-extension scenario. (newspack-event-aggregator/includes/class-server-registry.php, tests/unit/ServerRegistryTest.php)