@sealant/mend 0.16.0 → 0.18.0

package/man/mend-codex.1

@@ -0,0 +1,60 @@
+.TH MEND-CODEX 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-codex \- launch codex, claude, or opencode in a recorded worktree
+.SH SYNOPSIS
+.B mend codex ["prompt"] [\-\-name <worktree>] [\-\-worktree <existing>] [\-\-model <id>] [\-\-effort <level>] [\-\-base <ref>] [\-\-ask] [\-\-fast] [\-\-detach|\-d] [\-\-foreground] [\-\-project <p>]
+.br
+also mend claude, mend opencode, with the same options
+.SH DESCRIPTION
+.PP
+mend codex, mend claude, and mend opencode are the same command with a different harness. The session runs in a workspace on the platform, in its own git worktree, and everything it does is recorded. This terminal attaches to it.
+.PP
+The worktree's name is asked first. \-\-name skips the ask; an existing name joins that worktree as a new session. \-\-worktree joins only and fails if the name is unknown. A quoted prompt becomes the first message.
+.PP
+Detach with Ctrl+] and the session keeps running. Reattach from any terminal with mend attach, or from the phone.
+.SH OPTIONS
+.TP
+.B \-\-name <worktree>
+name the worktree; an existing name joins it
+.TP
+.B \-\-worktree <existing>
+join an existing worktree only
+.TP
+.B \-\-model <id>
+the harness's model id
+.TP
+.B \-\-effort <level>
+low, medium, high, xhigh, or max
+.TP
+.B \-\-base <ref>
+the branch or sha the worktree starts from
+.TP
+.B \-\-ask
+keep the harness's permission prompts
+.TP
+.B \-\-fast
+priority processing where the harness offers it (codex)
+.TP
+.B \-\-detach, \-d
+launch without attaching
+.TP
+.B \-\-foreground
+stop the session when this CLI exits
+.TP
+.B \-\-project <p>
+the project by name, when the current directory is not inside it
+.SH EXAMPLES
+.PP
+.B mend claude "add a health endpoint"
+.br
+asks for a worktree name, then runs
+.PP
+.B mend codex \-\-name auth\-rework \-d
+.br
+start in the background
+.PP
+.B mend codex \-\-worktree auth\-rework
+.br
+a second session in the same worktree
+.SH SEE ALSO
+mend(1), mend\-attach(1), mend\-stop(1), mend\-run(1), mend\-sessions(1)

package/man/mend-completions.1

@@ -0,0 +1,14 @@
+.TH MEND-COMPLETIONS 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-completions \- print the TAB\-completion hook
+.SH SYNOPSIS
+.B mend completions zsh|bash
+.br
+.SH DESCRIPTION
+.PP
+Commands complete, and live session ids complete under TAB by asking the server.
+.SH EXAMPLES
+.PP
+.B mend completions zsh > "$fpath[1]/_mend"
+.SH SEE ALSO
+mend(1)

package/man/mend-connect.1

@@ -0,0 +1,25 @@
+.TH MEND-CONNECT 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-connect \- send this machine's provider credential to the platform
+.SH SYNOPSIS
+.B mend connect <claude|codex|github> [\-\-from\-stdin] [\-\-remove]
+.br
+.SH DESCRIPTION
+.PP
+Sessions run on the platform, so the platform needs your provider login. This reads the file the provider's own CLI wrote when you logged in (claude, codex) or asks gh for its token (github) and stores it under your own user. Nothing is shared with other users.
+.SH OPTIONS
+.TP
+.B \-\-from\-stdin
+paste a credential instead of reading the provider's file
+.TP
+.B \-\-remove
+disconnect the provider
+.SH EXAMPLES
+.PP
+.B mend connect claude
+.br
+after `claude login` on this machine
+.PP
+.B mend connect github \-\-remove
+.SH SEE ALSO
+mend(1), mend\-accounts(1)

package/man/mend-continue.1

@@ -0,0 +1,11 @@
+.TH MEND-CONTINUE 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-continue \- resume a session with its pending review follow\-up
+.SH SYNOPSIS
+.B mend continue [session\-id]
+.br
+.SH DESCRIPTION
+.PP
+The review comments you sent to the session become its first message. With no id, the newest session with a pending follow\-up is taken.
+.SH SEE ALSO
+mend(1), mend\-resume(1), mend\-sessions(1)

package/man/mend-doctor.1

@@ -0,0 +1,11 @@
+.TH MEND-DOCTOR 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-doctor \- check this machine's setup
+.SH SYNOPSIS
+.B mend doctor
+.br
+.SH DESCRIPTION
+.PP
+Read\-only. One line per fact: the server, the sign\-in, the platform connection, the provider accounts, the git key. Each unfinished line ends with the command that fixes it.
+.SH SEE ALSO
+mend(1), mend\-login(1), mend\-connect(1), mend\-keys\-init(1)

package/man/mend-dotfiles-sync.1

@@ -0,0 +1,15 @@
+.TH MEND-DOTFILES-SYNC 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-dotfiles\-sync \- capture config files from this machine into your store
+.SH SYNOPSIS
+.B mend dotfiles sync [\-\-all | paths...]
+.br
+.SH DESCRIPTION
+.PP
+Copies the named files from your home directory into your store on the server. \-\-all takes the known shell, git, and editor files. Setups that rely on ZDOTDIR do not transfer.
+.SH OPTIONS
+.TP
+.B \-\-all
+every known config file
+.SH SEE ALSO
+mend(1), mend\-dotfiles(1)

package/man/mend-dotfiles.1

@@ -0,0 +1,11 @@
+.TH MEND-DOTFILES 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-dotfiles \- your dotfiles on the server: repo and synced files
+.SH SYNOPSIS
+.B mend dotfiles [show]
+.br
+.SH DESCRIPTION
+.PP
+Workspaces apply your dotfiles at launch, from a repository you point the server at or from files mend dotfiles sync captured. This shows what is set.
+.SH SEE ALSO
+mend(1), mend\-dotfiles\-sync(1)

package/man/mend-env-cluster.1

@@ -0,0 +1,26 @@
+.TH MEND-ENV-CLUSTER 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-env\-cluster \- bind Kubernetes secrets and configmaps to the workspaces
+.SH SYNOPSIS
+.B mend env cluster add secret|configmap <name>
+.br
+.B mend env cluster remove <kind>/<name>
+.br
+.B mend env cluster sa <name> | sa \-\-clear
+.br
+.B mend env cluster [\-\-project <p>]
+.br
+.SH DESCRIPTION
+.PP
+For a Mend server running in Kubernetes. The platform mounts the named objects into the project's workspaces at launch; Mend never reads their contents. sa sets the service account the workspaces run as. Changes apply from the next launch; running workspaces keep what they started with.
+.SH OPTIONS
+.TP
+.B \-\-project <p>
+the project by name, when the current directory is not inside it
+.SH EXAMPLES
+.PP
+.B mend env cluster add secret app\-env
+.PP
+.B mend env cluster remove secret/app\-env
+.SH SEE ALSO
+mend(1), mend\-env\-load(1)

package/man/mend-env-load.1

@@ -0,0 +1,21 @@
+.TH MEND-ENV-LOAD 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-env\-load \- load a .env into the project
+.SH SYNOPSIS
+.B mend env load [file] [\-\-project <p>] [\-\-secret [A,B]]
+.br
+.SH DESCRIPTION
+.PP
+Ordinary names become configuration. Secret\-shaped names (KEY, TOKEN, PASSWORD, and the like) become secrets, which Mend stores encrypted and never shows again. Sessions receive both at launch. Default file: .env in the current directory.
+.SH OPTIONS
+.TP
+.B \-\-project <p>
+the project by name, when the current directory is not inside it
+.TP
+.B \-\-secret [A,B]
+send every name to secrets, or only the named ones, e.g. DATABASE_URL
+.SH EXAMPLES
+.PP
+.B mend env load .env.production \-\-secret DATABASE_URL,STRIPE_KEY
+.SH SEE ALSO
+mend(1), mend\-env\-show(1), mend\-env\-cluster(1)

package/man/mend-env-show.1

@@ -0,0 +1,15 @@
+.TH MEND-ENV-SHOW 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-env\-show \- what the project store holds: names only, never values
+.SH SYNOPSIS
+.B mend env show [\-\-project <p>]
+.br
+.SH DESCRIPTION
+.PP
+Configuration names and secret names for the project. Values never print.
+.SH OPTIONS
+.TP
+.B \-\-project <p>
+the project by name, when the current directory is not inside it
+.SH SEE ALSO
+mend(1), mend\-env\-load(1)

package/man/mend-help.1

@@ -0,0 +1,11 @@
+.TH MEND-HELP 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-help \- this index, or one command's page
+.SH SYNOPSIS
+.B mend help [command...]
+.br
+.SH DESCRIPTION
+.PP
+mend help alone lists every command by section. mend help <command> prints that command's page: usage, description, options, examples. mend <command> \-\-help is the same page.
+.SH SEE ALSO
+mend(1), mend\-man(1)

package/man/mend-keys-init.1

@@ -0,0 +1,11 @@
+.TH MEND-KEYS-INIT 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-keys\-init \- generate this machine's Mend deploy key (ed25519)
+.SH SYNOPSIS
+.B mend keys init
+.br
+.SH DESCRIPTION
+.PP
+Creates a key under ~/.config/mend/keys for projects adopted with \-\-auth mend\-key. Add the public key on your git host as a deploy key.
+.SH SEE ALSO
+mend(1), mend\-keys\-show(1), mend\-adopt(1)

package/man/mend-keys-share.1

@@ -0,0 +1,11 @@
+.TH MEND-KEYS-SHARE 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-keys\-share \- relay this machine's ssh\-agent to the server
+.SH SYNOPSIS
+.B mend keys share
+.br
+.SH DESCRIPTION
+.PP
+Bridge mode for projects adopted with \-\-auth bridge: the server's git operations sign with the keys in this machine's ssh\-agent, so hardware keys never leave here. Runs until Ctrl\-C.
+.SH SEE ALSO
+mend(1), mend\-adopt(1)

package/man/mend-keys-show.1

@@ -0,0 +1,11 @@
+.TH MEND-KEYS-SHOW 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-keys\-show \- print the public key
+.SH SYNOPSIS
+.B mend keys show
+.br
+.SH DESCRIPTION
+.PP
+The key to add as a deploy key on your git host.
+.SH SEE ALSO
+mend(1), mend\-keys\-init(1)

package/man/mend-login.1

@@ -0,0 +1,20 @@
+.TH MEND-LOGIN 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-login \- sign this terminal in through the browser
+.SH SYNOPSIS
+.B mend login [\-\-url <server>]
+.br
+.SH DESCRIPTION
+.PP
+Opens <server>/authorize in your browser. You press Authorize there. The CLI saves a device token to ~/.config/mend/cli.json with mode 0600. No password is typed in the terminal, and the token can be revoked from the server at any time.
+.SH OPTIONS
+.TP
+.B \-\-url <server>
+the Mend server. Default: MEND_URL, then http://localhost:3105
+.SH EXAMPLES
+.PP
+.B mend login \-\-url http://10.0.0.216:3105
+.br
+sign in to a LAN server
+.SH SEE ALSO
+mend(1), mend\-logout(1), mend\-pair(1), mend\-doctor(1)

package/man/mend-logout.1

@@ -0,0 +1,11 @@
+.TH MEND-LOGOUT 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-logout \- revoke this terminal's device token and forget it
+.SH SYNOPSIS
+.B mend logout
+.br
+.SH DESCRIPTION
+.PP
+Other terminals and devices keep their own tokens.
+.SH SEE ALSO
+mend(1), mend\-login(1)

package/man/mend-man.1

@@ -0,0 +1,11 @@
+.TH MEND-MAN 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-man \- one command's page, or the whole manual, in man
+.SH SYNOPSIS
+.B mend man [command...]
+.br
+.SH DESCRIPTION
+.PP
+Renders the same pages as roff and opens them in man. Without man on the PATH, the text page prints instead. The npm package also installs mend(1) and mend\-<command>(1), so man mend works after a global install.
+.SH SEE ALSO
+mend(1), mend\-help(1)

package/man/mend-pair.1

@@ -0,0 +1,15 @@
+.TH MEND-PAIR 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-pair \- pair a phone or a second machine
+.SH SYNOPSIS
+.B mend pair [\-\-url <base url>]
+.br
+.SH DESCRIPTION
+.PP
+Prints a QR code, the code itself, and the URL this server is reached at. The pairing is for one device, once, and expires after 10 minutes.
+.SH OPTIONS
+.TP
+.B \-\-url <base url>
+the address the other device should use for this server
+.SH SEE ALSO
+mend(1), mend\-login(1)

package/man/mend-projects.1

@@ -0,0 +1,11 @@
+.TH MEND-PROJECTS 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-projects \- adopted projects and their live sessions
+.SH SYNOPSIS
+.B mend projects
+.br
+.SH DESCRIPTION
+.PP
+One line per project, with the sessions running in it.
+.SH SEE ALSO
+mend(1), mend\-adopt(1), mend\-sessions(1)

package/man/mend-refresh.1

@@ -0,0 +1,11 @@
+.TH MEND-REFRESH 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-refresh \- fetch origin's branches into the store
+.SH SYNOPSIS
+.B mend refresh [project]
+.br
+.SH DESCRIPTION
+.PP
+New sessions base on the tips the store holds; this brings them up to date with origin. Default: the project the current directory belongs to.
+.SH SEE ALSO
+mend(1), mend\-adopt(1)

package/man/mend-rejoin.1

@@ -0,0 +1,15 @@
+.TH MEND-REJOIN 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-rejoin \- attach if live, otherwise resume
+.SH SYNOPSIS
+.B mend rejoin [session\-id] [\-\-harness <h>]
+.br
+.SH DESCRIPTION
+.PP
+With no id, the newest live session wins; failing that, the newest settled one.
+.SH OPTIONS
+.TP
+.B \-\-harness <h>
+the harness to resume with, when resuming
+.SH SEE ALSO
+mend(1), mend\-attach(1), mend\-resume(1)

package/man/mend-resume.1

@@ -0,0 +1,15 @@
+.TH MEND-RESUME 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-resume \- rejoin a settled session with its state restored
+.SH SYNOPSIS
+.B mend resume [session\-id] [\-\-with <harness>]
+.br
+.SH DESCRIPTION
+.PP
+Starts a new agent process from the saved harness state, so the conversation continues where it stopped. \-\-with switches the harness; the conversation carries over between claude and codex.
+.SH OPTIONS
+.TP
+.B \-\-with <harness>
+claude or codex; default: the one the session used
+.SH SEE ALSO
+mend(1), mend\-stop(1), mend\-rejoin(1)

package/man/mend-run.1

@@ -0,0 +1,18 @@
+.TH MEND-RUN 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-run \- run any command as a session
+.SH SYNOPSIS
+.B mend run [\-\-project <p>] \-\- <command...>
+.br
+.SH DESCRIPTION
+.PP
+The same worktree, record, and review as mend codex, with a command of your own in place of a harness. Everything after \-\- is the command.
+.SH OPTIONS
+.TP
+.B \-\-project <p>
+the project by name, when the current directory is not inside it
+.SH EXAMPLES
+.PP
+.B mend run \-\- aider \-\-model gpt\-5
+.SH SEE ALSO
+mend(1), mend\-codex(1)

package/man/mend-service-add.1

@@ -0,0 +1,21 @@
+.TH MEND-SERVICE-ADD 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-service\-add \- adopt a port something in the workspace already listens on
+.SH SYNOPSIS
+.B mend service add [session] <port> [\-\-name <n>] [\-\-udp] [\-\-http|\-\-https]
+.br
+.SH DESCRIPTION
+.PP
+For a server the agent started itself. The port becomes a Service, reachable on this machine like one mend service run started.
+.SH OPTIONS
+.TP
+.B \-\-name <n>
+the service's name. Default: the port
+.TP
+.B \-\-udp
+a UDP port
+.TP
+.B \-\-http, \-\-https
+how a browser should open it
+.SH SEE ALSO
+mend(1), mend\-service\-run(1), mend\-service\-list(1)

package/man/mend-service-connect.1

@@ -0,0 +1,15 @@
+.TH MEND-SERVICE-CONNECT 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-service\-connect \- bring live Services to this machine's loopback
+.SH SYNOPSIS
+.B mend service connect [name...] [\-\-port <p>]
+.br
+.SH DESCRIPTION
+.PP
+Each connection tunnels through the server, authenticated as you. With no names, every live Service. Ctrl\-C closes them.
+.SH OPTIONS
+.TP
+.B \-\-port <p>
+the local port, when connecting one Service
+.SH SEE ALSO
+mend(1), mend\-service\-list(1)

package/man/mend-service-init.1

@@ -0,0 +1,15 @@
+.TH MEND-SERVICE-INIT 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-service\-init \- scaffold mend.toml from package.json and compose ports
+.SH SYNOPSIS
+.B mend service init [\-\-yes]
+.br
+.SH DESCRIPTION
+.PP
+Writes a mend.toml in the current repository with one Service per script and exposed port it can find. Edit it afterwards; sessions read it from their worktree.
+.SH OPTIONS
+.TP
+.B \-\-yes
+write without asking
+.SH SEE ALSO
+mend(1), mend\-service\-run(1)

package/man/mend-service-list.1

@@ -0,0 +1,11 @@
+.TH MEND-SERVICE-LIST 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-service\-list \- every live service and its observed state
+.SH SYNOPSIS
+.B mend service list
+.br
+.SH DESCRIPTION
+.PP
+Name, session, port, whether it listens, and where it is reachable from here.
+.SH SEE ALSO
+mend(1), mend\-service\-run(1), mend\-service\-connect(1)

package/man/mend-service-logs.1

@@ -0,0 +1,15 @@
+.TH MEND-SERVICE-LOGS 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-service\-logs \- follow a supervised service's output
+.SH SYNOPSIS
+.B mend service logs <name\-or\-id> [\-\-from <sequence>]
+.br
+.SH DESCRIPTION
+.PP
+Replays the recorded output, then follows it live. Ctrl\-C stops following.
+.SH OPTIONS
+.TP
+.B \-\-from <sequence>
+start the replay at a record sequence
+.SH SEE ALSO
+mend(1), mend\-service\-run(1)

package/man/mend-service-restart.1

@@ -0,0 +1,11 @@
+.TH MEND-SERVICE-RESTART 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-service\-restart \- re\-run a service's recorded command, same URL
+.SH SYNOPSIS
+.B mend service restart <name\-or\-id>
+.br
+.SH DESCRIPTION
+.PP
+The port and the local address stay the same, so open tabs keep working.
+.SH SEE ALSO
+mend(1), mend\-service\-stop(1)

package/man/mend-service-run.1

@@ -0,0 +1,38 @@
+.TH MEND-SERVICE-RUN 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-service\-run \- start and supervise a server in the session's workspace
+.SH SYNOPSIS
+.B mend service run [session] \-\-port <port> [\-\-name <n>] [\-\-udp] [\-\-http|\-\-https] [\-\-no\-connect] \-\- <command...>
+.br
+.B mend service run [session] <name> [\-\-no\-connect]
+.br
+.SH DESCRIPTION
+.PP
+With \-\-, the command after it is started in the workspace and supervised: its output is recorded, and mend service restart re\-runs it. Without \-\-, the name is a Service declared in the worktree's mend.toml. mend service <name> is the shorthand for that.
+.PP
+The port is tunnelled to this machine's loopback as soon as it listens, unless \-\-no\-connect.
+.SH OPTIONS
+.TP
+.B \-\-port <port>
+the port the command listens on inside the workspace
+.TP
+.B \-\-name <n>
+the service's name. Default: the command
+.TP
+.B \-\-udp
+a UDP port
+.TP
+.B \-\-http, \-\-https
+how a browser should open it
+.TP
+.B \-\-no\-connect
+do not tunnel the port to this machine
+.SH EXAMPLES
+.PP
+.B mend service run \-\-port 3000 \-\- pnpm dev
+.PP
+.B mend service web
+.br
+the Service named web in mend.toml
+.SH SEE ALSO
+mend(1), mend\-service\-init(1), mend\-service\-connect(1), mend\-service\-logs(1)

package/man/mend-service-stop.1

@@ -0,0 +1,11 @@
+.TH MEND-SERVICE-STOP 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-service\-stop \- stop a service and close its host port
+.SH SYNOPSIS
+.B mend service stop <name\-or\-id>
+.br
+.SH DESCRIPTION
+.PP
+Ends the process and the tunnel. The record of its output remains.
+.SH SEE ALSO
+mend(1), mend\-service\-restart(1)

package/man/mend-sessions.1

@@ -0,0 +1,27 @@
+.TH MEND-SESSIONS 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-sessions \- sessions with their review facts
+.SH SYNOPSIS
+.B mend sessions [\-\-all] [\-\-project <p>] [\-\-json | \-\-json=v2]
+.br
+also mend status, with the same options
+.SH DESCRIPTION
+.PP
+One line per session: harness, worktree, status, and what the review found. Live sessions by default.
+.PP
+The JSON is stable for integrations. \-\-json is the v1 flat list; \-\-json=v2 groups sessions by worktree, the same shape mend worktrees prints.
+.SH OPTIONS
+.TP
+.B \-\-all
+settled sessions too
+.TP
+.B \-\-project <p>
+the project by name, when the current directory is not inside it
+.TP
+.B \-\-json
+the v1 flat list
+.TP
+.B \-\-json=v2
+grouped by worktree
+.SH SEE ALSO
+mend(1), mend\-worktrees(1), mend\-projects(1)

package/man/mend-shell.1

@@ -0,0 +1,13 @@
+.TH MEND-SHELL 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-shell \- open a shell in a live session's workspace
+.SH SYNOPSIS
+.B mend shell [session\-id\-prefix]
+.br
+.SH DESCRIPTION
+.PP
+A second terminal into the same workspace the agent works in, beside it. Useful for running the tests yourself or looking at a file.
+.PP
+With no id, the one live session is taken; with several, a picker opens. A prefix of the id is enough.
+.SH SEE ALSO
+mend(1), mend\-attach(1), mend\-service\-run(1)

package/man/mend-skills-push.1

@@ -0,0 +1,21 @@
+.TH MEND-SKILLS-PUSH 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-skills\-push \- upload ~/.agents/skills into the library
+.SH SYNOPSIS
+.B mend skills push [\-\-project [p]] [\-\-prune] [\-\-dir <path>]
+.br
+.SH DESCRIPTION
+.PP
+Scans the directory codex and claude read skills from and uploads every bundle. Sessions receive the library at launch. Unchanged bundles are skipped.
+.SH OPTIONS
+.TP
+.B \-\-project [p]
+push into the project's library instead of yours
+.TP
+.B \-\-prune
+remove server\-side skills the directory no longer has
+.TP
+.B \-\-dir <path>
+scan another directory. Default: ~/.agents/skills
+.SH SEE ALSO
+mend(1), mend\-skills(1)

package/man/mend-skills.1

@@ -0,0 +1,15 @@
+.TH MEND-SKILLS 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-skills \- your skill library on the server, or a project's
+.SH SYNOPSIS
+.B mend skills [list] [\-\-project [p]]
+.br
+.SH DESCRIPTION
+.PP
+Skills are instruction bundles the harness loads at launch. Yours apply to every session; a project's apply to sessions in that project.
+.SH OPTIONS
+.TP
+.B \-\-project [p]
+the project's library instead of yours
+.SH SEE ALSO
+mend(1), mend\-skills\-push(1)

package/man/mend-ssh-setup.1

@@ -0,0 +1,15 @@
+.TH MEND-SSH-SETUP 1 "" "mend 0.18.0" "mend manual"
+.SH NAME
+mend\-ssh\-setup \- make this machine ready to ssh into workspaces, once
+.SH SYNOPSIS
+.B mend ssh setup [\-\-key <path>]
+.br
+.SH DESCRIPTION
+.PP
+Registers a public key with the gateway (a key already in your ssh\-agent is preferred; nothing new is created unless there is none) and writes a Host mend\-ws block to ~/.ssh/config.
+.SH OPTIONS
+.TP
+.B \-\-key <path>
+the public key to register
+.SH SEE ALSO
+mend(1), mend\-ssh(1), mend\-shell(1)