# `MutagenEx.Progress`
[🔗](https://github.com/iautom8things/mutagen_ex/blob/v0.2.0/lib/mutagen_ex/progress.ex#L1)

Human-readable per-site progress feedback written to stderr.

Contract: `mutagen.mutation_pipeline.r15` (default-on-TTY, suppressed
with `--no-progress`).

`Mix.Tasks.Mutagen` drives progress from the runner's
`:on_site_completed` callback (the same per-site seam NDJSON streaming
rides). When progress is enabled it wraps the callback so each
completed site invokes `report/2` here with a meta map carrying the
running `index`, the total site count, and the site's status. No
`:telemetry` event is involved — the callback fires once per site, in
input order, in both `--max-concurrency 1` and `> 1` modes.

Output format:

    [12/345] killed   path/to/file.ex:42 :arith
    [13/345] survived path/to/file.ex:43 :arith
    [14/345] timeout  path/to/file.ex:51 :case_drop

- Lines are written to stderr; consumers redirect stdout (NDJSON or
  the final JSON document) without losing the progress feed.
- The status column is left-padded to a stable width so the eye
  tracks the file column.
- No carriage-return / cursor magic — `mix mutagen`'s consumers run
  under CI buffered I/O where re-paint tricks are a no-op anyway.

# `enabled?`

```elixir
@spec enabled?(:auto | :on | :off) :: boolean()
```

Decide whether to emit progress under the given `mode`.

`mode` shapes:
  * `:on`   — always emit (used by `--progress`-like overrides).
  * `:off`  — never emit (set by `--no-progress`).
  * `:auto` — emit only when stderr is connected to a terminal.

The TTY check uses `:io.getopts/1` against the `:stderr` device.
Returns a boolean.

# `report`

```elixir
@spec report(map(), IO.device()) :: :ok
```

Emit a single progress line for a completed site.

`meta` is the per-site meta the Mix task builds from the runner's
`:on_site_completed` callback. Only `:file`, `:line`, `:mutator`,
`:status`, `:index`, and `:total` are read.

---

*Consult [api-reference.md](api-reference.md) for complete listing*
