# DigiDala v0.4.0-alpha.46.5 — release changeset

Alpha.46.5 completes the current multi-Mandala destruction-observer correction. It restores the client-side reconstruction order needed by the server-authoritative destruction lifecycle, synchronizes remote reset with the end of the local particle animation, and prevents interaction with a Mandala while its remote destruction view is intentionally invisible.

## Release identity

```text
Commit:
06afd97f70df3feeba82af1cbd4be33778ee133a

Tag:
v0.4.0-alpha.46.5

Active release:
/opt/pixdala/releases/v0.4.0-alpha.46.5
```

## Release chain

Alpha.46.5 is the verified endpoint of the following controlled fixes:

- Alpha.46.3: changed Mini App cache-busting URLs to the release-specific `0.4.0-alpha.46.3` value so the updated client code is fetched by Telegram/WebView.
- Alpha.46.4: restored the pre-destruction client model reconstruction order used by the working Alpha.41 implementation, while preserving the multi-Mandala fields introduced later.
- Alpha.46.5: synchronized remote destruction reset with the end of the local observer animation and prevented clicks on an intentionally invisible Mandala container.

Historical tags remain immutable; no earlier release was retagged.

## Alpha.46.5 implementation scope

- added `remoteDestructionResetPending` to remember a server reset that arrives before the remote particle animation finishes;
- delayed the observer's final local reset until both the visual animation and the server reset are ready;
- preserved the existing destroyer-only server reset behavior;
- restored `mandalaWrap` visibility and pointer interaction when the remote reset completes;
- prevented interaction with the Mandala while its remote destruction view remains intentionally invisible;
- did not change backend lifecycle authority, Mandala storage, payment flow, support-Mandala identity, or polling transport.

## Verification

```text
Structure: OK
JavaScript syntax: OK
Unit: 10/10
Integration: 25/25
API: 13/13
Total: 48/48
```

The exact `v0.4.0-alpha.46.5` tag was fetched by the VPS and deployed successfully. The active `current` release became:

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

The release-managed web, API and bot services were restarted successfully by the deployment script.

## Manual Telegram QA

Passed:

- last participant sees the completion flow and can start destruction;
- an already-open observer receives the completion state and sees the filled Mandala during the transition;
- the observer sees the same Mandala's destruction particle animation after the destroyer starts the ritual;
- the observer is reset after the remote animation and the Mandala becomes visible and usable again;
- the observer does not independently perform the server-side destruction reset;
- Sandbox and Support Mandalas remain independent: destroying one does not reset the other;
- the same behavior is valid for the tested multi-client flow.

## Remaining UX finding

A short visual flash remains when switching between Mandalas: for a very brief interval the newly selected view can render the previous free-cell presentation containing the text `Пока свободно` before the new Mandala-specific rendering settles.

This is a client-side rendering transition artifact. It is **not** a lifecycle or data-isolation defect and is intentionally carried forward as a separate follow-up UX fix.

## Acceptance status

Alpha.46.5 is **verified for the destruction-observer and multi-Mandala independence scenarios tested in Telegram**. The transient old free-cell rendering during Mandala switching remains open as a small UX issue.