Add typed JSON output to theme delete

[gonzaloriestra]

WHY are these changes introduced?

theme delete has no JSON result contract, so automation must parse terminal output.

Part of shop/issues-develop#23692.

WHAT is this pull request doing?

Return status: "success" alongside the deleted themes only after every requested deletion succeeds. Reuse the shared mutation success schema. In multiple environments, the status belongs to each result; the response does not claim overall success when another environment fails.

Return deleted theme data and move final output into a presenter. Add an opt-in result collector to the shared theme runner; this preserves store sequencing and analytics while JSON results are encoded once. JSON environment diagnostics use the shared event channel. Add --json, expose the domain-owned schema, and refresh the manifest, README, and generated docs.

Normal output includes:

The theme 'Original' (#1) was deleted from example.myshopify.com.

Matching JSON:

{
  "status": "success",
  "themes": [
    {
      "id": 1,
      "name": "Original",
      "role": "unpublished",
      "processing": false,
      "createdAtRuntime": false,
      "shop": "example.myshopify.com"
    }
  ]
}

The optional src field is retained when present. Multiple environments return {"environments":[{"environment":"staging","result":...}]} in configured order. Failed or invalid environments are omitted and reported on stderr; total failure returns {"environments":[]}. Existing exit behavior and single-environment presentation are preserved.

How to manually test your changes?

pnpm shopify theme delete --help
pnpm shopify theme delete --json-schema
pnpm shopify theme delete --store "$STORE" --theme "$THEME_ID" --force
pnpm shopify theme delete --store "$STORE" --theme "$THEME_ID" --force --json
pnpm shopify theme delete --environment staging --environment production --theme "$THEME_ID" --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]

Let's include also status: success in the result, maybe abstract it to a shared "status" schema for other commands to reuse?

[isaacroldan]

It can be a zod.literal

[gonzaloriestra]

Added status: zod.literal('success') through the shared ThemeMutationSuccessSchema, introduced in #8640 and reused by delete, publish, and rename. Delete returns success only after all requested deletions succeed. Multiple environments carry the status per result, without claiming overall success.

[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;