@aopslabs/aops 0.3.1 → 0.3.3

package/README.md

@@ -1,8 +1,8 @@
 # @aopslabs/aops
 
-AOPS CLI and terminal setup application. It can connect to a remote AOPS Server
-without installing a local Server, or manage a separately installed local
-Server.
+AOPS CLI and terminal setup application. The package brings the exact compatible
+local Server runtime, but remote-only users can use the CLI without configuring
+or starting that local Server.
 
 ```sh
 npm install --global @aopslabs/aops
@@ -16,11 +16,9 @@ aops cockpit
 aops assets
 ```
 
-For a local installation, install the Server package separately:
-
-```sh
-npm install --global @aopslabs/aops @aopslabs/aops-server
-```
+That one command also installs the exact compatible `@aopslabs/aops-server`
+runtime. npm installation itself never starts services or runs migrations;
+`aops setup init` is the explicit first-time setup boundary.
 
 The source repositories remain private. Customer-required runtime dependencies
 may also be published as public npm packages so ordinary installation never
@@ -166,10 +164,11 @@ Eligible DDL runs transactionally under a non-waiting migration lock and the
 live semantic schema is read back before success. Optional audit-write failure
 does not invalidate that result.
 
-The CLI package does not force-install `@aopslabs/aops-server`. Remote users need
-only the CLI; local users install the matching Server package separately. No
-customer path requires Git or a source checkout. Advanced developers can still
-run an explicit checkout with `--source-root`.
+The CLI package depends exactly on the compatible `@aopslabs/aops-server`
+release, so local installation remains a single npm command. Remote users may
+leave that local runtime unconfigured and connect only to their selected remote
+target. No customer path requires Git or a source checkout. Advanced developers
+can still run an explicit checkout with `--source-root`.
 A stopped installation can move between valid checkout/npm roots through the
 same setup command without reset or duplicate rollback copies; same-root npm
 byte drift still requires reinstalling the package.
@@ -197,7 +196,9 @@ Opening the TUI does not by itself start or stop either service. Use the TUI's
 explicit actions or the CLI command families. The convenience
 `aops cockpit` command may start safely stopped services before opening the
 browser; the explicit server and Cockpit lifecycle commands never stop or
-start the other service.
+start the other service. For setup path 2, an ordinary `aops server stop`
+leaves the managed PostgreSQL container running; only the explicit destructive
+installation reset removes its verified container and volume.
 
 The npm package includes `launchers/aops-server.sh` and
 `launchers/aops-server.ps1` for running the installed server in the current