@jami-studio/core 0.92.30 → 0.92.32

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 (33) hide show
  1. package/corpus/README.md +1 -1
  2. package/corpus/core/CHANGELOG.md +20 -0
  3. package/corpus/core/package.json +1 -1
  4. package/corpus/core/src/agent/production-agent.ts +7360 -7302
  5. package/corpus/core/src/deploy/build.ts +4193 -4127
  6. package/corpus/core/src/file-upload/types.ts +9 -0
  7. package/corpus/templates/analytics/changelog/2026-07-11-tracking-and-session-replay-ingest-endpoints-are-reachable-f.md +6 -0
  8. package/corpus/templates/analytics/package.json +9 -0
  9. package/corpus/templates/clips/actions/create-recording.ts +16 -1
  10. package/corpus/templates/clips/app/components/recorder/recorder-engine.ts +60 -14
  11. package/corpus/templates/clips/app/routes/record.tsx +35 -9
  12. package/corpus/templates/clips/changelog/2026-07-11-uploads-now-stream-straight-to-s3-compatible-storage-r2-s3-m.md +6 -0
  13. package/corpus/templates/clips/server/lib/s3-upload-provider.ts +256 -0
  14. package/corpus/templates/clips/server/lib/streaming-upload-mode.ts +9 -3
  15. package/corpus/templates/clips/server/lib/upload-chunk-limits.ts +19 -0
  16. package/corpus/templates/clips/server/routes/api/uploads/[recordingId]/chunk.post.ts +15 -4
  17. package/corpus/templates/clips/server/routes/api/uploads/[recordingId]/reset-chunks.post.ts +49 -1
  18. package/dist/agent/production-agent.d.ts +15 -1
  19. package/dist/agent/production-agent.d.ts.map +1 -1
  20. package/dist/agent/production-agent.js +61 -15
  21. package/dist/agent/production-agent.js.map +1 -1
  22. package/dist/collab/routes.d.ts +1 -1
  23. package/dist/deploy/build.d.ts +21 -1
  24. package/dist/deploy/build.d.ts.map +1 -1
  25. package/dist/deploy/build.js +736 -676
  26. package/dist/deploy/build.js.map +1 -1
  27. package/dist/file-upload/actions/upload-image.d.ts +1 -1
  28. package/dist/file-upload/types.d.ts +9 -0
  29. package/dist/file-upload/types.d.ts.map +1 -1
  30. package/dist/file-upload/types.js.map +1 -1
  31. package/dist/provider-api/corpus-jobs.d.ts +2 -2
  32. package/dist/resources/handlers.d.ts +2 -2
  33. 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,25 @@
1
1
  # @agent-native/core
2
2
 
3
+ ## 0.92.32
4
+
5
+ ### Patch Changes
6
+
7
+ - 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.
8
+
9
+ ## 0.92.31
10
+
11
+ ### Patch Changes
12
+
13
+ - 7dda086: Agent raw-tool-input validation survives codegen-restricted runtimes. Ajv
14
+ compiles JSON-schema validators via `new Function`, which Cloudflare's
15
+ workerd rejects (`EvalError: Code generation from strings disallowed`) — on
16
+ the unified worker EVERY tool whose action entry lacks a live zod schema was
17
+ refused with "tool schema is invalid" before execution (the slides agent was
18
+ fully paralyzed; dispatch's tool-search failed every call). When Ajv cannot
19
+ compile, validation now degrades to a non-codegen structural check (object-
20
+ ness + `required` keys); the action's own parameter validation remains
21
+ authoritative at execution time. Node runtimes keep full Ajv validation.
22
+
3
23
  ## 0.92.30
4
24
 
5
25
  ### Patch Changes
package/corpus/core/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agent-native/core",
3
- "version": "0.92.30",
3
+ "version": "0.92.32",
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": {