Orchestrator Extraction — Remove Orchestrator Code, Add Plugin Loader

[frostebite]

Orchestrator Extraction — Remove Orchestrator Code, Add Plugin Loader

Extracts the orchestrator subsystem from unity-builder into the standalone game-ci/orchestrator repository. Unity-builder becomes a lean GitHub Action; all orchestrator, CLI, and cloud provider features live in the standalone repo.

Standalone repo: https://github.com/game-ci/orchestrator (public)
Documentation: game-ci/documentation#541
Closes PRs: #777, #778, #783, #784, #786, #787, #790, #791, #798, #799, #804, #806, #808, #809, #813, #814, #815, #816

---

Why

Problem	Impact
9 heavy AWS/K8s npm deps bundled into every action run	~15MB bundle bloat for users who never use orchestrator
148+ production + test files in src/model/orchestrator/	Contributor confusion — orchestrator internals dwarf the core action
Orchestrator and core action share one release cadence	Cannot ship orchestrator fixes without touching the action
BuildParameters is a god object mixing both concerns	Tight coupling makes both harder to evolve

---

What Changes for Users

The orchestrator is now a separate package that lives in its own repository (game-ci/orchestrator). What this means depends on your build strategy:

Local builds (providerStrategy: local) — No change required

If you use the default local Docker builds, nothing changes. Unity-builder works standalone with no extra install step:

steps:
  - uses: actions/checkout@v4

  - uses: game-ci/unity-builder@v4
    with:
      targetPlatform: StandaloneLinux64

Cloud builds (providerStrategy: aws, k8s, etc.) — Install the orchestrator first

For cloud provider strategies, you now need to install the orchestrator before running unity-builder. The install adds the game-ci CLI and the @game-ci/orchestrator package so that unity-builder's plugin loader can detect it automatically.

GitHub Actions example:

steps:
  - uses: actions/checkout@v4

  - name: Install Game CI Orchestrator
    run: curl -fsSL https://raw.githubusercontent.com/game-ci/orchestrator/main/install.sh | sh

  - uses: game-ci/unity-builder@v4
    with:
      providerStrategy: aws
      targetPlatform: StandaloneLinux64
      gitPrivateToken: ${{ secrets.GITHUB_TOKEN }}

That is all that changes: one extra step to install the orchestrator before the build step. Unity-builder automatically detects the orchestrator via its plugin loader and enables cloud providers and all services.

Install commands by platform

Platform	Command
macOS / Linux	curl -fsSL https://raw.githubusercontent.com/game-ci/orchestrator/main/install.sh | sh
Windows PowerShell	irm https://raw.githubusercontent.com/game-ci/orchestrator/main/install.ps1 | iex

Standalone CLI usage (optional)

The orchestrator can also be used directly from the command line without GitHub Actions:

game-ci build \
  --providerStrategy aws \
  --projectPath ./my-unity-project \
  --targetPlatform StandaloneLinux64

---

What This PR Does

118 files changed, 3,741 insertions, 15,404 deletions

Deleted

• Entire src/model/orchestrator/ directory (148 .ts files)
• src/cli.ts and src/cli/ (CLI moved to orchestrator repo)
• src/integration/orchestrator-github-checks-integration-test.ts
• src/test-utils/orchestrator-test-helpers.ts
• .github/workflows/orchestrator-async-checks.yml
• .github/workflows/orchestrator-integrity.yml
• .github/workflows/release-cli.yml
• 12 npm dependencies: @aws-sdk/* (5), @kubernetes/client-node, async-wait-until, aws-sdk, base-64, kubernetes-client, shell-quote, uuid
• CLI deps: yargs, @types/yargs, pkg
• Install scripts (install.sh, install.ps1) — moved to orchestrator repo

Added

• Plugin loader (src/model/orchestrator-plugin.ts): Dynamic import('@game-ci/orchestrator') with graceful degradation
• Type declarations (src/types/game-ci-orchestrator.d.ts): Ambient module for optional @game-ci/orchestrator package
• Plugin interface tests (src/model/orchestrator-plugin.test.ts): 15 tests covering both installed and not-installed paths
• Validate orchestrator workflow (.github/workflows/validate-orchestrator.yml): Per-PR health checks — builds both repos, tests plugin loader, verifies type declarations
• Integration test workflow (.github/workflows/validate-orchestrator-integration.yml): Nightly exhaustive suite — k8s (k3d), AWS (LocalStack), local-docker, rclone

Changed

• build-parameters.ts: Replaced 44 OrchestratorOptions.* with Input.getInput(), inlined constants
• github.ts: Stripped to minimal class
• input.ts: Removed OrchestratorQueryOverride
• input-readers/: Replaced OrchestratorSystem.Run with child_process.exec
• index.ts: Plugin loader pattern for services

---

How the Plugin Loader Works

// orchestrator-plugin.ts
export async function loadOrchestrator() {
  try {
    const { Orchestrator } = await import('@game-ci/orchestrator');
    return {
      run: async (buildParameters, baseImage) => {
        const result = await Orchestrator.run(buildParameters, baseImage);
        return { exitCode: result.BuildSucceeded ? 0 : 1, ...result };
      },
    };
  } catch {
    return undefined; // Package not installed — graceful degradation
  }
}

---

Test Results

• 443 tests pass (22 suites), 2 skipped
• TypeScript compiles with zero errors
• ESLint passes
• dist/ bundle rebuilt (~4MB vs ~15MB before)

Orchestrator Repo Status

• 769+ tests pass (46 suites) including CLI
• All content from 15 closed PRs verified present
• Middleware pipeline, all providers, all services included

---

Checklist

• All orchestrator code removed from unity-builder
• CLI moved to orchestrator repo
• Install scripts moved to orchestrator repo
• Plugin loader with graceful degradation
• Plugin interface tests (15 tests)
• Per-PR validation workflow (plugin health)
• Nightly integration tests (k8s, AWS, local-docker, rclone)
• All 15 feature PRs verified in orchestrator repo
• All linked issues closed
• 443 unity-builder tests pass
• 769+ orchestrator tests pass
• Documentation update: Orchestrator: LTS 2.0.0 documentation#541

[frostebite]

Cross-references:

• Documentation update: Orchestrator: LTS 2.0.0 documentation#541
• Orchestrator README + CLAUDE.md: game-ci/orchestrator@d602ea3

[webbertakken]

Do we do a CLI as part of this?

[frostebite]

Do we do a CLI as part of this?

There is a CLI provided by orchestrator now it's standalone. It's a pretty good entrypoint for a CLI generally for Game-CI. This change specifically doesn't add it or require it, because this just implements orchestrator as a standalone plugin.

CLI Getting Started

 irm https://raw.githubusercontent.com/game-ci/orchestrator/main/install.ps1 | iex