A hundred lines of Python, no vector database, and a real PDF. That is the baseline this author ships, with answers that cite exact lines. The part worth borrowing for WordPress work is the answer schema: typed JSON, verifiable quotes, and a null path that refuses to invent.
WooCommerce 10.9 shipped an experimental dual API: PHP classes that generate a GraphQL API. Here is how it stacks up against the REST and Store APIs, what it means for plugin developers, and which surface I would put under a real integration today.
WooCommerce is shipping read-only abilities across Subscriptions, WooPayments, shipping and marketing extensions, and it published the agent skills used to build them. I’d skip the hype and use those skills on your own plugin: install, audit, register behind a version guard, then verify.
WordPress 7.0 shipped an AI Client, a Connectors API, and a Connectors screen, and left the actual features to plugins. Here is what that means for self-hosted sites, where provider keys should live, and what to test before enabling anything on production.
OCR failures don’t throw errors on a WooCommerce site; the engine stores garbage as confidently as clean text. This is my read on a fourteen-engine benchmark, why swapping engines moves the failure instead of fixing it, and the small PHP validation layer that catches silent failures.
Woo’s WordCamp Europe 2026 post is thin as an event announcement and useful as a roadmap signal. The topics they want to discuss, checkout blocks, MCP, AI workflows, are the ones worth preparing questions for, and the same questions work by email.
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.
Sales forecasts on store dashboards are usually trailing averages, which lag every trend and give no range. A pretrained time series model like Chronos-2 changes that: you hand it daily revenue plus known future facts and get quantiles back. Here’s how I’d wire it into WordPress.
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.
WordPress planned React 19 for 7.1, then moved it to a Gutenberg experiment. The bigger risk is plugins that bundle their own React, so check your builds and test a store on staging before core ships it.