@tinycloud/cli 1.5.0-beta.34 → 1.5.0-beta.36

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tinycloud/cli",
-  "version": "1.5.0-beta.34",
+  "version": "1.5.0-beta.36",
   "description": "TinyCloud CLI - manage data, delegations, and nodes from the terminal",
   "author": "TinyCloud, Inc.",
   "license": "EGPL",
@@ -33,13 +33,13 @@
     "sync:courier-skill": "rm -rf skills/courier && cp -R ../courier/skills/courier skills/courier"
   },
   "dependencies": {
-    "@tinycloud/share-sdk": "1.4.1-beta.3",
+    "@tinycloud/share-sdk": "1.4.1-beta.4",
     "@tinycloud/share-envelope": "1.4.0-beta.2",
-    "@tinycloud/node-sdk": "3.8.0-beta.22",
+    "@tinycloud/node-sdk": "3.8.0-beta.23",
     "@tinycloud/node-sdk-wasm": "1.7.8",
-    "@tinycloud/sdk-core": "3.8.0-beta.22",
+    "@tinycloud/sdk-core": "3.8.0-beta.23",
     "@tinycloud/sdk-services": "3.8.0-beta.22",
-    "@tinycloud/operations": "0.7.7-beta.21",
+    "@tinycloud/operations": "0.7.7-beta.22",
     "chalk": "^5.3.0",
     "commander": "^14.0.0",
     "jsdom": "26.1.0",
@@ -48,7 +48,7 @@
     "siwe": "^3.0.0"
   },
   "devDependencies": {
-    "@tinycloud/courier": "0.4.0-beta.22",
+    "@tinycloud/courier": "0.4.0-beta.23",
     "@tinycloud/replica": "0.4.0-beta.6",
     "@types/node": "^20",
     "tsup": "^8.0.0",

package/skills/tinycloud-cli/REFERENCE.md

@@ -376,6 +376,8 @@ tinycloud completion fish | source
 
 Publishing needs the publishing scope in the owner's `default` space, on a dedicated profile: `tinycloud init --name publisher --key-only`, then `tinycloud --profile publisher auth login --method openkey --paste --manifest builtin:share-publishing --expiry 30d`. Publish with `tinycloud --profile publisher share publish ...`.
 
+Sharing to an email address, domain or DID isn't available in this release; link shares are.
+
 ```bash
 tinycloud share publish ./note.md --json                                  # bearer link; JSON has no URL: use share show <id> --reveal-link
 tinycloud share publish ./note.md --to email:alice@example.com --notify   # addressed: exact email, emailed invitation (read required)

package/skills/tinycloud-cli/SKILL.md

@@ -101,6 +101,8 @@ A folder (a top-level `index.html` plus the CSS, scripts, images and fonts it us
 
 Without `--to`, publish creates a bearer link: anyone holding the complete URL can read it until it expires or `tinycloud share revoke <id>` revokes it. `--to email:`, `--to did:` and `--to domain:` create addressed links that only the named recipient can open after proving who they are. An addressed share of 120 seconds to 30 days gets a short link; any other addressed share, or `--full-link`, gets the full link (past 30 days with a warning on stderr and `linkNotice` in JSON), and the same full link with a notice if the links API cannot be reached. `tinycloud share unlink <id>` deletes a short link now; `tinycloud share revoke <id>` revokes the share and leaves the link to expire. A share too large to send as a link stops with `MAX_BYTES_EXCEEDED` before anything is shared. To send a share again, run `tinycloud share publish` again for the same file and recipients, or `tinycloud share notify <id>` while the short link is live. Keep complete URLs, including the `#` fragment, out of logs. `--notify` requires `read`; domain invitations also require `--notify-to <email>` at the exact domain, a matching sender/owner DID and node 1.17.3+. Invitation emails carry only a short link, and until the services that send them accept one `--notify` and `share notify` stop with `UNAVAILABLE` before sending anything. Session-only publishers can notify their own domain policies. Standalone `tinycloud share notify <id> --to <email>` refuses records without `read` and domain delivery on unsupported nodes before sending. It retries within 5 minutes of publication; after that it reports a non-retryable `partial-failure` (exit 9), and the sender must publish a new share to invite again. A confirmed repeat reports `already-delivered`; a failed history confirmation warns without hiding a successful delivery. Human publish prints only the URL; with `--notify --json`, the redacted publication JSON also contains `notification` with delivery status and attempts. The default lifetime is seven days, clamped to the verified session expiry; JSON output reports `expiryClamped`. Explicit `--expires` values beyond the session end fail; they are never shortened. See [REFERENCE.md](REFERENCE.md) for inspect, receive, list, show, unlink and revoke.
 
+Sharing to an email address, domain or DID isn't available in this release; link shares are.
+
 To show a person a document, page or small app, publish it as an artifact: a Markdown file, one self-contained HTML file, or a JSX component with a default export. Use `--to anyone` (the default) with `--artifact new --json`, then get the link with `tinycloud share show <id> --reveal-link`; `--json` output never contains the link. Revoke with `tinycloud share revoke <id>`. `--to anyone --action edit` is refused. See [REFERENCE.md](REFERENCE.md#artifacts) for the file kinds, the JSX library set and the `--tc-*` style tokens.
 
 After a share is published, a profile-lock or history-write failure warns: human output still shows the published link, but `--json` output stays redacted and `share show <id> --reveal-link` cannot recover an unrecorded share. Later `share list`, `share notify <id>`, and `share revoke <id>` cannot find it either. Standalone domain notification checks the recipient and local five-minute window before probing the node; an expired window stays a non-retryable partial failure even when `/info` is unreachable.