@vrplatform/api 1.3.1-stage.76 → 1.3.1-stage.84

package/package.json

@@ -3,7 +3,7 @@
   "publishConfig": {
     "access": "public"
   },
-  "version": "1.3.1-stage.76",
+  "version": "1.3.1-stage.84",
   "description": "",
   "main": "build/main/index.js",
   "module": "build/module/index.js",

package/src/generated/v1.ts

@@ -3717,7 +3717,7 @@ export interface paths {
          */
         get: operations["getListingsByIdOpeningBalance"];
         /**
-         * @description Update a listing opening balance. Setting an existing balance to zero can cross a statement-period boundary; books closing and direct owner-statement attachments still apply.
+         * @description Update a listing opening balance. A balance may cross imported pre-cutover statement history, and zero may cross an ordinary statement-period boundary; books closing, direct statement attachments, and stored live statements still apply.
          *
          *     Required scope: general-ledger:write
          */
@@ -6451,7 +6451,7 @@ export interface paths {
          */
         get: operations["getStatementsById"];
         /**
-         * @description Update an owner statement status (draft, inReview, published). Moving to a finalized status attaches the period journal entries to the statement and locks writes that reference the same ownership period; moving back to draft detaches them again. Submitting the current status never rewrites journal attachments. If the cached detail is current, the request is accounting-read-only; otherwise it refreshes the statement projection. A published request with emailDelivery still schedules the requested owner delivery. Transitions are rejected when the statement has blocking issues, when a later statement for the period is already finalized, or when a prior month is still unfinalized. For scoped API credentials, both publishing and moving a published statement away from published require the statements:publish scope. Publishing can optionally email owners via emailDelivery. Supports dryRun. See https://docs.vrplatform.app/guides/build/statements#status-transitions.
+         * @description Update an owner statement status (draft, inReview, published). Moving to a finalized status attaches the period journal entries to the statement and locks writes that reference the same ownership period; moving back to draft detaches them again. Imported historical snapshots cannot move to draft; re-post the import to replace their data. Submitting the current status never rewrites journal attachments. If the cached detail is current, the request is accounting-read-only; otherwise it refreshes the statement projection. A published request with emailDelivery still schedules the requested owner delivery. Transitions are rejected when the statement has blocking issues, when a later statement for the period is already finalized, or when a prior month is still unfinalized. For scoped API credentials, both publishing and moving a published statement away from published require the statements:publish scope. Publishing can optionally email owners via emailDelivery. Supports dryRun. See https://docs.vrplatform.app/guides/build/statements#status-transitions.
          *
          *     Required scope: statements:write
          */