[Performance] Memoize isShopify

[gonzaloriestra]

WHY are these changes introduced?

isShopify is called frequently (e.g., during analytics reporting) and performs a filesystem check to see if the dev executable exists. This I/O operation can be costly when repeated across the CLI lifecycle.

WHAT is this pull request doing?

Memoizes the result of the isShopify check when using the default process.env. It caches the promise of the operation to ensure concurrent calls await the same operation and avoid race conditions. An internal _resetIsShopifyCache function is exported and used in tests to ensure isolation.

How to test your changes?

CI

Post-release steps

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 — I've identified the correct bump type (patch for bug fixes · minor for new features · major for breaking changes) and added a changeset with pnpm changeset add

---

PR created automatically by Jules for task 16016265137240540030 started by @gonzaloriestra

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

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

@@ -173,4 +173,9 @@ export declare function getThemeKitAccessDomain(env?: NodeJS.ProcessEnv): string
  * @returns The domain to send OTEL metrics to.
  */
 export declare function opentelemetryDomain(env?: NodeJS.ProcessEnv): string;
+/**
+ * This function is only used during UnitTesting.
+ * It resets the memoized value of the shopify check.
+ */
+export declare function _resetIsShopifyCache(): void;
 export type CIMetadata = Metadata;
\ No newline at end of file