srvgov-cli 0.2.0 → 0.4.0

package/README.md

@@ -26,6 +26,9 @@ srvgov ctx use dev -o json
 srvgov status -o json
 srvgov ports -o json
 srvgov logs --unit sshd --since "1 hour ago" --lines 50 -o json
+srvgov svc status sshd -o json
+srvgov file stat /etc/hosts -o json
+srvgov docker list -o json
 srvgov exec --dry-run "uptime" -o json
 srvgov exec "uptime" -o json
 srvgov audit query --limit 20 -o json
@@ -93,6 +96,83 @@ operators. `ports` falls back from `ss` to `netstat`. Unit logs fall back from
 adds `sudo`; unavailable PID/process fields remain empty. Log text, process
 names, generated command text, caller output, and audit records are redacted.
 
+## Service Control
+
+`svc` exposes only a fixed service-operation whitelist. Unit names are treated
+as literal shell words, and every generated `systemctl` command goes through
+the same classifier and authorization path as `exec`.
+
+```bash
+# R0 read, still audited
+srvgov svc status nginx -o json
+
+# R2 change: human-supplied reason, ticket, and confirmation
+srvgov svc restart nginx \
+  --reason "apply reviewed configuration" --ticket OPS-123 --yes -o json
+```
+
+Available actions are `status`, `start`, `stop`, `restart`, `reload`, `enable`,
+and `disable`, for one unit at a time. Protected contexts raise service changes
+from R2 to R3 and additionally require human-supplied `--allow-destructive`.
+`svc` does not expose power, isolate, mask, or arbitrary systemctl operations.
+
+## File Operations
+
+File reads are structured R0 operations and remain audited:
+
+```bash
+srvgov file read /etc/hosts --max-bytes 1048576 -o json
+srvgov file stat /etc/hosts -o json
+srvgov file list /var/log -o json
+```
+
+Writes use `tee -- '<path>'` with content streamed over SSH stdin. They are R2
+for ordinary paths and R3 for sensitive paths such as SSH authorization files,
+shell dotfiles, and crontabs.
+
+```bash
+printf '%s\n' 'enabled=true' | srvgov file write /tmp/app.conf \
+  --reason "update reviewed configuration" --ticket OPS-123 --yes -o json
+
+srvgov file write /tmp/app.conf --content "enabled=true" \
+  --reason "update reviewed configuration" --ticket OPS-123 --yes -o json
+```
+
+Without `--content`, stdin is the file content and explicit `--yes` is required
+before authorization. With `--content`, stdin is never read and interactive
+confirmation remains available. Write output and audit records never contain
+file content; audit stores only the redacted path, byte count, and SHA-256.
+Writes are direct and non-atomic; temporary-file plus rename is not implemented
+in this release. `file` never uses SFTP and never adds `sudo`.
+
+## Docker Governance
+
+Docker reads provide stable, redacted structures:
+
+```bash
+srvgov docker list -o json
+srvgov docker inspect api -o json
+srvgov docker logs api --tail 100 -o json
+```
+
+`docker list`, `inspect`, and `logs` are audited R0 operations. Inspect uses a
+remote fixed-field projection and excludes container environment variables and
+the full inspect document. Logs default to 100 lines and accept `--tail`
+between 1 and 10000.
+
+Lifecycle changes are R2 and require human authorization:
+
+```bash
+srvgov docker restart api \
+  --reason "restart after reviewed deployment" --ticket OPS-123 --yes -o json
+```
+
+The fixed whitelist contains only `ps`/`list`, `inspect`, `logs`, `start`,
+`stop`, `restart`, and `rm`, one container at a time. It never exposes Docker
+run, create, exec, build, copy, compose, or prune. Protected contexts raise
+lifecycle changes to R3 and require human-supplied `--allow-destructive`.
+Container identifiers are shell-quoted.
+
 ## Governed Execution
 
 Preview without connecting or executing:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "srvgov-cli",
-  "version": "0.2.0",
+  "version": "0.4.0",
   "description": "Governed remote server command execution CLI for AI agents",
   "bin": {
     "srvgov": "bin/srvgov-cli.js",