@robosystems/client 0.5.8 → 0.5.10

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.
package/types.gen.d.ts CHANGED
@@ -364,6 +364,132 @@ export type AvailableGraphTiersResponse = {
364
364
  */
365
365
  tiers: Array<GraphTierInfo>;
366
366
  };
367
+ /**
368
+ * BackfillPeriodOutcome
369
+ *
370
+ * Per-month result of a plan-history backfill pass.
371
+ */
372
+ export type BackfillPeriodOutcome = {
373
+ /**
374
+ * Period
375
+ *
376
+ * The month, in YYYY-MM
377
+ */
378
+ period: string;
379
+ /**
380
+ * Status
381
+ *
382
+ * stamped: reopen → reclose completed. skipped_drafts: the month holds draft entries the backfill refuses to post — review via list-period-drafts, then close-period or re-run. failed: the reclose raised; processing halted (see detail).
383
+ */
384
+ status: string;
385
+ /**
386
+ * Statements Stamped
387
+ *
388
+ * Whether the reclose stamped canonical statement FactSets. False with a statement_stamp_note soft-skip when reporting isn't set up.
389
+ */
390
+ statements_stamped?: boolean;
391
+ /**
392
+ * Statement Stamp Note
393
+ *
394
+ * Soft-skip reason when statements_stamped is false
395
+ */
396
+ statement_stamp_note?: string | null;
397
+ /**
398
+ * Statement Rule Summary
399
+ *
400
+ * Statement-rule verification tally for the month's stamped sets (pass/fail/error/skipped); None when no rules ran.
401
+ */
402
+ statement_rule_summary?: {
403
+ [key: string]: number;
404
+ } | null;
405
+ /**
406
+ * Detail
407
+ *
408
+ * Human-readable detail for skipped/failed months
409
+ */
410
+ detail?: string | null;
411
+ };
412
+ /**
413
+ * BackfillPlanHistoryOperation
414
+ *
415
+ * Compile monthly statement history behind the close boundary.
416
+ */
417
+ export type BackfillPlanHistoryOperation = {
418
+ /**
419
+ * Start Period
420
+ *
421
+ * YYYY-MM period to backfill from. Clamped to the earliest month with ledger data; defaults to that month when omitted. Must be on or before `closed_through`.
422
+ */
423
+ start_period?: string | null;
424
+ /**
425
+ * Max Periods
426
+ *
427
+ * Maximum months to restamp in this call. Each month runs a full reopen → reclose cycle; keep chunks modest and loop on `remaining_periods`.
428
+ */
429
+ max_periods?: number;
430
+ /**
431
+ * Allow Stale Sync
432
+ *
433
+ * Override the sync-currency gate on each reclose. Historical months predate the last sync in the normal case, so this is rarely needed.
434
+ */
435
+ allow_stale_sync?: boolean;
436
+ /**
437
+ * Restamp
438
+ *
439
+ * Also re-derive months that ALREADY have canonical statement sets (default: skip them). Use after an engine improvement changes what a stamp produces — each month reruns the full reopen → reclose cycle and replaces its sets. A restamp run is not self-resuming (every month in range stays a candidate); advance `start_period` between chunks.
440
+ */
441
+ restamp?: boolean;
442
+ /**
443
+ * Note
444
+ *
445
+ * Free-form note attached to each close audit event
446
+ */
447
+ note?: string | null;
448
+ };
449
+ /**
450
+ * BackfillPlanHistoryResponse
451
+ *
452
+ * Response from one chunked plan-history backfill call.
453
+ */
454
+ export type BackfillPlanHistoryResponse = {
455
+ fiscal_calendar: FiscalCalendarResponse;
456
+ /**
457
+ * Earliest Available Period
458
+ *
459
+ * First month with ledger data — the hard floor for backfill
460
+ */
461
+ earliest_available_period: string;
462
+ /**
463
+ * Effective Start Period
464
+ *
465
+ * The start actually used after clamping to earliest_available_period
466
+ */
467
+ effective_start_period: string;
468
+ /**
469
+ * Closed Through
470
+ *
471
+ * The close boundary the backfill runs up to (inclusive)
472
+ */
473
+ closed_through: string;
474
+ /**
475
+ * Period Rows Created
476
+ *
477
+ * FiscalPeriod rows seeded (baseline-closed) for months the calendar didn't cover yet
478
+ */
479
+ period_rows_created?: number;
480
+ /**
481
+ * Processed
482
+ *
483
+ * Months this call attempted, oldest first
484
+ */
485
+ processed?: Array<BackfillPeriodOutcome>;
486
+ /**
487
+ * Remaining Periods
488
+ *
489
+ * Months still lacking canonical statement sets that this call did not attempt (beyond max_periods, or after a failure halt). Loop until empty.
490
+ */
491
+ remaining_periods?: Array<string>;
492
+ };
367
493
  /**
368
494
  * BackupCreateRequest
369
495
  *
@@ -1193,6 +1319,34 @@ export type ClosePeriodResponse = {
1193
1319
  * ids of schedule Structures whose rules were evaluated during the close. Pairs with rule_summary.
1194
1320
  */
1195
1321
  evaluated_structure_ids?: Array<string>;
1322
+ /**
1323
+ * Statements Stamped
1324
+ *
1325
+ * Whether the close stamped the period's canonical statement FactSets (the close-time pivot). False when the tenant hasn't set up reporting yet — see statement_stamp_note.
1326
+ */
1327
+ statements_stamped?: boolean;
1328
+ /**
1329
+ * Statement Stamp Note
1330
+ *
1331
+ * Soft-skip reason when statements_stamped is false: no_coa_mapping | no_entity | no_statement_structures | no_taxonomy.
1332
+ */
1333
+ statement_stamp_note?: string | null;
1334
+ /**
1335
+ * Stamped Statement Sets
1336
+ *
1337
+ * structure_id -> fact_set_id for every canonical statement FactSet minted by this close (report_id NULL; replaced on reclose).
1338
+ */
1339
+ stamped_statement_sets?: {
1340
+ [key: string]: string;
1341
+ };
1342
+ /**
1343
+ * Statement Rule Summary
1344
+ *
1345
+ * Aggregated statement-rule verification outcome across the stamped structures — keys: pass/fail/error/skipped. None when no statement rules exist. Distinct from rule_summary (the schedule-rule pass).
1346
+ */
1347
+ statement_rule_summary?: {
1348
+ [key: string]: number;
1349
+ } | null;
1196
1350
  };
1197
1351
  /**
1198
1352
  * ComputeForecastRequest
@@ -2143,6 +2297,18 @@ export type CreateForecastRequest = {
2143
2297
  * Lever assertions — at least one.
2144
2298
  */
2145
2299
  levers: Array<LeverAssertionRequest>;
2300
+ /**
2301
+ * Line Assertions
2302
+ *
2303
+ * Direct statement-line assertions (manual overrides). Each names a calc-DAG leaf and wins over driver rules and carry-forward for the months it asserts.
2304
+ */
2305
+ line_assertions?: Array<LineAssertionRequest>;
2306
+ /**
2307
+ * Line Growth
2308
+ *
2309
+ * Per-line growth trajectories. Each names an income-statement leaf and grows it month-over-month at the asserted rate — the generic form of the revenue growth lever, for lines the catalog doesn't drive (opex trajectories, cost-cut ramps).
2310
+ */
2311
+ line_growth?: Array<LineGrowthRequest>;
2146
2312
  /**
2147
2313
  * Entity Id
2148
2314
  *
@@ -3000,9 +3166,27 @@ export type DatabaseHealthResponse = {
3000
3166
  /**
3001
3167
  * Memory Usage Mb
3002
3168
  *
3003
- * Memory usage in MB
3169
+ * Instance memory in use, MB. Only populated for dedicated single-tenant instances; null on shared repositories and packed tiers.
3004
3170
  */
3005
3171
  memory_usage_mb?: number | null;
3172
+ /**
3173
+ * Memory Usage Percent
3174
+ *
3175
+ * Instance memory in use, percent. Expect high values during materialization — the engine deliberately boosts to near the whole instance while rebuilding. Read `resource_status` rather than this number alone. Dedicated instances only.
3176
+ */
3177
+ memory_usage_percent?: number | null;
3178
+ /**
3179
+ * Cpu Usage Percent
3180
+ *
3181
+ * Instance CPU in use, percent. Dedicated single-tenant instances only.
3182
+ */
3183
+ cpu_usage_percent?: number | null;
3184
+ /**
3185
+ * Resource Status
3186
+ *
3187
+ * Interpreted instance load: 'idle' (headroom), 'busy' (working normally — typical while materializing), 'constrained' (sustained pressure worth acting on). Null when resource metrics are not exposed.
3188
+ */
3189
+ resource_status?: string | null;
3006
3190
  /**
3007
3191
  * Storage Usage Mb
3008
3192
  *
@@ -3874,6 +4058,12 @@ export type ElementLite = {
3874
4058
  * Value-domain vocabulary (monetary | ratio | percent | multiple | days | string | …). None means untyped; fall back to is_monetary.
3875
4059
  */
3876
4060
  item_type?: string | null;
4061
+ /**
4062
+ * Documentation
4063
+ *
4064
+ * The element's documentation-role label — the catalog's authoritative value semantics (e.g. whether a percent driver is a growth rate or a rate-on-base fraction). None when the element carries no documentation label.
4065
+ */
4066
+ documentation?: string | null;
3877
4067
  };
3878
4068
  /**
3879
4069
  * ElementUpdatePatch
@@ -5003,6 +5193,18 @@ export type ForecastMechanics = {
5003
5193
  * Expanded lever assertions (authoring order).
5004
5194
  */
5005
5195
  levers: Array<LeverAssertionLite>;
5196
+ /**
5197
+ * Line Assertions
5198
+ *
5199
+ * Direct statement-line assertions (authoring order) — manual overrides that win over driver rules and carry-forward for the months they name.
5200
+ */
5201
+ line_assertions?: Array<LineAssertionLite>;
5202
+ /**
5203
+ * Line Growth
5204
+ *
5205
+ * Per-line growth trajectories (authoring order) — each grows an income-statement leaf month-over-month at the asserted rate, compounding from the base month.
5206
+ */
5207
+ line_growth?: Array<LineGrowthLite>;
5006
5208
  /**
5007
5209
  * Computed Months
5008
5210
  *
@@ -6924,13 +7126,21 @@ export type LeverAssertionLite = {
6924
7126
  * One lever's asserted values for the scenario.
6925
7127
  *
6926
7128
  * ``qname`` must resolve to an ``rs-driver:*`` catalog element (the
6927
- * create handler rejects anything else). Value conventions follow the
6928
- * catalog: percent levers are decimals per month (0.03 = 3%/month),
6929
- * days levers are day counts.
7129
+ * create handler rejects anything else). Each lever's value semantics
7130
+ * are defined by its catalog element's documentation — surfaced as
7131
+ * ``documentation`` on the elements bundled in the forecast block's
7132
+ * envelope (``get-information-block``). Percent levers are decimals but
7133
+ * their *meaning* varies by lever: growth levers are month-over-month
7134
+ * rates (``RevenueGrowthRate`` 0.03 = +3%/month, compounding), while
7135
+ * rate-on-base levers are fractions of the same month's base
7136
+ * (``CostOfRevenueRate`` 0.62 = cost of revenue at 62% of that month's
7137
+ * revenues — not a growth rate). Days levers (``DaysSalesOutstanding``,
7138
+ * ``DaysPayableOutstanding``) are day counts.
6930
7139
  *
6931
7140
  * ``value`` is a uniform fill across the whole horizon;
6932
7141
  * ``values_by_period`` overrides individual months (``"YYYY-MM"``
6933
- * keys). At least one of the two must be provided. Months covered by
7142
+ * keys) — e.g. a margin-compression ramp asserts a different rate each
7143
+ * month. At least one of the two must be provided. Months covered by
6934
7144
  * neither carry no assertion — the lever's rule is inactive for that
6935
7145
  * month and its target falls to the engine's carry-forward default.
6936
7146
  */
@@ -6956,6 +7166,196 @@ export type LeverAssertionRequest = {
6956
7166
  [key: string]: number;
6957
7167
  } | null;
6958
7168
  };
7169
+ /**
7170
+ * LineAssertionLite
7171
+ *
7172
+ * One statement line's persisted direct assertion inside
7173
+ * ``ForecastMechanics``.
7174
+ *
7175
+ * The manual-override sibling of :class:`LeverAssertionLite`: a lever
7176
+ * asserts a *driver* whose rule derives a line; a line assertion pins
7177
+ * the **line itself** (a calc-DAG leaf) to typed values for the months
7178
+ * it names — winning over driver rules and carry-forward for exactly
7179
+ * those months (a displaced rule surfaces in the compute response's
7180
+ * ``skipped`` list). Subtotals stay calc-DAG-derived, so a manual line
7181
+ * still articulates through RollUps, RE, balancing cash, and derived
7182
+ * CF, and stays verification-gated.
7183
+ *
7184
+ * Same persistence doctrine as levers: values are duplicated as
7185
+ * authored facts in the scenario's lever FactSet (facts are what
7186
+ * ``compute-forecast`` binds); this mechanics copy is the
7187
+ * operator-legible round-trip shape.
7188
+ */
7189
+ export type LineAssertionLite = {
7190
+ /**
7191
+ * Qname
7192
+ *
7193
+ * Asserted statement-leaf qname.
7194
+ */
7195
+ qname: string;
7196
+ /**
7197
+ * Element Id
7198
+ *
7199
+ * Resolved tenant element id.
7200
+ */
7201
+ element_id: string;
7202
+ /**
7203
+ * Item Type
7204
+ *
7205
+ * Format family from the element (monetary | ...).
7206
+ */
7207
+ item_type?: string | null;
7208
+ /**
7209
+ * Period Type
7210
+ *
7211
+ * The element's period type — duration assertions pin IS lines; instant assertions pin BS lines through the roll.
7212
+ */
7213
+ period_type?: string;
7214
+ /**
7215
+ * Values By Period
7216
+ *
7217
+ * Expanded per-month assertions keyed by ``YYYY-MM``.
7218
+ */
7219
+ values_by_period: {
7220
+ [key: string]: number;
7221
+ };
7222
+ };
7223
+ /**
7224
+ * LineAssertionRequest
7225
+ *
7226
+ * One statement line's directly asserted values for the scenario.
7227
+ *
7228
+ * The manual-override half of the authored surface: where a lever
7229
+ * asserts a *driver* (growth %, DSO) whose rule derives the line, a
7230
+ * line assertion asserts the **line itself** — an rs-gaap (or tenant
7231
+ * extension) statement leaf pinned to typed values for the months it
7232
+ * names. Assertions win over driver rules and carry-forward for those
7233
+ * months (a displaced rule lands in ``skipped``, legibly); months the
7234
+ * assertion doesn't name keep the engine's normal derivation.
7235
+ *
7236
+ * **Leaves only** — subtotals stay calc-DAG-derived, so a manually set
7237
+ * line still articulates through RollUps, RE, balancing cash, and the
7238
+ * derived CF, and stays verification-gated (the whole pitch vs a
7239
+ * spreadsheet cell). The create handler rejects calc-parent qnames.
7240
+ *
7241
+ * Value/period grammar is identical to levers: ``value`` is a uniform
7242
+ * fill across the horizon, ``values_by_period`` overrides individual
7243
+ * months. The canonical uses: zero out a base-month one-off so
7244
+ * carry-forward stops replicating it, or hold a line at a known budget
7245
+ * number no driver models.
7246
+ */
7247
+ export type LineAssertionRequest = {
7248
+ /**
7249
+ * Qname
7250
+ *
7251
+ * QName of the statement leaf to assert (e.g. ``rs-gaap:NonoperatingIncomeExpense``). Must be a calc-DAG leaf; rs-driver concepts belong in ``levers``.
7252
+ */
7253
+ qname: string;
7254
+ /**
7255
+ * Value
7256
+ *
7257
+ * Uniform value asserted for every month of the horizon.
7258
+ */
7259
+ value?: number | null;
7260
+ /**
7261
+ * Values By Period
7262
+ *
7263
+ * Per-month overrides keyed by ``YYYY-MM``. Wins over ``value`` for the months it names.
7264
+ */
7265
+ values_by_period?: {
7266
+ [key: string]: number;
7267
+ } | null;
7268
+ };
7269
+ /**
7270
+ * LineGrowthLite
7271
+ *
7272
+ * One statement line's persisted growth trajectory inside
7273
+ * ``ForecastMechanics``.
7274
+ *
7275
+ * The generic per-line form of the revenue growth lever: grows an
7276
+ * income-statement leaf month-over-month at the asserted rate
7277
+ * (``line[t] = line[t-1] * (1 + rate[t])``), compounding from the base
7278
+ * month's value. Months without a rate keep the engine's carry-forward.
7279
+ * Duration leaves only; disjoint from ``line_assertions`` and from any
7280
+ * active catalog rule's target (one owner per line).
7281
+ *
7282
+ * Persistence deviates from levers/assertions deliberately: rates are
7283
+ * NOT duplicated as facts in the scenario FactSet — a growth rate on a
7284
+ * monetary statement element would be a unit-lying fact. This mechanics
7285
+ * copy is the single authored store; ``compute-forecast`` binds rates
7286
+ * from here.
7287
+ */
7288
+ export type LineGrowthLite = {
7289
+ /**
7290
+ * Qname
7291
+ *
7292
+ * Grown statement-leaf qname.
7293
+ */
7294
+ qname: string;
7295
+ /**
7296
+ * Element Id
7297
+ *
7298
+ * Resolved tenant element id.
7299
+ */
7300
+ element_id: string;
7301
+ /**
7302
+ * Item Type
7303
+ *
7304
+ * Always 'percent' — the grid row renders rates, not values.
7305
+ */
7306
+ item_type?: string;
7307
+ /**
7308
+ * Values By Period
7309
+ *
7310
+ * Expanded per-month growth rates keyed by ``YYYY-MM``.
7311
+ */
7312
+ values_by_period: {
7313
+ [key: string]: number;
7314
+ };
7315
+ };
7316
+ /**
7317
+ * LineGrowthRequest
7318
+ *
7319
+ * One statement line's asserted growth trajectory for the scenario.
7320
+ *
7321
+ * The generic per-line sibling of ``rs-driver:RevenueGrowthRate``: where
7322
+ * the catalog lever grows *revenue* through its seeded rule, a line
7323
+ * growth entry grows **any income-statement leaf** at a month-over-month
7324
+ * rate — ``value`` -0.05 cuts the line 5% per month, compounding from
7325
+ * the base month's value. This is what expense trajectories ("opex +2%/mo
7326
+ * with inflation", "cut costs 5%/mo starting October") use; without it
7327
+ * every unmodeled line just carries flat.
7328
+ *
7329
+ * Semantics per month: ``line[t] = line[t-1] * (1 + rate[t])``. Months
7330
+ * the entry doesn't name keep the engine's carry-forward (grow-then-hold
7331
+ * ramps fall out of ``values_by_period`` naturally). **Duration leaves
7332
+ * only**: balance-sheet lines roll from the IS and the working-capital
7333
+ * levers — grow the driving IS line instead. A line already driven by an
7334
+ * active catalog rule (e.g. Revenues with ``RevenueGrowthRate`` set) or
7335
+ * named by a ``line_assertions`` entry is rejected — one owner per line.
7336
+ */
7337
+ export type LineGrowthRequest = {
7338
+ /**
7339
+ * Qname
7340
+ *
7341
+ * QName of the income-statement leaf to grow (e.g. ``rs-gaap:ResearchAndDevelopmentExpense``). Must be a calc-DAG duration leaf.
7342
+ */
7343
+ qname: string;
7344
+ /**
7345
+ * Value
7346
+ *
7347
+ * Uniform month-over-month growth rate for every month of the horizon (decimal: 0.02 = +2%/mo, -0.05 = -5%/mo).
7348
+ */
7349
+ value?: number | null;
7350
+ /**
7351
+ * Values By Period
7352
+ *
7353
+ * Per-month rate overrides keyed by ``YYYY-MM``. Wins over ``value`` for the months it names; months named by neither carry the line's prior value (rate 0).
7354
+ */
7355
+ values_by_period?: {
7356
+ [key: string]: number;
7357
+ } | null;
7358
+ };
6959
7359
  /**
6960
7360
  * LineItemMetadataPredicate
6961
7361
  *
@@ -7718,6 +8118,51 @@ export type OperationEnvelopeAssociationResponse = {
7718
8118
  */
7719
8119
  idempotentReplay?: boolean;
7720
8120
  };
8121
+ /**
8122
+ * OperationEnvelope[BackfillPlanHistoryResponse]
8123
+ */
8124
+ export type OperationEnvelopeBackfillPlanHistoryResponse = {
8125
+ /**
8126
+ * Operation
8127
+ *
8128
+ * Kebab-case operation name
8129
+ */
8130
+ operation: string;
8131
+ /**
8132
+ * Operationid
8133
+ *
8134
+ * op_-prefixed ULID for audit and SSE correlation
8135
+ */
8136
+ operationId: string;
8137
+ /**
8138
+ * Status
8139
+ *
8140
+ * Operation lifecycle state
8141
+ */
8142
+ status: 'completed' | 'pending' | 'failed';
8143
+ /**
8144
+ * Command-specific result payload
8145
+ */
8146
+ result?: BackfillPlanHistoryResponse | null;
8147
+ /**
8148
+ * At
8149
+ *
8150
+ * ISO-8601 UTC timestamp
8151
+ */
8152
+ at: string;
8153
+ /**
8154
+ * Createdby
8155
+ *
8156
+ * User ID that initiated the operation (null for legacy callers)
8157
+ */
8158
+ createdBy?: string | null;
8159
+ /**
8160
+ * Idempotentreplay
8161
+ *
8162
+ * True when this envelope came from the idempotency cache — the underlying command did not execute again. False on fresh executions.
8163
+ */
8164
+ idempotentReplay?: boolean;
8165
+ };
7721
8166
  /**
7722
8167
  * OperationEnvelope[BindTextBlockResponse]
7723
8168
  */
@@ -13916,11 +14361,13 @@ export type UpdateEventHandlerRequest = {
13916
14361
  *
13917
14362
  * Update a forecast block in place.
13918
14363
  *
13919
- * Mutable: name, scenario_kind, horizon_months, base_period, levers.
13920
- * ``levers`` is a **full replace** when provided (partial lever edits
13921
- * would make the asserted set ambiguous). Updating does NOT recompute —
13922
- * previously computed scenario months go stale until the next
13923
- * ``compute-forecast`` run (the compute-metrics drift semantics).
14364
+ * Mutable: name, scenario_kind, horizon_months, base_period, levers,
14365
+ * line_assertions. ``levers`` and ``line_assertions`` are each a
14366
+ * **full replace** when provided (partial edits would make the asserted
14367
+ * set ambiguous); replacing one leaves the other as stored. Updating
14368
+ * does NOT recompute — previously computed scenario months go stale
14369
+ * until the next ``compute-forecast`` run (the compute-metrics drift
14370
+ * semantics).
13924
14371
  */
13925
14372
  export type UpdateForecastRequest = {
13926
14373
  /**
@@ -13951,6 +14398,18 @@ export type UpdateForecastRequest = {
13951
14398
  * Full replacement of the lever set when provided.
13952
14399
  */
13953
14400
  levers?: Array<LeverAssertionRequest> | null;
14401
+ /**
14402
+ * Line Assertions
14403
+ *
14404
+ * Full replacement of the line-assertion set when provided. Pass an empty list to clear every assertion.
14405
+ */
14406
+ line_assertions?: Array<LineAssertionRequest> | null;
14407
+ /**
14408
+ * Line Growth
14409
+ *
14410
+ * Full replacement of the line-growth set when provided. Pass an empty list to clear every growth entry.
14411
+ */
14412
+ line_growth?: Array<LineGrowthRequest> | null;
13954
14413
  };
13955
14414
  /**
13956
14415
  * UpdateInformationBlockRequest
@@ -14953,7 +15412,7 @@ export type UpdateForecastArm = {
14953
15412
  */
14954
15413
  block_type: 'forecast';
14955
15414
  /**
14956
- * Forecast update payload.
15415
+ * Forecast update payload. Updating does NOT recompute — lever, horizon, or base-period changes leave the scenario's computed months stale until the next `compute-forecast` run.
14957
15416
  */
14958
15417
  payload: UpdateForecastRequest;
14959
15418
  };
@@ -17509,7 +17968,7 @@ export type GetGraphMetricsData = {
17509
17968
  graph_id: string;
17510
17969
  };
17511
17970
  query?: never;
17512
- url: '/v1/graphs/{graph_id}/analytics';
17971
+ url: '/v1/graphs/{graph_id}/metrics';
17513
17972
  };
17514
17973
  export type GetGraphMetricsErrors = {
17515
17974
  /**
@@ -17549,7 +18008,7 @@ export type GetGraphMetricsResponses = {
17549
18008
  200: GraphMetricsResponse;
17550
18009
  };
17551
18010
  export type GetGraphMetricsResponse = GetGraphMetricsResponses[keyof GetGraphMetricsResponses];
17552
- export type GetGraphUsageAnalyticsData = {
18011
+ export type GetGraphUsageData = {
17553
18012
  body?: never;
17554
18013
  path: {
17555
18014
  /**
@@ -17589,9 +18048,9 @@ export type GetGraphUsageAnalyticsData = {
17589
18048
  */
17590
18049
  include_events?: boolean;
17591
18050
  };
17592
- url: '/v1/graphs/{graph_id}/analytics/usage';
18051
+ url: '/v1/graphs/{graph_id}/usage';
17593
18052
  };
17594
- export type GetGraphUsageAnalyticsErrors = {
18053
+ export type GetGraphUsageErrors = {
17595
18054
  /**
17596
18055
  * Invalid request
17597
18056
  */
@@ -17621,14 +18080,14 @@ export type GetGraphUsageAnalyticsErrors = {
17621
18080
  */
17622
18081
  500: ErrorResponse;
17623
18082
  };
17624
- export type GetGraphUsageAnalyticsError = GetGraphUsageAnalyticsErrors[keyof GetGraphUsageAnalyticsErrors];
17625
- export type GetGraphUsageAnalyticsResponses = {
18083
+ export type GetGraphUsageError = GetGraphUsageErrors[keyof GetGraphUsageErrors];
18084
+ export type GetGraphUsageResponses = {
17626
18085
  /**
17627
18086
  * Successful Response
17628
18087
  */
17629
18088
  200: GraphUsageResponse;
17630
18089
  };
17631
- export type GetGraphUsageAnalyticsResponse = GetGraphUsageAnalyticsResponses[keyof GetGraphUsageAnalyticsResponses];
18090
+ export type GetGraphUsageResponse = GetGraphUsageResponses[keyof GetGraphUsageResponses];
17632
18091
  export type ExecuteCypherData = {
17633
18092
  body: CypherStatementRequest;
17634
18093
  path: {
@@ -22915,6 +23374,65 @@ export type ReopenPeriodResponses = {
22915
23374
  200: OperationEnvelopeFiscalCalendarResponse;
22916
23375
  };
22917
23376
  export type ReopenPeriodResponse = ReopenPeriodResponses[keyof ReopenPeriodResponses];
23377
+ export type BackfillPlanHistoryData = {
23378
+ body: BackfillPlanHistoryOperation;
23379
+ headers?: {
23380
+ /**
23381
+ * Idempotency-Key
23382
+ */
23383
+ 'Idempotency-Key'?: string | null;
23384
+ };
23385
+ path: {
23386
+ /**
23387
+ * Graph Id
23388
+ */
23389
+ graph_id: string;
23390
+ };
23391
+ query?: never;
23392
+ url: '/extensions/roboledger/{graph_id}/operations/backfill-plan-history';
23393
+ };
23394
+ export type BackfillPlanHistoryErrors = {
23395
+ /**
23396
+ * Invalid request
23397
+ */
23398
+ 400: ErrorResponse;
23399
+ /**
23400
+ * Authentication required
23401
+ */
23402
+ 401: ErrorResponse;
23403
+ /**
23404
+ * Access denied
23405
+ */
23406
+ 403: ErrorResponse;
23407
+ /**
23408
+ * Resource not found
23409
+ */
23410
+ 404: ErrorResponse;
23411
+ /**
23412
+ * Idempotency-Key conflict — key reused with different body
23413
+ */
23414
+ 409: ErrorResponse;
23415
+ /**
23416
+ * Validation error
23417
+ */
23418
+ 422: ErrorResponse;
23419
+ /**
23420
+ * Rate limit exceeded
23421
+ */
23422
+ 429: ErrorResponse;
23423
+ /**
23424
+ * Internal server error
23425
+ */
23426
+ 500: ErrorResponse;
23427
+ };
23428
+ export type BackfillPlanHistoryError = BackfillPlanHistoryErrors[keyof BackfillPlanHistoryErrors];
23429
+ export type BackfillPlanHistoryResponses = {
23430
+ /**
23431
+ * Successful Response
23432
+ */
23433
+ 200: OperationEnvelopeBackfillPlanHistoryResponse;
23434
+ };
23435
+ export type BackfillPlanHistoryResponse2 = BackfillPlanHistoryResponses[keyof BackfillPlanHistoryResponses];
22918
23436
  export type CreateReportData = {
22919
23437
  body: CreateReportRequest;
22920
23438
  headers?: {