compatibility.json

{
  "latestTested": "0.1.7-rc.2",
  "acceptedRuntimeRange": ">=0.1.1-rc.2 <0.2.0-0",
  "supported": [
    "0.1.1-rc.2",
    "0.1.2-alpha.2",
    "0.1.2-alpha.3",
    "0.1.2-alpha.5",
    "0.1.5-alpha.1",
    "0.1.5-alpha.2",
    "0.1.5-rc.1",
    "0.1.5-rc.2",
    "0.1.5-rc.3",
    "0.1.6-alpha.1",
    "0.1.6-alpha.2",
    "0.1.7-alpha.1",
    "0.1.7-alpha.2",
    "0.1.7-rc.1",
    "0.1.7-rc.2"
  ],
  "piAi": "0.85.1",
  "validation": {
    "0.1.5-alpha.1": "58 automated tests, real Cordis Loader/Connection activation with dynamic trustedHosts interpolation, and RPC authentication/disposal checks. User confirmed successful DSH startup with the corrected webRuntime/webServer dependency list; no live model or full account-flow verification.",
    "0.1.5-alpha.2": "Offline tests against the published host packages cover resolution and call preparation of every advertised Kimi model using the real PiAiAdapter, Cordis Loader/Connection activation and RPC authentication/disposal, and the actual adapter retry policy through the real retry executor and Session event validation (six retryable codes, finite backoff, two-retry limit, original failure preservation, provider-directed delays, and cancellation). No live model calls, real credential reads, or full GUI/account-flow verification.",
    "0.1.7-rc.1": "Offline tests run against the published 0.1.7-rc.1 host packages, the same version as the desktop app. They cover the desktop installer's peer-range gate, activation without the removed settings.register API, model resolution and call preparation through the real PiAiAdapter, Cordis Loader/Connection activation (including the legacy 0.1.2-alpha.5 Connection), RPC authentication/disposal, and the adapter retry policy. A scratch profile boot confirms the account route mounts. No live model calls, real credential reads, or desktop GUI verification.",
    "0.1.7-rc.2": "The desktop app auto-updated to this release. Its app-boot compatibility gate accepts the declared peer range, the client modules this plugin injects are all present, and `@deepseek-ai/dsh-llm` / `@deepseek-ai/dsh-llm-pi-ai` still export `LlmError`, `resolveRetryPolicy`, and `PiAiAdapter`. The settings service still has no `register`, so the volatile-Config path is the one that runs. A scratch profile boot on this kernel activates the account route. The device authorization request was also exercised against the live Kimi endpoint; the token exchange is covered by offline tests only, including the compressed-body and classified-failure paths. No live model calls or credential reads."
  }
}