CLI reference
=============

The pages in this section document the actual ``chargelink`` command tree found in the repository snapshot. Every page below includes the raw argparse help output plus production-oriented examples built around profiles, packages, suites, and hardware IDs present in the snapshot.

.. toctree::
   :maxdepth: 1
   :caption: CLI command groups

   evse
   evcc
   hil
   scenario
   campaign
   qualification
   suite
   report
   trace
   replay
   lab
   beckhoff
   protocol
   artifacts
   sequence
   macro
   verdict
   step
   profile
   template
   library
   batch
   campaign-stress
   service
   requirements
   backend
   evidence
   audit
   ports
   env
   capture
   ci
   sessions
   fault
   network
   fuzz

.. list-table::
   :header-rows: 1
   :widths: 22 78

   * - Group
     - What it controls
   * - :doc:`evse <evse>`
     - Operate ChargeLink as an EVSE simulator and lab endpoint. This is the operator surface you use to start, stop, inspect, and hardware-bind live SECC runtime sessions.
   * - :doc:`evcc <evcc>`
     - Operate ChargeLink as an EVCC simulator or as a controller for external EVCC backends such as Josev and EVerest.
   * - :doc:`hil <hil>`
     - Run the HIL adapter layer for bench-oriented MCS and hardware-backed execution paths.
   * - :doc:`scenario <scenario>`
     - Validate and execute single JSON scenarios.
   * - :doc:`campaign <campaign>`
     - Run packaged interoperability and conformance campaigns and inspect their outputs.
   * - :doc:`qualification <qualification>`
     - Build or verify protocol qualification bundles and launch gates.
   * - :doc:`suite <suite>`
     - Run named ChargeLink suites that aggregate campaigns and qualification checks.
   * - :doc:`report <report>`
     - Generate, archive, comment, and filter human-readable run reports.
   * - :doc:`trace <trace>`
     - Inspect protocol traces and stream or export message-level evidence.
   * - :doc:`replay <replay>`
     - Replay stored runs and compare two traces or sessions.
   * - :doc:`lab <lab>`
     - Perform lab preflight checks and document a network or HIL topology.
   * - :doc:`beckhoff <beckhoff>`
     - Export Beckhoff synchronization metadata used in EL6761 or ADS-backed bench environments.
   * - :doc:`protocol <protocol>`
     - Decode, validate, inspect, and sequence protocol artifacts.
   * - :doc:`artifacts <artifacts>`
     - Inspect a run directory and export it as a bundle.
   * - :doc:`sequence <sequence>`
     - Record repeatable operator sequences and execute them later.
   * - :doc:`macro <macro>`
     - Store and replay short CLI macro strings.
   * - :doc:`verdict <verdict>`
     - Assign a final verdict to an operator-controlled run.
   * - :doc:`step <step>`
     - Track operator steps and their pass, warn, or fail outcomes.
   * - :doc:`profile <profile>`
     - List, inspect, validate, clone, and derive connection settings from profiles.
   * - :doc:`template <template>`
     - Create starter JSON files for scenarios and campaigns.
   * - :doc:`library <library>`
     - Validate catalog or library directories.
   * - :doc:`batch <batch>`
     - Run a folder of inputs and continue or retry a batch later.
   * - :doc:`campaign-stress <campaign-stress>`
     - Stress the campaign engine across protocol families to exercise concurrency and pacing.
   * - :doc:`service <service>`
     - List service names and validate service behavior against a trace or run.
   * - :doc:`requirements <requirements>`
     - Map campaign content to requirements and link imported requirement IDs to runs.
   * - :doc:`backend <backend>`
     - Inspect and diagnose EVCC backend adapters.
   * - :doc:`evidence <evidence>`
     - Map evidence, validate manifests, attest, sign, import, list, and export MCS or release evidence bundles.
   * - :doc:`audit <audit>`
     - Run commercialization and source-origin audits, including SBOM and release-blocker exports.
   * - :doc:`ports <ports>`
     - Check whether important operator ports are available on the current host.
   * - :doc:`env <env>`
     - Run an environment doctor for the current workstation.
   * - :doc:`capture <capture>`
     - Start generic captures and run MCS bench capture automation.
   * - :doc:`ci <ci>`
     - Run scenario, campaign, or job inputs under CI-style wrappers and export reports or JUnit XML.
   * - :doc:`sessions <sessions>`
     - List or inspect runtime sessions by run ID.
   * - :doc:`fault <fault>`
     - Inject protocol faults from the supported fault catalog.
   * - :doc:`network <network>`
     - Apply or disable network impairments such as delay, jitter, and packet loss.
   * - :doc:`fuzz <fuzz>`
     - Run protocol-family fuzzing passes and store their results as artifacts.