Fleet import in ONE call (2026-07-21, built from a real 8-hour incident: 24 strategies took 24 serial save→backtest→deploy round-trips).

Body: {"items": [{"name", "strategy_spec"}, ...], "deploy_to": <desk id>?} — at most 50 items. Per item: validate (validate_spec + the dynamic- universe check) → save → if deploy_to, create the FORWARD-ONLY deployment (same path as the single deploy route). Items that fail validation don't block the others; every failure is named in that item's errors[].

NO backtest runs in this request. Grading backtests for the new deployments are QUEUED on the bounded worker lane and attach in the background — the whole call returns in seconds for a 50-item fleet.

Auth: session, principal X-Vega-Key, or account key pair (the same require_user_or_session as POST /v1/strategies). deploy_to adds desk authorization exactly like the single deploy route: a key PAIR must match that desk (403 otherwise); a session/principal caller must OWN it.