[P3] LivelockDetector: a body's own snapshots may read a correct hand-off as rapid state cycling #1180

#1185 moved the runner's feed to a round that timed out, which removed the false CRITICAL on healthy platform-thread runs. captureSnapshot() stays public for a body sampling its peers, and its rule is still five state changes in ten snapshots. By reading the rule, a correct ping-pong between two threads alternates states the same way, with no progress signal to tell them apart. Not measured: no row or probe has shown this yet.

Why not now. The runner no longer calls it, so it only affects a body that opts in, and the fix is a modelling decision.

What it would take. A probe with a correct SynchronousQueue ping-pong sampled through captureSnapshot(), then either a progress signal, a lower severity than CRITICAL, or removing the rule.