docs(v2): align runtime and operations documentation with compose behavior

CONTRIBUTING.md

@@ -45,6 +45,13 @@ docker compose -f docker-compose.yml -f docker-compose.dev.yml up --build
 docker compose -f docker-compose.yml -f docker-compose.release.yml up -d --build
 ```
 
+### Verify release topology assumptions
+
+```bash
+docker compose -f docker-compose.yml -f docker-compose.release.yml config
+./scripts/verify_release_topology.sh
+```
+
 ## Day-to-Day Feature Workflow
 
 1. Sync `develop`
@@ -88,6 +95,7 @@ docker compose -f docker-compose.yml -f docker-compose.dev.yml run --rm web sh -
 - Keep snapshot storage file-based and volume-backed.
 - Do not introduce MongoDB or Elasticsearch as source of truth.
 - Keep legacy provider/Celery sync code isolated behind `LEGACY_PROVIDER_STACK_ENABLED=1`.
+- Keep runtime/docs consistency aligned with `docs/runtime-consistency-checklist.md`.
 
 ## Repository Bootstrap Commands