agent-platform release v4.30.3

Fixed

• Preset qwen3-8-27b declares the Hub’s weight size, 25 GiB (was 15), and names the hardware it is tuned for; every shipped preset’s weightsGiB is checked against the Hub in CI (giantswarm/agent-platform#535). Two components judge whether a GPU pool hosts a preset from two inputs: cluster-manager’s create_node_pool sizes the pool from the preset’s declared weightsGiB + overheadGiB, model-manager’s check_fit / load_model size the weights from the Hub (model.safetensors.index.json total_size, else the safetensors files) and add the preset’s overheadGiB. qwen3-8-27b declared 15 GiB for a 24.57 GiB repository (Inferact/Qwen3.8-27B-NVFP4: six shards plus nvfp4_experts_mtp.safetensors), so a pool of one 48 GiB GPU was judged to host it on the form (45 GiB) and refused at the serve step (54.6 GiB). The preset now declares 25 GiB and its description says that, as tuned (25 GiB of weights + 30 GiB of overhead, the CUTE_DSL_ARCH pin, --gpu-memory-utilization=0.60), no size of the curated AWS accelerator families hosts it — its target is a single 128 GB unified-memory Blackwell node; the flags are unchanged. devstral-small-2 declared 48 GiB “at BF16” for a 24.02 GiB FP8 checkpoint (mistralai/Devstral-Small-2-24B-Instruct-2512: quant_method: fp8; the index totals the six model-* shards, the consolidated-* files are a second copy of the same weights) and now declares 25 GiB. New make verify-preset-weights (tests/verify-preset-weights.py; collected by verify-all, so CI runs it for every PR) sizes each preset’s spec.model.id the way model-manager does and fails a preset below the Hub’s size, more than 15 % above it, or one the Hub cannot size — never skipped; tests/fixtures/serving-preset-weights-{understated,overstated}.yaml are its negative controls. Every other shipped preset is within tolerance (+0.3 % to +6.9 %).