Commit Graph
600 Commits
Author SHA1 Message Date
Alby96 3f0e6357b1 fix(server): archive.json on its own timer, a live Scheduled tab in one time zone, schedule audit in words
- 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)
2026-10-27 09:57:23 +01:00
Alby96 e384564784 fix: logging never fails a job, one backup retention, first copy after the upgrade
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)
2026-10-27 09:56:47 +01:00
Alby96 422f33d5f3 fix(server): show the audit clean-up's real age limit and lock it before the first pass
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)
2026-10-27 09:56:46 +01:00
Alby96 ac121acf7c fix(logs): apply log settings from the first line and name the locking variable
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)
2026-10-27 09:56:46 +01:00
Alby96andClaude Opus 5.5 8d66be709c fix: one audit retention, scans at start, live deep analysis and a 6-hour upload sweep
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>
2026-10-27 02:51:04 +01:00
Alby96 bc786c12c4 feat(app): Jobs › Scheduled and the desktop scheduler
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)
2026-10-27 02:26:07 +01:00
Alby96 75daab7275 feat(server): scheduled jobs on the server and a Scheduled tab in the admin panel
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)
2026-10-27 02:25:01 +01:00
Alby96 e5508e7e69 feat(data): scheduler engine, schedules table and housekeeping jobs
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)
2026-10-27 02:08:11 +01:00
Alby96 0e84392f4f feat(logs): log level, retention, size limits and rotation on server and desktop
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)
2026-10-27 02:08:09 +01:00
Alby96andClaude Opus 5.5 1f089888e8 feat: owner review 2 phase 1: :latest, Unraid array space, Settings with About, whole-folder import (#9)
CI / Build and test (push) Successful in 5m11s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 6s
Release / Build, test and publish (push) Successful in 8m57s
CI / PostgreSQL 16 integration (push) Successful in 3m10s
CI / PostgreSQL 17 integration (push) Successful in 3m30s
CI / Docker image (push) Successful in 49s
Release / Server image (push) Successful in 1m4s
- :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>
v0.1.0-rc.3
2026-10-27 01:09:59 +01:00
Alby96andClaude Opus 5.5 5acdf146c7 docs: changelog and status for 0.1.0-rc.2 (#8)
CI / Build and test (push) Successful in 6m36s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 6s
CI / PostgreSQL 16 integration (push) Successful in 4m51s
CI / PostgreSQL 17 integration (push) Successful in 4m52s
CI / Docker image (push) Successful in 56s
Release / Build, test and publish (push) Successful in 11m38s
Release / Server image (push) Successful in 3m13s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
v0.1.0-rc.2
2026-10-23 14:41:07 +02:00
Alby96andClaude Opus 5.5 f80fc148bf fix(app): build update links from the releases repository address (#7)
CI / Build and test (push) Canceled after 2m45s
CI / PostgreSQL 16 integration (push) Canceled after 0s
CI / PostgreSQL 17 integration (push) Canceled after 0s
CI / Docker image (push) Canceled after 0s
CI / YAML check (push) Canceled after 0s
CI / Windows tests and installer (push) Canceled after 0s
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>
2026-10-23 14:39:10 +02:00
Alby96andClaude Opus 5.5 f2b58522b9 refactor!: rename Titano to Chronos and move CI and releases to Gitea (#6)
CI / Build and test (push) Successful in 8m14s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 7s
Release / Build, test and publish (push) Successful in 13m19s
CI / PostgreSQL 16 integration (push) Successful in 4m49s
CI / PostgreSQL 17 integration (push) Successful in 5m28s
CI / Docker image (push) Successful in 53s
Release / Server image (push) Failing after 10s
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>
v0.1.0-rc.1
2026-10-23 12:45:18 +02:00
Alby96 c99842cc86 Merge pull request #5 from Alby96/claude/owner-review-1
Claude/owner review 1
2026-10-19 12:11:57 +02:00
Alby96 5aeb6aa787 Add comprehensive tests for EditSection functionality in the Windows application
- 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.
2026-10-19 12:10:42 +02:00
Alby96andClaude Opus 5.5 4ea44bb917 feat: wider rail and admin sidebar that collapse to icons
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>
2026-10-16 21:50:48 +02:00
Alby96andClaude Opus 5.5 43b6871cdc feat: jobs run one at a time, parallelism per photo and a priority queue
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>
2026-10-16 14:56:24 +02:00
Alby96andClaude Opus 5.5 34d03051f5 fix: stalled jobs, editor cancellation stops and GoPro DNG decoding
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>
2026-10-16 10:20:26 +02:00
Alby96andClaude Opus 5.5 19265b36c2 build: debug the Windows programs from VS Code
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>
2026-10-15 14:53:12 +02:00
Alby96 48923d0776 Merge pull request #4 from Alby96/claude/keen-knuth-uhxv8w
fix: full verification against the brief — 137 confirmed findings fixed over six passes
2026-10-13 12:10:03 +02:00
Claude 9ce94244d0 docs: STATUS verification sentence reads as one list
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-13 00:31:49 +00:00
Claude efbab10ec5 docs: STATUS names the last verification check
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-13 00:31:41 +00:00
Claude 6186ab1a02 docs: record the last two verification fixes
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-13 00:31:30 +00:00
Claude 0085765a12 fix(archive,analysis): an unreadable photo changes nothing; a report stale by proxies never replaces a current one
The orphans fix and scans treated a folder whose only new photo could not be
read yet (held open, no permission, an offline placeholder) as changed: the
sidecar was rewritten, the covering flags cleared and analyses queued again at
every click. SequenceAdopter.Reconcile now returns null when it indexed nothing
and changed no flag, as its contract says.

A deep pass counted as current by frames version alone, so a pass whose verdict
a proxy made stale overwrote the report a later pass made from the proxies,
then dropped the deep status. It now counts as current only when its report
describes the frames as they are, and otherwise replaces only a saved report
that does not describe them either.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-13 00:31:30 +00:00
Claude 00823b0328 docs: record the fifth verification pass in DECISIONS, CHANGELOG and STATUS
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-13 00:02:02 +00:00
Claude bd9f4a2869 merge: fifth-pass data-layer fixes (Z-1..Z-4)
Merge branch fix5/data-edges into the verification branch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 23:59:17 +00:00
Claude b76b745d7d fix(archive): the orphans fix queues the deep analysis a scan would
A desktop scan queues a background deep analysis of the sequences whose
frames it changed when Settings > Analysis > After a scan is on; photos the
Archive screen's orphans fix indexed got only the light analysis, which then
dropped the deep status. ArchiveService.ReconcileAsync takes that setting
and queues the deep analysis too, at background priority. A follow-up is
left out when a queued job of its kind already covers the sequence, whatever
else that job targets, as the scan's follow-ups check.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 23:58:19 +00:00
Claude 7abab486e4 fix(analysis): a deep pass that leaves the saved report records that report
A deep pass overtaken by a frames change that keeps the frame count, with a
light analysis queued, leaves an analysis.json of that count in place rather
than save its own. It then still recorded its own report: the deep status,
summary, warning count and Auto values described a report that is not on
disk, and the queued light analysis kept that summary until the next deep
pass. SaveReport now says whether it saved; when it did not, the pass reads
the saved report as a light analysis would and records that one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 23:58:19 +00:00
Claude 92f4403c76 fix(archive): an equal frames version over other frames counts as a frames change
Each index of a shared archive bumps a sidecar put back behind its own row
to one version past that row, which can be the version another index holds
for other frames (a desktop rebuilding a damaged sidecar while the server is
one upload ahead). That index then took the sidecar's frames as unchanged:
it kept the project's positions and what covered the frames, and clients and
editors holding that version saw nothing. When the versions match, a scan
now also compares the row's frame ids and order with the sidecar's; other
frames are read again under the lease and written one version past the row.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 23:29:55 +00:00
Claude 06a1db7ae1 fix(archive): the orphans fix clears what covered the frames and queues their analysis
The Archive screen's orphans fix indexed photos copied in by hand but left
AnalyzedLight, ThumbsBuilt and ProxiesBuilt set and recorded the folder's
stamps, so no scan came back to it and the light analysis was never redone:
Auto values, warnings and preview-only tiers stayed those of the old frames.
It now clears the three flags in the sidecar and the row as a scan's
reconcile does, and queues the light analysis on the host's engine (on a
server, the thumbnails and proxies too).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 23:29:46 +00:00
Claude 52515897a4 fix(analysis): save a deep report under the sequence lock, never over a more current one
A deep pass saved analysis.json as soon as it finished, before it checked
that its frames were still the sequence's. A pass overtaken by an upload, or
by another Titano sharing the archive, replaced the report a later pass had
made of the frames as they are: the report endpoint answered 404 and the
next light analysis dropped that pass's deep status. The report now waits in
memory and is saved under the sequence lock, when its frames are current or
the saved report describes the frames as they are no better; the checkpoint
is deleted only then.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 23:28:45 +00:00
Claude 2cdc44abe4 fix(data): write a sequence's tags in one order on PostgreSQL
Each tag upsert locks its row until commit, and tags were written in the
order the caller listed them. A PATCH listing them in another order than
an upload, a scan or another edit of a sequence sharing two of them could
lock the rows in opposite orders, and PostgreSQL aborted one writer with a
deadlock that nothing retries. Tags are now written in the order of their
keys, and a set the sequence already carries is not written again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 23:28:40 +00:00
Claude e6129d2a11 docs: restore the decision log and changelog the fourth-pass update truncated
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
2026-10-12 23:01:37 +00:00
Claude 6e4636943f feat(i18n): the strings of the fourth verification pass in all 36 machine-translated languages
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 22:19:25 +00:00
Claude 90bf59871d docs: record the fourth verification pass in DECISIONS, CHANGELOG and STATUS
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 22:13:24 +00:00
Claude 8e8f802f93 merge: fourth-pass analysis and sync fixes (Y-1, Y-2, Y-7)
Merge branch fix4/analysis-sync into the verification branch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 22:09:58 +00:00
Claude 2466e9f7c6 merge: fourth-pass archive writer fixes (Y-3, Y-4, Y-5, Y-6)
Merge branch fix4/archive-writers into the verification branch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 22:09:04 +00:00
Claude 8927ac97e2 fix(sync): record scan stamps after a pulled title only when the index held the folder
ApplyLocallyAsync recorded the folder's scan stamps unconditionally after
writing the server's title, tags, rating or notes into the sidecar. Photos
another process (a desktop sharing this archive) had listed there since
this index last synced the folder then stayed out of the index until the
folder changed again, and the row's frames version stayed behind the
sidecar's, so analyses here recorded nothing for the sequence meanwhile.

It now asks ArchiveIndexer.InStepAsync before its sidecar write, as the
other partial writers do, and records the stamps only when that held.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 22:08:36 +00:00
Claude 79125b547a fix(analysis): record nothing over photos another Titano changed in a shared sidecar
An analysis compared only this host's index row with the frames version it
read at its start. On a desktop sharing a server's archive, the server's
upload bumps only the shared sidecar until the desktop's next scan, and a
desktop scan clears nothing. A desktop pass that recorded in that window
wrote Auto values and statuses for the old frame count over the server's
analysis in the shared project.json and sidecar, and nothing analysed the
photos again.

Under the sequence lock the analyser now reads the sidecar first. When its
frames version is not the row's, the photos changed in another process and
this index does not hold them yet: the pass records nothing, logs
Advisor.Log.FramesChangedElsewhere and queues nothing, since a light
analysis here would read the same index. The process that changed them
analyses them, and this host's next scan indexes them (a server's scan
then queues their analysis). A moved row still queues a light analysis
unless one is queued, in which case the pass records as before.

Tests cover the shared-archive case with a second index and engine, and
the queued-light escape on a one-worker engine.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 22:08:20 +00:00
Claude 343ef76798 fix(data): light statistics lock their sequences before their frames
FrameRepository.UpdateLightStatsAsync updated every frame of a sequence
in batches without locking the sequence row. On PostgreSQL a scan's or
rebuild's sync holds the row and rewrites every frame in its own order,
so a deep analysis writing its statistics at the same time could hold
some frames while waiting for others the sync held, and PostgreSQL
aborted one of the two jobs with a deadlock.

On PostgreSQL the method now locks the rows of its frames' sequences
first, in the same transaction, like every other writer of a sequence's
frames. SQLite's write lock already serialises writers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 22:08:05 +00:00
Claude bf93434bec fix(archive): an upload leaves photos copied in by hand to the next scan
An upload batch that found the folder out of step resynced the sequence
from its sidecar and recorded the photo directory's current stamp. When
the photo directory had changed since the last scan (a photo copied into
originals/ by hand or by another process), that stamp hid the change from
every incremental scan, so only a full scan or the orphans check indexed
the photo.

The batch now asks ArchiveIndexer.PhotosChangedAsync under the lease
before it files its photos. When the photo directory had changed, the
resync records the photo stamp the index held before (none when none was
recorded), so the next incremental scan still reconciles the folder.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 22:07:58 +00:00
Claude 098e5b27f6 fix(sync): keep a proxy cache stale while any frame lacks its proxy
A proxy download marked the cache filled whenever the server's sequence had
ProxiesBuilt, even when frames added since the server's last proxy pass got
a thumbnail or nothing (the flag offers their proxies, the endpoints answer
404 until the pass draws them), and frames without any cached file were not
counted at all. The agent never compared such a cache again, so the editor
kept thumbnails or blank frames until the frames changed.

The cache now counts as filled only when every frame, missing or damaged
ones aside, is cached as a proxy. On a server with ProxiesBuilt, a download
that left stand-ins is queued again once the server's update time moves, so
a frame the server cannot serve yet is not fetched at every refresh.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 21:37:07 +00:00
Claude d064719c11 fix(analysis): record nothing for frames that changed while an analysis ran
A light or deep analysis read its frames at the start and, under the
sequence lock, recorded AnalyzedLight, the warning count and the advisor's
Auto values for them whatever happened meanwhile. Frames added by an upload,
an import or a scan's reconcile then kept advice and warnings counted on the
old frame count, over a newer light analysis, and scans never queued another
one because AnalyzedLight was set again.

Under the lock the analysis now compares the row's frames version with the
one it read. When it moved and no light analysis is queued for the
sequence, it records nothing (a deep pass keeps only analysis.json and its
per-frame measurements), and the job logs it and queues a light analysis of
the frames as they are. A queued light analysis replaces what the pass
records, as for image passes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 21:37:00 +00:00
Claude 49f56bb689 fix(archive): an upload indexes the whole sequence when another writer changed it
ArchiveIngest appended the new frame rows and recorded the folder's stamps
whenever the batch appended at the end and the frame count matched, even
when a desktop sharing the archive had changed the sidecar alone (a
verify's hashes and Missing/Corrupt flags, decode tiers, duplicates, a
title). The server's frames then never got those changes, and the stamps
hid them from every incremental scan until a full scan.

A batch now asks ArchiveIndexer.InStepAsync under the lease, before it
changes the folder, and appends only when the index held the folder as it
was; otherwise it syncs the whole row and every frame from the sidecar.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 21:35:37 +00:00
Claude b187e6ce02 fix(archive): a scan never writes an older sidecar over a newer index commit
The scan's plain branch indexed a sidecar read without the lease. When an
upload or a partial writer (decode tiers, a verify) committed between that
read and the scan's transaction, the scan wrote its older copy over the
newer row and frames (dropping the uploaded frame rows), then recorded
the folder's current stamps, so incremental scans skipped the regression.

Under the row lock, SyncAsync now refuses an unleased read when the
sidecar no longer has the stamp the scan listed or the row holds another
frames version, and the scan reads the sidecar again under the lease. An
unleased sync records the stamps it was checked against, and the index
snapshot files each sidecar under the stamp it was read at. Under the
lease, a sidecar behind the locked row (an older copy put back) is
written again one frames version past the row, so the version never goes
back. Statuses cleared in this host's row only (Uncovered) now pass as a
parameter, so that rewrite never clears them in the shared sidecar.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 21:35:24 +00:00
Claude 1b84d74486 fix(archive): verify writes only the integrity flags of files still as checked
A verify's flush replaced every flag of a pending frame, in the sidecar
and the index, with the flags it computed from the frame as read without
the lease, possibly hours earlier. A preview-only or undecodable tier, a
duplicate flag or a repair recorded meanwhile was reverted, and a photo
an upload repaired during the run was flagged missing again, so the next
copy moved the good file aside.

Under the lease the flush now merges only Missing and Corrupt into the
frame's current flags, and the index sets and clears only those bits with
the hash, after locking the sequence row. A check whose sidecar record or
file (size and modification time taken before it was read) changed since
is left for the next verify.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 21:34:47 +00:00
Claude e369d1d20a fix(archive): lock the sequence row before its frames in every index write
FrameTiers.RecordAsync updated the frames of a sequence before its row,
while a scan's sync locks the row (FOR UPDATE) before rewriting every
frame. On PostgreSQL the two deadlocked and one job was aborted with
40P01. The tier writer now records the row first; the verify's integrity
flags (next commit) and maintenance's duplicate flags take the row lock
in the same transaction as their frames, so every writer of a sequence's
frames follows one order. A PostgreSQL test that deadlocked with the old
order covers it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 21:34:08 +00:00
Claude bb2f40c29f feat(i18n): the strings of the third verification pass in all 36 machine-translated languages
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 20:28:15 +00:00
Claude 279f8a6842 docs: record the third verification pass in DECISIONS, CHANGELOG and STATUS
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 20:22:15 +00:00
Claude f1720e7779 merge: third-pass archive, image and analysis fixes (W-1, W-5, W-7, W-13, W-14)
Merge branch fix3/data-images into the verification branch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
2026-10-12 20:18:40 +00:00