Studio 4.9.1: auto-size solves TP, workers and batch together

Follow-up driven by a real exported report: 4.9.0's auto-sizer kept batch fixed, which ballooned worker counts for latency-tolerant workloads and produced configurations its own recommendations then criticized.

• Auto-size now treats batch as part of the solution. Interactive workloads (any SLO set): fewest workers that admit the peak concurrency at batch 64 or less, grown until the configuration fits. No SLOs: treated as offline, minimal hardware, largest fitting batch, queueing accepted.
• A TTFT target widens TP before sizing, since prefill speed scales with TP.
• Cross-node TP with the penalty already modeled (interconnect 0.75 or less) is reported as an informational note, not a critical finding.
• Queue guidance computes worker needs correctly when TP spans workers and offers the batch value that admits everyone when memory allows.

Verified across seven scenarios from consumer 2x RTX 4090 chat to 2.8T-parameter models on B300 fleets: every auto-sized result fits and passes its SLOs. Example regression: Kimi K3 BF16, document generation, 250 concurrent went from 64 workers with 186 calls queueing to 16 workers with all 250 admitted.