Struct CheckListing 

pub struct CheckListing {

    pub id: String,
    pub short_name: String,
    pub stage: Stage,
    pub source: Source,
    pub declared_severity: Severity,
    pub effective_severity: Severity,
    pub severity_overridden: bool,
    pub fix: Fix,
    pub status: Status,
    pub reason: String,
    pub scope_files: Vec<String>,
    pub scope_opt_in: Vec<String>,
    pub command: Option<String>,
}

One check, as reported by amont list.

Deliberately flat — this is what gets rendered as text or serialised to JSON, and a reader (human or agent) parsing the latter should not have to chase nested objects for a yes/no question.

Fields

id: String

<trigger>-<name> — what hook.skip and amont.severity.<key> resolve against.

short_name: String

stage: Stage

source: Source

declared_severity: Severity

What the check (or manifest line) declared.

effective_severity: Severity

What registry::Overrides::of would actually apply — NOT the same as declared_severity once amont.severity.* is configured. This is the one thing the old text-only list_checks never reported, and the exact “declared vs. effective” gap that caused a real bug in the fleet’s own severity column (see amont-fleet/src/severities.rs).

severity_overridden: bool

fix: Fix

status: Status

reason: String

Empty when status == Status::Runs; the same prose the text output always showed for the other three states.

scope_files: Vec<String>

scope_opt_in: Vec<String>

command: Option<String>

Some only for a declared, Runnable external — a builtin has no command to show, and an Unusable external never got far enough to have one.

Trait Implementations

impl Clone for CheckListing

fn clone(&self) -> CheckListing

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CheckListing

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.