majordomus product providers

Every provider the tool has an adapter for, with what this repository does with it

Usage

majordomus product providers [OPTIONS]

Arguments

argument	value	default	description
--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)
--format	text \| json	text	Output shape (accepted by every subcommand) `text` — Lines for a person `json` — One JSON document, deterministic
--featured	flag	—	Only the features the homepage shows (accepted by every subcommand)
--all	flag	—	Include drafts and deprecated features, not only the stable ones (accepted by every subcommand)
--area	<AREA>	—	Only features serving this operational area of the why catalogue (accepted by every subcommand)
--module	<MODULE>	—	Only features made of this capability module (accepted by every subcommand)
--names-command	<NAMES_COMMAND>	—	Only features made of this shell command (accepted by every subcommand)
--surface	<SURFACE>	—	Only features exposed through this surface: cli, api, mcp, cockpit or docs (accepted by every subcommand)
-q, --query	<QUERY>	—	Case-insensitive text over identities, titles, headlines, summaries, tags and bodies (accepted by every subcommand)

Examples

Every provider the tool has an adapter for

One line per template the distribution ships, with the bootstraps this repository's policy renders through it, the client configuration it carries for the shared MCP server, and the hooks the policy wires. The set is the templates; nothing here is a list of vendors.
```
$ majordomus product providers
```
Verified by the example tests: exits 0; prints PROVIDER, agents.

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 product providers --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.