Skip to content

AI Launchpad: rework the sell goal to lead with store setup#50178

Open
Copons wants to merge 8 commits into
dotcom-17737-ai-launchpad-add-a-create-your-first-gallery-task-forfrom
dotcom-17738-ai-launchpad-rework-the-sell-goal-sequence-lead-with-store
Open

AI Launchpad: rework the sell goal to lead with store setup#50178
Copons wants to merge 8 commits into
dotcom-17737-ai-launchpad-add-a-create-your-first-gallery-task-forfrom
dotcom-17738-ai-launchpad-rework-the-sell-goal-sequence-lead-with-store

Conversation

@Copons

@Copons Copons commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Proposed changes

Reworks the AI Launchpad "sell" goal so it leads with store setup and shows the full commerce roadmap instead of collapsing to a couple of tasks on a fresh site.

  • Prepends two synthetic lead tasks: Install the WooCommerce plugin (to-do → installed-but-inactive "Activate" → complete-when-active) and Set up your store (completes when the WooCommerce core profiler is completed/skipped).
  • When WooCommerce is inactive, the woo_* commerce tasks that the catalog visibility gate would otherwise drop are kept as a disabled preview of the roadmap (muted, lock icon, expandable to the subtitle + an "Available once WooCommerce is active." hint, no CTA/Skip). They become actionable once WooCommerce is active.
  • Reorders the deterministic sell fallback list and the tailoring prompt to lead store-first.
  • Disabled previews never resolve completion or a CTA path — this avoids the WooCommerce completion callback's side-effect write firing during a read, and keeps a stale completion flag from rendering a locked task as "done".

Synthetic tasks are injected read-side in AI_Launchpad_REST; the shared launchpad catalog is untouched.

This is the third and last of the AI Launchpad first-pass design-feedback follow-ups, stacked on the gallery-task PR (#50166). Merge order: #50127#50166 → this.

Related product discussion/links

Does this pull request change what data or activity we track or use?

No.

Testing instructions

The AI Launchpad is behind a feature flag and off in production; test on an Atomic site where it's enabled (e.g. a WoA dev site with the mu-wpcom build synced).

  1. Ensure the site has a persisted sell tailored output (goal sell), with WooCommerce not active.
  2. Open wp-admin → AI Launchpad. You should see the full roadmap: Install the WooCommerce plugin and Choose a theme actionable; Set up your store, Customize your store, Add your products, Set up payment method, Launch your store shown as muted, locked cards that expand to their subtitle + "Available once WooCommerce is active." with no CTA/Skip.
  3. Install + activate WooCommerce. Reload — the commerce tasks become actionable, Install the WooCommerce plugin shows complete, and Set up your store links to the WooCommerce setup wizard.
  4. Complete or skip the WooCommerce setup wizard, reload — Set up your store shows complete.
  5. Edge case: with WooCommerce inactive but a commerce task previously marked complete in woocommerce_task_list_tracked_completed_tasks, the task still renders as a locked preview (not "done"), and loading the list does not write launchpad_checklist_tasks_statuses.

@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (WordPress.com Site Helper), and enable the dotcom-17738-ai-launchpad-rework-the-sell-goal-sequence-lead-with-store branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack-mu-wpcom-plugin dotcom-17738-ai-launchpad-rework-the-sell-goal-sequence-lead-with-store

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • 🔴 Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

@github-actions github-actions Bot added the [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. label Jul 2, 2026
@jp-launch-control

jp-launch-control Bot commented Jul 2, 2026

Copy link
Copy Markdown

Code Coverage Summary

No summary data is available for parent commit d60a111, so cannot calculate coverage changes. 😴

If that commit is a feature branch rather than a trunk commit, this is expected. Otherwise, this should be updated once coverage for d60a111 is available.

Full summary · PHP report · JS report

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request updates the AI Launchpad sell goal so store setup is always the lead-in, and WooCommerce-gated commerce tasks remain visible as a locked “roadmap” preview until WooCommerce is active. The change is implemented read-side in AI_Launchpad_REST (leaving the shared catalog untouched), with UI support for a new disabled task state and expanded PHPUnit/Jest coverage.

Changes:

  • Inject two synthetic lead tasks for sell: Install WooCommerce (to-do → activate → complete) and Set up your store (completes when WooCommerce onboarding profiler is completed/skipped).
  • Keep WooCommerce-gated commerce tasks in the tailored list as disabled preview cards (no CTA/skip, lock icon, expandable subtitle + hint) while WooCommerce is inactive.
  • Reorder the sell fallback and tailor prompt guidance to be store-first, with new tests covering disabled-task behavior and side-effect avoidance.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
projects/packages/jetpack-mu-wpcom/src/features/ai-launchpad/class-ai-launchpad-rest.php Adds store-task injection for sell, introduces disabled-preview behavior for Woo tasks when WooCommerce is inactive.
projects/packages/jetpack-mu-wpcom/tests/php/features/ai-launchpad/AI_Launchpad_REST_Test.php Adds PHPUnit coverage for new sell flow, disabled previews, and side-effect-free reads.
projects/packages/jetpack-mu-wpcom/src/features/ai-launchpad/js/tailored-list/model.ts Extends task model with disabled, updates actionability and auto-expand logic to skip disabled previews.
projects/packages/jetpack-mu-wpcom/src/features/ai-launchpad/js/tailored-list/model.test.mts Adds Jest tests for disabled behavior in isTaskActionable and nextIncompleteId.
projects/packages/jetpack-mu-wpcom/src/features/ai-launchpad/js/tailored-list/task-card.tsx Renders disabled tasks as locked preview cards; adds CTA labels for new synthetic tasks.
projects/packages/jetpack-mu-wpcom/src/features/ai-launchpad/js/tailored-list/style.scss Adds muted styling for disabled cards and a hint line style.
projects/packages/jetpack-mu-wpcom/src/features/ai-launchpad/js/lib/prompts.ts Updates sell-goal hard rule to keep commerce tasks ordered store-first.
projects/packages/jetpack-mu-wpcom/src/features/ai-launchpad/js/lib/fallback.ts Reorders deterministic sell fallback task IDs to lead with store customization.
projects/packages/jetpack-mu-wpcom/src/features/ai-launchpad/js/lib/fallback.test.mts Adds coverage asserting updated sell fallback ordering.
projects/packages/jetpack-mu-wpcom/changelog/add-ai-launchpad-store-setup-task Adds changelog entry describing the new sell goal sequencing and roadmap preview behavior.

Comment on lines +302 to +306
if ( ! function_exists( 'is_plugin_active' ) ) {
require_once ABSPATH . 'wp-admin/includes/plugin.php';
}
$woo_active = is_plugin_active( 'woocommerce/woocommerce.php' );

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No change needed: this calls WordPress core’s global is_plugin_active(), which already returns true for network-activated plugins (it ORs is_plugin_active_for_network() internally). Additionally, AI Launchpad only runs on WoA/Atomic sites, which are single-site, not multisite networks.

@Copons Copons force-pushed the dotcom-17737-ai-launchpad-add-a-create-your-first-gallery-task-for branch from b693df4 to d60a111 Compare July 2, 2026 16:33
Copons added 8 commits July 2, 2026 17:34
Leads the sell sequence with an "install WooCommerce" task (CTA to the
wp-admin plugin-install search); completes live once WooCommerce is active,
so the visibility-gated woo_* tasks surface only after the store exists.
Reorder the sell fallback list and tailoring prompt store-first (customize
store, then products, then payments), and add the "Set up store" CTA label.
Make the store and gallery synthetic tasks mutually exclusive by goal (a sell
site with a visual niche no longer gets an off-target gallery task), drop the
store task once WooCommerce is active instead of pinning a completed lead card,
and inline the single-use goal predicate.
Replace the single store task with two single-concern lead tasks: an
"Install the WooCommerce plugin" task (to-do / in-progress-when-inactive /
complete-when-active) and a "Set up your store" task that appears once
WooCommerce is active and completes when the core profiler is finished or
skipped. All states read live from the plugin and woocommerce_onboarding_profile
options.
Give the install task a distinct "Activate WooCommerce" CTA in its
installed-but-inactive state instead of the draft-oriented "Continue", and
simplify the lead injection to a plain array_merge (dropping the now-redundant
insert_lead_task helper).
A disabled woo preview kept flowing through is_task_complete(), whose
WooCommerce callback marks the task complete as a side effect — a
persistent write during a read — and produced a completed flag the card
rendered as done. Disabled tasks now short-circuit to completed=false
with no CTA path, and the card checks disabled before completed.
@Copons Copons force-pushed the dotcom-17738-ai-launchpad-rework-the-sell-goal-sequence-lead-with-store branch from d6d4480 to 562901e Compare July 2, 2026 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[mu wpcom Feature] Ai Launchpad [Package] Jetpack mu wpcom WordPress.com Features [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. [Tests] Includes Tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants