docs: second-round fixes from cross-check analysis

- Add 4 missing webhook trigger events: snapshot_create, snapshot_delete,
  branch_create, branch_delete
- Fix stale PG 9.6 references in FAQ and Joe Bot overview
- Add missing admin endpoints to API reference table (billing-status,
  activate, instance/logs WebSocket)
- Fix ws-auth method from POST to GET in API reference
- Add cross-link from RDS howto to RDS/Aurora refresh tool

https://claude.ai/code/session_011sPDgBjzL2N2X6jiYyoTjQ

Author: claude

docs/dblab-howtos/administration/data/rds.md

@@ -143,3 +143,7 @@ sudo rm -rf /var/lib/dblab/dblab_pool/data/*
 sudo umount /var/lib/dblab/dblab_pool/dump
 sudo rm -rf /var/lib/dblab/dblab_pool/dump
 ```
+
+## Alternative: RDS/Aurora refresh tool
+
+For large production databases, running `pg_dump` directly against production can hold xmin horizon for hours and create significant load. The [RDS/Aurora refresh tool](/docs/dblab-howtos/administration/data/rds-refresh) provides an alternative approach that dumps from a temporary RDS clone instead, leaving production untouched.

docs/joe-bot/index.md

@@ -23,7 +23,7 @@ This process is fully automated and takes only a few seconds, even for multi-ter
 
 ## Features
 - "Serverless EXPLAIN": engineers do not need to worry about the provisioning of independent database clones. The process is fully automated, so all the work looks like requests to analyze some query execution plan or modify database schema – and Joe takes care of it, ensuring that delivered results are identical to production.
-- PostgreSQL versions 9.6, 10, 11, and 12 are currently supported.
+- PostgreSQL versions 10 through 18 are supported.
 - Currently, Joe is provided in the form of Slack chatbot.
 - The provisioning of a new clone takes only a few seconds, regardless of the database size.
 - Each database clone is fully independent, so developers do not interfere with each other and do not need to wait.

docs/questions-and-answers.md

@@ -98,7 +98,7 @@ Yes. Monitoring can run in PostgresAI Cloud or in your own infrastructure. We se
 
 ## What Postgres versions are supported?
 
-postgres_ai monitoring supports Postgres 14+. DBLab Engine supports Postgres 9.6+.
+postgres_ai monitoring supports Postgres 14+. DBLab Engine supports Postgres 10+.
 
 ## Does it work with managed Postgres?
 

docs/reference-guides/database-lab-engine-api-reference.md

@@ -89,7 +89,10 @@ curl -H "Verification-Token: YOUR_TOKEN" http://localhost:2345/status
 | POST | `/admin/config` | Set config |
 | GET | `/admin/config.yaml` | Get full config (YAML) |
 | POST | `/admin/test-db-source` | Test source database connection |
-| POST | `/admin/ws-auth` | WebSocket authentication |
+| GET | `/admin/ws-auth` | WebSocket authentication token |
+| GET | `/admin/billing-status` | Billing status |
+| POST | `/admin/activate` | Activate billing |
+| GET | `/instance/logs` | Instance logs (WebSocket) |
 
 ## New in DBLab Engine 4.1
 

docs/reference-guides/database-lab-engine-configuration-reference.md

@@ -447,6 +447,10 @@ Webhooks provide a way to notify external systems about clone lifecycle events.
     - `clone_delete` - triggered when a clone is deleted. Supported since DBLab Engine 4.1.
     - `clone_protection_expiring` - triggered when a clone's protection lease is about to expire (based on `protectionExpiryWarningMinutes`). Supported since DBLab Engine 4.1.
     - `clone_protection_expired` - triggered when a clone's protection lease has expired and protection has been automatically removed. Supported since DBLab Engine 4.1.
+    - `snapshot_create` - triggered when a new snapshot is created. Supported since DBLab Engine 4.1.
+    - `snapshot_delete` - triggered when a snapshot is deleted. Supported since DBLab Engine 4.1.
+    - `branch_create` - triggered when a new branch is created. Supported since DBLab Engine 4.1.
+    - `branch_delete` - triggered when a branch is deleted. Supported since DBLab Engine 4.1.
 
 ### Webhook payload format
 Webhook requests are sent as HTTP POST with JSON payload containing: