lenso-cli 0.4.0

Authoring CLI and library for Lenso App Plans and Modules.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

# Migrating to the intent-level CLI

Cargo `lenso-cli` 0.4 and npm `@lenso/cli` 0.12 intentionally reduce the
public command surface. Ordinary Module authors now work with four top-level
commands; App Definition editing remains under `lenso app`.

## Command replacements

| Before | Now |
| --- | --- |
| `lenso module create NAME` | `lenso new NAME` |
| `lenso module dev` | `lenso dev` |
| `lenso module check` | `lenso check` |
| `lenso module verify` | `lenso verify` |
| `lenso add ...` | `lenso app add ...` |
| `lenso resolve ...` | `lenso app resolve ...` |

Top-level `run` and the `compose` command group have no direct replacement.
They exposed internal recipe, Plan, and Runner stages as an ordinary authoring
workflow. Product-owned Hosts now run reviewed immutable Plans; App owners use
the source-derived App Definition commands only when they need to inspect or
materialize those Plan bytes.

## Module workflow

```sh
lenso new greeting
cd greeting
lenso check
lenso dev
lenso verify
```

`check` is the fast diagnostic command. `verify` adds behavior, lifecycle, and
removal evidence. Existing project files remain valid inputs to these commands;
the migration changes the command interface rather than the Plan format.

## App Definition workflow

```sh
lenso app add example-greeting-module --definition lenso.app.json
lenso app check --definition lenso.app.json
lenso app resolve --definition lenso.app.json \
  --output .lenso/resolved-plan.json
lenso app remove greeting --definition lenso.app.json
```

Do not copy generated Module Descriptors, endpoint tables, or unambiguous
bindings into the App Definition. Keep only package selections, stable Instance
keys, configuration or secret references, optional lanes, and real ambiguity
decisions.