majordomus mesh state

The state every linked runtime converges on, summarised with its digest; --full for every session, claim, handover and review

Usage

majordomus mesh state [OPTIONS]

Arguments

argument	value	default	description
--full	flag	—	Every session, claim, handover and review, not the summary
--live-claims	flag	—	Only claims that are still held
--after	<AFTER>	—	Only what moved after this Lamport stamp
--session	<SESSION>	—	Only this session: its key or its bare id
--runtime	<RUNTIME>	—	Only this runtime (`<node>-<runtime>`), or every runtime of a node id
--kind	<KIND>	—	Only this collection: sessions, claims, overlaps, handovers or reviews
--limit	<LIMIT>	—	At most this many of each collection, the newest first kept
--open	flag	—	Only what is still open: active sessions, live claims, unanswered reviews, untaken handovers
--matching	<MATCHING>	—	Only what mentions this text: a path, a branch, an issue, a pull request, a word
--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) `vcs` — Tracked files, through the version-control index (the layer's contract); a layer none of which is tracked is read from the work tree `filesystem` — A walk of the work tree with the same glob semantics; untracked files included
--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 `text` — Lines for a person `json` — One JSON document, deterministic

Examples

The state every linked runtime converges on

Sessions, claims with their standing, handovers, reviews and the digest two runtimes compare — or, with no running server, why there is none.
```
$ majordomus mesh state
```
What it asserts: exits 0; prints cooperation inactive.
Tested by apps/majordomus-cli/tests/cli_examples.rs, which runs the command against the built executable and asserts what the page states.
Every claim still held

The whole state with only the claims still held, as docs/MESH.md lists it — or, with no running server, why there is none.
```
$ majordomus mesh state --full --live-claims
```
What it asserts: exits 0; prints cooperation inactive.
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 state --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.