[hendrikmennen]

Package updates

Bumps NuGet packages that are safe for plugins. PluginCompatibilityChecker rejects a plugin when the first two parts of a declared dependency's assembly version (major.minor) differ from the host's, so minor bumps of packages that plugins declare are skipped.

Package	Version
Microsoft.Extensions.DependencyInjection(.Abstractions), Logging(.Abstractions)	10.0.9 → 10.0.13 (assembly stays 10.0.0.0)
Microsoft.Extensions.AI.Abstractions	10.2.0 → 10.11.0
DynamicData	9.4.33 → 9.5.0
SharpCompress	0.50.4 → 0.50.5
Microsoft.NET.Test.Sdk	18.0.0 → 18.11.0
Microsoft.AspNetCore.SignalR.Client	10.0.2 → 10.0.13
System.IdentityModel.Tokens.Jwt	8.15.0 → 8.23.0
System.CommandLine	2.0.2 → 2.0.13
System.IO.Ports	10.0.2 → 10.0.13
GitHub.Copilot.SDK	1.0.13 → 1.0.21 (pinned Copilot CLI 1.0.83 → 1.0.97 to match the SDK)

Skipped:

• Avalonia 12 and related packages (Dock, PanAndZoom, Svg, Xaml.Behaviors, TreeDataGrid, DataGrid): major version jump.
• Jint and OnnxRuntime: plugins declare them (OneWare.AI), and the ONNX runtime downloads are pinned to 1.28.
• RestSharp 114 and xunit.runner.visualstudio 4: major version jump.

Copilot SDK features

• New Fast option for auto routing, in the chat tier picker and the setting.
• Live tool updates: IAiFunctionProvider.ToolsChanged (default interface event, so existing plugins keep working) is raised by RegisterFunction. Open Copilot sessions push the new tool list with SetToolsAsync, debounced by 250 ms, so tools registered after a chat started become usable without starting a new chat.
• CLI update check for all chats: the "Copilot CLI update available" prompt was skipped for every BYOK chat, which includes OneWare Agents. Users of those chats could keep a CLI that doesn't match the SDK version. The check now runs for every chat. BYOK chats still skip GitHub sign-in after updating.
• The "CLI required" and "CLI update available" messages in BYOK chats now say the CLI is only the local agent runtime and that no GitHub account or Copilot subscription is needed. The Copilot CLI package description says the same.

Package refresh fix

PackageService reloaded every package source on every settings save. That includes each OneWare Cloud token refresh, which happens every few minutes. When the cloud backend was down, the cloud package source returned an empty body, so a red "Failed to load package source" error appeared right after the connection dropped.

• Only refresh on save when the package source settings changed since the last refresh.
• Token refreshes only write the settings file when the signed-in account changes.

Validation

• dotnet build OneWare.slnx succeeds.
• dotnet test OneWare.slnx passes, including new tests in AiFunctionProviderTests and PackageServiceTests.
• Not run in the app.