Type Alias CombinedOutput 

pub type CombinedOutput = CombinedOutput<CheckOutput, CombinedDupesSection, HealthReport>;

Concrete combined check + dupes + health envelope for full analyses.

Aliased Type

pub struct CombinedOutput {
    pub schema_version: SchemaVersion,
    pub version: ToolVersion,
    pub elapsed_ms: ElapsedMs,
    pub gate_outcomes: Option<GateOutcomes>,
    pub request_outcomes: Option<RequestOutcomes>,
    pub package_baselines: Vec<PackageBaselineStatus>,
    pub meta: Option<CombinedMeta>,
    pub check: Option<CheckOutput>,
    pub dupes: Option<CombinedDupesSection>,
    pub health: Option<HealthReport>,
    pub workspace_diagnostics: Vec<WorkspaceDiagnostic>,
    pub next_steps: Vec<NextStep>,
}

Fields

schema_version: SchemaVersion

Combined output schema version.

version: ToolVersion

Fallow CLI version that produced this output.

elapsed_ms: ElapsedMs

Wall-clock analysis duration in milliseconds.

gate_outcomes: Option<GateOutcomes>

The verdict of every gate this run evaluated, keyed by name. The CLI always emits it, with the default exit rule of each section that ran (error-severity-findings, health-findings). Without --fail-on-issues or --ci, the machine formats of the combined run exit 0 for findings, so most entries have enforced: false. With one of these flags, the findings rules and duplication-threshold are enforced, and every format exits 1 when one fails. For the default exit rules (error-severity-findings, health-findings), status gives the verdict of the human run. An advisory entry can report fail without a failure of the human run: an example is a stale-baseline entry that --fail-on-stale-baseline did not arm. A gate fails the build when status is fail AND enforced is true. The typed programmatic API leaves it absent. See [crate::GateOutcomes].

request_outcomes: Option<RequestOutcomes>

Every narrowing or shaping request this run RECEIVED, keyed by name, absent when it was asked for nothing. An entry whose status is not applied means the run could not do what it was asked and reported something WIDER instead, so what follows is a valid report of a scope nobody requested. Honoured requests are published too, with status: "applied", so an absent object means “nothing was asked for”, never “nothing failed”. See [crate::RequestOutcomes].

package_baselines: Vec<PackageBaselineStatus>

Applied package Git refs of the check and dupes sections. The map does not narrow the health section.

meta: Option<CombinedMeta>

Per-section _meta blocks, when --explain was passed.

check: Option<CheckOutput>

Dead-code section of the combined run.

dupes: Option<CombinedDupesSection>

Duplication section of the combined run.

health: Option<HealthReport>

Health section of the combined run.

workspace_diagnostics: Vec<WorkspaceDiagnostic>

Workspace-discovery, source-discovery, and analysis-stage diagnostics for the run (issue #2366). See CheckOutput::workspace_diagnostics for the full contract: root-relative paths, omitted when empty. The combined envelope carries them here rather than inside a section, so a run that skips a section (--skip check, --only health, --only dupes) still reports every diagnostic its analyses recorded.

next_steps: Vec<NextStep>

Read-only follow-up commands aggregated across the combined run’s findings. See CheckOutput::next_steps for the contract.