@lenso/cli 0.1.24 → 0.1.26

package/README.md

@@ -16,27 +16,30 @@ cargo install lenso-cli
 lenso host init my-app
 cd my-app
 cp .env.example .env
+lenso console update
 lenso serve
 ```
 
 The package name defaults to the target directory name and can be overridden with
 `--name`. Pass `--force` to scaffold into a non-empty directory.
-Release builds of `lenso-cli` also copy the bundled Runtime Console into the
-new project, so the API serves it at `/console` without requiring Node.js or
-pnpm in the host application.
-
-Update the hosted console later by upgrading `lenso-cli` and running:
+Install or update the hosted Runtime Console with:
 
 ```sh
-lenso host update-console
+lenso console update
 ```
 
+The command downloads the latest `lenso-runtime-console` release artifact and
+installs it under `.lenso/console`, so the host API can serve `/console`
+without requiring Node.js or pnpm in the host application. For local builds,
+pass `--artifact <dir-or-tar.gz>`. For a pinned release, pass
+`--console-version vX.Y.Z`.
+
 After creating a password user, grant the first Runtime Console admin:
 
 ```sh
-lenso host bootstrap-admin --identifier admin@example.com
+lenso console bootstrap-admin --identifier admin@example.com
 # or
-lenso host bootstrap-admin --user-id usr_...
+lenso console bootstrap-admin --user-id usr_...
 ```
 
 `console.admin` is always added. Pass extra `--scope <name>` flags when the
@@ -76,7 +79,7 @@ lenso module create billing --remote --output-dir ../module-packages
 The Runtime Console package generator is available directly as:
 
 ```sh
-lenso console-package create billing
+lenso console package create billing
 ```
 
 ## Install a module

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lenso/cli",
-  "version": "0.1.24",
+  "version": "0.1.26",
   "description": "Lenso command-line interface for scaffolding and operating Lenso backend projects.",
   "license": "MIT",
   "homepage": "https://github.com/LioRael/lenso-cli",