@sealant/mend 0.24.2 → 0.25.0

package/README.md

@@ -41,18 +41,17 @@ pin rather than automatically downgrading or restoring the database.
 For local release assets and preloaded images:
 
 ```sh
-mend server setup --version 0.23.0 --assets-dir ./release-0.23.0 --offline --registry-port 5501
+mend server setup --version 0.23.0 --assets-dir ./release-0.23.0 --offline
 mend server upgrade --version 0.24.0 --assets-dir ./release-0.24.0 --offline
 ```
 
-Each asset directory must contain `compose.v1.yaml` and `postgres-init.sh`. Mend copies them into an
+Each asset directory must contain `compose.v2.yaml` and `postgres-init.sh`. Mend copies them into an
 immutable private generation; the source directory is not needed afterward. Preload official
 `postgres:17-alpine` and canonical `ghcr.io/sealant-sh/mend:VERSION`. Image labels and health must
 report that exact version. `--offline` forbids GitHub requests and release-image pulls.
-Start/restart always reuse local release images and retained assets. Startup still verifies the
-loopback registry by importing, pushing, removing and pulling its own tiny probe image. The registry
-defaults to port 5000; choose a free `--registry-port` when another registry, such as Sealant's,
-already uses it.
+Start/restart always reuse local release images and retained assets. The bundle publishes only the
+web port (`--port`, default `3105`) and the SSH gateway port (`--ssh-port`, default `2222`); the two
+must differ.
 
 Stop/restart/upgrade interrupt connections. Workspace containers and data remain, but active work
 may lose connectivity and need reconnection. No volumes are deleted. Status/logs never start an