@theokit/tauri 1.0.0-next.2 → 1.0.0

package/CHANGELOG.md

@@ -1,5 +1,51 @@
 # Changelog — @theokit/tauri
 
+## 1.0.0
+
+### Minor Changes
+
+- ecda4ae: The agent-module parameter names what it accepts, so a wrong shape fails at compile time
+
+  `streamAgentTurnInProcess` and `compileAgentModule` took `mod: unknown`, so the contract lived only
+  in the runtime guard. A consumer whose producer became `async` handed a `Promise` straight through
+  and shipped two releases in which no turn could run — with typecheck, 1213 tests, lint and twelve CI
+  checks green. The runtime was never wrong: it refused the Promise and threw a typed error. What
+  failed was the moment.
+
+  Both now take `AgentModule`, exported alongside them and re-exported from `theokit/server/agent`.
+  The type mirrors the runtime guard rather than the fuller `CompiledAgentOptions` — an array under
+  `tools`, an object under `agents` — so it refuses nothing that compiled before.
+
+  `@theokit/tauri/sidecar`'s `runTurnToJsonl` is narrowed too: a desktop sidecar imports its agent
+  module statically, which is exactly where a type catches the mistake.
+
+  Entry points that receive a module from a path discovered at runtime keep taking `unknown`, and now
+  say so by calling the new `compileLoadedAgentModule`. Their `unknown` has a reason; before this, the
+  boundary that had one was indistinguishable from the one that did not.
+
+  Closes usetheokit/theokit#663.
+
+### Patch Changes
+
+- 3162888: **Released because its peer requirement moved, not because this package changed.**
+
+  Nothing inside `@theokit/tauri` changed in this release. It ships because `theokit` moved and this
+  package peers it, so the peer range it declares moved with it — from the 0.64 line to
+  `>=0.65.0-next.0`. For a consumer that is a real, breaking difference even though no code here
+  differs: a project pinned to `theokit@0.64.x` cannot install this version.
+
+  The version number says the same thing less clearly. A peer range that excludes versions it used to
+  admit is a breaking change to whoever installs it, which is why the bump is a major rather than a
+  patch — the code is untouched and the contract is not.
+
+  **What to do:** upgrade `theokit` to `>=0.65.0` alongside this package, or stay on the previous
+  `@theokit/tauri` while you stay on the 0.64 line. Nothing else about the Tauri glue — the
+  Channel/invoke transport, the JSONL sidecar — behaves differently.
+
+  This entry exists because the release would otherwise carry an empty section
+  ([#653](https://github.com/usetheokit/theokit/issues/653)), and an empty section is
+  indistinguishable from "nothing user-visible changed" — a claim nobody made about a major bump.
+
 ## 1.0.0-next.2
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theokit/tauri",
-  "version": "1.0.0-next.2",
+  "version": "1.0.0",
   "description": "Tauri desktop glue for TheoKit agents — the Channel/invoke transport source (webview) + the JSONL sidecar (node), over the unified client. UI is @theokit/ui; the runtime is @theokit/sdk.",
   "repository": {
     "type": "git",
@@ -39,8 +39,8 @@
     }
   },
   "devDependencies": {
-    "@theokit/presenter": "0.9.0-next.0",
-    "theokit": "0.65.0-next.3"
+    "@theokit/presenter": "0.9.0",
+    "theokit": "0.65.0"
   },
   "publishConfig": {
     "provenance": true,