Deploy Bulb

POST /v1/accounts/{id}/deploy — deploy a validated bulb onto a paper account.

Provide exactly ONE source for the spec:

• strategy_spec: an inline strategy spec dict (validated server-side), or
• strategy_id: id of a strategy previously saved by the SAME principal.

name is an optional human label for the deployment (e.g. "oversold-bounce").

Deploys are FORWARD-ONLY (founder rule, 2026-07-17): the desk starts trading at the moment of deployment and only ever shows trades that happened while it was deployed. Historical performance lives in the strategy's BACKTEST report (stored per deployment, shown separately) — it is never replayed onto the desk as if the desk had traded it. The old backfill_days field (default 60!) silently pre-filled two months of simulated trades on every deploy and was removed for exactly that reason; unknown fields sent by old clients are ignored by pydantic.

Response to a deploy: the new deployment id + its lifecycle status.

warning carries an honest advisory (plain-words message + the verdict / confidence label / provenance caveat) when the deployed strategy has a KNOWN prior backtest that graded SHELF or inconclusive — the deploy still succeeds (paper is for learning), the warning just makes the backtest's "no" loud.