feat: add setSelectedGraph and mark selectGraph deprecated

robosystems_client/api/graphs/select_graph.py

@@ -93,6 +93,9 @@ def sync_detailed(
 ) -> Response[ErrorResponse | HTTPValidationError | SuccessResponse]:
   """Select Graph
 
+   Deprecated: use `PUT /v1/user/selected-graph`, which writes the same selection. Remembers the graph
+  as the caller's current one.
+
   Args:
       graph_id (str):
 
@@ -122,6 +125,9 @@ def sync(
 ) -> ErrorResponse | HTTPValidationError | SuccessResponse | None:
   """Select Graph
 
+   Deprecated: use `PUT /v1/user/selected-graph`, which writes the same selection. Remembers the graph
+  as the caller's current one.
+
   Args:
       graph_id (str):
 
@@ -146,6 +152,9 @@ async def asyncio_detailed(
 ) -> Response[ErrorResponse | HTTPValidationError | SuccessResponse]:
   """Select Graph
 
+   Deprecated: use `PUT /v1/user/selected-graph`, which writes the same selection. Remembers the graph
+  as the caller's current one.
+
   Args:
       graph_id (str):
 
@@ -173,6 +182,9 @@ async def asyncio(
 ) -> ErrorResponse | HTTPValidationError | SuccessResponse | None:
   """Select Graph
 
+   Deprecated: use `PUT /v1/user/selected-graph`, which writes the same selection. Remembers the graph
+  as the caller's current one.
+
   Args:
       graph_id (str):
 

robosystems_client/api/operations/stream_operation_events.py

@@ -121,8 +121,9 @@ def sync_detailed(
 
   Args:
       operation_id (str): Operation identifier from initial submission
-      from_sequence (int | Unset): Start streaming from this sequence number (0 = from
-          beginning) Default: 0.
+      from_sequence (int | Unset): Replay stored events from this sequence number, then stream
+          live ones. A running operation replays nothing at 0 (live events only); a settled one
+          replays its history from here (0 = all) and closes. Default: 0.
       token (None | str | Unset): JWT token for SSE authentication
       authorization (None | str | Unset):
 
@@ -163,8 +164,9 @@ def sync(
 
   Args:
       operation_id (str): Operation identifier from initial submission
-      from_sequence (int | Unset): Start streaming from this sequence number (0 = from
-          beginning) Default: 0.
+      from_sequence (int | Unset): Replay stored events from this sequence number, then stream
+          live ones. A running operation replays nothing at 0 (live events only); a settled one
+          replays its history from here (0 = all) and closes. Default: 0.
       token (None | str | Unset): JWT token for SSE authentication
       authorization (None | str | Unset):
 
@@ -200,8 +202,9 @@ async def asyncio_detailed(
 
   Args:
       operation_id (str): Operation identifier from initial submission
-      from_sequence (int | Unset): Start streaming from this sequence number (0 = from
-          beginning) Default: 0.
+      from_sequence (int | Unset): Replay stored events from this sequence number, then stream
+          live ones. A running operation replays nothing at 0 (live events only); a settled one
+          replays its history from here (0 = all) and closes. Default: 0.
       token (None | str | Unset): JWT token for SSE authentication
       authorization (None | str | Unset):
 
@@ -240,8 +243,9 @@ async def asyncio(
 
   Args:
       operation_id (str): Operation identifier from initial submission
-      from_sequence (int | Unset): Start streaming from this sequence number (0 = from
-          beginning) Default: 0.
+      from_sequence (int | Unset): Replay stored events from this sequence number, then stream
+          live ones. A running operation replays nothing at 0 (live events only); a settled one
+          replays its history from here (0 = all) and closes. Default: 0.
       token (None | str | Unset): JWT token for SSE authentication
       authorization (None | str | Unset):
 

robosystems_client/api/robo_ledger_ledger_events/execute_event_block.py

@@ -113,11 +113,12 @@ def sync_detailed(
 ) -> Response[ErrorResponse | OperationEnvelopeExecuteEventBlockResponse]:
   """Execute Event Block
 
-   For events on a connection with write_policy='qb_authoritative' or 'hybrid', publish the captured GL
-  plan to the source-of-truth system (QuickBooks). Captures qb_txn_id on
-  event.metadata.qb_external_id, transitions status to 'fulfilled' (or 'pending' on rejection), and
-  promotes draft GL rows to 'posted'. Native-policy events fast-path through with no QB write —
-  RoboSystems is the system of record.
+   For events on a connection with write_policy='qb_authoritative' or 'hybrid', publish the event's
+  draft GL entries to the source-of-truth system (QuickBooks), each as its own JournalEntry. Records
+  the QuickBooks ids per entry on event.metadata.qb_entry_ids and promotes the published entries to
+  'posted'; the event goes 'fulfilled' once no draft remains, or 'pending' on rejection (what landed
+  is kept). Native-policy events fast-path through with no QB write — RoboSystems is the system of
+  record.
 
   **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
   return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
@@ -129,11 +130,12 @@ def sync_detailed(
           system.
 
           For events on a connection with `write_policy='qb_authoritative'`
-          (or `'hybrid'`), this triggers a synchronous write to QuickBooks
-          via the QB API. The returned `qb_txn_id` lands on
-          `event.metadata.qb_external_id` and the event transitions to
-          `committed` (in flight) → `fulfilled` (QB accepted) or `pending`
-          (QB rejected).
+          (or `'hybrid'`), this triggers a synchronous write to QuickBooks:
+          each draft entry posts as its own JournalEntry, with the entry id as
+          the RequestId, and its QuickBooks id is recorded per entry on
+          `event.metadata.qb_entry_ids`. The event goes `fulfilled` once no
+          draft remains, or `pending` when QuickBooks rejects an entry (what
+          landed is kept).
 
           `'native'`-policy events fast-path through with no QB write —
           RoboSystems IS the source of truth, no outbound publish needed.
@@ -168,11 +170,12 @@ def sync(
 ) -> ErrorResponse | OperationEnvelopeExecuteEventBlockResponse | None:
   """Execute Event Block
 
-   For events on a connection with write_policy='qb_authoritative' or 'hybrid', publish the captured GL
-  plan to the source-of-truth system (QuickBooks). Captures qb_txn_id on
-  event.metadata.qb_external_id, transitions status to 'fulfilled' (or 'pending' on rejection), and
-  promotes draft GL rows to 'posted'. Native-policy events fast-path through with no QB write —
-  RoboSystems is the system of record.
+   For events on a connection with write_policy='qb_authoritative' or 'hybrid', publish the event's
+  draft GL entries to the source-of-truth system (QuickBooks), each as its own JournalEntry. Records
+  the QuickBooks ids per entry on event.metadata.qb_entry_ids and promotes the published entries to
+  'posted'; the event goes 'fulfilled' once no draft remains, or 'pending' on rejection (what landed
+  is kept). Native-policy events fast-path through with no QB write — RoboSystems is the system of
+  record.
 
   **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
   return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
@@ -184,11 +187,12 @@ def sync(
           system.
 
           For events on a connection with `write_policy='qb_authoritative'`
-          (or `'hybrid'`), this triggers a synchronous write to QuickBooks
-          via the QB API. The returned `qb_txn_id` lands on
-          `event.metadata.qb_external_id` and the event transitions to
-          `committed` (in flight) → `fulfilled` (QB accepted) or `pending`
-          (QB rejected).
+          (or `'hybrid'`), this triggers a synchronous write to QuickBooks:
+          each draft entry posts as its own JournalEntry, with the entry id as
+          the RequestId, and its QuickBooks id is recorded per entry on
+          `event.metadata.qb_entry_ids`. The event goes `fulfilled` once no
+          draft remains, or `pending` when QuickBooks rejects an entry (what
+          landed is kept).
 
           `'native'`-policy events fast-path through with no QB write —
           RoboSystems IS the source of truth, no outbound publish needed.
@@ -218,11 +222,12 @@ async def asyncio_detailed(
 ) -> Response[ErrorResponse | OperationEnvelopeExecuteEventBlockResponse]:
   """Execute Event Block
 
-   For events on a connection with write_policy='qb_authoritative' or 'hybrid', publish the captured GL
-  plan to the source-of-truth system (QuickBooks). Captures qb_txn_id on
-  event.metadata.qb_external_id, transitions status to 'fulfilled' (or 'pending' on rejection), and
-  promotes draft GL rows to 'posted'. Native-policy events fast-path through with no QB write —
-  RoboSystems is the system of record.
+   For events on a connection with write_policy='qb_authoritative' or 'hybrid', publish the event's
+  draft GL entries to the source-of-truth system (QuickBooks), each as its own JournalEntry. Records
+  the QuickBooks ids per entry on event.metadata.qb_entry_ids and promotes the published entries to
+  'posted'; the event goes 'fulfilled' once no draft remains, or 'pending' on rejection (what landed
+  is kept). Native-policy events fast-path through with no QB write — RoboSystems is the system of
+  record.
 
   **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
   return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
@@ -234,11 +239,12 @@ async def asyncio_detailed(
           system.
 
           For events on a connection with `write_policy='qb_authoritative'`
-          (or `'hybrid'`), this triggers a synchronous write to QuickBooks
-          via the QB API. The returned `qb_txn_id` lands on
-          `event.metadata.qb_external_id` and the event transitions to
-          `committed` (in flight) → `fulfilled` (QB accepted) or `pending`
-          (QB rejected).
+          (or `'hybrid'`), this triggers a synchronous write to QuickBooks:
+          each draft entry posts as its own JournalEntry, with the entry id as
+          the RequestId, and its QuickBooks id is recorded per entry on
+          `event.metadata.qb_entry_ids`. The event goes `fulfilled` once no
+          draft remains, or `pending` when QuickBooks rejects an entry (what
+          landed is kept).
 
           `'native'`-policy events fast-path through with no QB write —
           RoboSystems IS the source of truth, no outbound publish needed.
@@ -271,11 +277,12 @@ async def asyncio(
 ) -> ErrorResponse | OperationEnvelopeExecuteEventBlockResponse | None:
   """Execute Event Block
 
-   For events on a connection with write_policy='qb_authoritative' or 'hybrid', publish the captured GL
-  plan to the source-of-truth system (QuickBooks). Captures qb_txn_id on
-  event.metadata.qb_external_id, transitions status to 'fulfilled' (or 'pending' on rejection), and
-  promotes draft GL rows to 'posted'. Native-policy events fast-path through with no QB write —
-  RoboSystems is the system of record.
+   For events on a connection with write_policy='qb_authoritative' or 'hybrid', publish the event's
+  draft GL entries to the source-of-truth system (QuickBooks), each as its own JournalEntry. Records
+  the QuickBooks ids per entry on event.metadata.qb_entry_ids and promotes the published entries to
+  'posted'; the event goes 'fulfilled' once no draft remains, or 'pending' on rejection (what landed
+  is kept). Native-policy events fast-path through with no QB write — RoboSystems is the system of
+  record.
 
   **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
   return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
@@ -287,11 +294,12 @@ async def asyncio(
           system.
 
           For events on a connection with `write_policy='qb_authoritative'`
-          (or `'hybrid'`), this triggers a synchronous write to QuickBooks
-          via the QB API. The returned `qb_txn_id` lands on
-          `event.metadata.qb_external_id` and the event transitions to
-          `committed` (in flight) → `fulfilled` (QB accepted) or `pending`
-          (QB rejected).
+          (or `'hybrid'`), this triggers a synchronous write to QuickBooks:
+          each draft entry posts as its own JournalEntry, with the entry id as
+          the RequestId, and its QuickBooks id is recorded per entry on
+          `event.metadata.qb_entry_ids`. The event goes `fulfilled` once no
+          draft remains, or `pending` when QuickBooks rejects an entry (what
+          landed is kept).
 
           `'native'`-policy events fast-path through with no QB write —
           RoboSystems IS the source of truth, no outbound publish needed.