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, 9 insertions, 0 deletions

diff --git a/packaging/build/build-cli.sh b/packaging/build/build-cli.sh
index b697f10..b6bd563 100755
--- a/packaging/build/build-cli.sh
+++ b/packaging/build/build-cli.sh
@@ -50,6 +50,15 @@ run_venv -m meshbay_cli.manpage | gzip -9n > "$ROOT/usr/share/man/man1/meshbay-c
 [ "$(gzip -dc "$ROOT/usr/share/man/man1/meshbay-cli.1.gz" | head -c 3)" = ".TH" ] || {
     echo "!! the man page did not generate" >&2; exit 1; }
 
+# bash-completion loads it the first time Tab is pressed after `meshbay-cli`.
+echo "    generating the bash completion"
+COMPLETIONS="$ROOT/usr/share/bash-completion/completions"
+mkdir -p "$COMPLETIONS"
+MESHBAY_CLI_HOME="$STAGING/cli-home" run_venv -m meshbay_cli completion bash \
+    > "$COMPLETIONS/meshbay-cli"
+grep -q '^complete -F _meshbay_cli meshbay-cli$' "$COMPLETIONS/meshbay-cli" || {
+    echo "!! the bash completion did not generate" >&2; exit 1; }
+
 # --- The CLI and its own dependencies, out of the common tree ---------------
 # MOVE (not copy), as build-hub.sh and build-node.sh do: dpkg/rpm then know
 # these files belong to meshbay-cli. The list is kept for the maintainer