@mutmutco/installer-launcher 1.0.1 → 1.2.0

package/README.md

@@ -15,13 +15,26 @@ registration, PKCE + browser, code exchange), adapted to the launcher's token st
 ```
 launcher login [--config <path>] [--dir <path>]    sign in (the ONLY command that opens a browser)
 launcher logout                                     wipe tokens AND payload
-launcher install                                    login if no token -> fetch+verify+unpack -> print next step
-launcher update                                     same fetch, re-checks manifest; no-op when current
-launcher doctor                                     config, token presence/expiry, payload version, paths
+launcher install                                    refresh the launcher, login if no token -> fetch+verify+unpack -> last mile
+launcher update [--dry-run]                         refresh the launcher, then the payload; no-op when current
+launcher status [--json]                            read-only: launcher, payload vs the release, sign-in, auto-update
+launcher doctor                                     launcher report (no network), then the payload's doctor
+launcher autoupdate on|off|status                   hourly per-user schedule (hidden via wscript on Windows)
+launcher <verb> [args…]                             forwarded untouched when payload.json declares it
 launcher --run <file> [args…]                       run a payload ESM file with the launcher's own runtime
-launcher --version
+launcher --version                                  `<bin> <payload version> (launcher <version>)`
 ```
 
+Every screen that is not an install/update run is drawn by `@mutmutco/installer-face` (#7072):
+usage, notices, the status/doctor report, and refusals (stderr). Launcher flags (`--config`,
+`--dir`, `--json`, `--no-color`, `--dry-run`, `--help`, `--version`) are read before the command
+and around the launcher's own verbs only. Only mutating verbs take the installation lock.
+
+`@mutmutco/installer-launcher/refresh` exports `refreshLauncher` and `readLauncherRecord` (#7070):
+the signed `GET <host>/release/launcher` record (manifest shape and signing) keeps the one-line
+installer's launcher current from every update path. A SEA run records its own path in
+`<productDir>/launcher.json` so the refresh finds it.
+
 `--run <file> [args…]` runs a payload file with the launcher's OWN embedded runtime — no Node on
 the machine. `<file>` resolves against the cwd and is loaded with `import()`; the file sees
 `process.argv = [execPath, <abs file>, ...args]` and its `process.exitCode` is propagated. A