@lotics/cli 0.311.5 → 0.311.7

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.
Files changed (8) hide show
  1. package/AGENTS.md +1 -1
  2. package/dist/src/cli.js +37 -10
  3. package/docs/agent_surface.md +1 -1
  4. package/docs/app_bindings.md +2 -2
  5. package/docs/cli_reference.md +1 -1
  6. package/docs/design.md +7 -7
  7. package/docs/workflows.md +2 -2
  8. package/package.json +1 -1
package/AGENTS.md CHANGED
@@ -101,7 +101,7 @@ something exists, read `lotics --help` § COMMANDS — the whole section, not a
101
101
  so try a write on a throwaway record.
102
102
  - **Exit codes are assertable, and they report the WORK rather than the call.** `lotics run` exits
103
103
  non-zero when a `run_app_workflow` or `run_app_agent` result's own envelope carries a failed
104
- `status` (`error`/`failed`/`cancelled`) — any other tool's top-level status is data and exits 0 —
104
+ `status` (`error`/`failed`/`cancelled`, or `not_previewed`: a preview asked for and not given) — any other tool's top-level status is data and exits 0 —
105
105
  so `lotics run … && next-step` cannot walk past a refused run; `workspace doctor` exits non-zero on
106
106
  findings. An unrecognized status exits 0 — the list is an allowlist of failure, so a status added
107
107
  later never turns a working script red — and a parked run (`awaiting_input`) is not a failure.