Studio 4.10: explainable auto-sizing and a saner input flow

Usability release, driven by testing with real exported reports.

Auto-size explains itself
The decision now stays on screen under the button: why this TP (with the exact GB math), the trade-off when one copy spans several workers, the precision change that would keep it inside one node, and an honest bottom line: fits and passes, or fits but an SLO fails for reasons hardware cannot fix.

Input flow matches how people decide
SLO targets live in the Workload station where presets set them. Hardware runs GPU, then GPUs per worker, then resilience, then Auto-size; workers and TP sit after it as labeled fine-tune controls. MFU, MBU, interconnect and overhead fold into an Advanced tuning drawer.

Honest P95 verdicts
A new recommendation distinguishes a fixable P95 miss (it names the batch value that would meet the target, or speculative decoding) from a workload whose reasoning + output token count cannot meet the target on any amount of hardware, and says which workload knob to change. The Balanced configuration card and the bottleneck line no longer contradict a failing SLO.