mirror of
https://github.com/storytold/photocraft.git
synced 2026-10-23 18:45:56 +02:00
BFlatandClaude Opus 5.5
1df68e9a5d
* CLI --quality refuses every value outside 1-100 (#491) --quality was parsed as a u8 and clamped, so 0 and 101-255 were silently accepted while 256 and above were rejected. Every value outside 1-100 is now a bad --quality error, checked before any file is read or written. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * CLI batch: --format with a leading dot names outputs <stem>.<ext> (#490) batch built output names from the raw --format value, so --format .jpg wrote a..jpg. One leading dot is now dropped, as the save path and file.automate.batch already do. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * CLI batch --actions takes recorded-action and droplet steps (#489) batch read only {"command", "params"} objects, so the [id, params] pairs a recorded action or droplet stores failed with 'missing "command"'. It now uses the engine's action parser (automate_cmds::parse_action, split out of parse_script), which takes [id, params], objects and bare ids, bare or wrapped in {"steps": ...} or a droplet; {"actions": ...} still works. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * CLI batch refuses an --out folder that is the --in folder (#492) Results are saved as <out>/<stem>.<ext>, so --out naming the input folder silently replaced the originals. batch now compares the canonical folders (relative spellings, trailing separators, symbolic links) and fails before writing anything, naming the folder; the new --in-place flag opts in. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>