Keep adjudication queues distinct from ordinary compliance queues

A customer-owned adjudication queue should not be an alias for an ordinary compliance-pending workflow. Define its own root-only membership, access scope, and decision readiness: approval may require server-confirmed readiness while rejection can remain immediately available. Preserve episode decisions in history alongside other resolutions without merging their authority models. During change archaeology, report helpers separately from UI wiring; adding a count function does not prove that per-tab badges were connected.