SignalAuditResult

The three ways a signal audit and its exception list can disagree.

In the namespace construct::diag. Declared in src/libs/libconstruct/construct/batch/WorkerSignalAudit.hpp.

Detailed description

`undocumented` is the original question: unconnected, and nobody has said why. The other two are the list going stale, which a plain known-set cannot detect and which is how these lists rot:

- `stale` — the exception says "deliberately unconnected", but the signal now HAS a receiver. Someone wired it and left the excuse behind. - `obsolete` — the exception names a signal that no longer exists on any audited object. Renamed or deleted, and the entry outlived it.

Both are silent today and both make the next reader trust a document that is wrong, which is the failure mode §CIE-C3 (derive, never restate) is about.