pub fn advisories(map: &AssertionMap) -> Vec<String>Expand description
Things worth telling the author that do not make the map wrong.
A redundant watch is the one that matters today. Supercov already marks
every flow dirty when a dependency manifest or the execution configuration
changes, so naming one of those files per flow catches nothing extra. It
does teach a false model – that per-flow watching is how dependency drift
is caught – and an author who believes it spends the effort on entries that
change nothing instead of on the helper their claim actually rests on.