# Alpha 50.6.5 — Competitive queued-creation response fix

## Summary

Alpha 50.6.5 fixes a bot-side failure when `/new_competitive` creates a Competitive campaign while another Competitive campaign is already active.

## Root cause

The internal Competitive creation API returned two different response shapes:

- an active campaign returned a full campaign view with nested `campaign.mandala`;
- a queued campaign returned the compact queue entry without `campaign.mandala`.

The administration bot expects the create response to expose `campaign.mandala.cell_price_pix`, so creating a queued campaign failed at the final confirmation step with:

```text
Cannot read properties of undefined (reading 'cell_price_pix')
```

The problem predates the 50.6.4 size-selector logic; Alpha 50.6.4 exposed it during manual QA because a new campaign was being added while an existing Competitive campaign was active.

## Fix

`createCompetitiveCampaign()` now returns one consistent full Competitive campaign view for both active and queued campaigns, including the concrete Mandala data under `campaign.mandala`.

The API regression test now verifies the queued create response contains the Mandala price and dimensions.

No Mini App client change is required for this fix.

## Verification

Expected automated verification remains:

- Structure: OK
- JavaScript syntax: OK
- Unit: 14/14
- Integration: 46/46
- API: 17/17
- Total: 77/77

## Deployment / manual QA

Pending.