Guide: trace, replay, diagnostics, reporting, and artifacts
===========================================================

The artifact model is one of ChargeLink's most important product surfaces. Every meaningful run should become explainable through files, not only through live console output.

Core artifacts to know
----------------------
.. list-table::
   :header-rows: 1
   :widths: 35 65

   * - Artifact
     - Why it matters
   * - ``summary.json``
     - Fast high-level status and verdict.
   * - ``session.json``
     - Protocol and session identity.
   * - ``protocol_summary.json``
     - Protocol-centered summary for tooling and dashboards.
   * - ``protocol_report.json``
     - Standards- and behavior-oriented report payload.
   * - ``message_trace.json`` and ``trace.jsonl``
     - Message-by-message debugging.
   * - ``frames.jsonl`` and ``events.jsonl``
     - Transport and runtime event evidence.
   * - ``conformance_traceability.json``
     - Pack and case traceability.

Recommended operator loop
-------------------------
- Use ``chargelink trace`` when you need a fast message-level view.
- Use ``chargelink protocol validate`` when you want a quick semantic check.
- Use ``chargelink replay`` to compare two runs or to prove that a change did not regress a known-good path.
- Use ``chargelink report`` and ``chargelink artifacts`` when the output is leaving engineering and entering customer or release workflows.