skillscript-runtime v0.22.1
Upgrade impact: none (additive)
- Allowlist denial messages now tell agents to escalate, not self-edit. When a skill hits an off-allowlist shell binary or filesystem path, the runtime's remediation (
ShellBinaryNotAllowedError,FilePathNotAllowedError) and theshell-binary-not-allowedlint rule previously read as an operator runbook — "add it toSKILLSCRIPT_SHELL_ALLOWLISTin your.env, then restart." Returned to a connecting agent through the MCP error, that reads as an instruction: the agent edits.envto self-grant the capability, defeating the operator boundary. The messages now lead with an agent-facing "stop — this is a human-operator boundary; ask the operator, don't edit config yourself," with the wiring how-to clearly labeled operator-only (and a pointer toblocked_shell_attemptsas the operator's review surface). Allowlist enforcement itself is unchanged. - CLI reference accuracy. The README + landing-page CLI table dropped three commands removed back in v0.2.1 (
register-trigger/unregister-trigger/list-triggers) and a deadrunalias, addedinit/list/approve/reapprove, and now mirrors the CLI's own command order. - Quickstart restructured around the human/agent division of labor — the human installs, configures, and wires the MCP; the human and agent author the first skill together — and the dashboard step is corrected (it's a blocking foreground server, so the browser is opened separately).
.env.exampletrimmed to what each setting does (the security rationale moved to the adopter playbook), and its example port corrected to7878.