# Alpha 50.9.5 — Post-Moderation QA Checkpoint

## Release

- Exact tag: `v0.4.0-alpha.50.9.5`
- Commit: `4dbe56b`
- Deployment: test VPS
- Current release after deployment: `/opt/pixdala/releases/v0.4.0-alpha.50.9.5`

## Scope of Alpha.50.9.5

Alpha.50.9.5 is a patch release for the post-moderation workflow introduced in Alpha.50.9.4.

### Fixed

- The Mini App cell-report form now replaces the occupied-cell detail dialog instead of opening underneath it.
- The report target remains available while the report form is open, so the complaint can be submitted successfully.
- A regression test covers the corrected cell-report dialog transition.

## Automated verification

Current local and deployment verification:

- Structure: OK
- JavaScript syntax: OK
- Unit: 47/47
- Integration: 57/57
- API: 22/22
- Total: 126/126

## Manual Telegram / Mini App QA

Passed:

- Cell-content complaint can be submitted from an occupied cell.
- The complaint reaches the moderation workflow.
- The complaint can be processed by the moderator.
- Mandala-visual complaint can be submitted and processed.

## Open QA issues

### 1. Quarantined Mandala visual presentation

When the whole Mandala visual is hidden by moderation, the current Mini App presentation is not correct:

- the original artwork remains partially visible underneath the cell layer as a darkened/desaturated image;
- the moderation explanation is not presented directly inside the visual area.

Target behavior:

- completely remove the original artwork from the public visual layer;
- show a neutral quarantine state in the same visual area;
- display an explicit notice that the Mandala visual is temporarily hidden by moderation;
- preserve the cell structure and the user's ability to inspect the remaining public state where appropriate.

### 2. Moderation state propagation to already-open clients

After a moderator changes moderation state, an already-open Mini App currently reflects the result only after the page is refreshed or the application is restarted.

Target behavior:

- active clients should receive the new moderation state automatically;
- manual reload/restart should not be required;
- the first implementation should preferably extend the existing server-state synchronization / polling mechanism;
- a new realtime transport (SSE/WebSocket) should be considered only if the current synchronization model cannot provide sufficiently prompt and reliable propagation.

## Current status

The moderation foundation is implemented and functionally exercised, but it is **not yet fully verified** because the two QA issues above remain open.

No new functional release should be treated as the final moderation checkpoint until both issues are fixed and re-tested in the deployed Telegram Mini App.