@alienplatform/core 3.3.16 → 3.3.17

package/dist/index.js

@@ -6857,7 +6857,7 @@ z$2.object({
 	"domainEgressRules": z$2.boolean().describe("Egress can be restricted to a hostname allowlist"),
 	"egressDeny": z$2.boolean().describe("Whether a declared `deny` is actually enforced, rather than accepted and dropped"),
 	"enforcedLimits": z$2.boolean().describe("The platform enforces the declared cpu, memory and disk ceilings"),
-	"files": z$2.boolean().describe("Files can be moved in and out of a session\n\nEvery backend but Azure, whose data plane exposes exec and lifecycle and no transfer."),
+	"files": z$2.boolean().describe("Files can be moved in and out of a session\n\nEvery backend but Azure, whose binding implements no transfer."),
 	"preview": z$2.boolean().describe("An authenticated, port-scoped capability to reach a service inside the sandbox"),
 	"processLimit": z$2.boolean().describe("The platform can cap how many processes a session runs"),
 	"reconnect": z$2.boolean().describe("A later call can reach a session created by an earlier one"),
@@ -9572,8 +9572,8 @@ var Queue = class extends ResourceBuilder {
 *
 * Capabilities are not uniform. Call `capabilities()` on the binding and branch, or handle the
 * typed error — an unsupported capability never silently succeeds. Notably GCP cannot
-* reconnect to a session (its session id is scoped to one Cloud Run instance), Azure has no
-* file transfer, and no platform supports a hostname egress allowlist.
+* reconnect to a session (its session id is scoped to one Cloud Run instance), the Azure
+* binding implements no file transfer, and no binding renders a hostname egress allowlist.
 *
 * Limits are enforced ceilings, not scheduling hints, and are validated when the stack is
 * planned. A platform that cannot enforce them rejects the sandbox rather than ignoring them.