Jetpack AI: show current featured image on modal

[CGastrell]

Proposed changes:

When a featured image is already set, the Featured Image generator modal shows empty on open.
With this change, if a featured image is set, we load it on the modal for visibility.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

p1733840898030829-slack-C054LN8RNVA

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

No

Testing instructions:

Open the editor with a new post. Click on Sidebar's "Set featured image" and select "Generate with AI".

• opening the featured image generator modal with not context (no post content nor title) should open and do nothing
• close the modal, add a title or some content on the post and open the modal again, this time an image generation should trigger
• set the generated image as featured image and close the modal
• open the modal again, see the current featured image should show on the modal and no generation should be triggered

[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 WordPress.com Simple 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, and enable the change/jetpack-ai-featured-image-show-current branch.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack change/jetpack-ai-featured-image-show-current
  

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 Team Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ 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 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? 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 semi-continuously (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly. The next release is scheduled for January 7, 2025 (scheduled code freeze on undefined).

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

[CGastrell]

Using jetpack_featured_media_url to decide is a bit more of a nuance (I think). The post attribute is only set on saving, not immediate

[CGastrell]

jetpack_featured_media_url is added on save as a backend API field hook. It should always respond to the current media ID (featured_media attribute). If we add this as a param to rely on I think we'll be introducing yet another point where things can go out of sync or be in a "dirty" state. I'd stick to just considering featured_media attribute.