WordPress has no Markdown parser in core, so the rendering is always yours to wire up. The tempting shortcut is to echo the parsed HTML straight out. On a WordPress site that string usually comes from user input, so it needs wp_kses before it reaches the page.
WooCommerce is closing stale GitHub issues in bulk, so the queue reflects work someone can actually reproduce. This covers where a bug report belongs, why a fresh issue beats reopening an old one, and what the updated contribution rules expect when a tool wrote your patch.
The WordPress AI plugin is moving toward encrypted API keys and slowing to a monthly release cadence, both before WordPress 7.1 Beta 1 in July. This is how I’d audit client sites now, and why the Connectors field registry matters for self-hosted models.
A Towards Data Science post claims big savings from a semantic cache, router and circuit breaker for RAG. The diagnosis holds, but the implementation assumes one long-lived Python process. Here’s how the same ideas map onto transients, the object cache, and a spend counter that survives PHP-FPM.
Batch gradient descent reads the whole dataset before changing anything, and that habit is what makes it slow at scale. I map the same trade onto Action Scheduler queues, WP-Cron timing, and WooCommerce jobs that still loop over every order in one request, with code for the mini-batch version.
The week after WordPress 7.0 shipped, the dev chat agenda quietly listed the field guide, three dev notes, a PHP clarification and unicode email support. I run the same four-pass triage on every agenda like this before touching a client site. This is the checklist.
Most advice on running agents at once is about attention: overview screens, alerts, recaps. On WordPress client work the shared checkout and the shared database break first. This is how I split the work, and when I stick to one session.
::checkmark styles the tick of native checkboxes, radios and selects without touching markup, which matters when WooCommerce owns the template. Here’s how I’d ship it, with a plain fallback first, @supports as the gate, and a plan for testing in Safari.
An AI pass over your products can finish with valid JSON and no errors while it quietly corrupts the data. A better prompt won’t fix that. The queue WooCommerce already ships will: one item per action, retries, checkpoints, and output you can audit with a script.
contrast-color() reached Baseline in April 2026. On WordPress it matters because clients edit the palette, and hardcoded text colors on those presets keep breaking. One declaration covers most of it, with some limits.