@gea-ai/extensions-sdk 0.1.260825-alpha.4 → 0.1.260827-alpha.0

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 (2) hide show
  1. package/README.md +16 -3
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -606,9 +606,15 @@ canonical Tool-output continuation API. Call the host-owned
606
606
  newly created stream as shown above. If this action is omitted, display-only
607
607
  YAML continues to render and interactive request controls are not mounted.
608
608
 
609
- Interactive YAML is joined to its request tool part only when the YAML `root`
610
- exactly matches `tool.input.requestKey`; submission then targets that part's
611
- runtime `toolCallId`.
609
+ Interactive YAML is read directly from `tool.input.yaml` without a Markdown
610
+ fence and rendered at that request tool part's position. Submission targets the
611
+ same part's runtime `toolCallId` and sends the complete current form state.
612
+ Legacy request-key parts and interactive YAML copied into assistant text are
613
+ not mounted. During `input-streaming`, partial YAML is display-only: the
614
+ renderer shows a loading placeholder or a locked last-valid preview and never
615
+ calls the host. `input-available` triggers final strict validation and unlocks
616
+ the form; the existing persisted `messageId` plus `toolCallId` submission path
617
+ is unchanged.
612
618
 
613
619
  ## Host Context, Theme, And Locale
614
620
 
@@ -694,6 +700,13 @@ resource handles from that bootstrap and exposes them as typed `app.resources`
694
700
  when the frontend uses `useExtensionApp()` from a runtime created with the
695
701
  declaration.
696
702
 
703
+ Declared resource handles are an authoring and lifecycle convenience, not an
704
+ additional permission boundary. The curated `app.gea.context` methods may also
705
+ operate on existing Context resources. Every call runs as the current signed-in
706
+ user and keeps the target Context route's ordinary API-scope, organization,
707
+ workspace, resource, and row-scope authorization; an Extension never gains
708
+ permissions that the user does not already have.
709
+
697
710
  > **Warning:** Syncing a declaration that removes resources may deactivate
698
711
  > their bindings immediately, including bindings used by the currently
699
712
  > published extension. The underlying workspace resources and their data are
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@gea-ai/extensions-sdk",
3
- "version": "0.1.260825-alpha.4",
3
+ "version": "0.1.260827-alpha.0",
4
4
  "private": false,
5
5
  "homepage": "https://musegea.com/developers/extensions",
6
6
  "license": "Apache-2.0",
@@ -52,7 +52,7 @@
52
52
  "dependencies": {
53
53
  "@tanstack/react-query": "^5.101.0",
54
54
  "zod": "4.3.6",
55
- "@gea-ai/contract": "0.1.260825-alpha.4"
55
+ "@gea-ai/contract": "0.1.260827-alpha.0"
56
56
  },
57
57
  "devDependencies": {
58
58
  "@types/react": "^19.2.0",