Related issues

• Fixes STU-832

Proposed Changes

• Extract blogname from setSiteOptions blueprint steps and use it as the default site name in the add-site form. Follows the same pattern as blueprintSuggestedDomain for custom domains. The name syncs back to the blueprint on submit so the user's changes are preserved.
• Improves the reset logic when a user clicks back and starts a new flow to avoid leaking the site name between flows.

Testing Instructions

Automated Tests

npm test -- common/lib/tests/blueprint-settings.test.ts src/modules/add-site/hooks/tests/use-blueprint-deeplink.test.tsx

Manual Tests

1. Catalog blueprint with blogname

1. Create a test blueprint JSON file with a setSiteOptions step:

   {
     "$schema": "https://playground.wordpress.net/blueprint-schema.json",
     "steps": [
       {
         "step": "setSiteOptions",
         "options": {
           "blogname": "My Custom Blog"
         }
       }
     ]
   }

blueprint-name-1.json

2. Open Studio and click Add site
3. Select Start with a Blueprint
4. Click on "Choose Blueprint file" and select the JSON file above
5. Click Continue
6. Verify: The site name field shows "My Custom Blog"
7. Open advance settings and confirm the path is the name slugified
8. Change the name to something else (e.g. "Renamed Blog")
9. Click Add site
10. Verify: The site is created with the name "Renamed Blog" (user override is respected)
11. If the site name or path already exist, then the name will append a sequential number like My Custom Blog2

BEFORE

AFTER

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?