@byok-sdk/cloud 0.24.0 → 0.25.0-rc.1

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.
Files changed (7) hide show
  1. package/README.md +0 -1
  2. package/dist/capabilities.d.ts +1 -1
  3. package/dist/cloud.d.ts +1 -1
  4. package/dist/index.js +1 -1
  5. package/dist/index.js.map +1 -1
  6. package/dist/recurring.d.ts +2 -18
  7. package/package.json +3 -3
package/README.md CHANGED
@@ -33,7 +33,6 @@ await cloud.enqueueToolsetOffer(tenantId, deviceId, {
33
33
  payload: {
34
34
  instruction: 'Research the account and prepare the next sales action.',
35
35
  runtime: 'claude',
36
- policy: { mode: 'auto' },
37
36
  requiredToolsets: ['salesko.prospecting'],
38
37
  },
39
38
  });
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-v8`
76
+ * no DEVICE capability either: the device-level `agent-input-preparation-v9`
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
@@ -298,7 +298,7 @@ export interface ByokCloud {
298
298
  * Host control plane: enqueue an offer for an already-counted preparation.
299
299
  *
300
300
  * Admission requires the device to durably advertise both the Agent-home
301
- * contract and `agent-input-preparation-v8` — the second because only a device
301
+ * contract and `agent-input-preparation-v9` — the second because only a device
302
302
  * that can prepare holds the durable record this offer names. A device that
303
303
  * advertises neither never receives the message, and a device whose protocol
304
304
  * 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-v8`
1220
+ * no DEVICE capability either: the device-level `agent-input-preparation-v9`
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