👷 parallelize test app builds

[BenoitZugmeyer]

Motivation

yarn build:apps builds all test apps sequentially, making it slow (~1m22s on a typical machine). Since most apps are independent, they can be built in parallel.

Changes

• Add runAsync() to the command builder (async spawn-based counterpart to run()), with a mutex that automatically serializes git commands to avoid index lock conflicts
• Rewrite build-test-apps.ts to build all apps concurrently using a dependency-aware ensureBuild() function; react-router-v7-app waits on react-router-v6-app, and the two extensions wait on base-extension
• Update the secureCommandExecution ESLint rule to accept .runAsync() as a valid terminal call

Wall-clock time drops from ~1m22s to ~37s (~2x faster).

Test instructions

Run yarn build:apps and verify all apps build successfully.

Checklist

• Tested locally
• Tested on staging
• Added unit tests for this change.
• Added e2e/integration tests for this change.
• Updated documentation and/or relevant AGENTS.md file

[cit-pr-commenter-54b7da]

Bundles Sizes Evolution

📦 Bundle Name	Base Size	Local Size	𝚫	𝚫%	Status
Rum	179.65 KiB	179.65 KiB	0 B	0.00%	✅
Rum Profiler	6.17 KiB	6.17 KiB	0 B	0.00%	✅
Rum Recorder	27.03 KiB	27.03 KiB	0 B	0.00%	✅
Logs	56.78 KiB	56.78 KiB	0 B	0.00%	✅
Rum Slim	135.50 KiB	135.50 KiB	0 B	0.00%	✅
Worker	23.63 KiB	23.63 KiB	0 B	0.00%	✅

🚀 CPU Performance

Action Name	Base CPU Time (ms)	Local CPU Time (ms)	𝚫%
RUM - add global context	0.004	0.0068	+70.00%
RUM - add action	0.0138	0.0188	+36.23%
RUM - add error	0.013	0.0188	+44.62%
RUM - add timing	0.0028	0.0041	+46.43%
RUM - start view	0.0127	0.0176	+38.58%
RUM - start/stop session replay recording	0.0007	0.0008	+14.29%
Logs - log message	0.0144	0.0191	+32.64%

🧠 Memory Performance

Action Name	Base Memory Consumption	Local Memory Consumption	𝚫
RUM - add global context	31.90 KiB	30.95 KiB	-974 B
RUM - add action	58.38 KiB	59.60 KiB	+1.22 KiB
RUM - add timing	32.49 KiB	32.22 KiB	-279 B
RUM - add error	59.66 KiB	63.63 KiB	+3.97 KiB
RUM - start/stop session replay recording	32.28 KiB	31.19 KiB	-1.09 KiB
RUM - start view	484.73 KiB	485.93 KiB	+1.20 KiB
Logs - log message	111.39 KiB	104.68 KiB	-6.71 KiB

🔗 RealWorld

[datadog-prod-us1-4]

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 77.02% (+0.02%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 2e3c7f8 | Docs | Datadog PR Page | Give us feedback!}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2e3c7f84e0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Honor withInput() when running asynchronously

When callers use the new runAsync() path with withInput() (for example the existing gh auth login --with-token/ssh-add - patterns if they are converted to async), the configured input is never written to the spawned process. Because spawn() creates a stdin pipe here but the parent neither writes nor closes it, commands that read from stdin can hang indefinitely or fail with missing input, unlike run() which passes input to spawnSync().

Useful? React with 👍 / 👎.

[BenoitZugmeyer]

Right, but we'll fix when we need it.