Owner review 2, R7 (part 1): rename and move existing sequences with the archive's folder, file and title templates, on the web panel and the desktop. Request: docs/requests/2026-10-26-owner-review-2.md.
Reorganize… (panel Library and Archive toast; desktop Archive manager, Library bar, Settings › Archive toast): the three templates, a dry run listing what is renamed, moved, kept and blocked with the reason, then an explicit Apply that runs as a move job.
One naming rule (FrameNaming) for import, upload and Reorganize; photos adopted in place, unhashed or missing keep their names.
Crash-safe: a plan journal per run and a two-phase file journal per sequence; resumed at archive open or by the job; held plans wait for their job; an unreadable journal is logged and never stops the archive from opening.
The job does exactly what the confirmed dry run showed (fingerprint by file digest; 409 plan_changed otherwise); leases against scans, uploads, deletes, restores and renders; exports move with their folder in the same transaction.
Writers (sync Take server / Save both, render filing, proxies, thumbnails, editor saves, Download originals, resumed renders) refuse a folder another program moved or gave to another sequence, never writing or deleting there.
Server: POST /api/v1/archive/reorganize (dry run → plan with a bounded plan cache; apply → job), archive_reorganized audit entry, template rules (invalid_template).
Also merged: the phase 3 docs and translations; the phase 3 request Commit cell.
Strings in all 38 languages. BRIEF, DECISIONS (25 rows), CHANGELOG [0.1.0-rc.6], STATUS, ARCHITECTURE updated.
Review: one adversarial review round (36 confirmed findings, 5 high) and six fix rounds, each fix checked by an independent checker.
Tests (Windows, local): Core 1291, Data 613 (+177 PostgreSQL skipped), Server 260 ×2, Tools 60, App 690 (five classes excluded on this PC as usual); format, i18n check (0 warnings), xaml-lint, package-guard clean.
Owner review 2, R7 (part 1): rename and move existing sequences with the archive's folder, file and title templates, on the web panel and the desktop. Request: `docs/requests/2026-10-26-owner-review-2.md`.
- **Reorganize…** (panel Library and Archive toast; desktop Archive manager, Library bar, Settings › Archive toast): the three templates, a dry run listing what is renamed, moved, kept and blocked with the reason, then an explicit Apply that runs as a `move` job.
- One naming rule (`FrameNaming`) for import, upload and Reorganize; photos adopted in place, unhashed or missing keep their names.
- Crash-safe: a plan journal per run and a two-phase file journal per sequence; resumed at archive open or by the job; held plans wait for their job; an unreadable journal is logged and never stops the archive from opening.
- The job does exactly what the confirmed dry run showed (fingerprint by file digest; 409 `plan_changed` otherwise); leases against scans, uploads, deletes, restores and renders; exports move with their folder in the same transaction.
- Writers (sync Take server / Save both, render filing, proxies, thumbnails, editor saves, Download originals, resumed renders) refuse a folder another program moved or gave to another sequence, never writing or deleting there.
- Server: `POST /api/v1/archive/reorganize` (dry run → plan with a bounded plan cache; apply → job), `archive_reorganized` audit entry, template rules (`invalid_template`).
- Also merged: the phase 3 docs and translations; the phase 3 request Commit cell.
- Strings in all 38 languages. BRIEF, DECISIONS (25 rows), CHANGELOG `[0.1.0-rc.6]`, STATUS, ARCHITECTURE updated.
Review: one adversarial review round (36 confirmed findings, 5 high) and six fix rounds, each fix checked by an independent checker.
Tests (Windows, local): Core 1291, Data 613 (+177 PostgreSQL skipped), Server 260 ×2, Tools 60, App 690 (five classes excluded on this PC as usual); format, i18n check (0 warnings), xaml-lint, package-guard clean.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Owner review 2, R11 asked for more log settings. The file sink now writes daily or
hourly files, continues a full file in numbered parts and prunes by age and by the
total size (never the file being written); its options change while it runs.
Server: the file and console levels are separate and read by the logging filters
at every line, so the admin panel's new Logs group applies without a restart; the
engine's level follows the lower of the two. This also fixes a bug: the file logger
was fixed at Information, so CHRONOS_LOG_LEVEL=Debug or Trace never reached the
files. New variables CHRONOS_LOG_CONSOLE_LEVEL, CHRONOS_LOG_RETENTION_DAYS,
CHRONOS_LOG_MAX_FILE_MB, CHRONOS_LOG_MAX_TOTAL_MB, CHRONOS_LOG_ROTATION,
CHRONOS_AUDIT_RETENTION_DAYS and CHRONOS_DIAGNOSTICS_LOG_MB lock their settings like
the others; the diagnostics zip keeps the configured share of each log.
Desktop: Settings > Advanced gains Log level, Keep logs, File size, Logs total,
Rotation and Diagnostics logs, applied at every save; Advanced's Reset section
restores them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit cc875784e4952ee0e4c807b9d9c18496d3d5a8c3)
Owner review 2, R10: every timer that queues work becomes a visible schedule,
so the server and the desktop need one shared engine to run them.
- Migration 0007: schedules table (system rows keyed by system_key) and
jobs.schedule_id; Job.ScheduleId, JobDto.ScheduleId, JobRepository
HasPendingAsync / ListPendingTargetsAsync / ListByScheduleAsync.
- ScheduleRepository: seeding that keeps user edits, reset, compare-and-set
claim of a run (one winner across processes), outcomes.
- Scheduling: in-house recurrence (every/daily/weekly/monthly, DST gap moves
forward, ambiguous time runs once), ScheduleActions resolving scan, verify,
thumbnails, proxies, analysis, maintenance, backup, cleanup, duplicates and
orphans into archive jobs, IScheduleHost, and the Scheduler loop (catch-up,
clock going back, run now, CRUD as API v1 DTOs).
- New job kinds Backup (16) and Cleanup (17) with handlers, shared clean-up
steps (job history, audit log, trash report that never deletes) and host
steps through ArchiveServiceOptions; read-only Duplicates and Orphans report
handlers, so the server can run those kinds too.
- JobEngine no longer purges history at start: the housekeeping schedule's
job-history step does; JobEngine.CanRun and an EnqueueAsync with scheduleId.
- Protocol DTOs for schedules; job kind names in en and it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit eb0edd2483a493db7c6945d5b494461cabb2a4ad)
Owner review 2, R10: nothing may run out of sight, so every timer the server
ran becomes a system schedule the admin panel shows and manages, and
administrators create their own.
- SchedulerHost runs the shared Scheduler on the job engine (started after
JobEngineHost, stopped before it); ServerScheduleHost gives it the
container's time zone (UTC with a warning when TZ is unknown), the archive
refreshed from archive.json at every run (what ArchivePolling did), the
clean-up steps and the system schedules: archive-scan every 10 minutes
(no catch-up, also run once at start like the polling), upload-cleanup
every 30 minutes, index-backup at 03:00 (SQLite only), housekeeping (job
history) at 04:00 and audit-cleanup at 04:30.
- ArchivePolling and DatabaseBackupService are gone; UploadMaintenance only
recovers commits at start, its sweep is the "uploads" clean-up step.
- /api/v1/schedules (ManageArchive, audited): list with actions and time
zone, create, PUT/PATCH, delete (409 schedule_system), run now (409
schedule_pending), reset (409 schedule_no_defaults), runs paged by cursor;
invalid fields are 400 invalid_schedule naming the field.
- CHRONOS_AUDIT_RETENTION_DAYS (AuditRetentionDays, default 365) seeds the
audit clean-up; set by the environment it is applied at every start and
locked. Job history leaves Settings: it is the housekeeping schedule's age
limit, and the setting is what a reset restores.
- Admin panel: Jobs has Queue and Scheduled tabs; schedules with when (in
the panel's language and the server's zone), next run, last result, a
switch, Run now, Edit, Delete or Reset, their runs linking to the jobs, and
a side panel for the action, recurrence and parameters; job rows a
schedule queued carry a Scheduled pill. Strings in en and it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 808ce94ae29e3bf4522cb4d40dfd76d4f8529c64)
Owner review 2, R10 on the desktop: every timer that queued work out of
sight is now a visible, editable schedule of this PC.
- DesktopScheduleHost implements IScheduleHost: the PC's time zone, the
archive at Settings › Archive's folder (refreshed from archive.json,
none while it is offline), and three system schedules: archive-scan
(every:<ScanIntervalMinutes>m, seeded once from the old setting, no
catch-up), index-backup (every day with catch-up, replacing
DatabaseBackups.RunDailyAsync) and housekeeping (daily 04:00 with
catch-up: job history 90 days and the new cache-trim step).
- AppServices starts the Scheduler after the engine, once the archive was
reopened; an unplugged archive is looked for every minute and the
scheduler woken when it is back. The rescan loop and the daily backup
loop are gone; ApplyJobSettings wakes the scheduler.
- CacheStore.Trim brings the cache to Settings › Storage › Cache limit,
oldest files first, skipping files in use and the proxies, render-node
and server-import folders; CacheTrimStep runs it as a clean-up step.
- Jobs gets a Queue | Scheduled segmented control. Scheduled lists the
schedules (switch, name, action, when, next run, last result) with Run
now, Edit, Reset (system) or Delete (user's, confirmed), the selected
schedule's last runs with Show in queue, and an in-window editor that
checks every field with the scheduler's limits. Jobs a schedule queued
carry a "Scheduled" pill; the history line follows the housekeeping's
job-history days.
- JobNotices: a scheduled background run raises a toast only when it
fails (upkeep stays silent).
- Settings › Archive › Rescan every is removed; ScanIntervalMinutes stays
only as the seed. Strings in en and it; the others are retranslated.
- The capture shows jobs-scheduled and jobs-schedule-editor on a stopped
scheduler clock with sample schedules.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit e25d812feb3f417cb9251c748c29e8035fd9b03c)
Settle what the R10 scheduler and R11 log packages left open when they were
integrated (owner review 2, phase 2).
- Audit retention has one source of truth, the audit-cleanup schedule's age
limit. AuditRetentionDays defaults to 0 (the audit log is kept forever, so
an upgrade deletes nothing; the schedule is seeded off) and accepts 0-3650,
what a schedule's age limit takes. Saving Settings › Logs › Keep audit sets
the schedule's limit (on with a limit, off at 0) without a restart;
CHRONOS_AUDIT_RETENTION_DAYS locks it and Reset goes back to it.
- Both hosts scan right after start again, as their polling did: the server
after the scheduler starts, the desktop once the archive was reopened and
again when an unplugged one is back. Scheduler.RunSystemNowAsync runs the
archive-scan schedule when it is enabled and has not run since the start,
and skips while its scan is pending.
- Desktop scans follow Settings › Analysis › After a scan at every run: a scan
schedule without its own deep parameter asks the host
(IScheduleHost.DeepAnalysisAfterScan), the archive-scan schedule no longer
freezes the setting, and the editor offers deep only for analyses, so the
setting's tooltip stays true.
- The server's upload clean-up runs every 6 hours instead of every 30
minutes, to keep the job history readable; idle uploads still expire after
UploadRetentionHours.
- The Unraid template and docker-compose leave CHRONOS_LOG_LEVEL empty or
commented out, and say that setting it locks both log levels, so the admin
panel can change them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The desktop opened its log files with the default limits and wrote its first
line, which prunes, before Settings › Advanced › Logs were applied. Every start,
and every launch that only hands its file to the running Chronos, deleted logs
older than 14 days and cut the folder to 1 GB whatever the user kept.
AppLogging.Open now builds the sink from the stored settings before that line;
the settings are read again once the launch owns the data folder.
A total below one file deleted each finished file as the next one opened. The
rule now lives in LogFileOptions.TotalBelowFile: the server keeps refusing it,
the desktop raises the total to the file size and its rows no longer offer the
combination.
The desktop log rows threw on negative sizes from an imported or hand-edited
file and showed raw values the files never got; they now show the applied ones.
Upgraded Unraid and compose installs keep CHRONOS_LOG_LEVEL=Information, which
locks both levels. The lock stays; the server now reports which variable fixes
each locked setting (LockedBy), so the panel's tooltip names it exactly and says
to remove it to change the value there. The releases README tells upgraders.
The former-constructor log test no longer fails across midnight UTC.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 8ba7162bd5926d34c5ec4e40e2a2dad063ee19c3)
Settings › Logs › Keep audit showed ServerOptions.AuditRetentionDays, a second
copy of the audit clean-up schedule's age limit. Edits made on Jobs › Scheduled
never reached it, so the panel could say "kept forever" while entries were
being deleted every night. Saving 0 there then changed nothing, because the
endpoint only compared against the stale option value.
- GET and PUT /server/settings now report the schedule's limit in force (0
while the schedule is off). Saving compares against that value. A value sent
back unchanged leaves the server.json reset default and the env lock alone. A
new value sets the schedule and becomes the reset default.
- ApplyAgeAsync also turns the schedule on when it already holds the days but
is off.
- CHRONOS_AUDIT_RETENTION_DAYS is now applied before the scheduler's first
pass, through a new Scheduler.StartAsync overload with a beforeFirstPass hook.
Before, a missed 04:30 run was caught up at start with the stale days, which
could delete entries the variable says to keep. While the variable fixes a
limit above 0, turning the schedule off is a 409 setting_locked.
- Corrected the comments in SchedulerHost, ServerOptions, ServerSettingsStore,
LogSettingsDto, the header of settings.js and ARCHITECTURE.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 490ed286e9f32745174b13b1963d6ec91955196b)
Owner review 2, phase 2 review findings (scheduler core).
- Log.Write caught only IOException. Microsoft.Extensions.Logging wraps
provider failures in an AggregateException, so a log line that could not
be written (in tests: the process-wide sink of a stopped server whose log
folder was gone) escaped JobEngine.RunAsync's catch before the failure was
stored: the job stayed running and the worker faulted. This was the cause
of the intermittent JobApiTests/ArchiveModuleTests failures. Log.Write now
drops any non-fatal sink failure, TeeLogSink keeps a line from the other
sinks, FileLogSink drops a line it cannot write and reopens the file at the
next one, and LoggerSink drops what the providers throw. The scheduler's
loop relies on the same guarantee.
- The daily backup loop (RunDailyAsync, IsDue, Interval, CheckInterval) had
no caller since the index-backup schedule replaced it; it is removed and
the DatabaseBackups summary describes the schedule.
- The first copy after the upgrade no longer waits a day (or for 03:00):
SystemSchedule.LastDone seeds a new row due at once when its work was last
done a period or more before, and both hosts pass the newest copy in the
backups folder for index-backup.
- Back up now (Settings and Archive), the copy kept before a restore and a
backup job that keeps fewer prune to the largest Copies kept of the backup
schedules (DatabaseBackups.KeptAsync), not a fixed three. The four
tooltips that promised three daily copies are reworded (en, it) and their
stale translations deleted.
- New tests for the scheduler loop itself: a tick, Wake, a pass that threw,
and dispose during a pass.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit c5ad0c4c3f636129afe5dd1ce039185516da5621)
- SchedulerHost reads archive.json every 10 minutes on its own timer. The archive-scan
runs that used to do it are skipped while a long scan is pending, and the schedule may
be off or daily, so uploads kept a desktop's old folder template or proxy size.
- Every schedule change and run, a skipped run included, is published as a
scheduleChanged event. The Scheduled tab reloads on it, so skipped runs, next-run moves
and other administrators' edits show without waiting for a job.
- The Scheduled tab still draws when the schedule a job links to, or an expanded one, no
longer exists: its runs are dropped instead of failing the whole load.
- Every time on the Scheduled tab (next run, last result, runs) is in the server's time
zone, as its "Times in" line says.
- Audit details name a system schedule after its key (system:<key> · name · ...). The
dashboard and the Logs page show it by its localized name and the recurrence code in
words, as the Scheduled tab does. Older entries keep their recorded name.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit c20f573d0bdf1cdcf3a86e9702ac76a4bf9508d9)
Owner review 2, phase 2 (R10) review findings on the desktop:
- Showing the Scheduled tab (and coming back to Jobs on it) reads the
actions' availability again, as does a Run now answered unavailable;
rows and an open editor follow, so turning proxies on no longer needs a
restart.
- A delete the index refuses keeps the row: the failed call no longer
reads as Deleted (the enum's default), so a live schedule never leaves
the page.
- SchedulerReady completes false when the index (or the engine) does not
open, so the tab shows that the schedules do not run instead of an
empty panel.
- A read of a schedule's last job that started before a live change or a
later read is ignored, so a finished job no longer shows as running.
- The editor's Action, Unit and Priority dropdowns follow a language
change, keeping what was chosen.
- Weekly days in the table read from the UI language's first day, as the
editor's toggles do.
- Backup tooltips no longer promise daily copies with three kept (their
translations are dropped for retranslation); two tooltips now name the
real Settings rows (Proxy size; Spazio su disco › Limite della cache).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit c137e2c74cddef299b2e4179ef0417fa4977953c)
The audit retention in force ignored the audit clean-up's steps: with the
audit step unticked nothing was deleted, yet Settings › Logs still showed the
age limit. It is now 0 without that step, and setting a limit (Settings › Logs
or CHRONOS_AUDIT_RETENTION_DAYS at start) ticks the step again, so a saved or
fixed retention always takes effect. While the variable fixes a limit above 0,
an edit that drops the step is 409 setting_locked like turning the schedule off.
The admin panel's Scheduled tab disables what the variable fixes (the row's
switch, the form's Enabled and audit step, the age limit) with the locked
tooltip, and points a setting_locked refusal at the field actually refused.
The Copies kept tooltips now say the backups folder keeps as many copies as
the backup schedule that keeps the most; the LastDone and Newest comments
state the real first-copy rule; Keep audit is documented last-writer-wins.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 2, R6: the web panel manages the library without editing it, so
the engine and the server must delete single photos safely, keep them out of
sync afterwards, and let an administrator restore or finally erase the trash.
- Migration 0008: frame_removals (tombstones by sequence and SHA-256, reason,
replacement); the sidecar gains "removed" (omitted when empty) and frames a
reserved "source"; the indexer writes the tombstones on every sync, so a
rebuild keeps them, and drops a hero frame that is gone.
- FrameTrash: dry run (busy, frames changed, offline, would empty), delete under
the sequence lease with a write-ahead journal that the next writer undoes
after a crash, files to trash/photos/<seq>-<time>/originals with a record,
sidecar without the frames plus tombstones, index sync clearing analyses,
thumbnails and proxies, proxies renamed to follow their frames, follow-up
jobs. Restore re-hashes every file, keeps mismatches in the trash, puts the
same frame records back and drops their tombstones, or files the photos into
a new sequence through the ingest when theirs is gone.
- Project positions on vanished photos are translated by photo and wait as
pending frames, so they come back with a restore.
- Trash entries have a kind (sequence, photos, replaced); emptying is a dry run
with a fingerprint and a new EmptyTrash job (18) that erases exactly the
planned entries, refuses a stale plan and erases replaced originals only
while their replacements still hash right.
- Sync honours tombstones: nothing one side deleted is offered back, local
files are never deleted, replaced photos count as their replacement; the
server answers an upload of a tombstoned SHA-256 as already there.
- Server: sequence thumbnail, photo delete, bulk delete/retag/jobs, trash
list/restore/empty endpoints with their error messages; a verify of
sequences now targets their archive (POST /jobs failed before).
- Desktop trash dialog lists photo entries and empties the trash after a
typed confirmation through the same job.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 35bb56690a1d69eae57153d036e1409201cd73f7)
The web panel now manages the library without editing it: the owner can
browse and view sequences and photos, delete sequences and photos into the
archive's trash, restore or empty the trash and run mass operations, as
R6 asks, on top of the engine endpoints of the previous commit.
- Library page right after the Dashboard: search, Year/Camera/Status/Tag
filters fed by a new GET /api/v1/sequences/facets, sort, cards or list
(remembered per browser), lazy cover thumbnails, Load more by cursor,
multi-select with Shift ranges and "Select all N" of the filter, and a
sticky bar for the selection: Analyse, Proxies, Thumbnails, Verify,
Tags (add/remove), Export CSV (client-side) and Delete (dry run, list
of what moves to the trash, then the move). Filters live in the address,
so Back from a sequence finds them again.
- Sequence view (#/library?id=): inline title, tags, rating and notes,
facts, photos in pages of 500 with content-visibility, a photo viewer
(proxy, arrows, Esc, Exif facts), Set cover, Download original, Delete
photos (typing the count above 20 photos), Delete sequence, renders to
download. No video editing controls.
- Trash view (#/library?view=trash, also linked from Archive): entries,
Restore, and Empty (dry run, list, the localised word typed, the plan's
fingerprint sent back, the job followed to its end).
- Live updates from sequenceChanged and jobState; keyboard grid (one tab
stop, arrows, Space, Shift+Space, Enter, Ctrl+A, Esc); RTL, dark theme.
- GET /sequences takes rendered=true|false for the Status filter.
- ui.js: confirmDialog's typed confirmation by name, word or count, with a
list of what the action concerns; formDialog. api.js: putBytes for the
web upload, which the Library imports on demand (upload.js, optional).
- New web icons from icons.py (Image for the Library, trash, grid/list,
arrows, stars, cover); directional glyphs mirror in right-to-left pages.
- Strings in en and it; tests for the facets (both dialects), the rendered
filter, the menu, the modules and the on-demand upload import.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 029cf334f66cb6fa1265b96a6f8faff2964c11ea)
Owner review 2, R3: the panel can add photos to an existing or a new
sequence without the desktop app. upload.js is a dialog the library pages
open (openUpload({ api, sequence, onDone })): file picker or drag and drop
(folders are counted and left out: whole-folder import stays on the
desktop), per-photo state, a total bar, Cancel that deletes the started
uploads, and a leave-page guard while sending. Each photo is hashed in a
same-origin module worker with an in-house incremental SHA-256 (8 MiB
reads; crypto.subtle cannot hash in pieces), which runs the FIPS 180-4
known answers and a crypto.subtle cross-check before its first hash and
refuses to hash on any mismatch; the server verifies the hash again.
Chunks go through api.putBytes with the session's CSRF header, two files
and two chunks at a time, retrying no answer, 429 and 503; quota, space
and permission refusals stop the run with the server's message, and a
photo deleted from the sequence shows as deleted before.
server/info now lists the photo extensions the archive files, so the
dialog offers and sends only those. The CSP already allows the worker
(worker-src falls back to script-src 'self'); tests pin that, the module
walk follows the worker, and a browser-shaped upload runs end to end
through the cookie session.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit c64c60ab8bb41c102182e284177ac04a56bf1058)
The phase 3 packages land together, so the panel's pieces must stay in step:
- Admin files are served with Cache-Control: no-cache and their content
ETag (If-None-Match lists, W/ tags and * honoured). With max-age=3600 a
browser that loaded the panel before an upgrade could run new modules
next to cached old ones for up to an hour; now it revalidates each file
and only what the upgrade changed is sent again.
- The Library's Upload and a sequence's Add photos open upload.js, which
now ships with the panel: the test requires the module (no 404), the
dynamic import and the openUpload({ api, sequence, onDone }) calls.
- Bulk jobs over more than 1000 sequences queue one job per 1000; the
toast now says how many were queued, also when a later chunk failed.
- The live refresh re-reads every loaded row, a thousand per request,
instead of dropping rows beyond the first 1000 back to Load more.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The review of owner review 2 phase 3 found that the photo trash could destroy or
strand originals outside the Empty job and let deleted photos come back.
- A restore into a new sequence stages each original inside its own entry
(<entry>/.restoring), never in a staging folder other restores share or
maintenance sweeps; any failure moves it back, the commit runs to its end once
the file has left, a cancel stops between photos with the record kept true,
and the next restore of the entry puts back what a crash left staged. Nothing
erases a staging folder any more.
- A restore into an existing sequence writes .chronos/restore.pending.json before
its first move; SequenceWriter.ReadLocked settles it (files back into the entry
before the sidecar was written, record rewritten after), cancellation is
checked once before the journal, and a companion that cannot follow puts its
photo back whole. Only an intact frame keeps a trashed copy out.
- A deletion's record keeps a .pending name until its sidecar is written, so the
trash neither lists, restores nor empties half an entry; a failed sidecar
write undoes the moves, and scans settle any of the three journals.
- Photos never hashed are hashed as they go and get their tombstone; a photo
with neither hash nor original blocks the plan (FrameDeleteBlock.Unhashable).
Sidecars rebuilt from the photos, and sequences restored without one, keep
their tombstones; the index drops a tombstone whose content a frame holds.
- Emptying re-reads and re-measures each entry under its lease before erasing.
- Once the sidecar is written a deletion or restore stands when the index cannot
follow (logged; the next scan resyncs it).
- XMP companions are listed once per directory, case-insensitively; a restore
into a new sequence picks a name its companions can follow, and one that still
cannot is kept in the record as a leftover.
- thumbs.pack is re-keyed with the frames on delete and restore, so the queued
pass reuses the thumbnails; the server checks the fingerprint of thumbnails of
frames never hashed too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 0bb631dd83d082e2569b98d127d827adc2e7f899)
Sync:
- A server frame that has not been hashed is known by content only once it is
downloaded: one this PC deleted (or holds as its replacement) is now deleted
from staging instead of filed again, which also dropped its tombstone.
- An unhashed local original that turns out to be a photo the server deleted
is not uploaded, and the archive verify then writes the hashes into the
index, so the row settles instead of offering Upload for good.
- A tombstone leaves a photo out of the comparison only when its side no longer
holds that content, so a tombstone left beside a held copy does not keep the
other side's copy missing forever.
Uploads:
- StartUploadRequest.Restore (optional, never sent by sync or older clients)
lets an explicit user upload file a photo deleted from the sequence again,
also after the trash was emptied; the completion repeats it with
?restore=true and the ingest drops the tombstone.
- The completion checks the tombstone again: a photo deleted while its bytes
were on the way is not filed (409 photo_removed, upload cancelled); the
protocol client reports that as not sent.
- A tombstone of content a frame of the target still holds refuses no repair.
- Hidden dot names (AppleDouble "._" files) are refused, as the archive
scanner leaves them out.
Web upload dialog:
- Upload again on rows marked Deleted before; the tooltip no longer promises
a trash restore that may be impossible.
- Sends a capture time: the Exif DateTimeOriginal of a JPEG or TIFF-based file
(minimal in-house reader, capture-time.js), else the file's time, so photos
without Exif keep their order.
- Esc is stopped at keydown during a run (Chromium allows one prevented cancel
per activation); hidden dot files are left out; a completion refused while
another one files the upload waits for it; the same photo picked under two
names waits for its first copy.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit d051bcfc351f5a08500ca864a6508576a95492a4)
- frames/delete carries its own request body limit (about 4.8 MB), so the
documented 100,000 ids fit; the server's 1 MiB stopped at about 26,900.
- Restore tells a damaged or foreign sidecar of the target sequence
(409 sidecar_mismatch) from an entry whose files no longer match its
record (422 trash_mismatch, now a TrashMismatchException); frames/delete
answers sidecar_mismatch instead of 500, and 404 when the sequence left
the index between plan and delete, also on the re-plan.
- With the archive offline, the trash list and the empty plan answer
503 archive_offline instead of an empty trash; a read-only archive still
lists and plans but cannot be emptied.
- The empty request is audited as trash_empty_requested: the job checks
the plan again and may erase nothing, so the entry no longer claims an
erase that has not happened.
- API tests for these paths, a named subset emptied, sequence-entry
restore and sequence_in_library, photos restored into a new sequence,
viewer 403 on bulk routes and admin deletes of another user's photos.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit fa35831d55c44746f7f76e0cff262ed6aecf8e72)
Review fixes for owner review 2, phase 3 (R6 Library on the web panel):
- Trash: the worker can end an emptying before the browser has read the
POST's 202, so its jobState arrived while the page did not know the job
yet; Empty then stayed disabled ("being emptied") and no result showed.
The page now keeps the last state of the jobs that ended and looks its
job up there before following it. Any ended job also reloads the list
(an emptying from another tab or the desktop sends no sequenceChanged),
and a Restore answered 404 shows the trash as it is now.
- Sequence: thumbnail, proxy, verify and analysis jobs send no
sequenceChanged, so tiles and the cover stayed placeholders and the
status chips stale. An ended job now schedules one refresh (not pushed
back by the next): the sequence is read again and failed images are
asked for again under a retry address (shared retryImages).
- Library list: Esc, Ctrl+A or unticking every card left the "Select all"
snapshot in place, hiding Select all and stopping the live refresh from
pruning the selection. It is dropped once no selected sequence lies
beyond the loaded rows; Clear filters clears the selection too.
- The sequences' delete dialog lists at most 500 names (blocked ones
first, with their reasons), like the photos' dialog (shared LISTED).
- Admin.Trash.RestoreSequence.Tip promised a SHA-256 check that a sequence
restore never makes (it moves the folder back); it now says so and names
Verify (en, it; no other culture had the key).
- The upload test's name and comments say what it checks: upload.js is
only imported dynamically, not loaded on click.
Tests pin each change in SystemEndpointTests; the pages were also driven
in a browser against a fake API, where the pre-fix modules fail and the
fixed ones pass.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 78f66082fd85543d619375574c82cc63a233b7a8)
The desktop trash dialog sent the "N files stayed in the trash" sentence
through ShowError. ArchiveFailures.Cause has no arm for it, so after a
partial restore the red line and Narrator said "A file of the archive could
not be read or written." The sentence itself appeared only in the tooltip.
The same thing happened to an entry none of whose files matches its record.
- ArchiveDialogViewModel.ShowMessage shows a sentence that is already
localized. The trash dialog uses it for kept files, and its tooltip names
the files kept (six of them, then "+ N more").
- ArchiveFailures.Cause passes FrameTrash's Archive.Error.TrashMismatch
sentence through. It matches the sentence's text because the engine throws
a plain InvalidDataException. Any other InvalidDataException, such as a
sidecar that belongs to another sequence, still reads as a file error.
- Archive.Trash.List, Tooltips.Archive.Trash and Tooltips.Archive.TrashRestore
changed meaning in English: they now cover photo entries as well as
sequences. They are removed from the 36 cultures other than en and it, so
those cultures fall back to English and `i18n check` lists the keys as
untranslated instead of showing the old sequence-only wording.
- The XAML comments describe what the trash dialog and its error line show
now.
Tests: the dialog restores a photo entry and a sequence entry and checks
which rows are left. A photo entry with one tampered file shows the
KeptFiles sentence and keeps its row. An entry with every file tampered
shows the TrashMismatch sentence.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 2524a11445c87d37625b01095ef7c2a84a2ee422)
Second fix round of owner review 2, phase 3 (engine, server, desktop).
- A photo never hashed whose original is missing can be deleted again: it goes
into its trash record without a file and without a tombstone (nothing is left
to name), stays listed until Empty erases it, and a restore keeps it with the
reason "no file". FrameDeleteBlock.Unhashable now blocks only a present
original that cannot be read; the API answers it as 409 photo_unreadable
naming the photo, and every block has its own code and message.
- Deleting a whole sequence first settles an interrupted photo deletion,
restore or ingest of it (ReadLocked under its lease), so no journal or half
entry travels into the sequence's trash entry; it refuses while a restore
into it waits for its busy entry.
- FrameTrash.Settle takes the photo entry's lease and leaves the journal for
later while the entry is busy (an emptying), so it never races EraseAsync;
meanwhile no other restore writes its journal over it and scans do not adopt
its files.
- The hashes computed for frames that stay (to find a twin of a deleted photo)
go into the sidecar and index, and only a frame whose first and last 64 KiB
match a deleted photo's is read whole.
- A restore into a new sequence rewrites its record after each photo filed, so
a crash or a database failure never leaves filed photos listed.
- An upload completion no longer has a window before the commit: the ingest
checks the sidecar's tombstones under the sequence lease a deletion takes
(IngestRequest.RefuseRemoved), unless the upload asked to bring it back.
- A restore reports each kept photo with its reason (no longer matches its
record, could not be moved back, already in the sequence, had no file); the
desktop line and the API message say so in en and it, and the tooltip holds
the whole sentence. The desktop tells TrashMismatchException by its type.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 1858f1f450a35fb8383ede8d80ce5f8de9b7ceac)
The upload dialog's completion helper called `api`, which only exists inside
openUpload, so every web upload failed with a ReferenceError at its last step.
complete() now takes the dialog's api. A new test lexes every admin module and
fails when a top-level function uses api without taking it; it flags the old
upload.js.
During a run Esc is now stopped on the document in the capture phase. The old
listener sat on the dialog, so with the focus on the body (Start disables
itself, a click on the dialog's text) a second Esc closed the dialog and threw
the uploads away. The listener is added when a run starts and removed when it
ends or the dialog closes.
A sequence page refreshes after any ended job, because jobState names no
sequence. That refresh now redraws the header only when the sequence changed,
and the renders only when their list did. Stars, tags and renders are redrawn
through redraw(), so the keyboard focus stays put. restoreFocus finds an
unnamed control by its place, not as the first unnamed one. Failed thumbnails
are retried with a doubling wait and at most 8 tries, counted again once the
sequence changes.
The trash page reads the emptying it follows from /api/v1/jobs/{id} on every
load and after the event socket reconnects (api.events now emits
"reconnected"), so Empty no longer stays disabled when the job's end was lost.
A Restore in flight stays disabled across redraws.
The Library list counts cancelled jobs as ended (shared JOB_ENDED). Comments
are corrected in shared.js and library.js.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 641b9cd96b95d523990d1414c2bdead4138c5f4d)
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)
Owner review 2, R7 asks to rename and move sequences after import, on the web panel too.
The Library's mass bar gets Reorganize… for the selection (every sequence after Select all
without a filter, else at most a thousand ids), and saving a changed folder or file template
on the Archive page offers it for all sequences in the save toast.
The dialog (reorganize.js) has a switch and a field for the folder, file and title templates,
prefilled from the archive settings; each change asks POST /archive/reorganize for a dry run,
one request at a time, and the table shows every step before and after (title, folder, renamed
files with samples, photos that keep their names and why). Apply confirms with the counts of
sequences, folders and photos, sends the shown plan's fingerprint back, and the toast links to
the queued job; a plan_changed refusal plans again. Server refusals land on the field they name.
Toasts can carry an action; the audit entry archive_reorganized reads as a sentence.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 13939dff9a1e8a23ce7802ac38f2ded7fdbc2a74)
Owner review 2, R7 asks to rename and move sequences after import on the desktop too.
The desktop now uses the engine's Reorganize, the same plan and job as the web panel.
- One Reorganize… dialog replaces Rename… and Move… in the Archive manager and Move… in
the Library. It has three templates: folders, file names and titles. Each one has a
switch and is checked as it is typed. Folders and file names start on, filled from the
archive's settings; titles start off as {title}. Renaming only titles is the Titles
switch alone.
- The dry run stays in the dialog and follows the typing. Each sequence shows its folder,
title and first file names before and after. Sequences carried along with a folder are
marked, and photos that keep their names are listed with the reason. A summary counts
the sequences that change, the files renamed and the names kept.
- Apply no longer changes the archive from the dialog. It queues the engine's move job
with exactly the plan shown (its fingerprint), so the work can be paused, resumed after
a restart and followed in Jobs. The job refuses the plan if the archive changed after
the dry run.
- The Library's Reorganize… works on the selected sequences of one archive. The Archive
screen reads the archive again when a move job ends.
- After Settings › Archive saves a new folder or file template to an archive that holds
sequences, a toast offers Reorganize… for every sequence. Its templates are the ones
changed since; a second change made while the toast is up adds to that toast instead of
opening another.
- Strings in en and it. The keys of the old Rename and Move were removed and pruned from
every translation, so the 36 other languages show the new keys as untranslated instead
of keeping "Move".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 7bbf451f737a71b768dcd70a77b998daaef851f3)
Integrating owner review 2 phase 4a (R7) onto the reviewed phase 3 code.
- RenamePlanner: a sequence already at its expanded folder, or at the " (n)" of it that
filing or an earlier Reorganize gave it, keeps that folder (in the template's case, unless
another sequence holds that exact name). The planner seeded its claimed folders with the
sequence's own, so "2026-09-28 (2)" was planned to "(3)" and back to "(2)" by the next
run; a second Reorganize with the same templates now plans nothing.
- MassRenamer: each step settles what a crash or a busy trash entry left in its sequences
(SequenceWriter.ReadLocked) and waits, as a sequence deletion does, while a restore from
the trash is not settled (FrameTrash.EnsureSettled), before its folder or any file name
changes: that restore's journal names files by the names they had. Trash records keep
restoring after a Reorganize: into the sequence where it is now, under the record's own
name made free (_2) with its companion following.
- Jobs.Kind.Move and Admin.Job.Kind.Move now mean "Reorganize": their old "Move archive"
translations are removed from the 36 other cultures so they are translated again.
- Tests: a second run plans nothing (planner and archive), companions found alike by the
trash and Reorganize whatever their case, a photo deleted before a Reorganize comes back
beside the new names, a Reorganize waits for a busy restore and settles it first.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The v0.1.0-rc.5 release build failed on the shared runner when the last renewal
timer ran 75 ms late: the test now checks that the expiry moved on.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 2, phase 4a review findings on the renamer.
- File rename recovery is safe to run again from wherever it stopped: once every
file is at its temporary name the journal says phase 2, as Run does, so a second
recovery (after a failure, a crash or a sidecar that could not be written) never
moves a file that reached its new name. A new name something else took meanwhile
is never written over: that photo and its companions go back to their old names,
or to the first free _2, _3, recorded in the journal before they move, and the
frame names where its photo is. A journal is never deleted while a temporary file
of it is still there.
- Every check that can refuse a step runs under the step's leases before anything of
it moves: where its sequences are, strangers inside, its new folder taken since the
plan (a restore, an upload), a sidecar of a newer format, a title edited since the
plan (compare-and-set against the planned from-title, sidecar and index), and its
file renames, compared by a digest of every move at the planned frames version (a
verify that hashes photos does not bump the version). Once the folder moved, every
index row follows it before any file is renamed, and a photo in use or files found
changed keep their names: the step completes.
- The same checks run up front for a held plan, so its retry either fits or is given up.
- A failed move job holds its plan, as a pause does: an archive open no longer
applies the rest unasked; only the job's retry does. File renames a step left
half-way are still completed at an archive open.
- Each sequence changed is told as its step is journaled, so a pause or a failure
never keeps it untold; the plan's journal keeps the tally of every run, so the job
log counts the whole plan.
- A selected sequence deleted while the job waited is named in the log and the plan
refused with the localized stale-plan error, not a raw ArgumentException.
- The dry run renames no file of a newer-format sidecar.
New log lines and error (en, it): title and file names kept, file names kept because
a photo was in use.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 1d1c888120edd709dbb5341c1922bf85085c4857)
Reorganize with the archive's own templates planned renames and moves for
photos just filed, and some templates could strip extensions, hide sequences
from scans or stall a dry run. Owner review 2, phase 4a findings.
- Filing and Reorganize share one context: uploads and imports name every
photo with the sequence's camera and lens (its first photo's, or the
creator's hint), an upload's folder from its first frame in the new
sequence, and a missing capture time from the sequence start instead of
the current time. The planner expands folder and title templates from the
first frame in the sidecar ({name}, {ext}, {iso}...), never today's date.
- Titles expand as text (ExpandText): "Paris: night" stays as typed.
- A sequence whose sidecar cannot be read (torn, another sequence's) keeps
its folder, title and names, listed with why, and so does every folder
around it; the dry run reads every sidecar, nested ones included.
- Kept never gives one folder to two sequences of a plan whatever the case,
and a case-only move onto another folder is refused instead of taken as
done.
- Shared template rules (TemplateRules) for the server's Reorganize and
archive settings and the desktop's fields: a file template must keep the
photo's extension ("{n}{ext}" refused) and tell a session's photos apart;
a folder template may not write a level scans skip (a leading dot,
originals, proxies, exports). Levels a title gives are escaped with "_".
- {ext} comes from the file, or from the original name when the file lost
a photo's extension, so a Reorganize can put it back.
- Unique names cost linear time (UniqueNames) with the same names as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 6c734777e01476881a3f34b3188571cc3f7150ab)
A Reorganize step that moves a sequence folder carries its exports/ with it, but only
the sequences and frames rows followed: renders.output_path kept naming the old folder,
so the server answered 404 for the export, Get/Send exports and Reveal lost it, and no
scan or trash restore could repair it. RenderRepository.RebaseFolderAsync now rewrites
the archive-relative output paths of the step's sequence in the same transaction as the
frames (idempotent on resume; absolute outputs and the archive root are untouched).
Writers that read a sequence row before taking its lease wrote into the folder a
Reorganize had moved meanwhile, creating it again (project.json from the editor or a
sync, a thumbnail pack) or failing on its missing sidecar. They now take the folder from
the index row read under the lease (SequenceWriter.FolderAsync): the editor's save
refuses with FramesChangedException and reloads at the new folder, FramesCurrentAsync
reports a moved folder, and the sync apply, project store, thumbnail pass and its
status, decode tiers, analyses, verify, info edits, ingest, duplicate flags, pack
compaction and photo restores write where the sequence is now; a photo deletion planned
before the move is refused as stale.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit be28d8acf0d96012c94a266f8af61e9bbafaa28d)
An all:true dry run reads every sidecar and photo folder of the archive inside
the request, and the confirm planned the whole archive again before answering
202. The server now keeps each dry run's plan for five minutes (eight plans at
most) by archive, selection, templates and a stamp of the archive's index rows:
the same dry run again and its confirmation take the kept plan, and any change
the index records (an upload, an edit, a move, a scan, a verify) gives another
stamp and a new plan. A change made on disk alone is not in the stamp; the move
job still plans again and refuses a plan that no longer matches.
Server tests now cover an all:true apply around a sequence already in place, a
real plan_changed after an upload, a move job paused between two sequences and
resumed, archive_offline, job_unavailable, more than 1,000 ids and the kept
plans themselves; a Data test covers the index stamp.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 71bb53fbf8eb7d0327ea692d046634b12f8d37e9)
Review of owner review 2, phase 4a (R7): the Reorganize dialogs of the desktop and the web panel.
Desktop
- Clicking Apply first takes the focus from the template field, which committed it and started
a dry run identical to the one on screen: Apply turned off under the click. A commit now plans
only when the templates differ from the shown plan (or the last dry run failed).
- The Settings toast's Reorganize… disposed whatever dialog the Archive screen had open, so a
running Delete stopped without being asked. An open dialog now stays and its archive is not
switched; Reorganize says it waits and opens once that dialog closes, with the archive's
templates read again and every part the toasts offered meanwhile.
- Each Settings toast takes its own archive's offer (one pending offer per archive), and a toast
gone early (dismissed, pushed out) lets the next change of that archive raise its own toast:
Toast.Closed now says when a toast leaves the screen.
Web panel
- The Library sends the selected ids up to a thousand. all:true is used only above that, when
the selection is exactly what Select all fetched without a filter and the archive has not grown
since, so a sequence unticked or added later is never reorganized; otherwise the toast asks to
select again.
- The preview's "before" of an untitled sequence is its old name, not the new title twice.
- A dry run of the same request answering during the confirmation no longer drops the confirmed
apply; a plan that really changed is shown and said (Admin.Reorganize.PlanChanged).
- Enter in a template plans at once (the form never submitted on Enter).
- The confirm tooltip and the module header no longer say the moves are verified: moves and
renames are not hashed.
Strings in en and it; the reworded key exists in no other culture.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit bed718fb5af2ef69943fd348690c689259872a34)
A Reorganize with a file template failed its job at the step of a sequence
a camera was still uploading into, and its retry gave the rest up. Photos
changed since the plan now never refuse a step: that sequence keeps its file
names (FilesKept), its folder and title change as planned, the other steps go
on and the job ends with ReorganizeKept. The fingerprint, the job's
confirmation and the check under the leases pin file renames by their digest
instead of the frames version, so photos filed under the names the plan gives
them no longer make a dry run or a queued job stale.
- A step whose folder or files a template names after {title} checks the
title as a retitle does (RenameStep.NamedByTitle): no name comes from a
title edited since the plan.
- Recovery sends a photo that already took its new name back together with a
companion whose new name was taken, so the two never end up apart.
- ArchiveService.OpenAsync logs a NewerFormatException from resuming a plan
and keeps its journal, so a server still boots.
- Once a step's folder moved, every index row of the step follows it even
when a sidecar cannot be read or written; the step then fails for a retry.
- Job log lines and errors give the real reason for files kept busy (in use
or a new name taken) and for a sidecar of a newer format (new Newer
outcome; strings en and it).
- A plan an archive open completes tells sequenceChanged; the docs that
promised more than that are corrected.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit f8554b8af0828ab9b0ff128e694abacdd53e6fd7)
Second fix round of owner review 2, phase 4a (planner findings).
- A sequence keeps a folder that differs from its own in case only while no
other folder holds that exact name (RenamePlanner.ExistsExactly, every level
compared exactly). On a case-sensitive file system a stray "Trip (2)" beside
the sequence at "trip (2)" no longer gives a case-only step that MoveFolder
refuses at every archive open: the plan gives "Trip", and a plan whose
target appeared since is refused under the step's leases before anything
moves (or dropped when it resumes). A change of case in an outer level no
longer looks like two folders on Windows.
- A file name longer than 200 characters is shortened before the ".{ext}" the
template ends with, never through it, so a long title never strips the
photo's extension.
- The archive engine's own settings check applies the template rules the
server and the desktop apply (a folder scans skip, a lost extension, names
that repeat), so archive.json can no longer take such a template.
- The server's invalid_template answer names the rule after the field
("fileTemplate:extension") with the desktop's sentence as its message; both
admin panels show it on the field.
- FrameNaming keeps only the naming overloads production uses.
- Comments about Unreadable say the whole sequence stays as it is.
- Tests pin filing against Reorganize: an upload without a capture time, a
card's second session with {session}, a duplicate skipped mid-session, and a
whole folder of two cameras named with the first one's camera.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 50fe59aec1e180daa1733bcb951892a79dceba6c)
Second review of owner review 2, phase 4a (Reorganize), cross-cutting findings.
- A second index of the archive (a desktop sharing a server's archive, or a folder moved by
hand) moved the sequence row at its next scan but left renders.output_path at the old
folder: the export answered 404 there. The scan now rebases the render rows in the same
transaction when it finds a sequence in another folder.
- The rebase covers every render of the archive under the old folder: the sequence's own
exports always, and another sequence's export saved inside it (through the Export folder
picker) when its file moved with the folder. That check keeps the exports of a sequence
that took the old folder since (a later Reorganize on the other index) where they are. A
change of case only counts as a move.
- The desktop now tells an open editor after each Reorganize step
(ArchiveServiceOptions.SequenceChanged -> AppServices.SequenceReorganized), and the editor
reads its sequence again where it is now, so frames no longer decode blank until the next
save. LocalSequenceSource.LoadAsync also requires the same folder on both row reads, so a
move that commits during the frame listing is never taken as current.
- Writers that wrote without the lease, or trusted a row another index had moved, could
create the old folder again. A proxy sent by a client is now filed under the sequence's
lease into the folder the index has then, and a gone sequence or folder answers 404
(sequence_busy 503 after the lease wait). The server files a render a client or render
node sends under the lease (ArchiveService.UnderLeaseAsync). "Save both" keeps its copy
under the lease. The proxy pass holds the thumbnail lease, as the thumbnail pass does. The
deep analysis opens its checkpoint under the sequence lock only while the folder is still
there, and a pass whose folder another process moved records nothing (the job logs
Advisor.Log.FramesChangedElsewhere). Editor saves and sync applies refuse when the folder
is gone.
- ARCHITECTURE.md no longer claims more than this: a render of another process whose folder
moves while it runs is still not stopped.
- ArchiveVerifier.FlushAsync: corrected the comment. A move keeps each file's stamp, so only a
check that found the file missing no longer applies.
Tests cover the scan path with a later swap into the vacated folder, another sequence's
export inside a moving folder, a photo deletion refused when the folder moved while it
waited for the lease, proxies sent and made after a move, Save both during a move, a deep
analysis whose folder another index moved, a render filed after a move on the server, and
an open editor reloaded by a Move job.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit c857b98f795b22956c060f1c5acf4d94b6d1c994)
A kept dry run was keyed on a stamp of every sequence row of the archive,
updated_at and verified_at included, so any upload, ingest status write,
verify or tag edit anywhere invalidated it and the confirm planned the whole
selection again. The plan was also bound to the request, so a proxy cutting
the request off cancelled it and a retry started over.
- The stamp (SequenceRepository.GetStampAsync) now hashes only what the
planner reads from the index: every row's id and folder (collisions and
what a moving folder carries), the planned rows' title, first capture,
camera, lens, photo count and frames version, and the titles of the rows
inside a planned folder. With all, every row is planned.
- ReorganizePlanCache makes a plan on the thread pool with the host's
stopping token, once per key for concurrent requests; a request cut off
only stops waiting, and the same request again waits for the plan or
takes it. Refusals and failures are still not kept.
- A kept plan is dropped by its own timer five minutes after it was made
(and never used past that), instead of staying until the next request.
- The protocol and endpoint docs say that plan_changed answers changes the
index has; one made on disk alone is found by the job, which fails and
changes nothing. The Capacity doc no longer claims a step per sequence.
- Tests: what the stamp follows and ignores, a kept plan surviving an upload
elsewhere and a verify, one plan for concurrent requests and after a
cut-off, the timer, an all:true apply carrying a nested sequence beside a
blocked-only one, the first sequence told before a pause. The
no-archive-module job_unavailable test expected a folder the planner no
longer plans without a sidecar; it now expects the unreadable step.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 7e01a4f85fe4b880ddd98a481fc8591649cec254)
A Reorganize step whose photos changed after the plan kept its file names but still moved its folder and wrote
the title the plan had computed from the old first photo, so a trashed first photo or an earlier photo filed
since left the sequence named after a photo that is no longer first. The plan now journals its folder and
title templates, and under the step's leases each folder move or retitle is expanded again from the settled
sidecar: it is applied only when it gives what the plan gives (the folder itself or its " (n)"); otherwise the
sequence stays as it was (Dropped, "changed after the plan"), or keeps its title and file names when an
interrupted run moved its folder already (TitlesKept). Plans journaled before this change are applied as made.
A Move job that ended failed with sequences kept, or whose held plan was given up, kept its plan:<id>
checkpoint after the plan's journal was gone, so a retry logged "completed when the archive was opened" and
ended done. Such a job now saves the checkpoint "applied": a retry plans again and applies only a plan that is
still the one confirmed. A job that succeeds keeps plan:<id>, so a crash before it is marked done still finds
the plan completed.
Sequences a folder was to carry when that folder stayed (dropped, its title edited, its names no longer given,
or a newer sidecar) were reported as "changed after the plan", and a newer-format carrier failed the job with
ReorganizeKept. They are now a separate outcome, CarriedKept (journaled), logged with the new
Archive.Log.ReorganizeCarriedKept (en+it) and not counted in the job's error, which follows the carrier's own
reason.
When a step's sidecar cannot be read or written after its folder moved, every sequence of the step is told
(sequenceChanged "reorganized") before the failure is thrown, since the retry that would tell them may never
come.
Tests: Core APlanKeepsItsTemplatesSoTheNamesOfAFirstPhotoNoLongerFirstAreTold; Data
AFolderOrTitleNamedAfterAPhotoNoLongerFirstIsNeverGiven, ARetryOfAJobThatKeptSequencesPlansAgain,
ASequenceAFolderWasToCarryIsToldItStayedWithIt, AnArchiveOpensWhenAnInterruptedRenameMeetsASidecarOfANewerFormat,
AResumedStepWhoseFolderMovedKeepsATitleEditedSinceAndTheNamesFromIt, and
AMovedFolderWhoseSidecarCannotBeReadThereHasItsIndexRowFollowAndIsTold, which breaks the sidecar with a
relative symbolic link instead of a read-only file, so it also runs on the Linux runner as root.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 130701afab224d47ea066eb7cc8debb16d1fb432)
Reorganize refused a case-only folder target whenever a folder of that exact
name was on disk. On a case-insensitive file system that folder can be the
sequence's own, when the disk spells it as the template does and the index
does not (renamed in Explorer, or an outer level a change of case left as it
was), so the plan gave a needless " (n)" folder. RenamePlanner.Kept now
refuses only when both exact names exist, the condition MassRenamer.TargetTaken
and MoveFolder already use.
ArchiveSettings.Problem held both templates to the template rules on every
UpdateSettingsAsync, so an archive.json saved before the rules made every
desktop Settings > Archive edit fail. A template the file already holds is now
only checked for being usable; a template the edit gives, and both templates
of a new archive, meet every rule. A broken rule throws TemplateRuleException
(an ArgumentException naming the field), and the desktop toast shows that
rule's sentence instead of "Something went wrong".
Also corrects comments that ignored RenameBlock.Unreadable (the whole
sequence stays as it is) and the ARCHITECTURE Naming row.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit ac7a0c36df83b6d43651caf0225c530466242c97)
Third fix round of owner review 2, phase 4a (Reorganize), cross-cutting items.
- Server render filing now runs under the sequence lease, so it can meet a busy
sequence or an offline archive. Both completions (client render uploads and
render-node results) used to answer 500 and leave the upload stuck in
Committing until a restart. They now answer 503 sequence_busy or
archive_offline, which clients retry. The upload goes back to receiving with
its part file and the node keeps its job (UploadService.ReceiveAgainAsync).
- Save both: when this PC's copy cannot be written (another index moved the
folder), the server's version is no longer applied, even if this index's scan
relocates the row before the apply would run. A copy that has to be dropped is
deleted from where the folder is now, as a best effort.
- Export rebase on a folder move (scan and Reorganize): the sequence's own
export follows the folder unless its file is still at the old path and not at
the new one. A file written into a re-created old folder therefore keeps a row
that finds it, so the file is never stranded.
- A render job refuses to start when its folder is not where the index has it,
which also stops it from re-creating the old folder. Renders fetched by sync
are now filed under the sequence lease into the current folder, or not at all
(new string Errors.Archive.FolderMoved, en and it).
- The proxy pass holds the thumbnail lease one batch at a time (a quarter of
the lease wait), then lets it go for longer than a waiter's poll and reads
the folder and sidecar again. Before, another process's Reorganize, sequence
deletion or pack compaction could wait out its lease wait and fail. Updated
the stale comments on that lease and ARCHITECTURE.md to match.
Tests cover each fix, and each new test fails with its fix reverted. Also
covered: proxy store and pass in a moved folder, RenderStore with the folder
gone, Take server with the folder moved, and an editor save with the folder
moved.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 811509d32a118ed50ad10d47d4b002e534da9d77)
The kept-plan stamp left out whether a planned sequence's photos are hashed.
A verify writes frames.sha256 (and only status and verified_at on the row)
without another frames version, so after verifying never-hashed photos the
same dry run kept answering "verify the sequence first" for up to five
minutes, and its confirmation queued a job certain to fail.
- SequenceRepository.GetStampAsync adds, for every planned sequence, how many
of its photos have their hash in the index (one grouped query over the
archive with all, the selected ids in batches of 500 otherwise).
- ReorganizePlanCache keeps a refusal (nested_target, not_found) as it keeps
a plan: for the same stamp and templates it is the same, and a long plan
that ends refused after a cut-off is no longer planned again on every retry.
Failures are still not kept.
- Planning is bounded: at most two plans are made at once, the others wait for
their turn; a plan still being made 15 minutes after it was asked, let go at
capacity, or when the server stops is cancelled, and whoever waits for it
gets 503 plan_dropped. A read that hangs keeps its turn until it returns but
no longer keeps its waiters.
- The Capacity summary now says what eviction does (the kept plan asked for
first, else the plan being made asked for first); the stamp, protocol and
endpoint docs say that a verify hashing photos is a change the plan reads.
- Tests: a scan's photos, verified, are planned again and renamed by the job;
the stamp follows hashes of planned photos only; refusals kept, failures
not; turns, eviction and deadline of plans being made, a hung read included.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 56582df45453fc555e525f19de7de1803204d12c)
A selected sequence nested in another selected sequence's moving folder moves
out first. When the templates no longer gave it its folder (its first photo
gone, or an earlier one filed), it stayed inside, and the outer step then found
it as a stranger: StaleRenamePlanException at every retry, the plan held forever.
- A moving folder now takes along the sequences of earlier steps that stayed
inside it (their index row still there): locked, moved and recorded with it,
keeping their title and file names. They are reported TitlesKept instead of
Dropped; a carried sequence whose carrier stayed is simply changed (or
TitlesKept when it was to change more than its folder); Newer stays Newer.
RefuseStaleAsync exempts exactly those, so a held plan either fits or is given up.
- MoveJobHandler: a journal not found on an offline archive tells nothing. A
failed job keeps its plan:<id> checkpoint instead of becoming 'applied', and a
retry while the archive is offline fails with "archive offline" instead of
logging ReorganizedEarlier and ending done.
- The Fit.Names warning now says what happens to the folder (moved already,
carried, or not moved to the planned one); stale ApplyAsync, RefuseStaleAsync,
FitAsync and job docs corrected.
Tests: the nested case (fresh run and held retry, three levels), the same through
a held job, a carrier named otherwise with a carried sequence, Fit.Names on a
resumed step whose folder moved (held and not), and an offline retry that keeps
its plan and completes it once the archive is back.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit c5ffc87f1a3900442920693763fd04d28cb43aee)
The web panel's archive settings save checked both request templates against
every template rule before the engine ran, so an archive.json saved before the
rules made every save fail, even of the name or proxy size. Only a template that
differs from the stored one is now held to the rules, as ArchiveService already
does, and a TemplateRuleException from the engine (archive.json changed since the
form was read) answers invalid_template with its rule instead of archive_policy.
Exports follow a moved folder correctly in two more cases. Image-sequence exports
are folders, so the rebase now tests Path.Exists instead of File.Exists. An
export left at the old path no longer pins a sequence's row when that path now
belongs to another sequence (its sidecar holds the old folder, or its render row
names the path); the row follows to the new path, so it never names another
sequence's file.
RenderStore throws FolderMovedException when the sequence is not in the folder
the index has. That is transient until this index's next scan, so client render
uploads and render-node results now answer 503 folder_moved, keep the part file
and the node's job, instead of failing them for good with a wrong reason.
Save both and Take server refused because the folder moved now say
Errors.Archive.FolderMoved (try again after the next scan) instead of the
"changed again, choose again" sentence, which repeated until a scan.
Doc wording: the ReorganizeDialogViewModel summary covers a sequence kept whole,
and RenamePlanner.Plan's existsExactly says the own folder is found under at most
one of the two names.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit d898798657197d48f4e19b7f776003eb2fc441b5)
An archive open lists the pending rename plans; one journal that was not valid JSON threw out of
ArchiveService.OpenAsync, so the archive (and the server, at boot) did not open until the file was
removed by hand. It is now logged and left in place; its own job fails with the reason instead of
planning again over a half-applied plan.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Round 4 let every row under the old folder follow when that folder holds another sequence
now. When the scan took the new holder first, its own row (already rebased into the old
folder) then followed the moving sequence too and named that sequence's file, leaving its
own export without a row; a second scan did not repair it. Only the moving sequence's own
rows now follow because the old folder is taken, and a row of the sequence holding the old
folder never follows: its export is in its own folder whatever the other one took along
under the same name. The rebase callback now gets the owner of each row.
Writers that file into the folder the index has for a sequence checked only that the folder
existed. After another index moved the sequence away and another one into that folder, Take
server wrote the server's settings into the other sequence's project.json, Save both wrote
this PC's copy into its .chronos, and a render sent for the sequence was filed among its
exports. SequenceFolders.Holds treats a folder whose sidecar names another sequence exactly
like a missing one, and every such writer asks it: settings sync and conflict resolution
(Errors.Archive.FolderMoved), Save both's copy and its clean-up, server render filing (503
folder_moved, the upload kept), export downloads, render jobs as they start, proxies sent and
proxy passes, the deep analysis checkpoint and the editor's project save. A thumbnail pass
refuses a sidecar of another sequence before it opens the pack.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit b406a4f6a9a7a3121e9e40289663fb62ee31948e)
The phase 4a docs were written before the last two fix rounds landed. They
now describe the code at 8c2b9f1b: a sequence left as it was inside a moving
folder is taken along instead of keeping that folder in place; a held plan on
an offline archive keeps its plan and fails as offline; render filing answers
503 folder_moved; a rebase never moves the rows of the sequence that took the
old folder (with its known limitation); every writer refuses a folder another
sequence holds (SequenceFolders.Holds). Three DECISIONS rows added, six
updated; five fix rounds in STATUS and the request.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 31d479c5f4dd0b7076b39331246815e95895a1fa)
Round 5 stopped clearing "behind" for rows of a third sequence (neither the one moving nor the
one now holding the old folder). Such a row, an export one sequence saved in another's exports
through the Export folder picker, then stayed at its old path whenever the sequence that moved
into the folder brought an export of the same name, and named that sequence's file (Send exports
would upload it). A file at the old path is never "behind" while the old folder holds another
sequence: it is that sequence's, so every row other than the holder's follows its file.
A resumed render job deleted the output its crashed attempt was writing at the absolute path in
the checkpoint. After another index moved the sequence away and another sequence into the folder
it left, and this index scanned, that path named the other sequence's export. The checkpoint now
keeps the sequence's folder when the output was chosen; a pending output there is rebased into the
folder the sequence is in now, one in the sequence's current exports or outside the archive (an
export folder chosen on a client) is discarded as before, and one anywhere else in the archive is
left alone (the entry renders under another name). Older checkpoints, without the folder, only
discard in the current exports.
Download originals put an original flagged missing back at the path read before the transfer,
with no lease and no check of the folder: after another index moved the sequence, it recreated
the folder it left or filed the photo among another sequence's originals. The restores now run
after the transfers under the sequence's lease, in the folder the index has then, which must hold
the sequence (SequenceFolders.Holds), at each frame's path read under that lease. Otherwise
nothing is restored, the copies stay staged for the next attempt and the job fails with
Errors.Archive.FolderMoved after its other work.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit ad46ef68180845de4b9b605a4ce2529a148c6f13)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Owner review 2, R7 (part 1): rename and move existing sequences with the archive's folder, file and title templates, on the web panel and the desktop. Request:
docs/requests/2026-10-26-owner-review-2.md.movejob.FrameNaming) for import, upload and Reorganize; photos adopted in place, unhashed or missing keep their names.plan_changedotherwise); leases against scans, uploads, deletes, restores and renders; exports move with their folder in the same transaction.POST /api/v1/archive/reorganize(dry run → plan with a bounded plan cache; apply → job),archive_reorganizedaudit entry, template rules (invalid_template).[0.1.0-rc.6], STATUS, ARCHITECTURE updated.Review: one adversarial review round (36 confirmed findings, 5 high) and six fix rounds, each fix checked by an independent checker.
Tests (Windows, local): Core 1291, Data 613 (+177 PostgreSQL skipped), Server 260 ×2, Tools 60, App 690 (five classes excluded on this PC as usual); format, i18n check (0 warnings), xaml-lint, package-guard clean.
🤖 Generated with Claude Code
Owner review 2, R3: the panel can add photos to an existing or a new sequence without the desktop app. upload.js is a dialog the library pages open (openUpload({ api, sequence, onDone })): file picker or drag and drop (folders are counted and left out: whole-folder import stays on the desktop), per-photo state, a total bar, Cancel that deletes the started uploads, and a leave-page guard while sending. Each photo is hashed in a same-origin module worker with an in-house incremental SHA-256 (8 MiB reads; crypto.subtle cannot hash in pieces), which runs the FIPS 180-4 known answers and a crypto.subtle cross-check before its first hash and refuses to hash on any mismatch; the server verifies the hash again. Chunks go through api.putBytes with the session's CSRF header, two files and two chunks at a time, retrying no answer, 429 and 503; quota, space and permission refusals stop the run with the server's message, and a photo deleted from the sequence shows as deleted before. server/info now lists the photo extensions the archive files, so the dialog offers and sends only those. The CSP already allows the worker (worker-src falls back to script-src 'self'); tests pin that, the module walk follows the worker, and a browser-shaped upload runs end to end through the cookie session. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit c64c60ab8bb41c102182e284177ac04a56bf1058)The phase 3 packages land together, so the panel's pieces must stay in step: - Admin files are served with Cache-Control: no-cache and their content ETag (If-None-Match lists, W/ tags and * honoured). With max-age=3600 a browser that loaded the panel before an upgrade could run new modules next to cached old ones for up to an hour; now it revalidates each file and only what the upgrade changed is sent again. - The Library's Upload and a sequence's Add photos open upload.js, which now ships with the panel: the test requires the module (no 404), the dynamic import and the openUpload({ api, sequence, onDone }) calls. - Bulk jobs over more than 1000 sequences queue one job per 1000; the toast now says how many were queued, also when a later chunk failed. - The live refresh re-reads every loaded row, a thousand per request, instead of dropping rows beyond the first 1000 back to Load more. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>Review fixes for owner review 2, phase 3 (R6 Library on the web panel): - Trash: the worker can end an emptying before the browser has read the POST's 202, so its jobState arrived while the page did not know the job yet; Empty then stayed disabled ("being emptied") and no result showed. The page now keeps the last state of the jobs that ended and looks its job up there before following it. Any ended job also reloads the list (an emptying from another tab or the desktop sends no sequenceChanged), and a Restore answered 404 shows the trash as it is now. - Sequence: thumbnail, proxy, verify and analysis jobs send no sequenceChanged, so tiles and the cover stayed placeholders and the status chips stale. An ended job now schedules one refresh (not pushed back by the next): the sequence is read again and failed images are asked for again under a retry address (shared retryImages). - Library list: Esc, Ctrl+A or unticking every card left the "Select all" snapshot in place, hiding Select all and stopping the live refresh from pruning the selection. It is dropped once no selected sequence lies beyond the loaded rows; Clear filters clears the selection too. - The sequences' delete dialog lists at most 500 names (blocked ones first, with their reasons), like the photos' dialog (shared LISTED). - Admin.Trash.RestoreSequence.Tip promised a SHA-256 check that a sequence restore never makes (it moves the folder back); it now says so and names Verify (en, it; no other culture had the key). - The upload test's name and comments say what it checks: upload.js is only imported dynamically, not loaded on click. Tests pin each change in SystemEndpointTests; the pages were also driven in a browser against a fake API, where the pre-fix modules fail and the fixed ones pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 78f66082fd85543d619375574c82cc63a233b7a8)The upload dialog's completion helper called `api`, which only exists inside openUpload, so every web upload failed with a ReferenceError at its last step. complete() now takes the dialog's api. A new test lexes every admin module and fails when a top-level function uses api without taking it; it flags the old upload.js. During a run Esc is now stopped on the document in the capture phase. The old listener sat on the dialog, so with the focus on the body (Start disables itself, a click on the dialog's text) a second Esc closed the dialog and threw the uploads away. The listener is added when a run starts and removed when it ends or the dialog closes. A sequence page refreshes after any ended job, because jobState names no sequence. That refresh now redraws the header only when the sequence changed, and the renders only when their list did. Stars, tags and renders are redrawn through redraw(), so the keyboard focus stays put. restoreFocus finds an unnamed control by its place, not as the first unnamed one. Failed thumbnails are retried with a doubling wait and at most 8 tries, counted again once the sequence changes. The trash page reads the emptying it follows from /api/v1/jobs/{id} on every load and after the event socket reconnects (api.events now emits "reconnected"), so Empty no longer stays disabled when the job's end was lost. A Restore in flight stays disabled across redraws. The Library list counts cancelled jobs as ended (shared JOB_ENDED). Comments are corrected in shared.js and library.js. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 641b9cd96b95d523990d1414c2bdead4138c5f4d)Owner review 2, R7 asks to rename and move sequences after import on the desktop too. The desktop now uses the engine's Reorganize, the same plan and job as the web panel. - One Reorganize… dialog replaces Rename… and Move… in the Archive manager and Move… in the Library. It has three templates: folders, file names and titles. Each one has a switch and is checked as it is typed. Folders and file names start on, filled from the archive's settings; titles start off as {title}. Renaming only titles is the Titles switch alone. - The dry run stays in the dialog and follows the typing. Each sequence shows its folder, title and first file names before and after. Sequences carried along with a folder are marked, and photos that keep their names are listed with the reason. A summary counts the sequences that change, the files renamed and the names kept. - Apply no longer changes the archive from the dialog. It queues the engine's move job with exactly the plan shown (its fingerprint), so the work can be paused, resumed after a restart and followed in Jobs. The job refuses the plan if the archive changed after the dry run. - The Library's Reorganize… works on the selected sequences of one archive. The Archive screen reads the archive again when a move job ends. - After Settings › Archive saves a new folder or file template to an archive that holds sequences, a toast offers Reorganize… for every sequence. Its templates are the ones changed since; a second change made while the toast is up adds to that toast instead of opening another. - Strings in en and it. The keys of the old Rename and Move were removed and pruned from every translation, so the 36 other languages show the new keys as untranslated instead of keeping "Move". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 7bbf451f737a71b768dcd70a77b998daaef851f3)Reorganize with the archive's own templates planned renames and moves for photos just filed, and some templates could strip extensions, hide sequences from scans or stall a dry run. Owner review 2, phase 4a findings. - Filing and Reorganize share one context: uploads and imports name every photo with the sequence's camera and lens (its first photo's, or the creator's hint), an upload's folder from its first frame in the new sequence, and a missing capture time from the sequence start instead of the current time. The planner expands folder and title templates from the first frame in the sidecar ({name}, {ext}, {iso}...), never today's date. - Titles expand as text (ExpandText): "Paris: night" stays as typed. - A sequence whose sidecar cannot be read (torn, another sequence's) keeps its folder, title and names, listed with why, and so does every folder around it; the dry run reads every sidecar, nested ones included. - Kept never gives one folder to two sequences of a plan whatever the case, and a case-only move onto another folder is refused instead of taken as done. - Shared template rules (TemplateRules) for the server's Reorganize and archive settings and the desktop's fields: a file template must keep the photo's extension ("{n}{ext}" refused) and tell a session's photos apart; a folder template may not write a level scans skip (a leading dot, originals, proxies, exports). Levels a title gives are escaped with "_". - {ext} comes from the file, or from the original name when the file lost a photo's extension, so a Reorganize can put it back. - Unique names cost linear time (UniqueNames) with the same names as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 6c734777e01476881a3f34b3188571cc3f7150ab)A Reorganize with a file template failed its job at the step of a sequence a camera was still uploading into, and its retry gave the rest up. Photos changed since the plan now never refuse a step: that sequence keeps its file names (FilesKept), its folder and title change as planned, the other steps go on and the job ends with ReorganizeKept. The fingerprint, the job's confirmation and the check under the leases pin file renames by their digest instead of the frames version, so photos filed under the names the plan gives them no longer make a dry run or a queued job stale. - A step whose folder or files a template names after {title} checks the title as a retitle does (RenameStep.NamedByTitle): no name comes from a title edited since the plan. - Recovery sends a photo that already took its new name back together with a companion whose new name was taken, so the two never end up apart. - ArchiveService.OpenAsync logs a NewerFormatException from resuming a plan and keeps its journal, so a server still boots. - Once a step's folder moved, every index row of the step follows it even when a sidecar cannot be read or written; the step then fails for a retry. - Job log lines and errors give the real reason for files kept busy (in use or a new name taken) and for a sidecar of a newer format (new Newer outcome; strings en and it). - A plan an archive open completes tells sequenceChanged; the docs that promised more than that are corrected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit f8554b8af0828ab9b0ff128e694abacdd53e6fd7)Second fix round of owner review 2, phase 4a (planner findings). - A sequence keeps a folder that differs from its own in case only while no other folder holds that exact name (RenamePlanner.ExistsExactly, every level compared exactly). On a case-sensitive file system a stray "Trip (2)" beside the sequence at "trip (2)" no longer gives a case-only step that MoveFolder refuses at every archive open: the plan gives "Trip", and a plan whose target appeared since is refused under the step's leases before anything moves (or dropped when it resumes). A change of case in an outer level no longer looks like two folders on Windows. - A file name longer than 200 characters is shortened before the ".{ext}" the template ends with, never through it, so a long title never strips the photo's extension. - The archive engine's own settings check applies the template rules the server and the desktop apply (a folder scans skip, a lost extension, names that repeat), so archive.json can no longer take such a template. - The server's invalid_template answer names the rule after the field ("fileTemplate:extension") with the desktop's sentence as its message; both admin panels show it on the field. - FrameNaming keeps only the naming overloads production uses. - Comments about Unreadable say the whole sequence stays as it is. - Tests pin filing against Reorganize: an upload without a capture time, a card's second session with {session}, a duplicate skipped mid-session, and a whole folder of two cameras named with the first one's camera. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 50fe59aec1e180daa1733bcb951892a79dceba6c)