v0.0.2

docs/data-migration.md

@@ -1,11 +1,10 @@
-# Importing data from the Python/TypeScript release
+# Data migration
 
-The current release does not perform automatic data migration and does not expose the
-old `migrate` command. The supported path is the explicit, copy-only
-`import-python` command. See [data-import.md](data-import.md) for the full source
-discovery, validation, rollback, and failure rules.
+Version **0.0.2** performs automatic, transactional schema migration for supported Rust databases. A database created by Rust 0.0.1 uses schema v1; on startup 0.0.2 validates it, adds `default_routeros_username` and `default_routeros_password`, updates `schema_info.schema_version` to `2`, validates the resulting schema, and then starts the service. No manual `sqlite3` command is required.
 
-For the standard layout of the supplied legacy project:
+The automatic migration applies only to the supported Rust schema. It does not convert the previous Python/TypeScript application database. For that source, use the explicit, copy-only `import-python` command described in [data-import.md](data-import.md).
+
+For the standard legacy Python layout:
 
 ```sh
 DATA_DIR="$PWD/storage-imported" \
@@ -15,7 +14,4 @@ DATABASE_PATH="$PWD/storage-imported/routeros_backup_next.db" \
   --backup-root docker-data
 ```
 
-Stop the old application first. The destination directory must be new and must not
-contain an existing database. The import preserves application records and copies
-referenced backup files. It intentionally does not copy external environment secrets,
-service-manager files, operating-system permissions, or external SSH host-trust files.
+Stop the old Python/TypeScript application first. The import destination must be new and must not contain an existing database.