@@ -550,7 +550,7 @@ After direct-provider connect:
   Do not run devices as a pre-open catalog probe for direct providers; it can allocate the deferred provider session. Limrun is the exception for apps: before allocation it lists uploaded assets for the selected platform.
 
 Device cloud interfaces:
-  CLI is the canonical bootstrap path: connect limrun/browserstack/aws-device-farm/testmu/revyl, then use normal open/snapshot/click/close/disconnect commands; artifacts are provider-dependent.
+  CLI is the canonical bootstrap path: connect limrun/browserstack/aws-device-farm/testmu/revyl, then use normal open/snapshot/click/close/artifacts/disconnect commands.
   JavaScript can skip persisted connect state by passing leaseProvider plus provider fields to createAgentDeviceClient or per-command options.
   MCP exposes operational tools such as open, snapshot, click, close, and artifacts. It does not expose connect/disconnect; run CLI connect first in the same state dir before relying on MCP tools.
 
 
@@ -146,8 +146,13 @@ try {
   await client.interactions.click({ selector: 'label="Continue"' });
 } finally {
   // Releasing the lease ends the Revyl session, so a failure cannot leave a device rented.
-  await host.client.leases.release({ ...scope, leaseId: lease.leaseId });
-  await host.close();
+  // The inner finally closes the host even when the release itself fails; otherwise the embedded
+  // daemon stays alive and nothing retries the release.
+  try {
+    await host.client.leases.release({ ...scope, leaseId: lease.leaseId });
+  } finally {
+    await host.close();
+  }
 }
 ```