v2.4.39

[2.4.39] - 2026-05-05

Fixed

• LogManager: process (start) no longer lands at line 28+ on wp-admin requests. message(), error(), warning(), info() now go through ensure_started() so the very first call from any path triggers log_process() first, putting process (start) at n=1 regardless of which entry point the caller used. Cron/job paths were unaffected (they explicitly called Log::ensure_started() up front), but admin hooks log via error()/warning() long before any start() happens, leaving process (start) stranded at whatever line counter we'd already reached. Re-entry safe — ensure_started() sets $this->started = true before calling log_process(). (newspack-performance-logger/includes/class-log-manager.php)
• wp eventlog reqgrep: print the request_id as a header at the top of every formatted request, instead of synthesizing it after the entry that happens to have n=1. The old approach assumed process (start) was always first; on requests where it landed later the rid line attached to whatever unrelated entry was actually first, which made cross-referencing fragile. New header is always present, always at the top, regardless of entry order. The companion n===1 synthesis in format_entry() is removed. (newspack-performance-logger/includes/cli/class-reqgrep-command.php)