Add typed JSON output to app import dashboard-extensions

[isaacroldan]

WHY are these changes introduced?

Give scripts a typed dashboard-extension import result. Related to #23958.

WHAT is this pull request doing?

Add --json with absolute artifact paths and skipped, cancelled, or partial outcomes. Wait for started imports before final JSON, keep completed work when another import fails, and preserve text and identifier writes. Picker Cancel retains exit 1; a sibling failure produces partial.

Text: Imported the following extensions from the dashboard: • "Example action" at: extensions/example-action.
JSON: {"status":"success","reason":null,"extensions":[{"id":"e7282f2d-3017-4608-a9a4-54dd5a7a70aa","name":"Example action","type":"flow_action_definition","directory":"/tmp/app/extensions/example-action","configurationPath":"/tmp/app/extensions/example-action/shopify.extension.toml","changed":true}],"errors":[],"identifiersUpdated":true}.

How to manually test your changes?

Use a linked test app with a dashboard-managed Flow extension. Use a fresh copy for each check so saved UUIDs do not exclude the extension.

1. Run shopify app import dashboard-extensions --path <app> --json > imports.json and select the extension. Check one success result, its absolute TOML path, and the UUID in .env.
2. In two fresh copies, create the extension directory and a local TOML first. Choose Keep local TOML in one and Cancel in the other. Keep preserves the file bytes and reports changed: false; Cancel returns one cancelled result and exit 1.
3. Run without --json in another copy to compare text. Run shopify app import dashboard-extensions --json-schema to inspect the contract.

Checklist

• I've considered possible cross-platform impacts
• I've considered documentation changes
• I've considered analytics changes
• Added the required changeset

[isaacroldan]

/snapit

[github-actions]

🫰✨ Thanks @isaacroldan! Your snapshot has been published to npm.

Built from dc72f10a130de832373d043d4a77c014303bdb1b. Workflow run.

Test the snapshot by installing your package globally:

pnpm i -g --@shopify:registry=https://registry.npmjs.org @shopify/cli@0.0.0-snapshot-20261007120950

Caution

After installing, validate the version by running shopify version in your terminal.
If the versions don't match, you might have multiple global instances installed.
Use which shopify to find out which one you are running and uninstall it.

[isaacroldan]

/snapit

[github-actions]

🫰✨ Thanks @isaacroldan! Your snapshot has been published to npm.

Built from 396595cd5300bfa0ad3661add397d3a2bca8fdce. Workflow run.

Test the snapshot by installing your package globally:

pnpm i -g --@shopify:registry=https://registry.npmjs.org @shopify/cli@0.0.0-snapshot-20261007133911

Caution

After installing, validate the version by running shopify version in your terminal.
If the versions don't match, you might have multiple global instances installed.
Use which shopify to find out which one you are running and uninstall it.

[isaacroldan]

/snapit

[github-actions]

🫰✨ Thanks @isaacroldan! Your snapshot has been published to npm.

Built from d2387c94442e9305af5a1356f176a8b6b31b7a20. Workflow run.

Test the snapshot by installing your package globally:

pnpm i -g --@shopify:registry=https://registry.npmjs.org @shopify/cli@0.0.0-snapshot-20261007140409

Caution

After installing, validate the version by running shopify version in your terminal.
If the versions don't match, you might have multiple global instances installed.
Use which shopify to find out which one you are running and uninstall it.

[isaacroldan]

/snapit

[github-actions]

🫰✨ Thanks @isaacroldan! Your snapshot has been published to npm.

Built from ccf8f51fffc5bdb86c5115f0da616215f6729a23. Workflow run.

Test the snapshot by installing your package globally:

pnpm i -g --@shopify:registry=https://registry.npmjs.org @shopify/cli@0.0.0-snapshot-20261009084827

Caution

After installing, validate the version by running shopify version in your terminal.
If the versions don't match, you might have multiple global instances installed.
Use which shopify to find out which one you are running and uninstall it.

[dmerand]

Small note from the LLM, otherwise changes LGTM.

[dmerand]

[P2] Flush the JSON result before the silent exit

This throw can cut off a large JSON result when stdout is a slow pipe. ExtensionImportCancelledError extends AbortSilentError. The shared error handler returns without flushStdout(), then Oclif calls process.exit(1). The partial path at line 148 has the same problem.

I reproduced both paths with the exact-head compiled launcher, real import service, result writer, TOML conversion, and local files. App/auth context, dashboard transport, picker answers, and telemetry were simulated; no live import was run. With 250 completed imports and a reader that starts after two seconds (... --json | { sleep 2; cat; }), cancellation and identifier-write failure each returned only 65,536 bytes. Both results failed JSON.parse, although all 250 TOML files existed. Success and fatal controls through the same pipe returned complete JSON documents. An independent repeat gave the same failures.

Please await flushStdout() after the result write and before either silent throw. Keep the intended exit code 1. The defect is the incomplete result, not the cancellation exit code.