docs(sandbox): say the Azure binding lacks these, not the cloud

crates/alien-core/src/resources/sandbox.rs

@@ -169,7 +169,7 @@ pub struct SandboxSessionPolicy {
 pub struct SandboxCapabilities {
     /// Files can be moved in and out of a session
     ///
-    /// Every backend but Azure, whose data plane exposes exec and lifecycle and no transfer.
+    /// Every backend but Azure, whose binding implements no transfer.
     pub files: bool,
     /// A later call can reach a session created by an earlier one
     pub reconnect: bool,
@@ -862,9 +862,9 @@ mod tests {
         assert!(!gcp.enforced_limits);
 
         let azure = SandboxCapabilities::for_platform(Platform::Azure).expect("azure is supported");
-        assert!(!azure.files, "the Azure data plane has no file transfer");
+        assert!(!azure.files, "the Azure binding implements no file transfer");
         assert!(gcp.files, "every other backend moves files");
-        // The Azure data plane takes neither an egress policy nor a ceiling, so a declaration of
+        // The Azure binding renders neither an egress policy nor a ceiling, so a declaration of
         // either is refused rather than accepted and dropped.
         assert!(!azure.domain_egress_rules);
         assert!(!azure.egress_deny);
@@ -911,7 +911,7 @@ mod tests {
     }
 
     /// No backend expresses a hostname allowlist: AWS and Kubernetes match CIDRs, and the Azure
-    /// data plane takes no egress policy at all. Accepting one anywhere would leave a stack
+    /// binding renders no egress policy at all. Accepting one anywhere would leave a stack
     /// reading as restricted while the sandbox reaches the whole internet.
     #[test]
     fn a_hostname_allowlist_is_refused_on_every_backend() {
@@ -973,7 +973,7 @@ mod tests {
 
         let error = egress_only
             .validate_for_platform(Platform::Azure)
-            .expect_err("the Azure data plane takes no egress policy, so deny cannot be kept");
+            .expect_err("the Azure binding renders no egress policy, so deny cannot be kept");
         assert_eq!(error.code, "SANDBOX_CAPABILITY_UNSUPPORTED");
         assert!(
             error.message.contains("egressDeny"),

packages/core/src/sandbox.ts

@@ -33,8 +33,8 @@ export { SandboxSchema as SandboxConfigSchema } from "./generated/index.js"
  *
  * 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.