Complete the execution cluster under the active UI instead of leaving JobEngine, Scheduler, Dead-Letter, and Scanner support flows split across stale aliases or half-wired pages.
Keep operator workflows usable end to end: inspect jobs, open DAG context, manage quotas, replay dead-letter entries, follow scheduler runs, and finish scanner-support actions without console-only placeholders.
Jobs & Queues is the execution overview, not a dead-end card deck. It must deep-link into JobEngine, Scheduler, Dead-Letter, and related operator pages.
Jobs & Queues must not advertise fake row-level mutations. If the overview cannot perform run, pause, drain, or replay locally, its visible actions must be relabeled as honest handoffs into the canonical downstream surfaces that own those operations.
Overview filters inside Jobs & Queues must be functional on every tab they appear on. Inert search/select controls are treated as a behavioral defect, not acceptable placeholder chrome.
JobEngine owns queue health, job detail, DAG context, and quota controls.
Scheduler owns run monitoring, schedule management, worker fleet, and run-stream drill-in.
Dead-Letter owns queue browse, replay, resolve, export, and handoff back to canonical job detail.
Scanner Ops remains scanner-owned, but its supporting actions must be honest and usable because it is part of the same operator journey.
