release: bump version to 0.65.0

docs/technical/en/ops-runbook.md

@@ -61,6 +61,22 @@ Per-module restart:
 
 Per-module restart is preferred during development to avoid interrupting unrelated services.
 
+## Destructive Reset
+
+```bash
+./planet.sh destroy
+```
+
+`destroy` returns a local development environment to a near-empty project state. It requires typing `Y` before it runs; source files and existing `.env` files are preserved.
+
+Cleanup order and boundaries:
+
+- If `planet_postgres` is running, the script first clears the `public` schema in `planet_db`. This prevents old `collected_data.is_current = true` rows from making Earth OOBE report `ready=true` if Docker volume removal later fails.
+- Docker cleanup targets resources whose Compose project is `planet`, plus the explicit volumes `planet_postgres_data`, `planet_redis_data`, `postgres_data`, and `redis_data`; do not delete unlabeled volumes by a broad `planet_*` pattern, because another local project could own them.
+- Local build state removes `.venv`, frontend `node_modules` / `dist`, Planet state/cache, and scattered Python / Vite cache directories.
+
+After the reset, run `./planet.sh init` again to recreate tables and default seed data. Old collected records are not restored, and Earth OOBE is evaluated from the backend's real collection state on the next visit.
+
 ## Health Check
 
 ```bash