Report PostgreSQL collation drift in live smoke

docs/CODEX_EXECUTION_LOG.md

@@ -1627,3 +1627,30 @@ Limitations:
 
 Next recommended pass:
 - Run release readiness, rebuild/deploy Tower and verify browser/GIS/demo smoke again.
+
+## Sprint 36 PostgreSQL collation maintenance visibility (2026-06-17)
+
+Changed:
+- Added PostgreSQL database collation version reporting to `scripts/live_migration_smoke.sh`.
+- The live smoke now prints `COLLATION_VERSION_MISMATCH` with stored and actual versions when a reused PostGIS volume was created under an older libc/collation runtime.
+- The smoke also prints the exact `ALTER DATABASE "... " REFRESH COLLATION VERSION;` acknowledgement command, but does not run it automatically.
+- Documented the Unraid maintenance procedure and backup/index review guidance.
+- Added regression coverage for the collation reporting path.
+
+Tested:
+- `cd backend && python -m pytest tests/test_live_migration_smoke_script.py -q`
+- `bash -n scripts/live_migration_smoke.sh`
+- `python -m compileall backend/app`
+- `cd backend && python -m pytest -W error::DeprecationWarning`
+- `cd frontend && npm run typecheck`
+- `cd frontend && npm run build`
+- `bash scripts/run_readiness_check.sh`
+
+Open:
+- Run the updated smoke against Tower to confirm whether the reused volume still reports a collation mismatch.
+
+Limitations:
+- The smoke reports and documents the maintenance action. It intentionally does not mutate collation metadata automatically.
+
+Next recommended pass:
+- Run release readiness, deploy Tower and decide whether to manually acknowledge the current collation version.