majordomus bench baseline update

Run the benchmarks and record them as this platform's baseline (a reviewable, tracked file)

Usage

majordomus bench baseline update [OPTIONS]

Arguments

argument	value	default	description
--profile	quick \| full \| ci	full	How much to measure `quick` — Fast developer feedback: few samples `full` — Stable evidence: many samples, many cold spawns `ci` — Conservative: structural gates plus a modest measurement
--allow-dirty	flag	—	Record even from a dirty work tree
--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) `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)

Examples

Record this platform's accepted baseline

Runs the benchmarks and writes the result under .ai/repo/benchmarks/rust/ as a tracked, reviewable file. The full profile is the default; the quick profile is for trying the path out. A dirty work tree is refused unless --allow-dirty says otherwise.
```
$ majordomus bench baseline update --profile quick --allow-dirty
```
Verified by the example tests: exits 0.

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 bench baseline update --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.