Release and Verification

Before release, check not only the changed template but the full user scenario: from opening the page to a successful action or a clear error.

Preparation

• Record the changed files.
• Check which pages and modules are affected.
• Make sure secrets did not enter templates, JavaScript, logs, or public files.
• Prepare a short change summary.

Technical Check

Check	What to Look At
Build	No CSS, JS, or template errors
API	Requests use documented operations and variables
Authorization	Session and guest scenarios work correctly
Errors	The user sees a clear message
Logs	No passwords, PIN codes, tokens, or payment details

Interface Check

Check pages in light and dark themes:

• desktop;
• tablet;
• mobile;
• long table values;
• empty lists;
• images and icons;
• loading state;
• error state.

Scenario Check

Minimum set for the client site:

• registration;
• login and logout;
• password recovery;
• server selection;
• player cabinet;
• game accounts;
• payment;
• shop or another changed module.

After Publication

After deployment, check the production domain:

• home page opens;
• CSS and JS are served without 404;
• favicon and images load;
• /graphql is available;
• browser console has no critical errors;
• mobile version does not break tables or menu.