anchors failures

The observed failures that the spec has not yet explained.

Lists the failures that HAPPENED (ingested with 'anchors ingest --logs') and
that carry no conclusion in the spec yet.

A spec declares a failure as POSSIBLE without knowing how it will happen — an
`if x == null` foresees the failure without knowing where the null comes from.
Once the application runs, the log has the context that answers it.

Three conclusions, and all three are progress:

  cause found    write it beside the rule — the handling can stop being generic
  resilient      `@resilient: <reason>` — it leaves the radar without leaving the record
  still unknown  `@observing: <what was ruled out>` — different from nobody having looked

The third is what no observability tool records, and it is knowledge: the next person to
look starts from what was already ruled out, instead of from zero.

Usage

anchors failures [flags]

Flags

Flag	Default	What it does
--all		also list the failures that already carry a conclusion (resilient or under observation)
--map		path to the map
--root	.	project root

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