@byok-sdk/cloud 0.21.0 → 0.22.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.
- package/dist/capabilities.d.ts +1 -1
- package/dist/cloud.d.ts +1 -1
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/package.json +3 -3
package/dist/capabilities.d.ts
CHANGED
|
@@ -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-v7`
|
|
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
|
@@ -285,7 +285,7 @@ export interface ByokCloud {
|
|
|
285
285
|
* Host control plane: enqueue an offer for an already-counted preparation.
|
|
286
286
|
*
|
|
287
287
|
* Admission requires the device to durably advertise both the Agent-home
|
|
288
|
-
* contract and `agent-input-preparation-
|
|
288
|
+
* contract and `agent-input-preparation-v7` — the second because only a device
|
|
289
289
|
* that can prepare holds the durable record this offer names. A device that
|
|
290
290
|
* advertises neither never receives the message, and a device whose protocol
|
|
291
291
|
* 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-v7`
|
|
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
|