Owner review 2, R7 asks for renaming and moving after import, on the web panel and the
desktop. This is the engine and the server API both UIs build on.
- FrameNaming (Core/Naming) is the one naming context and unique-name rule of a frame:
imports, uploads and Reorganize now produce identical names (behaviour of the ingest and
the import planner unchanged).
- RenamePlanner takes a file template: each step counts its renamed frames, shows the first
three and the frames version they were planned at, and lists what keeps its name (photos
in place outside originals/, never hashed, missing, unreadable sidecar). Names are given
in index order with _2, _3 as filing does; XMP companions follow their photo.
- MassRenamer renames a step's files under the same leases after its folder moved, checks
the frames version, journals .chronos/rename-files.json and moves files in two phases
through temporary names so chains and swaps never meet; then sidecar, index
(FrameRepository.RenameFilesAsync, both dialects) and journal. A failure puts every file
back; a crash is completed by the next writer or the plan's resume, the index following.
Plans a paused or cancelled job holds are left to that job.
- JobKind.Move gets MoveJobHandler: it plans again and applies only the confirmed plan
(fingerprint and frames versions), with progress and checkpoints per sequence.
- POST /api/v1/archive/reorganize: dry run with the plan and its fingerprint, otherwise a
202 move job; validated templates, audited, sequenceChanged reorganized events.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit aae1c3eb18ea932b4a6251c5e2a282b9295a5785)