Post-run evidence of whether the resource caps a `ProcessGroup` carried actually fired — one `LimitVerdict` per axis, read from the container the group itself owns. See `ProcessGroup.LimitEvidence()` for when it becomes available and what each axis means. Deliberately per-axis rather than one whole-group verdict: folding three honest three-valued verdicts into one would have to merge `NotTripped` and `Unknown` together, turning "we have no evidence" into "no". Sealed with an internal constructor — built only by the backend that reads it. Covers only `MemoryMax`, `MaxProcesses`, and `CpuQuota` (the `Cpu` axis is additionally guarded against `CpuTimeMax` — see `CappedAxes.GuardCpuVerdict`). `IoMax` and `CpuAffinity` have **no** corresponding axis at all: no containment mechanism here keeps a post-mortem "this whole-tree I/O or affinity cap engaged" counter, so there is nothing honest to report for them, ever — not even `Unknown`. `WindowsUiRestrictions` and `OomGroupKill` are policy toggles rather than caps that "fire", so they are likewise out of scope.