Respect doing_cron transient in wp cron event run --due-now

[Copilot]

• Explore codebase and understand the issue
• Modify run() in src/Cron_Event_Command.php to check/set/delete the doing_cron transient when --due-now is used
• Add Behat test in features/cron-event.feature covering the transient lock check
• Use standard doing_cron transient with plain numeric microtime value (same format as WordPress core)
• Fix CI failure: add DISABLE_WP_CRON true at the start of cron.feature:309 to prevent spawn_cron() from setting doing_cron between test steps
• Pass $lock_timeout as TTL to set_transient() so lock self-expires on unexpected termination
• Store lock value; only delete transient if it still matches our value (prevents wiping another process's lock)
• All static checks pass (lint, phpcs, phpstan)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>wp cron event run --due-now doesn't respect doing_cron transient</issue_title>
<issue_description>I use wp cron event run --due-now as my production cron. Every 5 minutes. But it's a heavy cron. Sometimes it takes more then 5 minutes. When that happens some events get executed twice. Mostly sending emails.

I would suggest a --no-doubles flag or something like that to prevent the cron from doing hooks twice.

When the flag is set, wp-cli should check for the doing_cron transient like core does. And set it if it's starting. Like core does.

Relevant core code

Why is it doing things twice

At the start of a cron all tasks are gathered with _get_cron_array, events get deleted once the start. And the remaing cron array is still executed. And still in the DB list So after 5 minutes the new cron get also does a _get_cron_array and will get all events that the first cron also is still handling (and deleting as it goes).</issue_description>

<agent_instructions>See previous attempts at https://gist.github.com/danielbachhuber/e76c5c5e1479c385863cc86f5f21eb87 and https://gist.github.com/danielbachhuber/800870993ce975f7e775219180cc37fa</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@danielbachhuber 👍 Seems reasonable. @schlessera I think this should even be the default behavior. I wouldn't consider this a breaking change, I'd classify this as a bug: We're diverting from expected Core behavior.

• Fixes wp cron event run --due-now doesn't respect doing_cron transient #27

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[codecov]

Codecov Report

❌ Patch coverage is 85.71429% with 2 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/Cron_Event_Command.php	85.71%	2 Missing ⚠️

📢 Thoughts on this report? Let us know!