I kept calling a Dusk node one job. Then I read the prover spec: proof generation is single-threaded, and each worker gets 1 core. Consensus uptime can look perfect while proof capacity is the bottleneck. Should dashboards show worker saturation—not just “online”? @Dusk $DUSK #dusk