@byok-sdk/cloud 0.19.0 → 0.20.0

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.
@@ -73,7 +73,7 @@ export declare const CLOUD_CAPABILITIES: {
73
73
  * DEVICE's only way to discharge a mailbox row this same deployment handed
74
74
  * it — withholding it would strand the device's redelivery cursor rather
75
75
  * than degrade a feature. For the same reason the completion route asserts
76
- * no DEVICE capability either: the device-level `agent-input-preparation`
76
+ * no DEVICE capability either: the device-level `agent-input-preparation-v5`
77
77
  * flag gates ADMISSION (`enqueueInputPreparation`) and nothing else, so an
78
78
  * unconfigured device is refused a row instead of being handed one whose
79
79
  * only honest answer — `input_preparation_unconfigured` — it could not then
package/dist/cloud.d.ts CHANGED
@@ -283,7 +283,7 @@ export interface ByokCloud {
283
283
  * Host control plane: enqueue an offer for an already-counted preparation.
284
284
  *
285
285
  * Admission requires the device to durably advertise both the Agent-home
286
- * contract and `agent-input-preparation` — the second because only a device
286
+ * contract and `agent-input-preparation-v5` — the second because only a device
287
287
  * that can prepare holds the durable record this offer names. A device that
288
288
  * advertises neither never receives the message, and a device whose protocol
289
289
  * build predates the type skips it whole rather than running it as an
package/dist/index.js CHANGED
@@ -1217,7 +1217,7 @@ var CLOUD_CAPABILITIES = {
1217
1217
  * DEVICE's only way to discharge a mailbox row this same deployment handed
1218
1218
  * it — withholding it would strand the device's redelivery cursor rather
1219
1219
  * than degrade a feature. For the same reason the completion route asserts
1220
- * no DEVICE capability either: the device-level `agent-input-preparation`
1220
+ * no DEVICE capability either: the device-level `agent-input-preparation-v5`
1221
1221
  * flag gates ADMISSION (`enqueueInputPreparation`) and nothing else, so an
1222
1222
  * unconfigured device is refused a row instead of being handed one whose
1223
1223
  * only honest answer — `input_preparation_unconfigured` — it could not then
@@ -2966,6 +2966,7 @@ function projectTerminalResult(taskId, receipt) {
2966
2966
  ...envelope.payload.document !== void 0 ? { document: envelope.payload.document } : {},
2967
2967
  ...envelope.payload.harnessId === void 0 ? {} : { harnessId: envelope.payload.harnessId },
2968
2968
  ...envelope.payload.usage !== void 0 ? { usage: envelope.payload.usage } : {},
2969
+ ...envelope.payload.preparedObservation === void 0 ? {} : { preparedObservation: envelope.payload.preparedObservation },
2969
2970
  recordedAt: receipt.recordedAt
2970
2971
  };
2971
2972
  case "task.fail":
@@ -2979,6 +2980,7 @@ function projectTerminalResult(taskId, receipt) {
2979
2980
  ...envelope.payload.retryable !== void 0 ? { retryable: envelope.payload.retryable } : {},
2980
2981
  ...envelope.payload.harnessId === void 0 ? {} : { harnessId: envelope.payload.harnessId },
2981
2982
  ...envelope.payload.usage !== void 0 ? { usage: envelope.payload.usage } : {},
2983
+ ...envelope.payload.preparedObservation === void 0 ? {} : { preparedObservation: envelope.payload.preparedObservation },
2982
2984
  recordedAt: receipt.recordedAt
2983
2985
  };
2984
2986
  // `task.decline` is the pre-claim terminal (§3.2, `Offered -> Failed`).