v0.27.3

docs/API_ACCESS.md

@@ -1,4 +1,4 @@
-# Administration API access - 0.27.2
+# Administration API access - 0.27.3
 
 ## Sign-in boundary
 
@@ -132,7 +132,7 @@ promise to erase browser/OS screenshots or data intentionally downloaded by an a
 ## First build / offline assets (fixed in 0.7.2)
 
 No `SWAGGER_UI_DOWNLOAD_URL` environment variable or `.cargo/config.toml` is required.
-The default is Swagger UI **5.32.11**, selected by `scripts/swagger_assets.py` and
+The default is Swagger UI **5.32.11**, selected by `scripts/build/swagger_assets.py` and
 called from this application's `build.rs`. The former `utoipa-swagger-ui` adapter
 is removed: there is no separate dependency build silently choosing its older
 historical browser default. Direct Cargo builds using `--manifest-path` use the
@@ -204,7 +204,7 @@ build server. Browser tests still label their simulated API/Swagger renderer.
 After running the built server:
 
 ```bash
-python3 scripts/admin_audit.py --url http://127.0.0.1:9090
+python3 tools/audit/admin_audit.py --url http://127.0.0.1:9090
 ```
 
 The script sends anonymous read-only loopback probes, follows no redirects, ignores