# DigiDala Alpha 50.9.13 — production infrastructure

**Status:** deployed to staging and production; production manual QA passed.

## Scope

This candidate adds the first version-controlled production runtime for DigiDala while preserving the existing staging environment unchanged.

### Production identity

```text
Public product: DigiDala
Domain:         https://digidala.ru/
Bot:            @DigiDala_bot
Root:           /opt/digidala
Web:            127.0.0.1:8082
API:            127.0.0.1:8091
Database:       /opt/digidala/data/digidala-production.db
```

### Added production infrastructure

- `digidala-production-web.service`
- `digidala-production-api.service`
- `digidala-production-bot.service`
- HTTP bootstrap and HTTPS Nginx configurations for `digidala.ru`
- `scripts/deploy-production.sh`
- `scripts/rollback-production.sh`
- `.env.production.example`
- production deployment documentation and regression tests

### Isolation

Production has its own runtime directory, database, campaign assets, ports, environment file and systemd service names.
The existing staging environment remains:

```text
im-test.bktis.ru
@PixDala_bot
/opt/pixdala
```

### Original candidate scope boundary

Before production bootstrap, the release did not switch DNS, create the production database on the VPS, issue the certificate, or start `@DigiDala_bot`.
Those were intentionally controlled as one-time infrastructure steps after the candidate passed staging checks.

## Post-release outcome — 2026-10-03

The exact tag `v0.4.0-alpha.50.9.13` was subsequently deployed and verified on both staging and production.

### Staging

```text
Structure: OK
JavaScript syntax: OK
Unit: 57/57
Integration: 58/58
API: 23/23
Total: 138/138
```

Manual Telegram QA passed before production promotion.

### Production

- Production runtime `/opt/digidala` was bootstrapped with independent services, HTTPS and a separate SQLite database.
- `@DigiDala_bot` was configured with Main Mini App and Menu Button pointing to `https://digidala.ru/apps/miniapp/`.
- The production Mini App and API responded successfully after deployment.
- Manual production QA passed for bot/Mini App launch, Telegram-authenticated Sandbox occupation, RU/EN, `/admin`, Competitive creation/queueing and `1 Star = 1 Pix`.
- The initial production database contains only release-provided configuration and production-created runtime data; staging/test data was not copied.
- A missing `TELEGRAM_SUPERADMIN_IDS` value was corrected in the production `.env` and required only a production-bot restart; the tagged application source was not changed.

Alpha.50.9.13 is therefore the current production application checkpoint. The next project change should follow the staged-release workflow documented in `AI_HANDOFF.md` and `docs/PRODUCTION_DEPLOYMENT.md`.