core: stellar version check + feature probes re-run on every subprocess with no memoization

[Dione-b]

Summary

runCommand runs checkStellarCliVersion() before every stellar invocation unless skipStellarVersionCheck is set (packages/core/src/shell/run-command.ts:27-29). checkStellarCliVersion (packages/core/src/stellar-cli/check-stellar-cli-version.ts:42-44) then runs probeMissingStellarCliFeatures, which spawns 3 more stellar <subcommand> --help probes (probe-stellar-cli-features.ts:30-38). There is no memoization, and checkBinary (packages/core/src/shell/check-binary.ts) does not set skipStellarVersionCheck, so the cascade triggers again from deploy-contract.ts:63, upload-wasm.ts:36, etc. A single ctg deploy ends up spawning ~10 subprocesses (version + 3 probes, sometimes twice) plus git/rustc metadata calls from artifacts/metadata.ts:15-34.

Why it matters

Every command pays a 5-10x subprocess tax that dominates wall-clock time, and the version check is re-run per subprocess instead of once per process.

Suggested fix

• Memoize checkStellarCliVersion results per process (keyed by cwd, invalidated only if the binary changes)
• Have checkBinary use skipStellarVersionCheck: true, since the actual command run right after will validate anyway
• Consider caching the probed features for the process lifetime

Priority: High | Release impact: Patch | Breaking: No

[DeFex-lab]

@DeFex-lab has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I’d be glad to take on this issue. I’ve worked on similar tasks before and have the experience needed to handle it. I’m ready to get started right away.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DeFex-lab to this issue.

[Kappa16]

@Kappa16 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

HI i can work on this issue FAST AND ACCURATE. expect PR IN LESS THAN 4HOURS

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Kappa16 to this issue.

[Okorie2000-code]

@Okorie2000-code has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I’ve reviewed the issue and I’m confident I can deliver a solid solution. Kindly assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Okorie2000-code to this issue.

[drips-wave]

Congratulations, @Okorie2000-code! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Okorie2000-code: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊