3 people f4b73f42ed Automation: reject an invalid document index instead of using the active document (#4160) (#4161) ...

Root cause: the JSON-lines server's `index_of` read `index` with `as_u64`, so a
string, negative, fractional or boolean index became None, which means "the
active document". `doc.close {"index":"0"}` therefore closed the active
(possibly unsaved) document instead of failing. The MCP server types the param
as Option<usize> and already rejects these values.

Fix: `index_of` returns Result<Option<usize>, AutomationError>. A missing or
null index still means the active document; a non-negative integer is used;
anything else is a bad request ("`index` must be a non-negative integer").
All doc.* call sites propagate the error with `?`.

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-12 20:37:40 -04:00

..

src

Automation: reject an invalid document index instead of using the active document (#4160) (#4161)

2026-10-12 20:37:40 -04:00

tests

Load and save Photoshop Actions (.atn) (#4356, #219) (#4434)

2026-10-12 18:39:57 -04:00

Cargo.toml

security: constrain automation filesystem access (#72)

2026-10-04 16:35:06 -04:00