v0.27.3

docs/MIGRATION.md

@@ -46,7 +46,7 @@ The administration server keeps the same strict Host/Origin/request-marker/CSRF
 
 There is no SQLite schema or saved-configuration migration. 0.25.1 reorganizes the Traffic dashboard and source tree only; existing Web Services, vhosts, traffic settings, cache state and administrator data remain compatible. Browser asset URLs remain `/assets/app.js` and `/assets/vhosts.js` even though their source is now split into bounded modules.
 
-When updating a source checkout by extracting the archive over an older tree, remove the obsolete source monoliths `src/admin/web/app.js` and `src/admin/web/vhosts.js` if they remain. Checkouts older than the Web Server module split may also retain obsolete `src/web_server.rs`; remove it as well. Do **not** remove `src/config.rs`, `src/docker.rs`, `src/runtime.rs`, `src/balance.rs`, `scripts/deploy.py`, `scripts/migrate_npm.py` or `docker-agent/main.go`: these are intentional module/CLI entry points in 0.25.1. Build/cache artifacts such as `target/` and `__pycache__/` may be deleted safely, but `.env`, `data/`, databases and local certificates are runtime/operator state and must not be deleted as part of a source refresh.
+When updating a source checkout by extracting the archive over an older tree, remove the obsolete source monoliths `src/admin/web/app.js` and `src/admin/web/vhosts.js` if they remain. Checkouts older than the Web Server module split may also retain obsolete `src/web_server.rs`; remove it as well. Do **not** remove `src/config.rs`, `src/docker.rs`, `src/runtime.rs`, `src/balance.rs`, `scripts/deploy/deploy.py`, `scripts/migration/migrate_npm.py` or `docker-agent/main.go`: these are intentional module/CLI entry points in 0.25.1. Build/cache artifacts such as `target/` and `__pycache__/` may be deleted safely, but `.env`, `data/`, databases and local certificates are runtime/operator state and must not be deleted as part of a source refresh.
 
 ## 0.24.10 -> 0.25.0
 
@@ -80,7 +80,7 @@ There is no schema or configuration-format migration. This patch changes only ad
 There is no new SQLite schema version in 0.15.0. Renewal observations remain in the existing
 schema-v3 `certificate_renewals` table. The application no longer contains a runtime JSON importer.
 
-When `upgrade.sh` / `scripts/upgrade.py` is used while RustProxy is stopped, an obsolete
+When `upgrade.sh` / `scripts/deploy/upgrade.py` is used while RustProxy is stopped, an obsolete
 `<data-dir>/certs/renewals.json` observation sidecar is validated as a regular file and removed as
 the final source-upgrade step. It is not imported and no second legacy copy is retained. If the
 source-upgrade transaction fails before that final removal, the old sidecar remains untouched.
@@ -189,7 +189,7 @@ removed in 0.7.2 (see the build notes above). Source-tree updates still back up
 replace that managed directory; retain any unrelated local Cargo settings from
 your private backup. Read [API_ACCESS.md](API_ACCESS.md) for current build inputs.
 
-Run `python3 scripts/admin_audit.py --url http://127.0.0.1:9090` after deployment.
+Run `python3 tools/audit/admin_audit.py --url http://127.0.0.1:9090` after deployment.
 It prints only status checks, no response bodies or credentials.
 
 ---
@@ -302,7 +302,7 @@ unzip RustProxy-0.4.0.zip -d /home/mg/rustproxy-040-staging
 cd /home/mg/rustproxy-040-staging/RustProxy
 ```
 
-`scripts/backup.py` is a legacy release-test helper and is not a complete Secret
+`tools/legacy/backup.py` is a legacy release-test helper and is not a complete Secret
 Store backup. For current backup/restore behavior see `SECRET_STORE_BACKUP.md`.
 
 A missing database means there is no database to back up. Do not initialize an empty
@@ -354,7 +354,7 @@ and CLI-only `rust-proxy backup restore`; it includes the encrypted Secret Store
 key material required to recover it, certificates and other durable application
 state while excluding cache, logs and runtime files.
 
-The historical `./dev.sh backup` / `scripts/backup.py` snapshot helper described by
+The historical `./dev.sh backup` / `tools/legacy/backup.py` snapshot helper described by
 older release notes is not sufficient after Secret Store migration and is retained
 only for offline compatibility/release tests.
 
@@ -378,7 +378,7 @@ Managed paths now include build.rs, langs, deploy and make_zip.py. Extra *.json
 language packs from the installed langs directory are copied into the new tree
 when the new distribution does not contain the same filename. Shipped packs are
 updated, with old bytes preserved in the source backup. Invalid custom packs can
-correctly block a build; review them with scripts/langs_check.py. No symlinked
+correctly block a build; review them with tools/checks/langs_check.py. No symlinked
 language pack is followed. The updater never copies a database from the package.
 
 The old lockfile is preserved in the managed source backup and a new dependency