@blotout/qinto-cli 0.1.29 → 0.1.31

package/README.md

@@ -505,14 +505,15 @@ Publishing installs nothing. Install the new version with `qinto app install` (b
 prints that command with the version filled in.
 
 **Source snapshot.** Every publish also uploads the app's source with the version: the text files in the app directory, without
-what a `.gitignore` names (in the app directory, a folder below it, or the enclosing git repository), dot-prefixed folders and files (`.git`, `.qinto`, `.env`), `node_modules`, binary files, and symbolic links. The
+what a `.gitignore` names (in the app directory, a folder below it, or the enclosing git repository), dot-prefixed folders and files (`.git`, `.qinto`, `.env`, `.wrangler`), `node_modules`, `coverage`, `test-results`,
+`playwright-report`, `*.tsbuildinfo`, `*.log`, `npm-debug.log*`, `wrangler.jsonc`, binary files, and symbolic links. The
 owners and developers of the app's organization can read it in the Qinto platform. When you submit the version to the app store,
 the Blotout reviewers can read it too. A source above 10 MiB is refused, and the error names the largest files so that you can
 add them to `.gitignore`.
 
 The snapshot is the record of the source a version was built from. A version without a source snapshot cannot be submitted to
-the app store. A version that an older CLI published has none: [update the CLI](#stay-up-to-date), publish again, and submit
-the new version.
+the app store. The Qinto platform refuses a publish from an older CLI that uploads no source. A version that an older CLI published
+has none: [update the CLI](#stay-up-to-date), publish again, and submit the new version.
 
 | Flag | What it does |
 | --- | --- |
@@ -548,7 +549,8 @@ qinto app install my-app --site example.com --version 1.4.1  # a specific versio
 | `--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. |
+| `--acknowledge-necessary` | Record that this app, and each app it needs that the install adds, runs without visitor consent. |
+| `--yes` | Install the apps it needs that the site lacks, and approve their private-function calls, without asking. |
 | `--no-input` | Disable all interactive prompts. |
 | `--json` | Print the install outcome as JSON. |
 
@@ -557,6 +559,12 @@ the CLI asks; in machine mode it exits `2` and names the flag to pass. An accept
 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.
 
+When the app needs apps the site does not have yet, the CLI prints each one (name, reason, the app that needs it, and whether
+the site has it) and the private functions the apps call, then asks before it installs them with the app and approves those calls. `--yes` installs
+them without asking; in machine mode without `--yes` it exits `2` and installs nothing. With `--json`, the plan is the `plan`
+field of the JSON error instead of text. An app it adds that runs without visitor
+consent also needs `--acknowledge-necessary` with `--yes`; interactively, confirming the question records it.
+
 ### Inspect — `status`, `versions`, `version cancel`
 
 ```sh