Detect runtime for copilot-sdk installs from engine.copilot.command via runtime manager

[Copilot]

When copilot-sdk: true is enabled, SDK installation previously assumed npm/Node even for custom engine.copilot.command runtimes. This change infers runtime from the command and emits the matching SDK install command with pinned SDK versioning and safe install flags.

• Runtime-aware SDK installation

  • Detects runtime from engine.copilot.command (including env ... <cmd> wrappers).
  • Integrates runtime detection with the runtime manager command mapping (commandToRuntime).
  • Maps to language-specific install commands:
    • Node.js/TypeScript → npm install @github/copilot-sdk@<version>
    • Python → pip install github-copilot-sdk==<version>
    • Go → go get github.com/github/copilot-sdk/go@v<version>
    • Rust → cargo add github-copilot-sdk@<version>
    • .NET → dotnet add package GitHub.Copilot.SDK --version <version>
    • Java → Maven artifact fetch for com.github:copilot-sdk-java:<version>
  • Preserves compatibility fallbacks for command tokens not currently represented in runtime manager mappings (cargo/rustc, mvnw, ts-node), and defaults unknown runtimes to Node SDK install.

• Custom command installation flow

  • engine.copilot.command no longer suppresses SDK installation when copilot-sdk: true.
  • In firewall mode, SDK install step is emitted alongside AWF runtime installation.

• Install command policy alignment

  • Keeps npm invocation hardened (--ignore-scripts) and non-mutating (--no-save).
  • Uses DefaultCopilotSDKVersion consistently across all runtime-specific install commands.

• Tests

  • Updated Copilot engine installation tests to validate:
    • Node default behavior remains unchanged
    • runtime-specific command selection for all supported SDK runtimes
    • runtime-manager-derived Java detection (gradle)
    • unsupported runtime fallback to Node SDK install
    • env-wrapped command detection
    • coexistence with firewall/AWF installation

workflowData := &WorkflowData{
  EngineConfig: &EngineConfig{
    Command:    "python3 main.py",
    CopilotSDK: true,
  },
}
// Emits: Install GitHub Copilot SDK (Python)
// run: cd "${GITHUB_WORKSPACE}" && pip install --disable-pip-version-check github-copilot-sdk==<DefaultCopilotSDKVersion>

[pelikhan]

@copilot integrate in runtime manager

[Copilot]

@copilot integrate in runtime manager

Implemented in dda01942c5: Copilot SDK runtime detection now uses the runtime manager command mapping (commandToRuntime) for engine.copilot.command, with compatibility fallbacks for tokens not yet represented there (cargo/rustc, mvnw, ts-node). Added tests for runtime-manager Java detection (gradle) and unsupported runtime fallback to Node SDK install.

[Copilot]

Pull request overview

This PR updates Copilot engine installation step generation so that when copilot-sdk: true is enabled, the workflow emits a runtime-specific Copilot SDK install step based on engine.copilot.command (including env ... <cmd> wrappers), instead of always assuming Node/npm.

Changes:

• Added runtime detection for engine.copilot.command and mapped it to language-specific Copilot SDK install commands (Node/Python/Go/Rust/.NET/Java).
• Ensured SDK install steps are still emitted even when a custom Copilot command is provided (and in firewall mode, alongside AWF installation).
• Expanded unit tests to cover runtime-specific SDK installation selection and firewall coexistence.

Show a summary per file

File	Description
pkg/workflow/copilot_engine_installation.go	Adds runtime-aware SDK install step generation and integrates it into Copilot engine installation flow.
pkg/workflow/copilot_engine_test.go	Updates existing assertions and adds coverage for runtime-specific SDK install steps with/without firewall.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 1