Forms: Enable Central Forms Management by default for all sites

[vianasw]

Proposed changes

• Enable Central Forms Management (wp-build dashboard and synced forms) by default for all sites, including self-hosted Jetpack installations.
• Flip the jetpack_forms_alpha filter default from false to true in class-dashboard.php (4 call sites) and class-contact-form-plugin.php (1 call site).
• Add the central-form-management editor feature flag from within the Forms package via a new enable_central_form_management_flag filter callback at default priority (10), so it works out of the box without external configuration.
• Update jetpack-mu-wpcom flags to explicitly disable CFM for excluded WordPress.com sites (e2e test sites, disable-central-forms-management sticker) instead of enabling for included ones.
• Update legacy dashboard tests to explicitly opt out of wp-build mode, since the default is now enabled.

Other information

• Generate changelog entries for this PR (using AI).

Related product discussion/links

• Continues the CFM rollout: jetpack-mu-wpcom: Add Central Forms Management feature flags for Simple + Atomic #47757 (10%), jetpack-mu-wpcom: Increase Central Forms Management rollout to 50% #47793 (50%), jetpack-mu-wpcom: Increase CFM rollout to 100% #47811 (100% on WordPress.com)
• Opt-out mechanism: jetpack-mu-wpcom: Add blog sticker to disable CFM for individual sites #47822 (disable sticker)

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

No.

Testing instructions

Self-hosted / Jetpack site (the new behavior)

1. On a self-hosted WordPress site with the Jetpack plugin active, go to Jetpack → Forms.
2. Before this PR: The legacy React dashboard loads (page slug jetpack-forms-admin).
3. After this PR: The new wp-build dashboard loads (page slug jetpack-forms-responses-wp-admin) with forms management, responses, and all CFM features.
4. Verify the block editor also has CFM features: insert a Contact Form block and confirm it creates a synced form on insertion.

Opt-out via filter

1. Add add_filter( 'jetpack_forms_alpha', '__return_false' ); to a plugin or theme.
2. Verify Jetpack → Forms falls back to the legacy dashboard.
3. Remove the filter and confirm the wp-build dashboard returns.

WordPress.com (no regression)

1. On a regular WordPress.com site, verify Jetpack → Forms still loads the wp-build dashboard.
2. On a site with the disable-central-forms-management sticker, verify the legacy dashboard loads instead.

[github-actions]

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 (Jetpack or WordPress.com Site Helper), and enable the update/forms-cfm-enable-default branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/forms-cfm-enable-default

bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/forms-cfm-enable-default

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]

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!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: March 31, 2026
  • Code freeze: March 31, 2026

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[jp-launch-control]

Code Coverage Summary

Coverage changed in 2 files.

File	Coverage	Δ%	Δ Uncovered
projects/packages/forms/src/contact-form/class-contact-form-plugin.php	608/1522 (39.95%)	0.36%	-3 💚
projects/packages/forms/src/contact-form/class-feedback-email-renderer.php	303/329 (92.10%)	1.82%	-6 💚

Full summary · PHP report · JS report