From b0bb0f4b56eb5ea1cba82f3d57b621fd6b322b36 Mon Sep 17 00:00:00 2001
From: Miguel Lezama <lezama@gmail.com>
Date: Mon, 25 May 2026 12:20:11 -0300
Subject: [PATCH 1/3] Block subscriptions and other wpcom-dependent Jetpack
 modules in local env

Add explicit caveat to the general Jetpack guidance in plugin-recommendations.ts:
- List modules that require a wpcom connection (subscriptions, blaze, stats, sync)
- Instruct the agent to NOT activate these in Studio's local PHP-WASM environment
- Redirect newsletter signup requests to Jetpack Forms (contact-form module)

Fixes the error youknowriad observed:
  wp jetpack module activate subscriptions
  Error: Newsletter could not be activated. Exit code: 1

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 apps/cli/ai/plugin-recommendations.ts | 1 +
 1 file changed, 1 insertion(+)

diff --git a/apps/cli/ai/plugin-recommendations.ts b/apps/cli/ai/plugin-recommendations.ts
index f23570db31..c15ec2ff15 100644
--- a/apps/cli/ai/plugin-recommendations.ts
+++ b/apps/cli/ai/plugin-recommendations.ts
@@ -101,6 +101,7 @@ Specific Jetpack rules above (e.g. Forms) take precedence; this rule only applie
 wp_cli eval 'foreach (\\WP_Block_Type_Registry::get_instance()->get_all_registered() as $n => $b) if (strpos($n, "jetpack/") === 0 && (!isset($b->supports["inserter"]) || $b->supports["inserter"] !== false)) echo $n . PHP_EOL;'
 \`\`\`
    If the block you expect isn't listed, the relevant Jetpack module is probably inactive. Run \`wp_cli jetpack module list\` to see the matrix and \`wp_cli jetpack module activate <slug>\` to turn it on, then re-list.
+   **Important — wpcom-dependent modules**: Some modules require a WordPress.com connection and **will fail with an error** in Studio's local environment. Do NOT attempt to activate: \`subscriptions\`, \`blaze\`, \`stats\`, \`sync\`, or any module that requires a live wpcom site. For newsletter signups, use the Jetpack Forms \`contact-form\` module (already covered above) — do not activate \`subscriptions\`.
 3. Use the block in the page markup and validate with \`validate_blocks\`.
 
 \`core/html\` with raw HTML stays a last resort for the cases the block content guidelines call out (inline SVG, marquee/cursor, a single bottom-of-page \`<script>\`).`,

From 16d473603cee1a1dd2540fb08c53f83da662f391 Mon Sep 17 00:00:00 2001
From: Miguel Lezama <lezama@gmail.com>
Date: Mon, 25 May 2026 12:21:28 -0300
Subject: [PATCH 2/3] Refine wpcom-dependent Jetpack module guidance

Check connection status first rather than blocking outright.
If the site is not connected to wpcom, fall back to Jetpack Forms
for newsletter signups instead of activating the subscriptions module.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 apps/cli/ai/plugin-recommendations.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/cli/ai/plugin-recommendations.ts b/apps/cli/ai/plugin-recommendations.ts
index c15ec2ff15..7081b4002e 100644
--- a/apps/cli/ai/plugin-recommendations.ts
+++ b/apps/cli/ai/plugin-recommendations.ts
@@ -101,7 +101,7 @@ Specific Jetpack rules above (e.g. Forms) take precedence; this rule only applie
 wp_cli eval 'foreach (\\WP_Block_Type_Registry::get_instance()->get_all_registered() as $n => $b) if (strpos($n, "jetpack/") === 0 && (!isset($b->supports["inserter"]) || $b->supports["inserter"] !== false)) echo $n . PHP_EOL;'
 \`\`\`
    If the block you expect isn't listed, the relevant Jetpack module is probably inactive. Run \`wp_cli jetpack module list\` to see the matrix and \`wp_cli jetpack module activate <slug>\` to turn it on, then re-list.
-   **Important — wpcom-dependent modules**: Some modules require a WordPress.com connection and **will fail with an error** in Studio's local environment. Do NOT attempt to activate: \`subscriptions\`, \`blaze\`, \`stats\`, \`sync\`, or any module that requires a live wpcom site. For newsletter signups, use the Jetpack Forms \`contact-form\` module (already covered above) — do not activate \`subscriptions\`.
+   **Important — wpcom-dependent modules**: Some modules (e.g. \`subscriptions\`, \`blaze\`, \`stats\`) require a WordPress.com connection and will fail with an error if the site is not connected. Before activating these, check: \`wp_cli jetpack connection status\`. If the site is not connected to wpcom, fall back to an equivalent that works locally — for newsletter signups, use Jetpack Forms (\`contact-form\` module, already covered above).
 3. Use the block in the page markup and validate with \`validate_blocks\`.
 
 \`core/html\` with raw HTML stays a last resort for the cases the block content guidelines call out (inline SVG, marquee/cursor, a single bottom-of-page \`<script>\`).`,

From a2a26abd72e700db94ae6e8113e1f88d6a9facd5 Mon Sep 17 00:00:00 2001
From: Miguel Lezama <lezama@gmail.com>
Date: Mon, 25 May 2026 16:19:09 -0300
Subject: [PATCH 3/3] Simplify: skip wpcom-dependent modules when disconnected,
 no prescribed fallback

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 apps/cli/ai/plugin-recommendations.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/cli/ai/plugin-recommendations.ts b/apps/cli/ai/plugin-recommendations.ts
index 7081b4002e..ccd7f95b05 100644
--- a/apps/cli/ai/plugin-recommendations.ts
+++ b/apps/cli/ai/plugin-recommendations.ts
@@ -101,7 +101,7 @@ Specific Jetpack rules above (e.g. Forms) take precedence; this rule only applie
 wp_cli eval 'foreach (\\WP_Block_Type_Registry::get_instance()->get_all_registered() as $n => $b) if (strpos($n, "jetpack/") === 0 && (!isset($b->supports["inserter"]) || $b->supports["inserter"] !== false)) echo $n . PHP_EOL;'
 \`\`\`
    If the block you expect isn't listed, the relevant Jetpack module is probably inactive. Run \`wp_cli jetpack module list\` to see the matrix and \`wp_cli jetpack module activate <slug>\` to turn it on, then re-list.
-   **Important — wpcom-dependent modules**: Some modules (e.g. \`subscriptions\`, \`blaze\`, \`stats\`) require a WordPress.com connection and will fail with an error if the site is not connected. Before activating these, check: \`wp_cli jetpack connection status\`. If the site is not connected to wpcom, fall back to an equivalent that works locally — for newsletter signups, use Jetpack Forms (\`contact-form\` module, already covered above).
+   **Important — wpcom-dependent modules**: Some modules (e.g. \`subscriptions\`, \`blaze\`, \`stats\`) require a WordPress.com connection and will fail with an error if the site is not connected. Before activating these, check: \`wp_cli jetpack connection status\`. If the site is not connected, skip that module.
 3. Use the block in the page markup and validate with \`validate_blocks\`.
 
 \`core/html\` with raw HTML stays a last resort for the cases the block content guidelines call out (inline SVG, marquee/cursor, a single bottom-of-page \`<script>\`).`,