majordomus mesh review answer

Answer a review request

Usage

majordomus mesh review answer [OPTIONS] <REQUEST>

Arguments

argument	value	default	description
<REQUEST>	<REQUEST>	required	The request's key, `<stream>/<review>`
--session	<SESSION>	required	The answering session's id within this runtime
--verdict	approved \| changes_requested \| commented	required	What the reviewer decided `approved` — the work is good as it stands and the requester may proceed `changes_requested` — the work needs changing before it proceeds; the note says what `commented` — an observation with no verdict: neither approval nor a request to change
--note	<NOTE>	—	The note
--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

Answer a review request from any runtime

approved, changes_requested or commented, with a note, replicated to every linked runtime. It needs the running server; without one it exits 10.
```
$ majordomus mesh review answer stream/r-000000000000 --session s1 --verdict approved
```
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 review answer --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.