Include Copilot CLI runtime assets in PackAsTool packages

[kondv]

Fixes #2067

Problem

Tool packages are produced from the publish layout, but the SDK registered its Copilot CLI runtime assets only for build output. When a PackAsTool project was packed without rebuilding — the usual CI sequence, and dotnet pack --no-build in general — the resulting package contained no runtimes/<rid>/native payload, and the installed tool failed:

System.InvalidOperationException: Copilot runtime wrapper not found at
'...\tools\net8.0\win-x64\runtimes\win-x64\native\copilot-runtime.exe'.

Change

Register the existing runtime asset items before publish item collection as well as build output, and give them CopyToPublishDirectory, so assets already staged for build output also reach the publish layout the tool package is built from.

The item set, RID selection, download and cache behavior, output paths, and runtime precedence are unchanged. This does not rename the explicit-CLI marker, change stale-file replacement, alter execute permissions, or add CI jobs.

Validation

• MSBuildTargetsTests — 11 passing on net8.0 and on net472; GitHub.Copilot.Test.Unit — 291 passing
• dotnet format --verify-no-changes
• The new test is a real regression test. It asserts every separately registered payload that an installed tool needs: the compatibility alias, copilot-runtime[.exe], runtime.node, the renamed FFI library (copilot_runtime.dll / libcopilot_runtime.*) that RuntimeConnection.ForInProcess() resolves, and a ripgrep asset. Reverting the targets change fails it, and so does dropping CopyToPublishDirectory from any single one of those registrations — each was confirmed by mutating that item alone.
• End-to-end A/B, each arm packing a locally built SDK, consuming it from an external PackAsTool project outside the repository, then installing the produced tool with dotnet tool install --tool-path and running it with all CLI overrides removed:
  • Unpatched main: 0 runtimes/*/native entries in the tool package; the installed tool crashed with the error above.
  • Patched: 67 native entries including copilot-runtime.exe and runtime.node; the installed tool started the real Copilot CLI from its own packaged assets and completed an RPC round trip.
  • Controls unchanged in both arms: pack -r <rid> and multi-RID RuntimeIdentifiers already packaged the assets before this change, so the defect is specific to packing without rebuilding.

[Copilot]

🟡 Changes recommended

The Windows net472 test build cannot resolve ZipFile without System.IO.Compression.FileSystem.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Fixes PackAsTool publishing so RID-specific packages include usable Copilot CLI runtime assets.

Changes:

• Publishes runtime assets and compatibility markers.
• Restores Unix executable permissions.
• Adds cross-platform packaging, launch tests, and CI coverage.

File summaries

File	Description
dotnet/test/Unit/RuntimeWrapperTests.cs	Tests CLI precedence and Unix executable restoration.
dotnet/test/Unit/MSBuildTargetsTests.cs	Tests RID-specific tool packaging.
dotnet/test/GitHub.Copilot.SDK.Test.csproj	Updates test-project compression references, but lacks the required System.IO.Compression.FileSystem reference for net472.
dotnet/src/Client.cs	Handles compatibility markers and Unix permissions.
dotnet/src/build/GitHub.Copilot.SDK.targets	Publishes RID-specific runtime assets.
.github/workflows/dotnet-sdk-tests.yml	Adds Unix .NET 6–8 compatibility coverage.

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 1
• Review effort level: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🟡 Changes recommended

The regression test must verify both required runtime assets.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 1
• Review effort level: Balanced

[Copilot]

🟡 Changes recommended

The regression test must assert the platform-specific renamed FFI library entry.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 1
• Review effort level: Balanced

[Copilot]

🟡 Changes recommended

The regression test must use a consistent architecture source; marker-only coverage should also be added.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

Suppressed comments (1)

dotnet/test/Unit/MSBuildTargetsTests.cs:252

• Add a marker-only tool-package case. This test passes CopilotCliBinaryPath but also seeds the runtime pair, so .copilot-explicit-cli is swept up by _CopilotRuntimeRootAsset; removing CopyToPublishDirectory from the marker's dedicated registration would still pass. With an explicit binary and no cached pair, CopilotClient relies on that marker to launch the alias instead of requiring copilot-runtime plus runtime.node, so this publish path remains unprotected.

        using var sandbox = MSBuildSandbox.Create(packAsTool: true);
        var preinstalled = sandbox.WritePreinstalledBinary("fake-cli-contents");
        sandbox.WriteRuntimeCacheAsset("prebuilds", GetReleasePlatform(), "runtime.node", "runtime");
        sandbox.WriteRuntimeCacheAsset("prebuilds", GetReleasePlatform(), RuntimeWrapperName, "wrapper");
        sandbox.WriteRuntimeCacheAsset("ripgrep", "bin", GetReleasePlatform(), "rg", "ripgrep");

• Files reviewed: 3/3 changed files
• Comments generated: 1
• Review effort level: Balanced

[Copilot]

🟡 Changes recommended

Add package coverage proving the explicit-CLI marker is included when no runtime wrapper pair is seeded.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 1
• Review effort level: Balanced

[Copilot]

🟢 Approval recommended

The fix and regression coverage are complete, with no unresolved issues.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[Copilot]

🟡 Changes recommended

Published runtime assets removed from later CLI bundles can remain stale and be packed by pack --no-build; cleanup and regression coverage are needed.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 1
• Review effort level: Balanced

[Copilot]

🟢 Approval recommended

The publish registration addresses the reported packaging failure and the regression tests cover each independently registered runtime payload.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 0 new
• Review effort level: Balanced