majordomus mesh handover publish

Publish this checkout's newest handover record (or the one named) to every linked runtime

Usage

majordomus mesh handover publish [OPTIONS]

Arguments

argument	value	default	description
--path	<PATH>	—	The record, relative to the repository root, under .ai/local/state/handovers/
--issue	<ISSUE>	—	The issue the handover belongs to
--milestone	<MILESTONE>	—	The milestone it belongs to
--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

Publish this checkout's newest handover

The newest record under .ai/local/state/handovers/ travels to every linked runtime, bounded and identified by its body's digest. It needs the running server; without one it exits 10.
```
$ majordomus mesh handover publish --issue '#184'
```
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 handover publish --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.