majordomus mesh build-cache key

Every lockfile the repository tracks, with the key its install or build directory is cached under: schema version, platform, toolchain and input digest

Usage

majordomus mesh build-cache key [OPTIONS]

Arguments

argument	value	default	description
--kind	cargo-build-dir \| mix-deps \| npm-modules	—	Only this kind `cargo-build-dir` — The cargo build directory of a workspace: the dependencies compiled on the way, without incremental state. Restored only into a directory that is cold `mix-deps` — The `deps/` directory `mix deps.get` fills `npm-modules` — The `node_modules/` directory `npm ci` fills
--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

What each lockfile's install is cached under

Every lockfile the repository tracks becomes a cacheable thing with a key: a schema version, the platform, the toolchain as its executables state it, and the digest of its inputs. `--kind` narrows it to one kind; a repository with no lockfile of that kind says nothing here is cacheable, and a kind whose toolchain is absent says why it has no key.
```
$ majordomus mesh build-cache key --kind mix-deps
```
What it asserts: exits 0; prints platform.
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 build-cache key --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.