# PixDala alpha.42 — release changeset

Alpha.42 is the verified bot-promotion and deployment-safety release following alpha.41.

## Release identity

```text
Migration commit:
de6136b

Final release commit:
f4db92d

Tag:
v0.4.0-alpha.42
```

## Change

Promoted the Telegram bot from the former test-bot naming to the main PixDala naming while
keeping the existing test Mini App environment.

Git-managed bot files are now:

```text
bot/bot.cjs
infra/systemd/pixdala-bot.service
```

The release deployment script now manages `pixdala-bot` and contains rollback compatibility
for the legacy `pixdala-test-bot` unit used by pre-migration releases. The legacy unit must not
run simultaneously with the new unit because both use the same Telegram bot token.

## Runtime configuration

The main Telegram bot is `@PixDala_bot`. The token remains external in:

```text
/opt/pixdala/.env
TELEGRAM_BOT_TOKEN
```

The Mini App URL remains:

```text
https://im-test.bktis.ru/apps/miniapp/
```

## Verification

```text
Structure: OK
JavaScript syntax: OK
Unit: 10/10
Integration: 17/17
API: 8/8
Total: 35/35
```

Deployment used the exact tag `v0.4.0-alpha.42` and completed successfully. Active release:

```text
/opt/pixdala/releases/v0.4.0-alpha.42
```

Manual Telegram QA passed on the main bot:

- `/start`
- Menu Button
- `/help`
- Mini App/API synchronization
- cell occupation

## Runtime migration note

After switching `/opt/pixdala/.env` to the main bot token, the bot picked up the new token after
restart while the API initially continued using the previous token. Restarting
`pixdala-test-api.service` synchronized the runtime configuration; the Mini App then returned to
normal API synchronization and cell occupation worked. This was a runtime restart/configuration
issue, not a code defect in alpha.42.

## Scope boundary

Alpha.42 does not implement Telegram Stars payment, pix/pixcoin, or any economic behavior.
The next planned stage is the minimal Telegram Stars payment foundation.