anchors coverage

Show coverage by scenario, by line, of the DIFF and the delta.

Reads the signals from 'anchors ingest' and answers the confidence questions:

  anchors coverage                    overview: scenarios with no green test + line < threshold
  anchors coverage <spec>             the scenarios of ONE spec and which are proven
  anchors coverage --diff main --lcov cov.info   is what I CHANGED (vs main) covered?
  anchors coverage --delta            has coverage DROPPED since the previous ingestion?

Three complementary questions:
- by SCENARIO: does each spec requirement have a test that passed? (semantics)
- of the DIFF: are the lines you changed (git diff) covered? (catches a bug on the new line)
- DELTA: has global coverage dropped vs. the previous measurement? (catches coverage regression —
  code fully covered in the diff, but which brought down the coverage of another part)

Usage

anchors coverage [<spec>] [flags]

Flags

Flag	Default	What it does
--delta		has coverage dropped since the previous ingestion?
--diff		coverage of the DIFF vs this git ref (e.g. main)
--diff-file		coverage of the DIFF from a unified diff (non-git fallback)
--lcov		the lcov to cross with the diff (mandatory with –diff)
--map		path to the map
--root	.	project root
--threshold	70	coverage threshold (%)

Confronting the project — family

Commands of the same family — what tells each apart:

Command	What it does
anchors check	Run the quality gates (the pipeline)
anchors verify	Run EVERYTHING the phase requires: Anchors gates + external tools
anchors coverage	Show coverage by scenario, by line, of the DIFF and the delta
anchors stale	List stale edges — what changed and has not been reconfronted
anchors impact	Impact analysis: what a change to this file reaches
anchors failures	The observed failures that the spec has not yet explained