[metalwarrior665]

Why

runBuilds (git) and runBuildsFromLocal each had their own copy of "prepare read-only, dry-run cutoff, start, wait, summarize". They were glued together with actorFullName Maps (buildConfigsByActorFullName, preparedByActorFullName, buildersByActorFullName) and a runAndSummarizeBuilds callback API. Every cross-cutting build feature has to be written twice. #217 (env var sync check) already does this: it threads requireEnvVarsInSync through both flows and both option types.

What

• BuildPlan: one Actor build, fully read and checked, with nothing written yet. It holds the builder, the fetched actorInfo, the version number, the cache flag, the dry-run summary and description, and a lazy toActorVersion(). For local builds that is where the upload happens, so it only runs for real builds.
• executeBuildPlans(plans, { label, dryRun }) is now the only place that handles dry runs, starts builds, waits for them and prints the summary. A dry run returns the same DryRunPlan object as before.
• loadActor is the shared first step: build the client and fetch the Actor once.
• Both flows now only build plans. The Maps, runAndSummarizeBuilds, waitAndSummarizeBuilds (now internal to the executor) and the unused getDefaultVersionAndTag are gone.
• uploadSourceZip takes the Actor id from the plan's actorInfo instead of fetching the Actor a second time. createVersionAndBuild now requires actorInfo (it was optional only so callers could skip a fetch).

Behaviour is unchanged: same logs, same dry-run JSON, builds returned sorted by Actor, and one builder (token check) per Actor. A dry run still never creates a version, build or upload.

Follow-ups this enables

• feat!: require env vars of test versions in sync with the default version #217's env-var check goes into one shared preflight step instead of two copies. A third build source (e.g. a tarball URL) would be one more plan factory.
• deleteOldBuilds could become selectBuildsToDelete(actorInfo, builds, now) plus a thin executor. I left it out to keep this PR to one idea.

Not touched on purpose

• The diff and git logic, which feat(get-affected-actors): three-dot diff, narrowed per Actor with --since #204 and refactor(file-diff): refactor changedFiles to do 3 ref diffing with intersection #209 rework.
• lib/, which refactor(lib): focused modules, declarative toFinishWith, paged datasets #206 and refactor(lib): declarative toFinishWith, memoized RunTestResult, shared test registration #207 rework.
• The legacy get-commits, get-latest-commit and get-changed-files commands. They look removable once get-affected-actors is the only consumer, but that needs a call from the maintainers.

Testing

Added unit tests for executeBuildPlans: starting and waiting, sorting, failure propagation, the dry run touching nothing, and empty input. The existing build and build-from-local tests pass unchanged. Type-check, lint, prettier and the unit and bundle tests pass, and I rebuilt .github/cli/apify-test-tools.mjs.

---

Generated by Claude Code