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)
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>
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 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, 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)
- 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 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)
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)
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)
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>
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)
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: 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, 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)
- :latest follows the highest stable release, or the highest pre-release while none is stable (Chronos.Tools release-channels); bad tags are refused before anything is built.
- Unraid: CHRONOS_SPACE_PATH and the template's Array view show the array's free space; the write volume (cache) is shown apart; completions check the archive volume (507).
- Settings is a gear, docked at the foot of the admin sidebar; About is the last part of Settings on the desktop and the panel.
- Import > Folder > Whole folder: one sequence per format (desktop only).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
Gitea writes a release's html_url and browser_download_url with its ROOT_URL,
which on the owner's server is the plain-http LAN address
http://192.168.30.23:3000. The update check accepts only https links, so it
ignored v0.1.0-rc.1 entirely. The page and download links now come from
ChronosReleasesUrl, the address the build names for its users; only the
tags, file names and sizes are read from Gitea's answer.
The lease renewal test's timer periods follow TestTiming too: on the shared
CI host a 100 ms renewal timer came 700 ms late once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
The owner renamed the product and moved the repository to the self-hosted
Gitea (https://gitea.encke-hake.ts.net/BalboSoft/Chronos) for more control,
and asked for Actions and a first automatic release with the server package
and the Windows exe (docs/requests/2026-10-23-chronos-gitea.md).
- Chronos everywhere: a byte-exact rename of contents and paths, then a
per-language review of the forms the old name's ending had dictated.
- Gitea instead of GitHub: the update check, licence, issue and support
links read ChronosReleasesUrl; the update check takes the highest stable
version, offers a pre-release build its final release and reports a
repository it cannot see as a failed check. EULA, security policy and
Gitea issue forms live at the repository root.
- Gitea Actions for the Linux act_runner (.gitea/workflows): CI, release,
nightly image and performance gates in the .NET SDK container with git
checkout and the system SQLite. The release cross-compiles the Windows
programs, checks their icon, version and DPI manifest, packs installers
and zips, publishes the Gitea release and pushes the server image
(REGISTRY_TOKEN). Windows-only tests run in an opt-in job on a Windows
runner (WINDOWS_RUNNER).
- New Chronos.Tools commands: zip, gitea-release, postgres-ci (replaces the
docker-exec script, which Gitea's service containers do not allow; the
throw-away server runs without durability) and pe-check.
- Timed tests take their budget from TestTiming (CHRONOS_TEST_TIME_FACTOR,
3 on the shared runner; the weekly performance gates keep theirs).
BREAKING CHANGE: programs, settings, data folders, file types, environment
variables and the Docker image use the new name; nothing is migrated from
Titano, which never had a release.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
- Implement tests for picker behavior, including loading sequences, searching, and handling empty libraries.
- Validate sequence opening via Enter key and double-click actions.
- Ensure proper handling of unsaved edits and sequence deletion scenarios.
- Verify accessibility features for picker rows across different languages.
- Introduce a dialog counting mechanism to manage unsaved edit confirmations.
Owner review 1, phase 3a (docs/requests/2026-10-15-owner-review-1.md, R1).
The desktop rail is 200 px wide, so the section names fit in every
language, and collapses to 48 px of icons with its ≡ button or Ctrl+B.
Collapsed, each icon's tooltip names its section before saying what it is
for, while screen readers keep the name and the description. The choice is
written to the settings file the moment it changes (nothing else restarts)
and survives Settings › Reset all and Import; Ctrl+B waits behind the
first-run dialog like Ctrl+1…6, and a held key toggles once.
The admin panel's sidebar is 256 px and collapses to icons the same way,
with its own ≡ button or Ctrl+B (on the physical key where the layout's B
types no Latin letter, so Cyrillic, Greek, Hebrew and Arabic layouts work).
The choice is kept in the browser, for the page when the browser refuses
storage, and the tables fit their columns again after each toggle. At
900 px and below it stays the top bar and Ctrl+B stays the browser's.
The wider rail leaves 49-72 px less for every screen at the 1200 px
minimum. Six adversarial review rounds found what that cut, and in every
shipped language no action is cut off now: the Jobs columns share their
width (Target and Progress give way first, Kind/Where/State capped on wide
windows), the editor's preview tools take a second line, a server job's
Cancel has its own header column, the Archive tree keeps a year's label,
the Import rows and result, the certificates and cache rows and the frame
table fit. Headers, titles and cells that may be shortened end in an
ellipsis and show their text in their tooltip; state tooltips start with
the state, and their explanations were reworded not to repeat it (a queued
job "waits for its turn", jobs running one at a time). The crop-result
tool sits beside Crop mask, disabled with its reason while the mask is
off. Tests check these rows in all 38 languages at 1200 px; the App test
program now shuts WPF down in order, so its exit no longer crashes after
every test passed.
Phase 3 lands as two commits: R7 (the Edit section) edits the same shell
files and follows. Also updates BRIEF (12.1, 14.8, 24), DECISIONS,
CHANGELOG, STATUS, the request file, DESIGN and the mockups; every new or
reworded string is in all 38 languages.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 1, phase 2 (docs/requests/2026-10-15-owner-review-1.md, R2).
Jobs now run one at a time on the desktop and on the server. Parallelism
(Settings > Rendering, TITANO_PARALLELISM) is how many photos the running
job processes at once: thumbnail and proxy passes draw that many photos
together and still write the pack and checkpoints in frame order, decode
tiers are probed that many at a time, the deep analysis measures that many
frames and a render decodes that many ahead. Wherever originals are
developed whole (TIFF, PNG, RAW without a usable preview), fewer run at
once within the memory budget, which the running job now has whole; the
server's frame window is sized to the host instead of 1 GiB.
A new job waits its turn and pausing the running job starts the next one.
An optional priority queue gives each job kind a level (renders, imports
and downloads high, verifies and proxies low by default): a queued job of
a higher level pauses the running one without asking, and that job goes
back to the queue with its checkpoint and resumes by itself afterwards.
Jobs of the same level, and a job's own follow-ups, never interrupt it.
The Jobs screen and the admin panel show the parallelism and the queue;
Settings > Rendering and the admin panel's Settings set them, at once.
TITANO_WORKERS and the Workers key of server.json still set the
parallelism (1 to 64, with a warning at start for the variable).
Titano.Tools gains i18n prune, which removed the renamed keys from the 36
machine-translated languages; the new strings are translated in all 38.
Found while testing: uploads and imports failed when a pass read the
sidecar while they wrote it (atomic writes now retry the rename while a
reader holds the file, and never for a read-only one), and taking a lease
just released while another process read it failed on Windows (the create
now waits for the reader). Five adversarial review rounds checked the
phase before this commit.
Also updates BRIEF (12.8, 14.6, 14.8, 14.9, 24), DECISIONS, CHANGELOG,
ARCHITECTURE, STATUS, the request file and the compose/Unraid templates.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 1, phase 1 (docs/requests/2026-10-15-owner-review-1.md).
Thumbnail and proxy jobs over several sequences counted sequences while
they checkpointed inside one: the rate decayed until the time left
overflowed TimeSpan, the job failed while publishing progress and again
while saving it, and stayed Running. The throughput is now seeded by the
first window with progress, the time left is bounded (JobEta), saving
progress never throws, image passes count frames, and job speeds use the
right unit (bytes for verify and import).
The debugger stops in WicDecoderProvider.cs when presets changed were
cancelled preview decodes leaving synchronous thread-pool delegates; the
editor's sources, LatestRunner and the render node's proxy task now keep
them in their own tasks, and a cancellation is never an unreadable frame.
GoPro DNGs converted by Adobe software were classified GPR and read only
through their 8-bit preview, and Windows' preview-only DNG decoder was
reported as a native decode. A DNG is GPR only when its raw image is
VC-5, WIC decodes RAW only through the Raw Image Extension and never DNG,
analyses and previews take an adequate embedded preview by choice while
renders develop natively, and frames already indexed as GPR are
reclassified by the next light analysis.
Also records the owner's request (docs/requests), the BRIEF amendments
(§8.1, §8.2, new §24), DECISIONS, CHANGELOG, STATUS and ARCHITECTURE.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
F5 in VS Code now starts Titano, the Uploader and the server under the C#
extension's debugger, as well as the --capture runs, Titano.Tools and the test
programs. Each configuration builds in Debug first and starts the program's
.exe rather than its .dll, because the programs read Environment.ProcessPath
(Setup's payload, the Run keys and tray icons). The server's session keeps its
data and archive in out/debug/server instead of %ProgramData% and
C:\TitanoArchive.
The build tasks use no reused MSBuild nodes, whose cached drive-letter case
made every F5 build restore and C# Dev Kit reload, and keep MSB3026 (a copy
that succeeds on a retry) a warning so a file held for a moment no longer
stops F5.
Design-time builds skip the icon generation, which on a fresh clone ran a
Titano.Tools.dll that did not exist yet (MSB3073 in VS Code), and log WPF's
MC1000 about projects not built yet as a message.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Commit 90bf598 rewrote docs/DECISIONS.md and docs/CHANGELOG.md with only the
fourth pass's entries. Both files are back as they were at 8e8f802, with those
entries appended, and the proxy-cache row the new one replaces is marked
superseded.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
The Windows README removed only the prompt's own account from a data folder
created by an unelevated console run, which missed a console run by a
standard user. It now removes the account the service's refusal names.
The DECISIONS rows on OneDrive sync roots and on the service's start-up
log say which later rows partly supersede them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
The Windows README told an administrator to run icacls /reset /T on a data
folder created by an unelevated console run, which let every local user read
the database, the TLS key and the temporary admin password until the next
successful start. It now takes ownership with takeown /A /R and removes only
the console account's entries with icacls /remove:g, so nobody else gains
access at any step.
The 2026-10-12 Start with Windows decision said the uninstaller leaves the
StartupApproved value; setup removes it with the entry, as the later Task
Manager state row says.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
- ArchiveImages.IsProxyOf compares capture times to the microsecond the index
keeps (sidecars and Exif keep 100 ns ticks), and for frames read through
proxies also applies the policy's size rule, so the proxy pass, uploads,
thumbnails, renders, analyses, tiers, manifests and downloads agree.
- Proxy headers are cached per file while length and write time are unchanged
(and the file has settled), so manifests cost a stat per proxy.
- FrameTiers.RecordAsync checks proxy presence when it writes the sidecar and
returns the sequence's frames as they are, so a deep analysis or render that
ran while proxies arrived no longer flags the frames preview-only again, and
the analysis advises from the current flags.
- Server manifests ignore ProxiesBuilt for frames the server cannot decode, so
frames added since the last proxy pass are asked for their proxies.
- GET /sequences/{id}/analysis/report answers 404 for a report that found
frames unreadable before their proxies arrived (DeepReports.ReadCurrentAsync).
- The deep checkpoint key marks only frames read from proxies, so checkpoints
written by earlier versions still resume.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
Settings synced between a PC and its server sequence were stored as they
came, in the other copy's frame order. When the inserted photos arrived
later (a download, an upload), the index moved those already-correct
positions a second time, so exclusions, the hero and camera keyframes
landed on other photos (V-21, CD-2).
- Settings are translated by photo (SHA-256, else size and capture time)
to the frames of the copy they go to: the server's before they are
compared or applied here, this PC's to the server's frames as its
manifest lists them before a push (SyncPositions).
- A position on a photo the receiving copy lacks waits in project.json as
a pending frame and takes its place when the photo arrives, on an
insertion or an append in step with the index; the Library's hero
frame follows. A hero chosen meanwhile wins, and advice does not fill
a hero while one waits. Old projects without the member are unchanged.
- Pushes send expectedFramesVersion; PATCH /api/v1/sequences/{id} answers
409 frames_conflict when the frames changed since, and the next
comparison translates again.
- A pulled payload equal to the local copy is settled without the
archive: an offline or read-only archive no longer fails the
comparison (V-10).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
The releases README told the operator to make Administrators the owner of a
data folder created by an unelevated console run. The server checks the owner
of every entry inside, and the TLS key and password file keep a protected DACL
that grants the console user, so it now gives takeown /A /R and icacls /reset
/T, and says that deleting the folder also deletes the SQLite database.
DECISIONS: the trusted-proxies row no longer endorses a Docker subnet, and the
sign-in entry cleanup row says an upgrade that renames a program moves its
entry rather than removing it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
BRIEF §6.2 forbids a SQLite index in a synchronised folder. AppEnvironment.Detect now resolves the data folder
through Core.Windows' AppPaths and OneDriveFolders: a portable copy whose .\data would lie under a OneDrive sync
root (a OneDrive folder, or a Desktop or Documents folder backed up into one) keeps its data in
%LOCALAPPDATA%\Titano and stays portable otherwise; AppEnvironment.SyncedFolder names the OneDrive folder so the
user can be told. The pure choice lives in Core/IO/DataLocation (tested on Linux); reading the OneDrive accounts
key no longer fails start-up when it cannot be read.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
STATUS no longer claims every --capture screen is pixel-diffed: with no
baseline committed the step compares nothing. Next steps now starts
with accepting the first baselines from ci-screenshots. DECISIONS marks
the folder-scoped Run cleanup row as superseded by the log-based rule
and drops the branch-merge notes from that rule's row.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
RemoveLeftovers deleted every Titano or Titano Uploader Run value that
started a file the upgrade removed, including a client or Uploader the
new version only renamed or moved. The new program then found no entry
to follow and Start with Windows was silently off. Setup now points such
an entry at the program of the same component in the new payload (its
shortcut target), keeping the options and the value name, and removes
it only when the component is no longer installed. Uninstall still
removes the entries of the programs its log lists.
StartupCommand.StartsFrom, left over from the superseded folder-scoped
cleanup, is gone; StartupCommand.Retarget replaces it and its misleading
test now covers how setup moves an entry.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
A service has no console, and a refused data folder or server.json throws
before the server's log file exists, so the SCM recorded only error 1064
and the entry to check was lost. ServiceMain and the stop path now also
write the reason to the Application event log (source TitanoServer,
advapi32 ReportEventW, no message file registered). The Windows README
says where to look and that a data folder created by an unelevated
console run must be deleted or given to Administrators first.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
Every workstream's decisions (dated 2026-10-12) and changelog entries, the merge choices (no decode tier from a
proxy, Reset all and the sign-in entry, card-only post-actions, restore summaries as labels), the new playback and
installer checks in the phase rows, and how to try the new Settings pages, project files and notifications.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC