Module profile 

Available on crate features std and ua only.

Client observations, retained evidence and user-agent emulation profiles.

The lifecycle is: capture traffic, retain counted evidence, analyze it, select correlated variants, then prepare them for replay. Each stage has a different contract; observed protocol support does not guarantee exact replay support.

• ProfileCapture binds typed protocol observations to a client and flow.
• ProfileEvidenceCollector retains bounded counts and samples.
• ProfileEvidence is the input to analyze_profile_evidence.
• AnalyzedProfile describes retained variants and inferred distributions.
• UserAgentDatabase indexes profiles for selection.
• EmulationContext carries deterministic connection and request draws.
• ProfilePreservationReport records where replay deviated from its capture.

CanonicalValue provides versioned bytes and stable identities for storage. Archive loaders validate retained evidence and recompute analysis; diagnostic JSON is a presentation of that data, not its canonical identity.

Legacy profile rows are converted into the same captured form when loaded. ProfileEmulateLayer applies selected profiles to traffic.

Modules

analysis

Derive bounded distributions and ordering rules from retained evidence.

capture

Typed observations of client traffic, before counting or inference.

compare

Retained tuple membership and bounded field diagnostics for complete captures.

evidence

Counts, samples and retention for observed client behaviour.

format

Stable canonical identities, versioned archives and legacy profile input.

model

Client identity, flow context and configuration-based profile models.

replay

Compile selected observations into request and connection configuration.

selection

Deterministic, independently keyed draws for profile selection.