Module coverage 

The CLI’s axis-coverage registry: every subcommand a caller can reach declares either which axes its clean verdict examined or why it emits no verdict at all. The rule, its vocabulary, and the validator live in memstead_base::ops::coverage; this module is the CLI consumer’s declaration, and the test at the bottom is the gate: it walks the live clap tree, so a new subcommand fails here until it declares, and a new axis fails every verdict row that has not met it.

Constants

HEALTH

memstead health under --strict: exit 0 is the clean verdict, and it answers exactly for the promoted set, always-on configuration and mount axes plus the include-gated promotions. Everything advisory by the strict contract is excluded by name.

PROJECTION_VERIFY

STATUS

VERIFY_ANCHORS

WORKSPACE_DUMP

Functions

surface_registry

Every CLI surface’s coverage row. Names are the clap path exactly as the walk below produces it (“workspace dump”, not “dump”). Feature-gated commands carry the same gate as their clap variant, so the lean build’s registry matches the lean build’s walk.