Phase 5c P4. The workspace no longer grows without bound: a daily
workspace-cleanup system schedule (04:30, catch-up) removes the media of
projects in step with their home that were not opened for Clean after,
and the size limit removes the least recently used after each copy.
Each project kept is logged with its reason (open in Edit, not in step,
home offline, jobs pending, renders not sent, unreadable, just copied).
- WorkspaceCleaner: cleans under the project's lease, re-checking every
condition; the originals the home no longer holds go to the workspace
trash, never away. The media index is marked Cleaned, so the project
reads as MediaRemoved and opening it copies the media again.
- WorkspaceTrash: lists entries with a fingerprint, and empties only the
plan the user confirmed (refused when the trash changed since).
- Trash dialog view model and view: Erase is enabled only after the user
types the number of entries.
- Removing a copy counts the unsent renders and the last originals. Send
first queues the renders' sending and refuses the removal until they
are sent.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Phase 5c (owner review 2, R8) is built by six packages in parallel. This
commit settles everything they share, so each one touches its own files:
- job kinds WorkspaceRender (21), WorkspaceSend (22) and WorkspaceMove (23)
with their wire names, default priorities, notices and parameter records;
their handlers are registered as skeletons that throw until their
package lands
- WorkspaceJobOptions and a new CreateHandlers overload; the earlier ones
stay and default the options
- originals in the media index (an index of phase 5b reads as proxies
only), their file names, and the exports/renders.json ledger of local
renders, written atomically
- the optional project and version of an uploaded render
- the workspace settings (size limit, default media, version on render,
clean-up age, project to open) and when each project was opened, which
Reset and Import keep and Export leaves out
- WorkspaceHost split into partial files, with stubs for usage, trash and
the folder move, removal hooks for unsent renders and last originals,
and a guard that holds work while the workspace moves
- every new string of the phase in English and Italian, with tooltips
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Convert photos already in the archive to JPEG, TIFF-16 or Linear DNG, from the panel's Library and the desktop's Archive and Library. Each run asks Replace (same frames, originals to the trash, recoverable) or New sequence. A dry run lists what converts, what is skipped and why, size before and after, and free space; the job converts exactly the confirmed photos, resumes, and commits all or nothing per sequence. A conversion never changes what Chronos reads from a photo. Replaced originals are erased only on the archive's own word that their conversion is gone. Desktop TIFFs that WIC showed black or as noise now go to the managed reader; the Edit picker no longer spins a core.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
- Jobs > Scheduled on the desktop and the admin panel. Every timer that queued work is now a visible system schedule: archive scan, upload clean-up, index backup, job-history and audit clean-ups, desktop housekeeping. New actions: verify, thumbnails, proxies, analysis, maintenance, backup, clean-ups, reports.
- The scheduler: migration 0007, in-house recurrence, compare-and-set claim, catch-up, scan at start.
- Log settings: levels, retention, size parts, total limit, daily or hourly rotation, audit retention, diagnostics share; the server writes Debug/Trace to its files again; logging never fails a job.
Upgrade: CHRONOS_LOG_LEVEL set in an existing container locks both levels; migration 0007 is one-way.
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>