@alvera-ai/platform-sdk 0.13.0-next.gf8f28bd → 0.14.0

package/dist/index.d.mts

@@ -540,7 +540,7 @@ type ActionStatusUpdaterResponse = {
    */
   datalake_id: string;
   /**
-   * JSON Schema the rendered events_template output is validated against on every poll (required for restapi updaters)
+   * JSON Schema the rendered events_template output is validated against on every poll (required for restapi updaters). FLOOR: it must describe an array whose items are objects listing "external_id" in "required" — every event has to name the message it reconciles, so the events_template maps the provider's own id (messageId / id / sid) into external_id. Add whatever else your provider guarantees on top; the platform only enforces the floor.
    */
   events_output_schema?: {
     [key: string]: unknown;
@@ -575,7 +575,7 @@ type ActionStatusUpdaterResponse = {
    */
   name: string;
   /**
-   * JSON Schema the rendered pagination_context_template output is validated against on every poll — requires has_next plus any provider cursor keys (required for restapi updaters)
+   * JSON Schema the rendered pagination_context_template output is validated against on every poll (required for restapi updaters). FLOOR: it must describe an object listing "has_next" in "required" — that key is what ends the page loop. Add the provider's cursor keys on top; the platform only enforces the floor.
    */
   pagination_context_output_schema?: {
     [key: string]: unknown;