Struct ToolFindingsLayer 

pub struct ToolFindingsLayer {
    pub run: AnalysisRun,
    pub findings: usize,
    pub page: Vec<Finding>,
    pub truncated: bool,
    pub omitted: usize,
}

One live layer: its run evidence, and a bounded page of its findings.

Why the count and the page are separate fields

findings here is the layer’s real size and page is what fits. A single field would have to be one or the other, and a model reading a truncated count as a total under-reports a security result — the failure mode the whole module is written against, one level down. This is the vocabulary rto_graph::tool_context already uses for the same reason: a bound that reports what it bound.

Fields

run: AnalysisRun

The run that owns this layer: analyzer, version, backend, isolation, advisory database, command policy, source identity and report digest.

findings: usize

Every finding this layer owns — the true count, never reduced by the page bound.

page: Vec<Finding>

The findings actually included, most severe first (see security_list for why this order and not the store’s).

truncated: bool

True when page is shorter than findings.

omitted: usize

How many of findings are missing from page.

Trait Implementations

impl Clone for ToolFindingsLayer

fn clone(&self) -> ToolFindingsLayer

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for ToolFindingsLayer

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

Formats the value using the given formatter.

impl Serialize for ToolFindingsLayer

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.