@jami-studio/core 0.92.29 → 0.92.31

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/corpus/README.md CHANGED
@@ -27,5 +27,5 @@ rg -n "defineAction|useActionQuery" node_modules/@agent-native/core/corpus
27
27
 
28
28
  ## Generated Counts
29
29
 
30
- - core files: 2157
30
+ - core files: 2158
31
31
  - template files: 5114
@@ -1,5 +1,35 @@
1
1
  # @agent-native/core
2
2
 
3
+ ## 0.92.31
4
+
5
+ ### Patch Changes
6
+
7
+ - 7dda086: Agent raw-tool-input validation survives codegen-restricted runtimes. Ajv
8
+ compiles JSON-schema validators via `new Function`, which Cloudflare's
9
+ workerd rejects (`EvalError: Code generation from strings disallowed`) — on
10
+ the unified worker EVERY tool whose action entry lacks a live zod schema was
11
+ refused with "tool schema is invalid" before execution (the slides agent was
12
+ fully paralyzed; dispatch's tool-search failed every call). When Ajv cannot
13
+ compile, validation now degrades to a non-codegen structural check (object-
14
+ ness + `required` keys); the action's own parameter validation remains
15
+ authoritative at execution time. Node runtimes keep full Ajv validation.
16
+
17
+ ## 0.92.30
18
+
19
+ ### Patch Changes
20
+
21
+ - 6b64db7: Collab routes decode percent-encoded `docId` router params. Structured docIds
22
+ (`plan:<id>:<block>`) that clients percent-encode as a path segment
23
+ (`plan%3A...`) reached resolvers undecoded — prefix checks failed and the
24
+ request 404'd even though the raw-colon form worked. Malformed escape
25
+ sequences fall back to the raw value.
26
+ - 7bcb7c1: Route warmup skips `.data` prefetching when the client manifest advertises no
27
+ server loaders/actions. Static-shell deployments (Cloudflare Pages worker
28
+ without a React Router request handler) strip those flags at build time —
29
+ `.data` requests can never be served there, so warming them produced a
30
+ guaranteed 404 per hovered/visible link (the residual `chat.data` 404 seen
31
+ after the manifest strip landed). SSR deployments are unaffected.
32
+
3
33
  ## 0.92.29
4
34
 
5
35
  ### Patch Changes
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agent-native/core",
3
- "version": "0.92.29",
3
+ "version": "0.92.31",
4
4
  "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
5
5
  "homepage": "https://github.com/studio-jami/jami-studio#readme",
6
6
  "bugs": {