@needmoretruth/nmts-cli 0.36.3 → 0.38.0

package/docs/commands/put.md

@@ -3,8 +3,8 @@
 Commands: put
 Tiers: put=medium · put.wallet=high(wallet)
 
-This is the command that spends. The price is one credit per started mebibyte, printed before the
-upload starts. In the default mode it asks first (answer at the terminal, or run with `--yes`);
+`put` spends credits: one per started mebibyte, and the price is printed before the upload
+starts. In the default mode it asks first (answer at the terminal, or run with `--yes`);
 in an auto mode it runs when you judge it is what the person wants.
 
 ```sh

package/docs/commands/wallet.md

@@ -74,12 +74,10 @@ Three coin subcommands sign, and every signed transaction is irreversible by any
   explorer. It is outside the wallet unlock and its ceiling. A standing share of every WAL
   payment is `nmts tip`, not a gift on its own.
 
-One more reads the gifts back, and one flag on it publishes a name:
-
-- `wallet hall` prints the gift hall of fame — the developer, then the ten largest senders as read
-  from the public chain, with the rest of the list at nmts.me/hall; reading it signs nothing and
-  needs no NMTS key. `--name <name>` (1 to 24 characters, no links, not an address) signs a
-  short message with the wallet this account pays from — the wallet a gift left from — so the
-  server shows that name beside its address, and `--remove` puts the entry back to a shortened
-  address. Reading which wallet that is opens the file list, so naming yourself needs an API key
-  where reading the hall needs none.
+`wallet hall` prints the gift hall of fame — the developer, then the ten largest senders as read
+from the public chain, with the rest of the list at nmts.me/hall; reading it signs nothing and
+needs no NMTS key. `--name <name>` (1 to 24 characters, no links, not an address) signs a
+short message with the wallet this account pays from — the wallet a gift left from — so the
+server shows that name beside its address, and `--remove` puts the entry back to a shortened
+address. Reading which wallet that is opens the file list, so naming yourself needs an API key
+where reading the hall needs none.

package/docs/commands/whoami.md

@@ -3,10 +3,10 @@
 Commands: whoami
 Tiers: whoami=none · whoami.reveal=high(reveal)
 
-Prints the account id the stored code belongs to, offline, with no server call. `--json` gives it
+Prints the account id the stored NMTS key belongs to, offline, with no server call. `--json` gives it
 to a program.
 
 `--reveal` prints the NMTS key itself. An agent never needs this — the tool already holds the
-code — so it is locked until a person runs `nmts unlock reveal` at a terminal, and then asked about
+key — so it is locked until a person runs `nmts unlock reveal` at a terminal, and then asked about
 on every run in every mode but skip-permissions. Never write the NMTS key anywhere it can be read
 again: a log, a commit, a file, a message. It is the only key to the account and cannot be rotated.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@needmoretruth/nmts-cli",
-  "version": "0.36.3",
+  "version": "0.38.0",
   "description": "Command-line and MCP access to NMTS (NeedMoreTruthStorage, https://nmts.me): open-source, end-to-end encrypted storage on the Walrus network. No fee to NMTS; you pay the network from your own wallet. For people and for their agents.",
   "license": "Apache-2.0",
   "publishConfig": {
@@ -77,6 +77,14 @@
       "types": "./dist/drive-paths.d.ts",
       "default": "./dist/drive-paths.js"
     },
+    "./drive-edit": {
+      "types": "./dist/drive-edit.d.ts",
+      "default": "./dist/drive-edit.js"
+    },
+    "./s3-gateway": {
+      "types": "./dist/s3-gateway.d.ts",
+      "default": "./dist/s3-gateway.js"
+    },
     "./upload-file": {
       "types": "./dist/upload-file.d.ts",
       "default": "./dist/upload-file.js"