mirror of
https://github.com/storytold/lightcraft.git
synced 2026-10-28 03:57:57 -06:00
Alex ChambersandClaude Opus 5.5
725eca2701
Fourth review round on6471d93b: - develop.merge: a stated correction equal to the photo's current one counts as not stated, so settings sent back whole (develop.get / MCP get_develop, rotation changed) turn the correction as Rotate does. It stayed in the old frame, 15.5 px mean off at 3200 x 4800. - The clipboard remembers the library it was copied in. After opening another library a photo with the copied photo's id is another file and keeps its own correction; it got the copied one. - The Presets panel's preview and thumbnails use Session::preset_look, the helper preset.apply and both import paths use, so the preview is what Apply stores (it was up to 15.4 px off). - "No crop" (HasCrop False, or the full frame unrotated) needs no frame: it applies on an unreadable or preview-only file without a warning and isn't listed again by Synchronize Folder. A held crop is news only while it differs from the photo's. The Crop* fields beside HasCrop False aren't reported as unimported. - Synchronize Folder's scan and read learn the file's orientation through the session's file probe, inside import's memory budget, not by reading whole files on their own. - Docs: guides and Constrain Crop move between files too; the Lightroom claim is attributed to community experts, with the conflicting Auto Sync reports and the stale same-mode correction noted. - Tests: the regressions above (failing on6471d93b), an MCP set_develop round trip, an older preset holding a correction, and same-file sweeps from copy to original and copy to copy (12,672 cases). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>