[AntonV1211]

https://app.doboard.com/1/task/58453

[Copilot]

🟡 Changes recommended

Excluding ordinary GET requests without a recurring background wakeup can delay scheduled security work for hours.

1 open issue

• No recurring wakeup stalls plugin tasks on anonymous GET-only sites · New

What changed in this PR

This PR limits the security plugin’s cron workload to reduce its impact on visitor requests.

Changes:

• Restricts cron ticks to POST and WordPress cron requests, excluding remote calls.
• Runs one task per tick, prioritizing the most overdue.
• Preserves skipped tasks’ schedules for later ticks.

File	Description
security-malware-firewall.php	Applies request gating before running cron.
lib/​CleantalkSP/​SpbctWP/​Cron.php	Defines eligible requests and the one-task limit.
lib/​CleantalkSP/​Common/​Cron.php	Limits and orders due tasks while preserving deferred work.

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Cron recovery can stall, scanner errors can terminate background ticks, and wakeup authentication and concurrency handling need correction.

5 open issues

• Authenticate before consuming the wakeup cooldown · New
• Add local cron recovery when loopback dispatch fails · New
• Allow key-independent execution of maintenance tasks · New
• Atomically claim wakeups to prevent parallel dispatches · New
• Return scanner errors to cron instead of terminating execution · New

1 resolved since last review

• No recurring wakeup stalls plugin tasks on anonymous GET-only sites

_{Review effort: Balanced}