majordomus mesh session close
Close a session; its claims end with it on every linked runtime
majordomus mesh session close
Usage
majordomus mesh session close [OPTIONS]Arguments
| argument | value | default | description |
|---|---|---|---|
| --session | <SESSION> | required | The session's id within this runtime |
| --repo | <PATH> | — | Start the search for the repository root here (default: the current directory) (accepted by every subcommand) |
| --discovery | vcs | filesystem | vcs | How declarative files are enumerated (accepted by every subcommand)
|
| --strict | flag | — | Refuse to proceed when any file of the layer carries an error diagnostic (accepted by every subcommand) |
| --share | <DIR> | — | The tool distribution's share directory (kinds.yaml, schemas/); default: $MAJORDOMUS_SHARE, then the repository's own share/, then the one beside the executable (accepted by every subcommand) |
| --format | text | json | text | `text` for a person, `json` for a machine; both render the same answer
|
Examples
-
Close a session and end its claims
Every claim the session holds ends with it, on every linked runtime. It needs the running server; without one it exits 10.
$ majordomus mesh session close --session s1What it asserts: exits 10.
Tested by apps/majordomus-cli/tests/cli_examples.rs, which runs the command against the built executable and asserts what the page states.
Where this comes from
Declared once in apps/majordomus-cli/src/cli.rs: clap for the structure, typed Rust metadata beside it for the examples. This page, majordomus mesh session close --help, docs/generated/cli.md and docs/generated/cli.json are projections of that one declaration.
The whole command line on one page: the registry's command-line page. The task lifecycle (init, start, finish, doctor, ...) belongs to the shell tool, a different program: Commands and its specification.