FSM coverage
You will learn
How state and transition coverage see the arcs a run never took.
A state machine is verified by its arcs, not its states: 4 states with 12 transitions is 12 ways to be wrong, and visiting every state can leave half the arcs cold. The spec models it directly: state points and transition points, each with a hit count, and illegal transitions that fail the report the moment one warms. The widget is the discipline in another shape: 112 files pinned by sha256 in specs, every one accounted for -- 0 lost, 0 not kept, 0 unlocated. Nothing on the list is allowed to be unvisited.