@autonoma-ai/planner 0.1.19 → 0.1.21
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +24 -1
- package/dist/index.js +1149 -670
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -15,19 +15,42 @@ npx @autonoma-ai/planner@latest
|
|
|
15
15
|
Commands:
|
|
16
16
|
|
|
17
17
|
```bash
|
|
18
|
-
autonoma-planner [run] [--project <path>] [--
|
|
18
|
+
autonoma-planner [run] [--project <path>] [--frontend <path>] [--backends <path,path>] \
|
|
19
|
+
[--model <id>] [--step <name>] [--resume] [--non-interactive]
|
|
19
20
|
autonoma-planner status [--project <path>]
|
|
21
|
+
autonoma-planner upload [--project <path>]
|
|
20
22
|
```
|
|
21
23
|
|
|
22
24
|
`run` is the default and may be omitted. A run can take an hour or more; progress is saved, so you
|
|
23
25
|
can stop and `--resume` later.
|
|
24
26
|
|
|
27
|
+
`upload` re-uploads everything already generated in `~/.autonoma/<app>/` - the recipe and the
|
|
28
|
+
artifacts (test cases, `AUTONOMA.md`, `scenarios.md`, `entity-audit.md`) - without re-running the
|
|
29
|
+
whole planner. Useful when an upload failed. Both the recipe and artifact endpoints are idempotent,
|
|
30
|
+
so it is safe to run repeatedly. It needs the same `AUTONOMA_API_URL`, `AUTONOMA_API_TOKEN`, and
|
|
31
|
+
`AUTONOMA_GENERATION_ID` env vars as a run. Note that if a recipe submit fails during a run, the full
|
|
32
|
+
recipe JSON is also printed to stdout so it can be recovered even from an ephemeral container.
|
|
33
|
+
|
|
34
|
+
### Monorepos
|
|
35
|
+
|
|
36
|
+
The run starts by mapping your repository - discovering which folder(s) are frontends, which are
|
|
37
|
+
backends/data layers, and which are unrelated - so every later step scans only the relevant code
|
|
38
|
+
instead of the whole tree. In an interactive run you pick the frontend to test (and its backends)
|
|
39
|
+
from a menu. To scope non-interactively, pass:
|
|
40
|
+
|
|
41
|
+
- `--frontend <path>` - the one frontend directory to plan tests for.
|
|
42
|
+
- `--backends <path,path>` - comma-separated backend/data-layer directories it depends on. Omit to
|
|
43
|
+
default to the dependencies the mapper inferred for that frontend.
|
|
44
|
+
|
|
45
|
+
For a single-app repo the mapper resolves the scope on its own and no flags are needed.
|
|
46
|
+
|
|
25
47
|
## Output
|
|
26
48
|
|
|
27
49
|
Artifacts are written to `~/.autonoma/<project-slug>/`:
|
|
28
50
|
|
|
29
51
|
```
|
|
30
52
|
~/.autonoma/<app>/
|
|
53
|
+
├── project-map.json # discovered frontends/backends + the scope chosen for this run
|
|
31
54
|
├── AUTONOMA.md # knowledge base
|
|
32
55
|
├── scenarios.md # test-data scenario descriptions
|
|
33
56
|
├── entity-audit.md # database model audit
|