Commit 4556b46f0b5 for woocommerce

commit 4556b46f0b5ddd3024187c29267186aa53037392
Author: Luigi Teschio <gigitux@gmail.com>
Date:   Tue Oct 20 17:39:09 2026 +0200

    Document compatibility checks for Core and theme changes (#70035)

    Add compatibility guidance for Core and theme changes

diff --git a/AGENTS.md b/AGENTS.md
index 2cd31b9493a..fabafd2be0a 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -209,6 +209,10 @@ WordPress exposes more contracts than class and function signatures. The followi

 **Do not assume install layout.** WordPress could be configured to run in a subdirectory, with relocated `wp-content`, and behind reverse proxies. Never build paths or URLs by concatenation from the domain root; derive them (`plugins_url()`, `plugin_dir_path()`, `wp_upload_dir()`, and mind the `home_url()` vs `site_url()` distinction). A path that works on a root install and breaks elsewhere is a compatibility bug, not an edge case.

+### PRs that change Core and themes
+
+Flag any PR that changes both WooCommerce Core (`plugins/woocommerce/`) and themes (`themes/`) as a **potential compatibility change**. Updating themes alongside Core can hide a breaking change for stores that update Core without updating their theme.
+
 ### Before changing any public or externally exposed surface (agent checklist)

 1. Identify the contract you are touching: signature, hook, global/scope expectation, site topology, or install layout.