@tinycloud/cli 1.3.5 → 1.3.6-beta.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tinycloud/cli",
-  "version": "1.3.5",
+  "version": "1.3.6-beta.1",
   "description": "TinyCloud CLI - manage data, delegations, and nodes from the terminal",
   "author": "TinyCloud, Inc.",
   "license": "EGPL",
@@ -35,11 +35,11 @@
   "dependencies": {
     "@tinycloud/share-sdk": "1.3.0",
     "@tinycloud/share-envelope": "1.2.1",
-    "@tinycloud/node-sdk": "3.6.0",
+    "@tinycloud/node-sdk": "3.6.1-beta.1",
     "@tinycloud/node-sdk-wasm": "1.7.8",
     "@tinycloud/sdk-core": "3.6.0",
     "@tinycloud/sdk-services": "3.6.0",
-    "@tinycloud/operations": "0.7.4",
+    "@tinycloud/operations": "0.7.5-beta.1",
     "chalk": "^5.3.0",
     "commander": "^14.0.0",
     "jsdom": "26.1.0",
@@ -48,7 +48,7 @@
     "siwe": "^3.0.0"
   },
   "devDependencies": {
-    "@tinycloud/courier": "0.3.0",
+    "@tinycloud/courier": "0.3.1-beta.1",
     "@tinycloud/replica": "0.3.3",
     "@types/node": "^20",
     "tsup": "^8.0.0",

package/skills/tc-cli/AUTH.md

@@ -152,6 +152,8 @@ The `for_another_key` label requires a valid signed compact audience and CID mat
 
 `tinycloud --profile PROFILE auth grants remove <cid>` removes all local rows with that exact CID, without contacting the node; delegates may do this. An owner can add `--revoke --yes` to discover the verified local node (unless a host was explicitly selected), revoke there, then remove local rows only after successful revocation. Delegate-session profiles cannot use `--revoke`. If revocation succeeds but local removal fails, `GRANT_REVOKED_LOCAL_REMOVE_FAILED` includes a hint to retry `auth grants remove <cid>` **without** `--revoke`. `tinycloud delegation revoke <cid>` also revokes a CID directly when its target is known. OpenKey cannot sign raw `urn:cid` ReCap authority today: owner OpenKey revocation falls back to command-scoped `delegation/revoke` on an owner-signed CID-bound space, and fails immediately when no verified fallback space exists. The JavaScript SDK cannot currently issue a delegatee self-revocation, although the node accepts one. Local removal is not revocation.
 
+`tinycloud.delegation/revoke` on a space is space-wide: it can revoke any delegation in that space, including other apps' grants and the owner's own sessions. Request it only for the command that needs it, with a short expiry, and don't keep it: the CLI's own fallback asks for 5 minutes and stores nothing. Never put it in a long-lived grant or an app manifest.
+
 If another process already removed the row after the node revoke, `--revoke` succeeds with `removed: 0`. Other post-revoke local removal errors include the underlying `error.meta.causeCode` (for example `PROFILE_LOCK_TIMEOUT`) so automation can distinguish lock contention from a node failure.
 
 To replace an old grant without a proof, an owner can approve again with `tinycloud auth request --grant [--device]`, then remove the old CID. A delegate can emit a request with `tinycloud auth request --emit`, have the owner run `tinycloud auth grant`, import the signed result with `tinycloud auth import`, then remove the old CID. If the original artifact still includes `siweProof`, importing it again is also possible.

package/skills/tc-cli/REFERENCE.md

@@ -126,6 +126,8 @@ as a disposable replica child grant.
 
 Local `remove` deletes every row matching that exact CID, and is available to delegates. `--revoke` alone is owner-only: it uses normal verified local-node discovery unless a host is explicit, revokes on the node, and removes the rows only after success. If the local removal then fails, `GRANT_REVOKED_LOCAL_REMOVE_FAILED` directs a local-only retry without `--revoke`. OpenKey cannot sign raw `urn:cid` authority on the deployed version; owner OpenKey revocation uses a verified CID-bound owner-space fallback, or immediately fails `RAW_RECAP_RESOURCE_UNSUPPORTED`. Local removal does not revoke the delegation; delegated sessions cannot use `--revoke` because this SDK cannot issue a delegatee self-revocation.
 
+`tinycloud.delegation/revoke` on a space is space-wide: it can revoke any delegation in that space, including other apps' grants and the owner's own sessions. Request it only for the command that needs it, with a short expiry, and don't keep it: the CLI's own fallback asks for 5 minutes and stores nothing. Never put it in a long-lived grant or an app manifest.
+
 A concurrent local removal after revocation reports `removed: 0` as success. Other local cleanup failures include `error.meta.causeCode` (for example `PROFILE_LOCK_TIMEOUT`).
 
 ## Spaces

package/skills/tc-cli/SDK.md

@@ -56,6 +56,8 @@ await tc.account.delegations.query({ direction: "all" });
 await tc.delegationManager.revoke(cid);
 ```
 
+`tinycloud.delegation/revoke` on a space is space-wide: it can revoke any delegation in that space, including other apps' grants and the owner's own sessions. Request it only for the command that needs it, with a short expiry, and don't keep it: the CLI's own fallback asks for 5 minutes and stores nothing. Never put it in a long-lived grant or an app manifest.
+
 ## Properties
 
 ```typescript