@blotout/qinto-cli 0.1.22 → 0.1.23

package/README.md

@@ -124,7 +124,7 @@ The whole loop is a handful of commands:
 qinto app create my-app                       # scaffold, install, and offer to register
 qinto app dev                                 # run it against a local Qinto
 qinto app publish                             # build, upload, and publish a version
-qinto app publish --site example.com          # …and install it on a site
+qinto app install my-app --site example.com   # install the latest version on a site
 qinto app status my-app --site example.com    # desired vs deployed state
 ```
 
@@ -501,25 +501,19 @@ What a publish does, in order:
    exactly what was built. Redeclaring replaces the previous declaration, so a failed upload is fixed by publishing again.
 5. **Finalize** the version. `artifacts_stale` means the manifest changed after the build; the CLI rebuilds and redeclares once
    by itself.
-6. **Install**, when `--site` is given.
+Publishing installs nothing. Install the new version with `qinto app install` (below); the last line of the output
+prints that command with the version filled in.
 
 | Flag | What it does |
 | --- | --- |
 | `--bump <level>` | `patch` (default), `minor`, or `major`, from the highest ready version. |
 | `--version <version>` | Allocate this exact `x.y.z` instead of bumping. |
 | `--org <organization>` | Owning organization id or name, when the slug exists in several. |
-| `--site <site>` | Install the finalized version on this site (hostname or domain id). |
-| `--team <teamId>` | Authorized team to resolve `--site` in. |
-| `--accept-capabilities` | Accept the extra capabilities a newer version asks for. |
-| `--acknowledge-necessary` | Record that this app runs without visitor consent. |
-| `--dry-run` | Build and validate locally; allocate nothing and upload nothing. |
+| `--dry-run` | Build and validate locally; allocate nothing and upload nothing. The UI panel's build output (`ui.dir`) is restored to what it was before the run. |
 | `--restart` | Discard `.qinto/publish.json` and start a fresh publish. |
 | `--yes` | Confirm that publishing an app edited in the Qinto platform switches it to the CLI. |
 | `--no-input` | Disable all interactive prompts. |
-| `--json` | Print the published version, and the install when `--site` was given, as JSON. |
-
-Installing a version the visitor's consent or the capability set does not already cover fails until you accept it. Interactively
-the CLI asks; in machine mode it exits `2` and names the flag to pass.
+| `--json` | Print the published version as JSON. |
 
 **Editor apps.** An app created for the Qinto platform editor is refused until you confirm that publishing it with the CLI switches
 it to the CLI permanently. The switch happens when the version is finalized: the editor and its files are then gone, and editor
@@ -527,6 +521,32 @@ changes that were not published are lost. A failed or cancelled publish leaves t
 a publish from the editor is running: rerun `qinto app publish` when it has finished. Interactively the CLI asks; in machine mode
 it exits `2` unless you pass `--yes`.
 
+### Install — `qinto app install <slug> --site <site>`
+
+`install` puts a published version on one of your team's sites. Without `--version` it takes the latest ready version. When the
+app is already on the site, it moves the app to that version, or does nothing if the site already runs it. The site deploys in
+the background; `qinto app status` shows when the deployment has converged.
+
+```sh
+qinto app install my-app --site example.com                  # the latest version
+qinto app install my-app --site example.com --version 1.4.1  # a specific version
+```
+
+| Flag | What it does |
+| --- | --- |
+| `--site <site>` | Site to install on (hostname or domain id). Required. |
+| `--team <teamId>` | Authorized team to resolve `--site` in. |
+| `--version <version>` | Install this published `x.y.z` instead of the latest. |
+| `--accept-capabilities` | Accept the extra capabilities a newer version asks for. |
+| `--acknowledge-necessary` | Record that this app runs without visitor consent. |
+| `--no-input` | Disable all interactive prompts. |
+| `--json` | Print the install outcome as JSON. |
+
+Installing a version the visitor's consent or the capability set does not already cover fails until you accept it. Interactively
+the CLI asks; in machine mode it exits `2` and names the flag to pass. An acceptance applies to one version, so the CLI asks only
+when `--version` names it. Without `--version`, it exits `2` and asks you to rerun with it: a retry against "latest" could
+install a version published after the one you accepted.
+
 ### Inspect — `status`, `versions`, `version cancel`
 
 ```sh