majordomus devcontext explain

Why one canonical identifier is or is not in the context a request compiles to

Usage

majordomus devcontext explain [OPTIONS] <URI>

Arguments

argument	value	default	description
<URI>	<URI>	required	The canonical identifier, `majordomus://<kind>/<identity>`
--issue	<ISSUE>	—	An issue id (`I0301`) or its canonical identifier
--milestone	<MILESTONE>	—	A milestone id or slug, or its canonical identifier
--intent	<INTENT>	—	What the session is trying to do, in words; the only input the compiler infers from
--path	<PATHS>	—	A repository-relative path the work touches; repeat for each
--uri	<URIS>	—	A canonical identifier to seed with directly; repeat for each
--budget-tokens	<BUDGET_TOKENS>	—	The ceiling in estimated tokens
--max-depth	<MAX_DEPTH>	—	How far from a seed the walk goes
--floor	<FLOOR>	—	Relevance below which an entry is reported rather than given, between 0 and 1
--all-blocking-rules	flag	—	Every blocking rule of the layer, not only the ones the work reaches
--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	Output shape (accepted by every subcommand) `text` — Lines for a person `json` — One JSON document, deterministic

Examples

Why one thing is in the context

The identifier is judged under the same request `compile` takes: selected, excluded with the reason, folded into another identifier, held by the index and never reached, or unknown.
```
$ majordomus devcontext explain majordomus://issue/I0001 --issue I0001
```
What it asserts: exits 0; prints selected, majordomus://issue/I0001.
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 devcontext explain --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.