feat(cli): account, rm -r and mkdir, Tab completion

account shows the account and does what the sign-up form and the Profile
page do: register (the passphrase floor and the hub's proof of work checked
here, the recovery key printed once), verify, change the passphrase, reset a
forgotten one, change the e-mail address, sign out everywhere, delete. A new
passphrase carries the copy of the account's keys each node keeps for
browsers first — opened under the old M, the same keys sealed under the new
one — and only then tells the hub; a refusal sets the copies back. A reset
restores them from the recovery copy. The connections that do it never make
keys nor ask for a device approval. This machine keeps the M it changed away
from, so a node out of reach is carried at its next connection; a copy under
an M it does not know is no longer rewritten, which locked the browsers out
after a passphrase changed elsewhere.

rm -r removes a folder and all it holds, from the node's operator key: the
files, then the folders deepest first, one confirmation that counts them.
mkdir makes folders, --parents the missing ones (not -p, the passphrase).

completion bash|powershell prints the script that makes Tab complete actions,
verbs, options and the paths of the groups this machine is signed in to,
cached two minutes; the deb and rpm packages install the bash one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1 files changed, 29 insertions, 1 deletions

diff --git a/packages/meshbay-cli/src/meshbay_cli/manpage.py b/packages/meshbay-cli/src/meshbay_cli/manpage.py
index c4710f3..b2e4926 100644
--- a/packages/meshbay-cli/src/meshbay_cli/manpage.py
+++ b/packages/meshbay-cli/src/meshbay_cli/manpage.py
@@ -171,6 +171,25 @@ says so once.
 ends the session on the hub, retires this machine's device key and erases
 everything stored.
 .PP
+.B account register
+creates an account: a new passphrase, typed twice, must have 12 characters
+and be hard enough to guess, as in the application.
+It prints the account's recovery key once \(em MeshBay keeps it nowhere \(em
+and asks for the code e-mailed to the address, or
+.B account verify
+takes it later.
+.B account passphrase
+changes a known passphrase: the copy of your keys each node keeps for browsers
+is sealed again, the same keys, under the new one, and only then is the hub
+told; if the hub refuses, the copies are set back.
+A node out of reach keeps its copy as it was, and this machine seals it again
+the next time it connects there.
+.B account reset
+is for a forgotten passphrase: a code e-mailed to the account's address, a new
+passphrase, and, if you have it, the recovery key, which gives back your keys
+on each node; without it, a group whose keys this machine does not keep needs
+its operator.
+.PP
 The first time this machine opens a group whose node holds no copy of your
 keys (the application's "Browser access" turned off), it asks to be linked as
 a new device and prints a code.
@@ -320,7 +339,9 @@ the members whose messages were read, the browser access setting),
 .B store.key
 only where the system has no key storage, and
 .B interactive.log
-(the interactive mode's log).
+(the interactive mode's log) and
+.B completion\-cache.json
+(the groups and what they hold, as Tab completion last read them; two minutes).
 .TP
 \fIname\fB.meshbay\-part\fR, \fIname\fB.meshbay\-part.json\fR
 A download in progress, next to where the file lands.
@@ -348,6 +369,13 @@ nor
 .B \-\-password
 is given.
 .TP
+.B MESHBAY_NEW_PASSWORD
+The new passphrase for
+.BR "account passphrase" ,
+when
+.B \-\-new\-password\-file
+is not given.
+.TP
 .B MESHBAY_CLI_HOME
 The data directory, instead of the default (see FILES).
 .TP