pub struct HistoryResult {
pub results: Vec<FeatureResult>,
pub timings: Vec<(String, f64)>,
pub wire_harness: Option<WireHarnessReport>,
pub pmi: Option<PmiReport>,
pub ports: Option<PortsReport>,
}Expand description
The whole-history output.
Fields§
§results: Vec<FeatureResult>§timings: Vec<(String, f64)>Per-feature wall-clock execution time (feature id, milliseconds) in run
order — the lightweight timing surface the engine-native history tree’s
“N ms” readout consumes. A REUSED (cache-replayed) feature records 0.0
(its geometry was not re-executed this run). INTERNAL side-channel:
#[serde(skip)] so it never changes the caller-facing execute_history_json
shape; brep-render reads it natively via the re-exported struct.
wire_harness: Option<WireHarnessReport>The wire-harness tail’s routing report (None when the request carries
no wireHarness block). INTERNAL side-channel like timings: never on
the JSON ABI; brep-render ships it to the harness panel.
pmi: Option<PmiReport>The PMI tail’s resolution of every view’s annotations (None when the
request carries no pmi block). INTERNAL side-channel like timings.
ports: Option<PortsReport>The ports tail’s resolution of the declared-ports block (None when the
document declares none). INTERNAL side-channel like timings: the tail
is not a feature, so this is where its unresolved references and refused
names surface.