amadan
docs: carlos run names what carlos logs keeps of a run (#325)
Human
Prompt
re-up copy review?
From this commit's own message. The prompt ledger has no entries for it — which is what a squashed, rebased or amended commit looks like, and what every commit looks like in a repo without a ledger.
Summary
Adds the approved docs.run.logs sentence to the carlos run section. All 16 strings approved unchanged in copy review.
1 file changed,
+2
−0
docs/site/cli.md+2 −0
CI cancelled — superseded by a newer push — run details
CI log
=== gate === cd launchctx && go vet ./... && go test ./... -count=1 ok amadan.net/carlos/platform.git/launchctx 0.011s ? amadan.net/carlos/platform.git/launchctx/controlname [no test files] ? amadan.net/carlos/platform.git/launchctx/wireid [no test files] go vet ./... gofmt -l .: clean go test ./... -count=1 -timeout 30m amadan: job cancelled — a newer push superseded it
diff --git a/docs/site/cli.md b/docs/site/cli.md| index 22601a4d6..ebb4d60fc 100644 |
| --- a/docs/site/cli.md |
| +++ b/docs/site/cli.md |
| @@ -559,6 +559,8 @@ A hibernating instance is woken first. A live one keeps serving, and the command |
| carlos run exits with the command's own status, 128 plus the signal number when a signal ended it, 124 when it timed out, 125 when it was interrupted or the instance let go of it without a result, 130 when you cancelled it, 3 when the box refused it or did not pick it up within 60 seconds, and 2 when the console refused it. |
| +carlos logs shows when each run started, who asked for it and how it ended. The command's output is not kept there. |
| + |
| Arguments are kept in the account's audit log, with who ran them. Never put a secret in an argument. Pass it in a --file, or keep it in the instance's environment. |
| ### carlos schedule |