tine export

Added in v0.7, tine export loads a portable run and renders it as an OpenTelemetry GenAI OTLP/JSON document. Export is read-only: it never rewrites the source artifact or changes the v2 format.

Terminal

# Print one OTLP/JSON document to stdout
tine export result.tine

# Write a file, refusing an existing destination by default
tine export result.tine --output spans.json
tine export result.tine --output spans.json --force

# Send the same document to an OTLP/HTTP collector
tine export result.tine --endpoint http://127.0.0.1:4318
tine export result.tine --endpoint https://collector.example/v1/traces   --service-name coding-agent

Document or collector

The default --format otel-json writes the document to stdout or--output PATH. An existing file requires --force.
--endpoint URL implies --format otlp. Without an explicit endpoint, OTLP mode reads OTEL_EXPORTER_OTLP_ENDPOINT.
/v1/traces is appended unless the endpoint already ends there. A connection failure or non-2xx response exits nonzero instead of dropping the run.

Transport boundary

Runs can contain prompts, completions, and tool content. Cleartext HTTP is refused unless the host is a literal loopback IP such as 127.0.0.1 or::1, or --allow-insecure is explicit. Redirects and ambient proxy settings are not followed by the export transport.

Output contract

The document contains classic GenAI attributes alongside semantic-convention 1.36 structured messages, per-event span kinds, a scope schema URL, causal links, and reported cache, reasoning, and total usage. There is no separate --jsonflag: the command's document output is already JSON and uses the shared serializer.

The open v0.7.1 hardening pull request addresses audited depth, mixed-message-shape, and causal-edge round-trip cases. Until it is published, validate sensitive export/import workflows against representative runs.