Add typed JSON output to theme duplicate

[gonzaloriestra]

WHY are these changes introduced?

theme duplicate supports JSON, but its output contract is not discoverable and the service mixes mutation results with presentation.

Part of shop/issues-develop#23692.

WHAT is this pull request doing?

Add a shared success schema for theme mutations. Successful duplication returns status: "success", the original theme identity, and the new theme with preview_url. Validation and API errors return status: "failed"; an internally completed API call is not treated as success when it contains errors.

Add a domain-owned Zod schema, return typed outcomes from duplication, and move final output into a presenter. Preserve compact JSON, error messages, request-ID omission, terminal output, prompts, and exit behavior. Refresh help, the manifest, and the README.

For a theme named Original, normal output includes:

The theme 'Original' (#1) has been duplicated.

The matching JSON for the new copy is:

{
  "status": "success",
  "originalTheme": {
    "id": 1,
    "name": "Original",
    "role": "unpublished"
  },
  "theme": {
    "id": 2,
    "name": "Copy",
    "role": "unpublished",
    "shop": "example.myshopify.com",
    "preview_url": "https://example.myshopify.com?preview_theme_id=2"
  }
}

How to manually test your changes?

pnpm shopify theme duplicate --help
pnpm shopify theme duplicate --json-schema
pnpm shopify theme duplicate --store "$STORE" --theme "$THEME_ID" --name Copy --force
pnpm shopify theme duplicate --store "$STORE" --theme "$THEME_ID" --name Copy --force --json

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• A single changeset for all theme migrations is added in the last PR, #8682.

[isaacroldan]

I'm not seeing any of these fields in the final JSON result, I just see the theme object, but not the status, originalTheme or previewUrl, are we filtering those?

[gonzaloriestra]

Right, the presenter was filtering them. Successful JSON now includes status: "success", originalTheme (ID, name, and role), and theme.preview_url, matching the URL naming used by push and pull. Error responses include status: "failed". The internal completed status is not forwarded because the API can complete with user errors or no copied theme.

[github-actions]

Differences in type declarations

We detected differences in the type declarations generated by Typescript for this branch compared to the baseline ('main' branch). Please, review them to ensure they are backward-compatible. Here are some important things to keep in mind:

• Some seemingly private modules might be re-exported through public modules.
• If the branch is behind main you might see odd diffs, rebase main into this branch.

New type declarations

We found no new type declarations in this PR

Existing type declarations

packages/cli-kit/dist/public/node/base-command.d.ts

@@ -35,6 +35,7 @@ declare abstract class BaseCommand extends Command {
         argv: string[];
     }>;
     protected environmentsFilename(): string | undefined;
+    protected validateNonTTYFlags(flags: FlagOutput): void;
     protected failMissingNonTTYFlags(flags: FlagOutput, requiredFlags: string[]): void;
     private failMissingNonTTYFlagRequirements;
     private applicableNonTTYFlagRequirements;