Memberships: register WP Abilities API reads (plans, subscribers, earnings)

[enejb]

Proposed changes

• Adds Automattic\Jetpack\Plugin\Abilities\Memberships_Abilities, a Registrar-extending class at projects/plugins/jetpack/modules/memberships/abilities/class-memberships-abilities.php.
• Registers three read-only abilities on WP 6.9+ under the jetpack-memberships/* namespace:
  • jetpack-memberships/list-plans — paid membership tiers with plan_id consolidated-read.
  • jetpack-memberships/list-subscribers — paid-membership subscribers with status / plan filters.
  • jetpack-memberships/get-earnings-summary — zero-arg earnings summary for the current period.
• Case A wiring from modules/memberships/class-jetpack-memberships.php — registration only happens when the Memberships module is active.
• Gated by the jetpack_wp_abilities_enabled filter (default false).
• Permission callbacks mirror the underlying wpcom endpoints (edit_posts for plans, manage_options for subscriber + earnings reads).

Testing instructions

1. cd projects/plugins/jetpack && composer install.
2. composer phpunit -- --filter Memberships_Abilities_Test.
3. On a site with Memberships active and the gate filter enabled, curl /wp-json/wp-abilities/v1/abilities | jq '.[] | select(.name | startswith("jetpack-memberships/")) | .name' and confirm three slugs.

Plan reference

Abilities rollout plan — §3.3 Memberships module.

[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), and enable the add/ship-memberships-abilities branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/ship-memberships-abilities

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 🤖

---

🔴 Action required: We would recommend that you add a section to the PR description to specify whether this PR includes any changes to data or privacy, like so:

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

My PR adds *x* and *y*.

---

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!

[jp-launch-control]

Code Coverage Summary

Cannot generate coverage summary while tests are failing. 🤐

Please fix the tests, or re-run the Code coverage job if it was something being flaky.

Full summary · PHP report · JS report