@jami-studio/core 0.92.31 → 0.92.33

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.
Files changed (37) hide show
  1. package/corpus/README.md +1 -1
  2. package/corpus/core/CHANGELOG.md +12 -0
  3. package/corpus/core/package.json +1 -1
  4. package/corpus/core/src/deploy/build.ts +4234 -4127
  5. package/corpus/core/src/file-upload/types.ts +9 -0
  6. package/corpus/core/src/shared/global-scope.ts +32 -0
  7. package/corpus/core/src/shared/workspace-app-audience.ts +14 -3
  8. package/corpus/templates/analytics/changelog/2026-07-11-tracking-and-session-replay-ingest-endpoints-are-reachable-f.md +6 -0
  9. package/corpus/templates/analytics/package.json +9 -0
  10. package/corpus/templates/clips/actions/create-recording.ts +16 -1
  11. package/corpus/templates/clips/app/components/recorder/recorder-engine.ts +60 -14
  12. package/corpus/templates/clips/app/routes/record.tsx +35 -9
  13. package/corpus/templates/clips/changelog/2026-07-11-uploads-now-stream-straight-to-s3-compatible-storage-r2-s3-m.md +6 -0
  14. package/corpus/templates/clips/server/lib/s3-upload-provider.ts +256 -0
  15. package/corpus/templates/clips/server/lib/streaming-upload-mode.ts +9 -3
  16. package/corpus/templates/clips/server/lib/upload-chunk-limits.ts +19 -0
  17. package/corpus/templates/clips/server/routes/api/uploads/[recordingId]/chunk.post.ts +15 -4
  18. package/corpus/templates/clips/server/routes/api/uploads/[recordingId]/reset-chunks.post.ts +49 -1
  19. package/dist/deploy/build.d.ts +37 -1
  20. package/dist/deploy/build.d.ts.map +1 -1
  21. package/dist/deploy/build.js +769 -676
  22. package/dist/deploy/build.js.map +1 -1
  23. package/dist/file-upload/types.d.ts +9 -0
  24. package/dist/file-upload/types.d.ts.map +1 -1
  25. package/dist/file-upload/types.js.map +1 -1
  26. package/dist/notifications/routes.d.ts +1 -1
  27. package/dist/provider-api/corpus-jobs.d.ts +2 -2
  28. package/dist/resources/handlers.d.ts +1 -1
  29. package/dist/server/agent-engine-api-key-route.d.ts +1 -1
  30. package/dist/shared/global-scope.d.ts +4 -0
  31. package/dist/shared/global-scope.d.ts.map +1 -1
  32. package/dist/shared/global-scope.js +27 -0
  33. package/dist/shared/global-scope.js.map +1 -1
  34. package/dist/shared/workspace-app-audience.d.ts.map +1 -1
  35. package/dist/shared/workspace-app-audience.js +12 -3
  36. package/dist/shared/workspace-app-audience.js.map +1 -1
  37. package/package.json +1 -1
package/corpus/README.md CHANGED
@@ -28,4 +28,4 @@ rg -n "defineAction|useActionQuery" node_modules/@agent-native/core/corpus
28
28
  ## Generated Counts
29
29
 
30
30
  - core files: 2158
31
- - template files: 5114
31
+ - template files: 5117
package/corpus/core/CHANGELOG.md CHANGED
@@ -1,5 +1,17 @@
1
1
  # @agent-native/core
2
2
 
3
+ ## 0.92.33
4
+
5
+ ### Patch Changes
6
+
7
+ - b400c4a: Fix a unified-worker regression in 0.92.32's workspace env baking: per-app keys (app id, base path, audience, public/protected route lists) were baked into the SHARED `process.env` of the single Cloudflare isolate, so the first app's scope-init poisoned every sibling — all apps stripped request paths against dispatch's base path and 401'd their framework routes (A2A, auth/session). Per-app keys now travel through the per-module-graph scope (`setModuleGraphEnvDefaults` in `_scope-init.js`, read via `getModuleGraphEnvDefault` fallbacks in the audience/route-access env readers), the same isolation mechanism as the 0.92.28 registry scoping. Only workspace-identical keys (`AGENT_NATIVE_WORKSPACE`, the workspace-apps manifest JSON) remain `process.env` defaults.
8
+
9
+ ## 0.92.32
10
+
11
+ ### Patch Changes
12
+
13
+ - a61a17a: Cloudflare workspace deploys now bake the per-app workspace env (workspace-apps manifest, app id, base path, audience, public/protected route lists) into the generated `_scope-init.js` as `process.env` defaults. workerd has no filesystem and no ambient build env, so agent discovery could never see sibling workspace apps on the unified worker — `ask_app`/`call-agent` resolved apps to the builtin hosted prod URLs and failed with "internal error". Netlify's generated function entry already did this (`setBasePathEnv`); this is the Cloudflare-preset equivalent. Runtime bindings still win over baked defaults. Also adds an optional `resumable.preferredChunkBytes` to `FileUploadProvider` so S3-compatible providers can negotiate multipart part sizes (uniform >= 5 MiB) with upload clients.
14
+
3
15
  ## 0.92.31
4
16
 
5
17
  ### Patch Changes
package/corpus/core/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agent-native/core",
3
- "version": "0.92.31",
3
+ "version": "0.92.33",
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": {