Add repo setup orchestration commands

[kyle-schellen]

Depends on #175.

Closes shop/issues-checkout-kit#908.

This PR wires shared storefront configuration into dev up as the single setup path for the repo. It adds scripts/setup_dev_workspace, uses it from the root dev up, and keeps platform commands focused on post-setup work like build, test, lint, format, run, clean, and API checks.

The repo-owned setup step syncs sample app storefront configuration from the root .env, refreshes Swift sample entitlements from Storefront.xcconfig, installs/checks platform dependencies, and prints a summary so setup failures are visible without hiding later platform results. The public setup surface stays intentionally small: run dev up to get the repo ready, then use dev <platform> <command> for platform-specific work.

How to test

dev up
dev help --project
dev help android
dev help swift
dev help react-native
dev help rn
dev help web
scripts/test_setup_storefront_env

Note: There is a follow-up opportunity to move the setup/config parsing logic out of ad hoc Bash and into a small reusable dev utilities area for this monorepo. In particular, helpers for reading .env / .xcconfig values across packages could make these setup scripts easier to maintain and compose. This PR keeps the current command surface focused and tested, and leaves that implementation cleanup for a separate review. Issue created here.

[kyle-schellen]

• Add repo setup orchestration commands #176 : 2 dependent PRs (#177 , #225 ) 👈 (View in Graphite)
• Centralize sample storefront configuration #175
• Align workspace dev commands in root dev.yml #69
• Move React Native dev commands under root dev.yml #64
• Move Swift dev commands under root dev.yml #36
• Move Android dev commands under root dev.yml #35
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Web — Coverage Report

Lines	Statements	Branches	Functions
	98.96% (571/577)	90.41% (151/167)	100% (55/55)

[github-actions]

React Native — Coverage Report

Lines	Statements	Branches	Functions
	91.59% (316/345)	87.25% (178/204)	100% (82/82)

[Juanita-Dash]

---

Review assisted by pair-review

[Juanita-Dash]

Left 1 suggestion with the help of pair-review. Looks good otherwise.

[kyle-schellen]

@kiftio @kieran-osgood-shopify Wanted to sanity check the dev <platform> up direction before I push this stack.

I originally added it so people wouldn’t need to run a full dev up when they only cared about one platform. After testing it more, I think it adds more workflow surface than value.

The platform setup commands are partial: they skip DevHub/native provisioning, so the docs still need to say “run dev up if base tools are missing.” That gives us two setup concepts:

• dev up = complete setup
• dev <platform> up = partial setup if shared tools are already fine

Cached dev up is ~6-10s locally for me, and after clearing RN/Web workspace deps it was ~30s. So I don’t think the time savings justify the extra commands/flags.

I’m thinking we simplify to:

• dev up = setup the repo
• dev <platform> <work command> = build, test, lint, run, clean, etc.

And remove dev <platform> up/setup, dev bootstrap, and user-facing setup --check flags.

Repo-owned setup can still run best-effort internally and summarize failures, so one platform issue doesn’t hide everything else.

What do you folks think?

[kiftio]

Yeah, this makes sense to me 👍

[kyle-schellen]

I made it so the entitlements file is always generated to prevent staleness. Feel free to push back on that.

[kyle-schellen]

I removed the conditional Mint version shortcut and now the setup path just runs mint bootstrap directly. The previous check could skip bootstrap if one tool version was stale but the later check passed, so dev up could keep reporting setup as stale without actually fixing it. mint bootstrap is cheap when everything is already current, so this keeps the setup path simpler and more reliable.

[Juanita-Dash]

🎉

[kyle-schellen]

Merge activity

• Jun 1, 5:15 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jun 1, 5:35 PM UTC: Graphite couldn't merge this pull request because a downstack PR Centralize sample storefront configuration #175 failed to merge.
• Jun 1, 6:11 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jun 1, 6:13 PM UTC: Graphite rebased this pull request as part of a merge.
• Jun 1, 6:28 PM UTC: @kyle-schellen merged this pull request with Graphite.