ptp-telemetry-export

Run /ptp:telemetry export or /ptp:telemetry-export with no flags or arguments. It performs a global re-derivation of every epic's spans.csv plus _unattributed/spans.csv from the raw NDJSON stores and prints one JSON result object.

No. Export takes no flag, argument, or selector; every invocation is a global re-derivation. A scoped export would break the complete partition because the shared _unattributed CSV depends on reading every epic's raw store and ledger.

Export refuses non-fatally when a live ptp receiver for the same telemetry store answers its identity probe, since concurrent appends could be lost from the CSV. Stop the receiver with /ptp:telemetry stop first, then run export before any other funnel command.

No. The raw store is append-only and immutable; export never writes into raw/, never moves or marks entries, and only changes CSV placement. Re-attribution is purely a CSV-level outcome.

An incomplete trailing line is skipped, a malformed interior line is skipped and counted, and unrecognized entry kinds are skipped. Because the raw store is immutable, a torn entry is never repaired by any later export; the loss is bounded to the one record in flight.

Yes. Rows use a total ordering over start_ts, span_id, trace_id, then the serialized row, and each CSV is staged to a temporary file and published with one atomic rename, so an unchanged store yields byte-identical outputs.