Struct CheckoutReport 

pub struct CheckoutReport {
    pub materialized: usize,
    pub skipped_present: usize,
    pub bytes: u64,
    pub resumed_live_tree: bool,
    pub refused: usize,
    pub manifest_secs: f64,
    pub fetch_secs: f64,
    pub commit_secs: f64,
    pub reresolved: u32,
    pub scope: Option<Vec<String>>,
    pub out_of_scope: usize,
    pub ranged: usize,
}

Fields

materialized: usize

skipped_present: usize

bytes: u64

resumed_live_tree: bool

Restart-matrix row taken.

refused: usize

Citations left in place rather than materialized (D0.3 legacy .flint/ paths, containment refusals). Never a silent drop: each has a conflict record.

manifest_secs: f64

Phase attribution for the agent-blocking path. Without these the checkout wall clock cannot be split between the manifest GET, the fan-out fetch window, and the local commit — which is the one fact any read-path decision here rests on.

fetch_secs: f64

commit_secs: f64

reresolved: u32

Passes re-run because the pointer moved past the document a pass read and a handle it cited was collected (handles design 2026-09-19): the checkout re-resolves instead of asking the caller to.

scope: Option<Vec<String>>

The admitted set this checkout was scoped to, or None for the whole manifest.

out_of_scope: usize

Citations the scope DECLINED. Zero for an unscoped checkout, and the number that says a scope did anything at all: a scope that admits everything reads exactly like no scope.

ranged: usize

Objects materialised through the RANGED path. On a cluster nothing else can tell “ranging did not help” from “ranging did not run” — the knob is a threshold and a threshold that never fires reads exactly like an optimisation that does not work.

Trait Implementations

impl Debug for CheckoutReport

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

Formats the value using the given formatter.

impl Default for CheckoutReport

fn default() -> Self

Returns the “default value” for a type.