Update README.md

Added production usage checklist

Author: bakwc

README.md

@@ -30,6 +30,7 @@ With a focus on high performance, it utilizes batching heavily and uses C++ exte
   - [Advanced Features](#advanced-features)
     - [Migrations & Schema Changes](#migrations--schema-changes)
     - [Recovery Without Downtime](#recovery-without-downtime)
+- [Production usage](#production-usage)
 - [Development](#development)
   - [Running Tests](#running-tests)
 - [Contribution](#contribution)
@@ -304,6 +305,15 @@ tables: ['table_1', 'table_2*']
 
 In case of a failure or during the initial replication, `mysql_ch_replicator` will preserve old data and continue syncing new data seamlessly. You could remove the state and restart replication from scratch.
 
+## Production usage
+
+Here is the checklist for production. Please read it carefully and confirm every point. If you have any questions - feel free to ask in discussion / issues. Following the checklist is critical to avoid any issues on prod.
+
+#### Checklist
+
+- [ ] No manual changes are made directly to ClickHouse databases or tables. All modifications (indexes, table settings, etc.) must be applied as overrides in the mysql_ch_replicator config.yaml.
+- [ ] All MySQL migrations undergo either CI/CD or manual testing before deployment. No migration is applied to production without being tested. The tests verify that replication continues to work correctly and that new records are successfully replicated from MySQL to ClickHouse after the migration.
+
 ## Development
 
 To contribute to `mysql_ch_replicator`, clone the repository and install the required dependencies: