Expand app configuration through extension specifications

[isaacroldan]

WHY are these changes introduced?

Alternative to #8426, built on #8425. Deploying one events module per subscription needs support for multiple modules from one app configuration section. The events contract and identity rules belong in its specification.

WHAT is this pull request doing?

Add optional specification hooks for configuration expansion, module identity, and module target. The loader creates and validates every result through the same path, while the events specification owns the subscription split.

Expand event subscriptions by default, without an organization flag lookup. Require valid, unique subscription handles and reject the reserved legacy handle events. Keep app branding handles out of events validation, preserve extra subscription fields, and return no modules for an empty subscription list.

Validated with 350 tests across eight files, app type checking, lint on changed files, and Knip for the app workspace. Includes deploy/config-link round trips, identity stability, and invalid configuration cases. A live deploy has not been tested. The server must support single-subscription events modules before this CLI change is released.

How to manually test your changes?

pnpm shopify app deploy --path /path/to/app
pnpm shopify app config link --path /path/to/app

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
• The change is user-facing and includes a patch changeset

[isaacroldan]

/snapit

[isaacroldan]

We can't include handle here outside of events. This will receive the full app toml config, and handle is a field belonging to the branding module. We can only validate events and its children here.

[isaacroldan]

@rezaansyed this is a limitation of the expansion approach, i'm looking on ways to improve this.

[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/cli.d.ts

@@ -35,7 +35,6 @@ export declare function runCreateCLI(options: RunCLIOptions, launchCLI?: (option
 export declare const globalFlags: {
     'no-color': import("@oclif/core/interfaces").BooleanFlag<boolean>;
     verbose: import("@oclif/core/interfaces").BooleanFlag<boolean>;
-    'no-input': import("@oclif/core/interfaces").BooleanFlag<boolean>;
 };
 export declare const jsonFlag: {
     json: import("@oclif/core/interfaces").BooleanFlag<boolean>;

[isaacroldan]

/snapit

[github-actions]

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

Built from 294f999fa5b79d6784960e5b55791cb5b7238e0d. 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-20261002155739

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.

[gonzaloriestra]

I've been playing around and everything looks good 👍