# Alpha.50.9.9 — Changeset

## Scope

Alpha.50.9.9 supersedes the pre-deployment Alpha.50.9.8 candidate. It carries forward the report-control and moderator-notification improvements and adds the two follow-up fixes found during pre-deployment review. No Mandala mechanics, payment logic, moderation lifecycle, or locale-synchronization behavior is changed.

## 1. Moderator coordinate context

- Adds `mandala_cols` to the moderation repository query used to build cell complaint context.
- This supplies the configured grid width required to derive 1-based row and column coordinates for the moderator notification.
- No database migration or new persisted field is required.

## 2. Mini App report controls

- Applies the dedicated `report-action` class to the cell-content and Mandala-visual report buttons in `apps/miniapp/index.html`.
- This activates the subdued warm-neutral report style introduced for Alpha.50.9.8.
- Primary buttons and unrelated controls remain unchanged.

## 3. Candidate lineage

- `v0.4.0-alpha.50.9.8` was tagged from commit `51c1fef` but was not deployed.
- Commit `45cb428` adds the missing moderation repository field.
- Commit `8aa0f40` adds the missing Mini App report-button styling hooks.
- Alpha.50.9.9 is the deployment candidate containing both follow-ups.

## Verification

- Structure check: OK
- JavaScript syntax: OK
- Unit: 50/50
- Integration: 58/58
- API: 23/23
- Total automated tests: **131/131**

## QA gate

After deployment, manually verify:

1. The Mini App report buttons are readable but remain visually secondary in the dark theme.
2. A cell complaint notification in Telegram contains reason, comment, Mandala, cycle, cell number, participant, reporter, public name/message and 1-based row/column coordinates.
3. The previous moderation/realtime/locale behavior remains intact.
4. The newly deployed Mini App is picked up without manually clearing the client cache, validating the test-VPS Nginx HTML cache policy.

## Next product phase after successful QA

1. Finalize the User Agreement / Terms.
2. Finalize Rules and moderation/reporting policies.
3. Purchase the DigiDala domain and prepare the public web/branding baseline.
4. Plan staged distribution through Telegram groups with controlled onboarding and feedback.