phonedu 0f4c79b629 M0.9: a script runs as one undo step and resolves $step, like command.batch ...

`figcraft-cli run` ran each step of a script on its own, so a script's `{"$step": n}` reached
`parent` unresolved and the layer landed on the page while every step reported success — the same
commands through `command.batch` (the MCP `batch` tool, the control channel, plugins) put it inside
the frame. One `edit.undo` took back one step of a script rather than the script, and a failing step
left the earlier ones applied.

`Session::batch_step` is now the one path both take — one step of a batch, its `$step` references
resolved against the results before it — and `run_script` wraps its steps in `Session::grouped`: the
whole script is one undo step, and a step that fails takes the script back. The result lines come out
once the script is through, so none of them reports work a later failure took back; a failure prints
one line with `rolledBack: true` and exits 1. `docs/cli.md` documents the reference and the output.

2026-10-16 19:33:59 +08:00

..

src

M0.9: a script runs as one undo step and resolves $step, like command.batch

2026-10-16 19:33:59 +08:00

tests

fix(engine): read the documented gradient shorthand on every route (#252)

2026-10-14 01:02:45 -05:00

build.rs

Refuse incomplete SVG/PDF exports beyond the depth limit (#218)

2026-10-14 05:23:28 +07:00

Cargo.toml

M7: performance: retained canvas renders, virtual layers panel, shared text layouts, cargo xtask bench (#35)

2026-10-10 05:19:05 +07:00