Writing the README and wiring up CI is the part everyone puts off. OSA is a multi-agent tool that reads the repository, drafts the docs and docstrings, and generates the workflow files. Here is how it works and how to run it.
Notes from building a private GPU-as-a-Service platform on-prem: partitioning GPUs with MIG and time-slicing, keeping the cluster in sync with an idempotent reconciler, and working out the cost per million tokens before finance asks.
WooCommerce 10.5.2 reverts the change that left the Add to Cart button disabled on variable products when a theme or plugin altered how the variation scripts load. What went wrong, and the WP-CLI steps to update without stale variation data.
WooCommerce 10.6 stops accepting per_page=0 on Store API product and review requests, so those calls start returning 400 errors. How to move to batched requests, and the rest_endpoints filter to fall back on if you cannot refactor yet.
LLMs are non-deterministic, so three good prompts prove nothing. What to settle before you build an AI feature for WordPress or WooCommerce: the scenarios worth testing, KPIs that map to the business, and a log you can score later.
The SaaS moat is gone now that an agent can rebuild your product in an afternoon. Here is the case for a herd of small automated niche businesses over one unicorn, and the WordPress REST API and WP-CLI setup that makes running a dozen of them possible.
WordPress Core added an experimental wp-env runtime that runs PHP and SQLite through WebAssembly, so a full environment starts in seconds without Docker. Notes on the npx flag, the SQLite tradeoff, and the limits that still send me back to containers.
Slow reporting on WooCommerce is usually a schema problem, not a hardware problem. This covers custom analytical tables, the Inmon and Kimball warehouse schools, lakehouses, and where event-driven architecture fits a WordPress stack.
Dumping a relational database into a vector store gives you a slow, expensive system that has forgotten its own schema. This covers hybrid retrieval instead: ReAct tool routing, why FAISS post-filtering returns nothing, and a PHP dispatcher for WordPress.
Dashboards tell you a delivery was late. They do not say which team caused it. This post covers the MCP setup I use so Claude can read ERP, WMS and TMS timestamps and work out where the delay started.