* cli: report failures after keep-going scripts
Keep executing requested steps while retaining the first failure in Report, so failed scripts return nonzero before save/export.
* docs: describe first script failure in Report
Describe the first failing step without assuming all callers stop immediately.
* test: cover keep-going failure reporting and output guards
Exercise failures before and after a successful step, preserve the first failure, and require both output paths to remain absent.
Found while testing crates/engine/src/script.rs:50-54 (parse, compact `command {json}` branch)
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Found while testing crates/engine/src/script.rs:30-47 (parse: `t.lines().enumerate()` runs over the trimmed text)
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Extend the existing MCP tools instead of adding a second set (#259):
- every tool states destructiveHint and idempotentHint next to
readOnlyHint/openWorldHint; input schemas are closed
- the #776 unknown-key check walks the schema, so a misspelt key in a
batch step, a pointer event or mods is -32602 with its path instead
of being ignored
- script::parse refuses JSON step keys other than command/params
- a panic outside a command (rendering, inspection, the app connection)
is a tool error and the server keeps running
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>