@smartspace/api-client 0.1.0-pr.1112.30f628d → 0.1.0-pr.1112.55f7257

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.
@@ -725,21 +725,24 @@ const getSmartSpaceAdminAPI = () => {
725
725
  };
726
726
  /**
727
727
  * Frames are unnamed SSE `data:` events, each carrying a `kind`:
728
- `snapshot` (rows + total; always first), `events` (rows that just
729
- changed, same shape), `lagged` and `gap` (both mean re-read; the
730
- stream stays attached), and `unavailable` (the feature is not enabled
731
- on the install; sent once, then the stream ends — do not retry).
728
+ `snapshot` (rows + total; the AI side sends it first), `events`
729
+ (rows that just changed, same shape), `lagged` and `gap` (both
730
+ mean re-read; the stream stays attached), and `unavailable` (the
731
+ feature is not enabled on the install; sent once, then the stream ends —
732
+ do not retry).
732
733
 
733
734
 
734
- The client tracks no offset. The AI side subscribes to its change stream
735
- before reading the log, so nothing can land between the two, and a
736
- reconnect simply starts with a fresh snapshot.
735
+ The client tracks no offset. The AI side attaches to its change stream
736
+ before it reads the log, so rows written between the two arrive twice
737
+ rather than not at all, and where it could not, or lost rows later, it
738
+ sends `gap` or `lagged`. A reconnect simply starts with a fresh
739
+ snapshot. This API relays that contract; it does not enforce it.
737
740
 
738
741
 
739
- Rows carry structure and timings, never payloads — expand a step through
740
- M:SmartSpace.App.ConfigApi.Controllers.FlowRunsController.GetStepExecution(System.Guid,System.Guid) for those. Only persisted state appears
741
- here: LLM token deltas are never written down, so they are not on this
742
- stream and cannot be put on it.
742
+ The AI side sends rows with structure and timings and with value payloads
743
+ left out — expand a step through M:SmartSpace.App.ConfigApi.Controllers.FlowRunsController.GetStepExecution(System.Guid,System.Guid) for those —
744
+ and sends only persisted state, which does not include LLM token deltas.
745
+ Nothing here strips a payload: a row is relayed as it arrives.
743
746
 
744
747
 
745
748
  This endpoint does not return 501. The AI side answers 501 when the
@@ -2527,21 +2527,24 @@ export declare const flowRunsCancelFlowRunParams: zod.ZodObject<{
2527
2527
  }, zod.core.$strict>;
2528
2528
  /**
2529
2529
  * Frames are unnamed SSE `data:` events, each carrying a `kind`:
2530
- `snapshot` (rows + total; always first), `events` (rows that just
2531
- changed, same shape), `lagged` and `gap` (both mean re-read; the
2532
- stream stays attached), and `unavailable` (the feature is not enabled
2533
- on the install; sent once, then the stream ends — do not retry).
2530
+ `snapshot` (rows + total; the AI side sends it first), `events`
2531
+ (rows that just changed, same shape), `lagged` and `gap` (both
2532
+ mean re-read; the stream stays attached), and `unavailable` (the
2533
+ feature is not enabled on the install; sent once, then the stream ends —
2534
+ do not retry).
2534
2535
 
2535
2536
 
2536
- The client tracks no offset. The AI side subscribes to its change stream
2537
- before reading the log, so nothing can land between the two, and a
2538
- reconnect simply starts with a fresh snapshot.
2537
+ The client tracks no offset. The AI side attaches to its change stream
2538
+ before it reads the log, so rows written between the two arrive twice
2539
+ rather than not at all, and where it could not, or lost rows later, it
2540
+ sends `gap` or `lagged`. A reconnect simply starts with a fresh
2541
+ snapshot. This API relays that contract; it does not enforce it.
2539
2542
 
2540
2543
 
2541
- Rows carry structure and timings, never payloads — expand a step through
2542
- M:SmartSpace.App.ConfigApi.Controllers.FlowRunsController.GetStepExecution(System.Guid,System.Guid) for those. Only persisted state appears
2543
- here: LLM token deltas are never written down, so they are not on this
2544
- stream and cannot be put on it.
2544
+ The AI side sends rows with structure and timings and with value payloads
2545
+ left out — expand a step through M:SmartSpace.App.ConfigApi.Controllers.FlowRunsController.GetStepExecution(System.Guid,System.Guid) for those —
2546
+ and sends only persisted state, which does not include LLM token deltas.
2547
+ Nothing here strips a payload: a row is relayed as it arrives.
2545
2548
 
2546
2549
 
2547
2550
  This endpoint does not return 501. The AI side answers 501 when the
@@ -2009,21 +2009,24 @@ exports.flowRunsCancelFlowRunParams = zod_1.default.strictObject({
2009
2009
  });
2010
2010
  /**
2011
2011
  * Frames are unnamed SSE `data:` events, each carrying a `kind`:
2012
- `snapshot` (rows + total; always first), `events` (rows that just
2013
- changed, same shape), `lagged` and `gap` (both mean re-read; the
2014
- stream stays attached), and `unavailable` (the feature is not enabled
2015
- on the install; sent once, then the stream ends — do not retry).
2012
+ `snapshot` (rows + total; the AI side sends it first), `events`
2013
+ (rows that just changed, same shape), `lagged` and `gap` (both
2014
+ mean re-read; the stream stays attached), and `unavailable` (the
2015
+ feature is not enabled on the install; sent once, then the stream ends —
2016
+ do not retry).
2016
2017
 
2017
2018
 
2018
- The client tracks no offset. The AI side subscribes to its change stream
2019
- before reading the log, so nothing can land between the two, and a
2020
- reconnect simply starts with a fresh snapshot.
2019
+ The client tracks no offset. The AI side attaches to its change stream
2020
+ before it reads the log, so rows written between the two arrive twice
2021
+ rather than not at all, and where it could not, or lost rows later, it
2022
+ sends `gap` or `lagged`. A reconnect simply starts with a fresh
2023
+ snapshot. This API relays that contract; it does not enforce it.
2021
2024
 
2022
2025
 
2023
- Rows carry structure and timings, never payloads — expand a step through
2024
- M:SmartSpace.App.ConfigApi.Controllers.FlowRunsController.GetStepExecution(System.Guid,System.Guid) for those. Only persisted state appears
2025
- here: LLM token deltas are never written down, so they are not on this
2026
- stream and cannot be put on it.
2026
+ The AI side sends rows with structure and timings and with value payloads
2027
+ left out — expand a step through M:SmartSpace.App.ConfigApi.Controllers.FlowRunsController.GetStepExecution(System.Guid,System.Guid) for those —
2028
+ and sends only persisted state, which does not include LLM token deltas.
2029
+ Nothing here strips a payload: a row is relayed as it arrives.
2027
2030
 
2028
2031
 
2029
2032
  This endpoint does not return 501. The AI side answers 501 when the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@smartspace/api-client",
3
- "version": "0.1.0-pr.1112.30f628d",
3
+ "version": "0.1.0-pr.1112.55f7257",
4
4
  "description": "Generated TypeScript client for SmartSpace APIs",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",