majordomus mesh allocate

Reserve the next issue, case or ADR number for a session with one exclusive mesh claim on its id key, after surveying the tree, the worktrees, every ref and the journal; exits 10 when no server runs the mesh

Usage

majordomus mesh allocate [OPTIONS] <KIND>

Arguments

argument	value	default	description
<KIND>	issue \| case \| adr	required	The kind of identifier `issue` — An issue id, `I<nnnn>`, the name of `.ai/repo/project/issues/<id>.yaml` `case` — A case number, the identity before the first underscore of `test/cases/<n>_.sh` `adr` — An ADR number, the four digits that open `.ai/repo/adrs/<nnnn>-.md`
--session	<SESSION>	required	The mesh session the number is reserved for
--at-least	<N>	—	The lowest number to take: a survey run elsewhere, or a block a seat was given
--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

Reserve the next case number for a session

The number is reserved by one exclusive claim on `id:case/<n>` in the mesh of the server holding this checkout's lease, after surveying the tree, the sibling worktrees, every ref and every reservation the journal remembers. A reservation needs the running server that makes it atomic; without one the command exits 10 and says so.
```
$ majordomus mesh allocate case --session s1
```
What 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 allocate --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.