@jami-studio/core 0.92.28 → 0.92.30

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,38 @@
1
1
  # @agent-native/core
2
2
 
3
+ ## 0.92.30
4
+
5
+ ### Patch Changes
6
+
7
+ - 6b64db7: Collab routes decode percent-encoded `docId` router params. Structured docIds
8
+ (`plan:<id>:<block>`) that clients percent-encode as a path segment
9
+ (`plan%3A...`) reached resolvers undecoded — prefix checks failed and the
10
+ request 404'd even though the raw-colon form worked. Malformed escape
11
+ sequences fall back to the raw value.
12
+ - 7bcb7c1: Route warmup skips `.data` prefetching when the client manifest advertises no
13
+ server loaders/actions. Static-shell deployments (Cloudflare Pages worker
14
+ without a React Router request handler) strip those flags at build time —
15
+ `.data` requests can never be served there, so warming them produced a
16
+ guaranteed 404 per hovered/visible link (the residual `chat.data` 404 seen
17
+ after the manifest strip landed). SSR deployments are unaffected.
18
+
19
+ ## 0.92.29
20
+
21
+ ### Patch Changes
22
+
23
+ - b9c3561: Cloudflare Pages static-shell deployments: strip `hasLoader`/`hasAction` from
24
+ the React Router client manifest at build time. The CF worker intentionally
25
+ ships no React Router request handler (static app shell keeps the merged
26
+ worker under the platform bundle-size limit), but templates build with
27
+ `ssr: true`, so the hydrated router issued single-fetch `GET <route>.data`
28
+ requests on every client-side navigation into a route with a server loader —
29
+ nothing served them, they 404'd, and React Router tripped the route
30
+ ErrorBoundary (`No result found for routeId "..."`), breaking in-app
31
+ navigation across every app of a unified workspace deployment. With the
32
+ server-only flags stripped, client-side navigation behaves exactly like the
33
+ initial static-shell load: render with client data only. `hasClientLoader`/
34
+ `hasClientAction` are preserved; other presets are unaffected.
35
+
3
36
  ## 0.92.28
4
37
 
5
38
  ### Patch Changes
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agent-native/core",
3
- "version": "0.92.28",
3
+ "version": "0.92.30",
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": {