Merge pull request #19 from woocommerce/rename/woocommerce-claude

Rename: Hey Woo → WooCommerce for Claude

Author: garysmurray

.github/ISSUE_TEMPLATE/bug_report.md

@@ -26,7 +26,7 @@ assignees: ''
 
 ## Environment
 
-- **Hey Woo version:** <!-- e.g. 0.1.0 — see plugin header -->
+- **WooCommerce for Claude version:** <!-- e.g. 0.1.0 — see plugin header -->
 - **WordPress version:**
 - **WooCommerce version:**
 - **PHP version:**

.github/ISSUE_TEMPLATE/config.yml

@@ -4,5 +4,5 @@ contact_links:
     url: https://hackerone.com/automattic
     about: Please report security issues privately. See SECURITY.md.
   - name: Question or general help
-    url: https://github.com/woocommerce/hey-woo/discussions
+    url: https://github.com/woocommerce/woocommerce-claude/discussions
     about: For usage questions, please open a discussion rather than an issue.

.github/workflows/release.yml

@@ -1,14 +1,14 @@
 name: Release Plugin
 
-# Produce a distributable `hey-woo.zip` and publish it as a GitHub Release.
+# Produce a distributable `woocommerce-claude.zip` and publish it as a GitHub Release.
 #
 # Trigger: manual workflow_dispatch only — tag pushes do NOT trigger this
 # workflow; the tag + Release are CREATED by the workflow, not consumed by it.
 # This makes the release a deliberate UI action that goes through the full
 # build + validation path.
 #
 # Prerequisites (enforced at runtime, workflow fails fast if not met):
-#   - The `version` input must match the `Version:` header in hey-woo.php.
+#   - The `version` input must match the `Version:` header in woocommerce-claude.php.
 #     Bump the header on a PR and merge it first, then dispatch this workflow
 #     with the matching version.
 #   - The tag `v<version>` must not already exist on the remote.
@@ -17,7 +17,7 @@ on:
   workflow_dispatch:
     inputs:
       version:
-        description: 'Release version, e.g. 0.1.0 (must match the Version header in hey-woo.php)'
+        description: 'Release version, e.g. 0.1.0 (must match the Version header in woocommerce-claude.php)'
         required: true
         type: string
       draft:
@@ -47,15 +47,15 @@ jobs:
           INPUT_VERSION="${{ inputs.version }}"
           INPUT_VERSION="${INPUT_VERSION#v}"
 
-          HEADER_VERSION="$(awk '/^ \* Version:/ { print $3; exit }' hey-woo.php)"
+          HEADER_VERSION="$(awk '/^ \* Version:/ { print $3; exit }' woocommerce-claude.php)"
           if [[ -z "${HEADER_VERSION}" ]]; then
-            echo "ERROR: could not read Version header from hey-woo.php" >&2
+            echo "ERROR: could not read Version header from woocommerce-claude.php" >&2
             exit 1
           fi
 
           if [[ "${INPUT_VERSION}" != "${HEADER_VERSION}" ]]; then
             echo "ERROR: input version '${INPUT_VERSION}' does not match the Version header ('${HEADER_VERSION}')." >&2
-            echo "       Bump hey-woo.php on a PR first, merge it, then re-run this workflow." >&2
+            echo "       Bump woocommerce-claude.php on a PR first, merge it, then re-run this workflow." >&2
             exit 1
           fi
 
@@ -88,16 +88,16 @@ jobs:
 
       - name: Verify zip was produced
         run: |
-          if [ ! -f hey-woo.zip ]; then
-            echo "ERROR: hey-woo.zip not found" >&2
+          if [ ! -f woocommerce-claude.zip ]; then
+            echo "ERROR: woocommerce-claude.zip not found" >&2
             exit 1
           fi
 
       - name: Upload workflow artifact
         uses: actions/upload-artifact@v4
         with:
-          name: hey-woo-${{ env.VERSION }}
-          path: hey-woo.zip
+          name: woocommerce-claude-${{ env.VERSION }}
+          path: woocommerce-claude.zip
           retention-days: 30
 
       - name: Create GitHub Release
@@ -106,7 +106,7 @@ jobs:
           tag_name: ${{ env.TAG_NAME }}
           name: ${{ env.TAG_NAME }}
           target_commitish: ${{ github.sha }}
-          files: hey-woo.zip
+          files: woocommerce-claude.zip
           generate_release_notes: true
           draft: ${{ inputs.draft }}
           prerelease: ${{ inputs.prerelease }}

.wp-env.json

@@ -2,7 +2,7 @@
   "core": "WordPress/WordPress#6.9",
   "plugins": ["https://downloads.wordpress.org/plugin/woocommerce.zip"],
   "mappings": {
-    "wp-content/plugins/hey-woo": ".",
+    "wp-content/plugins/woocommerce-claude": ".",
     "wp-content/mu-plugins": "./tools/mu-plugins"
   },
   "config": {
@@ -11,12 +11,12 @@
     "SCRIPT_DEBUG": true
   },
   "lifecycleScripts": {
-    "afterStart": "wp-env run cli -- wp option update woocommerce_feature_mcp_integration_enabled yes && wp-env run cli -- wp plugin activate woocommerce hey-woo && wp-env run cli -- wp wc tool run install_pages --user=admin && wp-env run cli -- wp option update woocommerce_store_address '123 Main Street' && wp-env run cli -- wp option update woocommerce_store_city 'London' && wp-env run cli -- wp option update woocommerce_store_postcode 'EC1A 1BB' && wp-env run cli -- wp option update woocommerce_default_country 'GB' && wp-env run cli -- wp option update woocommerce_currency 'GBP'"
+    "afterStart": "wp-env run cli -- wp plugin activate woocommerce woocommerce-claude && wp-env run cli -- wp wc tool run install_pages --user=admin && wp-env run cli -- wp option update woocommerce_store_address '123 Main Street' && wp-env run cli -- wp option update woocommerce_store_city 'London' && wp-env run cli -- wp option update woocommerce_store_postcode 'EC1A 1BB' && wp-env run cli -- wp option update woocommerce_default_country 'GB' && wp-env run cli -- wp option update woocommerce_currency 'GBP'"
   },
   "env": {
     "tests": {
       "mappings": {
-        "wp-content/plugins/hey-woo-tests": "."
+        "wp-content/plugins/woocommerce-claude-tests": "."
       }
     }
   }

AGENTS.md

@@ -1,6 +1,6 @@
-# Hey Woo
+# WooCommerce for Claude
 
-The intelligence layer for an AI-ready WooCommerce store: analytics skills, knowledge resources, prompts, and an AI-readiness scoring engine, registered as WordPress Abilities and exposed through the plugin's own MCP endpoint at `/wp-json/hey-woo/mcp`.
+The intelligence layer for an AI-ready WooCommerce store: analytics skills, knowledge resources, prompts, and an AI-readiness scoring engine, registered as WordPress Abilities and exposed through the plugin's own MCP endpoint at `/wp-json/woocommerce-claude/mcp`.
 
 WordPress plugin, PHP 7.4+, GPL-3.0-or-later. Public repo — never commit secrets, internal-only URLs, or anything not intended for public distribution.
 
@@ -18,25 +18,25 @@ WordPress plugin, PHP 7.4+, GPL-3.0-or-later. Public repo — never commit secre
 
 **Re-stating the two highest-stakes rules** because they're load-bearing for every ability description and a single violation ships to a public release:
 
-- **Privacy.** Analytics responses are aggregated counts/sums/averages only. No customer names, emails, or addresses unless the `hey_woo_allow_customer_pii` option is opt-in **and** the response shape clearly justifies it. Default off.
+- **Privacy.** Analytics responses are aggregated counts/sums/averages only. No customer names, emails, or addresses unless the `woocommerce_claude_allow_customer_pii` option is opt-in **and** the response shape clearly justifies it. Default off.
 - **Merchant scope.** The AI is talking to a merchant. They can't add a tool, register a REST endpoint, or edit plugin code. Tool descriptions and merchant-facing text MUST NOT suggest "a future X skill would answer this" — substitute with something the merchant can action (a setting, a manual workflow, a connector, or an honest "this isn't something we can answer"). The static guardrail-sweep test (`tests/integration/test-ability-description-guardrails.php`) catches the obvious violations on every `./bin/check`.
 
 ## Layout
 
 ```
-hey-woo/
-├── hey-woo.php               # Plugin bootstrap (HPOS declaration, requirements, options migration)
+woocommerce-claude/
+├── woocommerce-claude.php               # Plugin bootstrap (HPOS declaration, requirements, options migration)
 ├── includes/
 │   ├── class-plugin.php      # Singleton — wires hooks, boots WP MCP adapter, registers own MCP server
 │   ├── abilities/            # One file per skill. wc-analytics/* (analytics tools),
-│   │                         # hey-woo/* (store/readiness/search tools), wc-knowledge/*
-│   │                         # (resources), wc-prompts/* (prompts), hey-woo-integrations/*
+│   │                         # woocommerce-claude/* (store/readiness/search tools), wc-knowledge/*
+│   │                         # (resources), wc-prompts/* (prompts), woocommerce-claude-integrations/*
 │   │                         # (dev-only prototype scaffolds — gated by wp_get_environment_type)
 │   ├── api/                  # REST controllers + AnalyticsController (shared SQL helper —
 │   │                         # no REST routes; abilities call into it)
 │   ├── knowledge/            # Provider pattern (store profile / catalog / product / policy)
 │   ├── scoring/              # Engine + 4 factors (product, schema, content, policy)
-│   ├── settings/             # WC > Settings > Hey Woo tab
+│   ├── settings/             # WC > Settings > WooCommerce for Claude tab
 │   └── telemetry/            # SkillTelemetry + handlers (log, Tracks-gated by opt-in toggle)
 ├── tests/integration/        # PHPUnit; runs inside wp-env tests-cli container
 ├── tools/
@@ -56,7 +56,7 @@ hey-woo/
 
 ```bash
 npx @wordpress/env start          # boots WP 6.9 + WC + this plugin on http://localhost:8888
-                                   # afterStart activates WC + Hey Woo, installs WC pages,
+                                   # afterStart activates WC + WooCommerce for Claude, installs WC pages,
                                    # sets a UK store address (London / GBP)
 ./bin/check                        # full pre-push gate (PHPCS, composer audit, PHPUnit, DCC)
 ```
@@ -72,10 +72,10 @@ npx @wordpress/env run cli -- wp eval-file /tmp/seed.php
 
 These are validated decisions. **MUST NOT** relitigate without strong new signal.
 
-- **Plugin-owned MCP server.** Hey Woo registers its own MCP server at `/wp-json/hey-woo/mcp` via the WordPress MCP adapter (vendored inside WooCommerce as `vendor/wordpress/mcp-adapter`). The plugin boots the adapter on `plugins_loaded` so the endpoint works regardless of WC's `mcp_integration` feature flag, then calls `$adapter->create_server('hey-woo', 'hey-woo', 'mcp', ...)` on `mcp_adapter_init` with a curated list of tools, resources, and prompts. Auth uses an `X-MCP-API-Key: ck:cs` header backed by a standard WC REST API key. The earlier "ride on WC's `woocommerce-mcp` server via `woocommerce_mcp_include_ability`" approach is gone — that endpoint is being deprecated upstream.
-- **Single Abilities API namespace.** Every analytics skill is at `wp-abilities/v1/abilities/wc-analytics/{skill}/run`. Earlier custom `hey-woo/v1/analytics/*` REST routes were folded into Abilities so MCP and direct callers hit one surface.
-- **Three plugin-owned ability prefixes**, declared in `Plugin::OWNED_ABILITY_NAMESPACES`: `wc-analytics/`, `hey-woo/`, `hey-woo-integrations/`. The WC auth scope filter trusts only routes under these prefixes — a Hey Woo consumer key cannot be replayed against abilities registered by other plugins. Adding a fourth prefix is a single-edit operation; the `Plugin::mcp_tool_ability_ids()` curated list must be updated in lockstep.
-- **Aggregated-only privacy by default.** PII gate (`hey_woo_allow_customer_pii`) is off; merchants opt in only when chaining with email/CRM MCPs that need real addresses. `wc_string_to_bool` reads the option (not `(bool)` — `'no'` would otherwise be truthy).
+- **Plugin-owned MCP server.** WooCommerce for Claude registers its own MCP server at `/wp-json/woocommerce-claude/mcp` via the WordPress MCP adapter (vendored inside WooCommerce as `vendor/wordpress/mcp-adapter`). The plugin boots the adapter on `plugins_loaded` so the endpoint works regardless of WC's `mcp_integration` feature flag, then calls `$adapter->create_server('woocommerce-claude', 'woocommerce-claude', 'mcp', ...)` on `mcp_adapter_init` with a curated list of tools, resources, and prompts. Auth uses an `X-MCP-API-Key: ck:cs` header backed by a standard WC REST API key. The earlier "ride on WC's `woocommerce-mcp` server via `woocommerce_mcp_include_ability`" approach is gone — that endpoint is being deprecated upstream.
+- **Single Abilities API namespace.** Every analytics skill is at `wp-abilities/v1/abilities/wc-analytics/{skill}/run`. Earlier custom `woocommerce-claude/v1/analytics/*` REST routes were folded into Abilities so MCP and direct callers hit one surface.
+- **Three plugin-owned ability prefixes**, declared in `Plugin::OWNED_ABILITY_NAMESPACES`: `wc-analytics/`, `woocommerce-claude/`, `woocommerce-claude-integrations/`. The WC auth scope filter trusts only routes under these prefixes — a WooCommerce for Claude consumer key cannot be replayed against abilities registered by other plugins. Adding a fourth prefix is a single-edit operation; the `Plugin::mcp_tool_ability_ids()` curated list must be updated in lockstep.
+- **Aggregated-only privacy by default.** PII gate (`woocommerce_claude_allow_customer_pii`) is off; merchants opt in only when chaining with email/CRM MCPs that need real addresses. `wc_string_to_bool` reads the option (not `(bool)` — `'no'` would otherwise be truthy).
 - **HPOS-compatible.** Declared via `FeaturesUtil::declare_compatibility('custom_order_tables', __FILE__, true)`. SQL must read from HPOS tables (`wp_wc_orders_meta` for attribution) when available, falling back to `wp_postmeta` only when HPOS isn't enabled. The runtime branch lives in `AnalyticsController::get_order_meta_source()`.
 - **No background work.** No cron, no polling, no sync jobs. The plugin runs only when an MCP/REST request arrives. This is the contract that lets the perf doc say "lighter than loading WC Analytics a few times an hour."
 - **Transient cache with stable keys.** Never pass live `DateTime` objects into cache-key generation; normalise to `Y-m-d H:i:s` strings before hashing. WC core's DataStore cache has a known microseconds-in-key bug — don't reach for it.
@@ -103,7 +103,7 @@ The DCC step (`bin/check-dcc`) is gated — it auto-skips when `vendor-plugins/w
 
 ### MCP requires HTTPS by default
 
-Local wp-env runs on plain HTTP. The Hey Woo MCP transport (`WP\MCP\Transport\HttpTransport`) does not enforce HTTPS, so curl-style local testing against `/wp-json/hey-woo/mcp` works without a TLS cert. Production stores should still front the endpoint with HTTPS.
+Local wp-env runs on plain HTTP. The WooCommerce for Claude MCP transport (`WP\MCP\Transport\HttpTransport`) does not enforce HTTPS, so curl-style local testing against `/wp-json/woocommerce-claude/mcp` works without a TLS cert. Production stores should still front the endpoint with HTTPS.
 
 ### Two-step skill addition
 
@@ -114,9 +114,9 @@ A new analytics skill needs **code + PHPUnit test + two static-sweep constants**
 
 The full how-to is in CONTRIBUTING.md (`Adding a new analytics Skill`). Don't shortcut the test — the coverage guard is the substitute for "did anyone actually verify this against real data?"
 
-### The `hey-woo-tests` mapping is the integration-tests mount
+### The `woocommerce-claude-tests` mapping is the integration-tests mount
 
-`.wp-env.json` mounts the repo into the dev environment as `hey-woo` and into the **tests** environment as `hey-woo-tests`. The PHPUnit container's working dir is `wp-content/plugins/hey-woo-tests` — that's why `bootstrap.php` does `glob($plugin_dir . '/hey-woo/...')` to find the production-side mount when loading WC. Don't rename either mount; the bootstrap and the CI workflow both rely on the slug.
+`.wp-env.json` mounts the repo into the dev environment as `woocommerce-claude` and into the **tests** environment as `woocommerce-claude-tests`. The PHPUnit container's working dir is `wp-content/plugins/woocommerce-claude-tests` — that's why `bootstrap.php` does `glob($plugin_dir . '/woocommerce-claude/...')` to find the production-side mount when loading WC. Don't rename either mount; the bootstrap and the CI workflow both rely on the slug.
 
 ### British English
 
@@ -132,4 +132,4 @@ The plugin is published as a UK-Automattic-shaped product (default seed store is
   3. Tool/ability descriptions don't violate the merchant-scope rule (the description-guardrail sweep enforces the obvious cases; review catches the rest).
   4. CONTRIBUTING.md "Design patterns worth knowing" section updated when a new reusable pattern is established.
   5. AGENTS.md (this file) updated when a new gotcha, command, or convention is introduced.
-- **Don't commit `hey-woo.zip`.** It's checked into the repo as a one-off artefact, but `*.zip` is in `.gitignore` and the release workflow rebuilds it from the tag. Don't update it in regular commits.
+- **Don't commit `woocommerce-claude.zip`.** It's checked into the repo as a one-off artefact, but `*.zip` is in `.gitignore` and the release workflow rebuilds it from the tag. Don't update it in regular commits.