ReadonlychannelsEvery channel whose fader lies on a detected ring — the STRUCTURED field the banner renders from (named + joined client-side, in the operator's locale). Merged across rings when there are several: each of these channels really is in a loop.
Optional ReadonlydetailThe rings as node paths (main → input.omx_head_input_2 → …). LOG / DEBUG ONLY —
English engine prose, never rendered on the surface (i18n rule: the wire carries codes
and structured fields, the client owns display text).
The routing loop (howl-round) the engine's TOPOLOGY detector currently sees — a ring in the desired audio graph, e.g. a bus output patched back onto a channel that feeds it.
Unrelated to FeedbackCandidatesMessage, which is spectral: that one hears a ring in the AUDIO, this one reads a ring in the ROUTING. A topological ring is the cause; the spectral candidates are the symptom, and only if the loop gain is above unity.