@sleds/cli 0.1.27 → 0.1.29

package/README.md

@@ -71,7 +71,8 @@ tmux       the default — any terminal; one detached session per node, `tmux at
 headless   Claude Code's -p with no terminal; the transcript goes to a file beside the prompt, nothing goes in
 command    your own launcher: --runner-cmd '<shell template>' with {prompt} {cwd} {name} {branch} {agent};
            it must block until the session ends, or the node reads as exited at once
-orca       for people who run agents in Orca: Orca makes the worktree and starts the agent in its terminal
+orca       for people who run agents in Orca: Orca makes the worktree, the engine starts the agent in an
+           Orca terminal with the same command tmux runs (--agent, --mode and --model all apply)
 ```
 
 The flags `sleds route run` and `sleds engine` share:
@@ -86,7 +87,11 @@ The flags `sleds route run` and `sleds engine` share:
 --repo <path> | --repos-dir <dir>   where the node's repo is checked out
 ```
 
-`sleds engine` also takes `--name <n>` (default the hostname; it signs as `engine:<n>`), `--interval <s>`, `--lease <min>`, `--idle <min>` (default 20: a session showing nothing new and no PR has ended) and `--once` for a single tick. `--jira` reads `JIRA_BASE_URL`, `JIRA_EMAIL` and `JIRA_TOKEN`. `sleds help` has the full list.
+`sleds engine` also takes `--name <n>` (default the hostname; it signs as `engine:<n>`), `--interval <s>`, `--lease <min>`, `--idle <min>` (default 20: a session showing nothing new and no PR is parked for a person, its last message the question, and the answer is typed back into it) and `--once` for a single tick. `--jira` reads `JIRA_BASE_URL`, `JIRA_EMAIL` and `JIRA_TOKEN`. `sleds help` has the full list.
+
+`sleds engine status [--name <n>] [--json]` says what that engine holds now: the nodes it runs (with where to watch each), the PRs it follows and their checks, the next check, and whether it is alive. It reads the engine's state file and the lock the engine keeps beside it (`<name>.lock`: its pid, written each tick, removed on a clean stop), not SLEDS, so it answers offline. `--json` is the contract a front end reads; both it and the state file carry a version, `v` (spec 28 §4.2). For a `sleds route run` engine, pass `--name <n>-<KEY>`.
+
+`sleds engine log [--name <n>] [--org <slug>] [--lines N] [--json]` prints the last N lines (default 200) of the log an installed engine's launchd agent writes (`<name>.log` beside its state file, in its org's directory). `--json` is `{v, engine, path, exists, lines}` — what the menu bar polls, so it never reads the path itself; an engine never installed is `exists: false`, not an error.
 
 ## Docs