Trace Manifest (traces.json)
Legacy trace discovery manifest and csv_logging behavior.
Scope: Legacy Days. At the end of a legacy run with csv_logging=true, the legacy logger records the nonempty
protocol certificate files under log_path:
{
"version": 1,
"traces": ["dcqcn_events.csv", "wfq_events.csv"]
}version is currently 1; every traces entry is a filename relative to
log_path. Candidate families include PFC, AQM, DCQCN, WFQ, DRR, CUBIC, and
TCP discovery surfaces.
With csv_logging=false, the logger does not create log_path, CSVs, or the
manifest. leanguard-run prefers a valid manifest and otherwise scans its
known filenames for nonempty files.
The schema is implemented in src/utils/trace_manifest.rs; the legacy logger in
legacy/src/utils/shared_logger.rs writes it.