Files
Chronos/docs/STATUS.md
T
Alby96andClaude Opus 5.5 3ade4b8d6c docs: document phase 5b, the server as a project home
Phase 5b had only module rows and the review's DECISIONS and CHANGELOG lines.
The brief now describes the server home as the code does after the review
fixes: the projects API, projectChanged, the capability, the settings PATCH
under the lease, renders of a project version, the panel's Projects section,
and the desktop's server projects (open, copy, sync, chip, renders, viewers).

DECISIONS gains the phase's own rows; the 5b rows are dated 2026-10-26 like
the other review-2 phases, and three 5a rows are marked partly superseded.
CHANGELOG, STATUS, the request's 5b row and ARCHITECTURE follow the code
(frames stamp, stored reads, the .thumb marker, followed renames, the
editor's sign-in).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-04 13:19:55 +01:00

31 KiB
Raw Blame History

Status

Phase plan: docs/BRIEF.md §22. CI runs on Gitea Actions (Linux runner, .gitea/workflows); Windows behaviour is verified by its windows job once a Windows runner is registered (WINDOWS_RUNNER), and on a Windows PC until then.

Phase State
0 Bootstrap Done: solution, rules, Chronos.Testing, zero-package guard, i18n, WPF shell, server skeleton, Docker, icons, CI.
1 Metadata and imaging Done: metadata parsers, managed codecs, native RAW development (DNG, CR2, NEF, ARW, PEF, RAF), WIC provider and codec inventory, decode tiers, thumbnails and proxies, diagnose. Real-camera fixtures wait for verified raw.pixls.us URLs (CI warns per missing sample).
2 Data layer and archive Done: SQLite binding, PostgreSQL wire client, migrations, repositories, job engine, archive layout, sidecars, scan, rebuild, verify, duplicates, orphans, adopt, mass rename. Gate measured: a 100,000-frame archive (400 sequences of 250 photos) rebuilds from sidecars into an index identical in every column in 1.8 s on SQLite and 4.7 s on PostgreSQL (budget 120 s).
3 Library and Archive manager Done: Library (virtualised grid and list, timeline with year bands, filters, saved views, quick actions, mass bar, Delete… into the archive's trash with a dry run, typed confirmation and Undo, cards for server-only sequences), Archive manager (tree, health, statistics charts, maintenance with Trash… and restore, verify, duplicates, orphans, adopt, mass rename and move with dry runs), Jobs, Settings, Welcome, Server and About. Gate measured on 500,000 photos: Library open 259 ms on SQLite and 181 ms on PostgreSQL on a new connection pool (warm OS cache; budget 1 s); every filter, search, sort and next page ≤ 6.4 ms (budget 200 ms).
4 Card import Done: device detection, card pool and camera profiles, plan with sessions (merge and split), hash-verified copy, post-actions (verified delete, format behind a typed confirmation, eject), auto-import, Archive, Folder and Server destinations. Gate: import from a simulated card folder end to end in tests; delete and format refuse any photo the import did not verify; screenshots on ci-screenshots.
5 Analysis advisor Done: light and deep analysis, reports and section charts, recommendations with localised reasons, sequence presets, Auto/manual controls and Optimise in the editor. Gate: golden recommendations for synthetic sequences; every reason key exists in en and it (i18n check); deep analysis streams with checkpoints and resumes after a restart.
6 Engine, encoding, editor Done: render pipeline, MP4/AVI/GIF/APNG/image sequences, Media Foundation H.264/HEVC/AV1 with managed fallbacks; the sequence editor (Frames, Exposure, Camera, Motion and Export tabs, preview tools, section charts, curve editor, undo/redo, batch export) for local and server sequences. Gate: self-test suite green; the in-house inspector validates the containers the tests write; the encoder in use is logged. Playback: MediaPlayer opens the Media Foundation output and a source reader decodes its first frame (Windows tests). The pixel diff of every --capture screen against tests/visual/baselines (screenshots diff, BRIEF §20.2) is wired into CI but not armed: no baseline is committed yet, so the step compares nothing and only warns until the first baselines are accepted from ci-screenshots (Next steps).
7 Server, sync, uploader Done: server (API, auth, uploads, jobs, render nodes, events, admin panel with light and dark themes, Windows service), Uploader, client sync (sync table, conflicts with Save both, proxies kept offline, metered pause), server sequences edited with proxies and rendered where the originals are, this PC as a render node. Gate covered in-process: a sequence uploaded from one PC downloads identically on another, interrupted uploads and downloads resume, server events update a PC, renders run on a node and on the server's managed fallback, jobs resume after a restart, sign-ins and administrative actions are audited. The run with two real PCs and the Uploader against the Docker server is part of the release test.
8 Release readiness Release pipeline end to end (installers, portable and server zips, SHA256SUMS, release notes, optional signing, server image in the Gitea container registry, optional separate releases repository), update check with verified download, scrubbed diagnostics bundles (desktop and server), performance gates, 38 cultures (en, it and 36 machine translations with glossaries and independent reviews), RTL pass (ar, he: mirrored windows, left-to-right islands for media, charts, numbers and paths; any right-to-left culture added later follows), accessibility pass (names, live regions, keyboard paths for charts and the curve editor). The installer test (silent install of the packed installers, run, upgrade in place, uninstall: files, Add/Remove Programs, shortcuts, file type, user data kept, exit codes) runs in CI's windows job on a Windows runner. Pending: the interactive install on a real PC, Unraid template validation on a real server.
8.1 Owner review 1 In progress (request, answers and plan: docs/requests/2026-10-15-owner-review-1.md). Phase 1 done: stalled thumbnail and proxy jobs no longer fail and stay Running (frame-counted progress, bounded time left, final state always written); the editor's cancelled decodes stay in their tasks (no debugger stops in WicDecoderProvider.cs); WIC decodes RAW only through the Raw Image Extension and never DNG; GoPro DNGs converted by Adobe software are DNGs, developed natively for videos, read through their embedded preview for analyses and previews, and reclassified in existing archives by the next light analysis. Phase 2 done: jobs run one at a time on the desktop and the server; Parallelism is how many photos the running job processes at once (thumbnail and proxy passes, tier probes, deep analysis, render decodes); pausing the running job starts the next; an optional priority queue by job kind (Settings › Rendering, admin panel › Settings › Jobs, CHRONOS_PRIORITY_QUEUE) pauses lower jobs and resumes them by themselves; CHRONOS_PARALLELISM replaces CHRONOS_WORKERS. Phase 3a done: the rail is 200 px and collapses to icons with ≡ or Ctrl+B (tooltips then name the sections, the choice saved at once); the admin panel's sidebar is 256 px and collapses the same way. Phase 3b done: the Sequence section is now Edit, one sequence at a time chosen in a picker inside the section (Change sequence, Ctrl+O; the sequence edited last selected first), and the editor's tabs are the steps of a guided, freely navigable path from a new Analysis step (every finding with the step that deals with it) to Export, each step showing where it stands, with Previous and Next. Next, after owner review 2 (the owner's order): phase 4, the visual crop locked to the output's proportions (R5) and mirroring, 90° rotations, straightening and colour filters (R6).
8.2 Chronos on Gitea Done (request: docs/requests/2026-10-23-chronos-gitea.md): Titano renamed Chronos everywhere, translations' grammar included; repository, update check, links, issue forms and registry moved to the self-hosted Gitea; Gitea Actions CI, release, nightly image and performance workflows for the Linux runner, with the Windows programs cross-compiled and checked (pe-check); new Chronos.Tools commands zip, gitea-release, postgres-ci, pe-check. Pre-releases v0.1.0-rc.1 and v0.1.0-rc.2 (the update check builds its links from ChronosReleasesUrl, since Gitea's use its LAN ROOT_URL) published; REGISTRY_TOKEN is set and the v0.1.0-rc.2 server image is in the registry.
8.3 Owner review 2 In progress (request, answers and plan: docs/requests/2026-10-26-owner-review-2.md). Phase 1 done and released as v0.1.0-rc.3 (one adversarial review round, 19 findings fixed; strings in all 38 languages): :latest follows the highest stable release, or the highest pre-release while none is stable (Chronos.Tools release-channels), :nightly stays the nightly build of main (R1); CHRONOS_SPACE_PATH and the Unraid template's Array view (/mnt/user0/<share> read-only at /space) make the admin panel show the array's free space, the cache apart as Write volume, the file system in the tooltip, and completing an upload checks the archive volume first (507, resumable) (R2); the Settings icon is a toothed gear and the admin panel docks Settings at the foot of its sidebar (R4); About is the last page of Settings on the desktop and the last group of Settings on the admin panel (R5); Import › Folder… › Whole folder imports a folder as one sequence per format, titled after the folder (R9). Phase 2 done and released as v0.1.0-rc.4 (one adversarial review round, 35 findings fixed; strings in all 38 languages): scheduled jobs (R10) — schedules (migration 0007) with an in-house recurrence form, one scheduler per host claiming runs by compare-and-set with catch-up, and Jobs › Scheduled on the desktop and the admin panel (/api/v1/schedules, scheduleChanged); every timer that queued work is a visible system schedule (server: archive scan, upload clean-up every 6 h, index backup at 03:00, job history and audit log clean-ups; desktop: archive scan, daily index backup, housekeeping with cache trim), the archive still scanned at start; new Backup and Clean-up jobs, duplicates and orphans reports as jobs, one backup retention, the trash only reported; log settings (R11) — file and console levels, retention, file and total size limits, daily or hourly rotation, audit retention (the audit clean-up schedule's) and the diagnostics share in the admin panel's Settings › Logs (CHRONOS_LOG_*, lockedBy) and the desktop's Settings › Advanced; the server's files take Debug and Trace again, and logging never fails a job. Phase 3 done and released as v0.1.0-rc.5 (one adversarial review round and two fix rounds, 40 findings fixed; strings in all 38 languages; Library, photo delete and restore and the web upload tried by hand): the admin panel manages and never edits (R6) — a Library page (facets filters, cards or list, keyboard selection, mass Analyse, Proxies, Thumbnails, Verify, Tags, Export CSV and Delete, 1,000 sequences a request), a sequence's page (inline title, tags, rating, notes, photo viewer, cover, downloads, photo delete) and the trash view (Restore, Empty… behind a dry run, the typed word and a fingerprint); photos deleted into trash/photos under crash-safe journals with tombstones in the sidecar and frame_removals (migration 0008), so sync and uploads never bring them back unless restored or uploaded again on purpose; trash kinds, restore reasons and the EmptyTrash job on the desktop's Trash… too (typed entry count); the panel's files revalidated (no-cache, ETag); upload from the panel (R3) — file picker or drop, no folders, a self-tested in-house SHA-256 in a module worker, Exif capture time, resumable chunks. Known limitations: a never-hashed photo whose file was already missing is deleted without a tombstone; an unhashed server frame of a photo deleted on a PC stays missing here until the server verifies it; jobState carries no kind, so panel pages refresh after any job. Phase 4a done and released as v0.1.0-rc.6 (one adversarial review round and six fix rounds; strings in all 38 languages): Reorganize after import (R7) on the desktop (Archive manager, Library, the toast after Settings › Archive templates change; it replaces Rename… and Move…) and the admin panel (Library, the Saved toast of Archive) — folder, file and title templates applied to filed sequences behind a dry run that lists every change, the photos that keep their names and why (in place, never verified, missing) and the sequences that stay whole (unreadable sidecar), applied by the move job of exactly the confirmed plan (fingerprint, POST /api/v1/archive/reorganize, plans kept a few minutes on the server), which holds the rest when paused, cancelled or failed (also while the archive is offline), lets a sequence still receiving photos keep its file names and takes along a sequence left as it was inside a folder that moves; files renamed in two phases under .chronos/rename-files.json, completed after a crash by the next writer; the index, frames and exports follow a moved folder in one transaction, here and at another index's next scan, and writers never create a folder a Reorganize left nor write into one another sequence took; import, upload and Reorganize name photos by one rule (the sequence's camera and lens), and templates follow one set of rules everywhere (no folder scans skip, the extension kept, names that tell photos apart), held only to templates given anew. Known limitations: a reader without the sequence's lease can miss a file while its files are renamed; a change made on disk alone after a server dry run is found by the job, which fails changing nothing; a photo restored from the trash after a Reorganize keeps its old name; a render of another program whose folder moves while it runs is not stopped. Phase 4b done and released as v0.1.0-rc.7 (one adversarial review round, 42 findings, and three fix rounds; strings in all 38 languages): mass conversion after import (R7) on the desktop (the Archive manager's set, the Library's selection) and the admin panel (the Library's selection) — JPEG with a quality, TIFF-16 or linear DNG (the archival choice, scene-referred so a RAW's highlights above white and colours outside sRGB survive), Replace or New sequence chosen at every run and never remembered, behind a dry run that lists each sequence's photos and sizes, the photos that stay as they are and why (on the server, what it cannot read at full resolution: convert on a PC) and the free space where the conversion writes; Replace confirmed by typing; the convert job (stored as 19) converts exactly the photos confirmed (their digest in its parameters, their ids in journal/convert-<job>.photos, pinned when it first comes to a sequence; a retried New sequence never makes a second copy), one sequence at a time and all or nothing, resumable through journal/convert-<job>.* and staging/convert-<job>/, never twice at once; full-resolution decodes with the managed decoders first (never a 16-bit file from an 8-bit RAW development, never a TIFF WIC would read as black or noise), what Chronos reads from a photo never changed (a JPEG or TIFF-16 carries the profile; a linear DNG takes sRGB values only, so Adobe RGB, Display P3, ProPhoto and gamma-1.0 photos go to TIFF-16 or JPEG), Exif carried, every file verified by the server's decoders; Replace swaps the files of the frames in place under replace.pending.json, the originals going into a replaced trash entry that the toast's Undo or Restore swaps back and that Empty erases only while the archive on disk shows each conversion intact, or deleted on its own word (a tombstone, the trash, or trash/.erased/<id>.json; named first in its confirmation); import still copies byte for byte and the card keeps a converted photo's copy; sync and the ingest count every encoding of a photo as one; POST /api/v1/archive/convert in the plan cache Reorganize uses. Known limitations: a photo that fails although its headers read well leaves its sequence as it was; a decode larger than the memory stops the job; a damaged file that still decodes converts as decoded; a read error while a dry run reads a TIFF, DNG or TIFF-based RAW header lists the photo as needing a PC, preview-only or unreadable rather than held (the reader swallows it; nothing beyond the plan converts); JPEG and TIFF-16 clip float values beyond 0..1; not verified: a TIFF whose first image is a thumbnail and whose main image only WIC reads would convert at the thumbnail's size; a PNG's gamma and primaries without a profile count as sRGB; a linear DNG bakes the white balance in and clips below black; the desktop's Undo lives in the job's end toast only (later: Restore). Phase 5a done and released as v0.1.0-rc.8 (one adversarial review round, 55 findings, and five fix rounds; strings in en and it): the desktop's workspace and projects with this PC's archive as the home (R8) — a sequence's projects (Main, mirrored both ways with the sequence's settings so older clients, analyses and sync keep working, and other named projects), each a linear history of immutable versions in the portable form (positions parked by photo, SHA-256 of canonical text), kept as sidecars in .chronos/projects/ and indexed by migration 0009 (projects, project_versions, renders.project_id/project_version_id), deleted only on the archive's word (the projects' trash read first), healed from the index when a record is lost or behind, one Main decided from the records; Edit opens only workspace projects: Open in workspace (project, proxies, copy size and free space), the workspace-copy job (stored as 20, desktop only, hash-verified, resumable, space checked, its cancel clean-up under the project's lease), the working state in a folder outside the library, the title's project button (state chip; Save version with Ctrl+S, Sync, History with Compare and Restore, Open, New, Rename, Delete, Remove local copy after a plan), push and pull with replay and field-level merge under crash-safe journals, conflicts only where both sides changed a setting (Keep mine, Take library's, Save both, Later), Update media, newer and damaged copies named and left untouched, renders at the home with the settings embedded, .chronos format 2; Settings › Workspace (Folder with Change…, Sync, Kept versions). Known limitations: a server sequence still opens with proxies (the server home is 5b); originals, local render, moving the folder with its projects, emptying <workspace>/.trash, clean-up and the size limit are 5c; a capture still edits the library; nothing restores from the projects' trash yet; a lost record waits 2 minutes of one running Chronos before it is written again. Phase 5b done, to be released as v0.1.0-rc.10 (one adversarial review round, 21 findings, 19 fixed; strings in en and it): a Chronos Server as the home of its sequences' projects (R8) — /api/v1/sequences/{sid}/projects on the archive's ProjectService (list with Main made at the first read, create, rename, delete by the owner, the maker or an admin, head, versions in size-capped pages, the stored check, push with its outcome, the frames and their stamp), the projects capability and projectChanged, Main taking settings written outside the projects soon after (ProjectCatchUp), a settings PATCH writing project.json under the lease, no projects for a sequence without photos, renders and render nodes of a project version, and the admin panel's Projects section (versions, Rename, Delete); on the desktop ServerProjectHome through the signed-in session: Open in workspace in Edit and on the Server screen, the proxies downloaded into the workspace (hash-checked, resumable, thumbnails standing in while the server has no proxy), push, pull, conflicts, history and the chip against the server (Server newer, Not on server), renames followed, renders and analyses on the server of the version it holds after Send and render; an account without Edit and an older server keep Open with proxies. Known limitations: projects read Offline when signed in to their server through another address; a copy reads the server's frames in one answer; History downloads every version's settings; the Server screen's row buttons wrap (server-* baselines not recaptured), and 8 baselines show the TEMP path.
9 Monetization Not started: requires explicit approval (§22).

Verification (2026-10-12)

A full audit against the brief, CLAUDE.md, the UI kit, the tests and the Docker and client setups confirmed 71 defects with independent verifiers. A second pass over the fixes confirmed 37 more (proxies and decode tiers, project positions crossing copies through sync, server scans and maintenance, desktop settings and polling, a portable copy inside OneDrive, setup and deployment guidance), a third pass 16 more (editors open while photos arrive, partial writers of the index row, image passes after another writer's import, smaller error-text and documentation gaps), a fourth pass 7 more (lock order of index writes, analyses and scans racing another writer), a fifth pass 4 more (tag lock order on PostgreSQL, the orphans fix's follow-up analyses, deep reports saved over newer ones, frames versions shared by two indexes), and a last check 2 more (an unreadable photo counted as a change, a deep report made stale by proxies). All are fixed, each with tests (rows dated 2026-10-12 in DECISIONS and CHANGELOG), except that the screenshot diff (BRIEF §20.2 visual regression) gates nothing until its first baselines are committed (Next steps). The Docker image was built and run with PostgreSQL 17, a fresh archive folder and remapped ports; the client installers were installed, run, upgraded and removed on GitHub's windows-latest by the installer CI job (since 2026-10-23 the last step of the windows job, on a Windows runner).

How to try it

dotnet build Chronos.slnx -c Release
dotnet run --project src/Chronos.Server            # https://localhost:8443/admin (set CHRONOS_DATA_PATH/CHRONOS_ARCHIVE_PATH)
src/Chronos.App/bin/Release/net10.0-windows/Chronos.exe                # Windows
src/Chronos.Uploader/bin/Release/net10.0-windows/Chronos.Uploader.exe  # Windows
docker compose -f deploy/docker/docker-compose.yml up -d             # server + PostgreSQL 17
CHRONOS_PERF=1 dotnet run --project tests/Chronos.Data.Tests -c Release -- --filter category:perf --verbose   # performance gates
src/Chronos.App/bin/Release/net10.0-windows/Chronos.exe --capture out/screenshots  # every screen with sample data, plus Arabic (RTL)
  • Diagnostics: Settings › Advanced › Diagnostics › Export bundle (desktop) or admin panel › Logs › Diagnostics (server, GET /api/v1/server/diagnostics). Open the zip: logs, reports, settings and failed jobs, no passwords or tokens.
  • Update download: Settings › Updates › Check for updates, then Download when a newer release exists; the verified setup (the portable zip in a portable copy) appears in Explorer. Cancel stops it; the next Download resumes. Settings › About shows the version, build, runtime and system.
  • Import: Import › Folder… (any folder of photos stands in for a card) › Import; the sequence opens from the Library. Delete a sequence with Delete… (dry run first) and bring it back from Archive › Trash….
  • Whole folder: Import › Folder… › Group › Whole folder: one plan row per file format (RAW+JPEG gives two), titled after the folder whatever the cameras and pauses; add photos to the folder and import it again: they join the same sequence.
  • Free space on Unraid: map /mnt/user0/<share> read-only to /space and set CHRONOS_SPACE_PATH=/space (the template's Array view and Space path); the admin panel's Dashboard and Archive show the array's free space, a Write volume line the cache's, and the figures' tooltip names the file system (fuse.shfs).
  • Admin panel: Settings at the foot of the sidebar; About is its last group, and #/about opens it there.
  • :latest: after the next pre-release tagged on a main that has phase 1, the release log says "…:latest: true" and docker pull gitea.encke-hake.ts.net/balbosoft/chronos-server:latest works. Re-publishing v0.1.0-rc.2 cannot do it: the workflow builds Chronos.Tools from the tag, which has no release-channels.
  • Sync: sign in on Server (trust the certificate once); the sync table lists every sequence of both sides. Open a server-only sequence from the Library to edit it with proxies; Render runs on the server or a render node.
  • Language: Settings › General › Language switches at once; Arabic and Hebrew mirror every window.
  • Settings: Import, Analysis and Formats pages; Archive rows edit the open archive's archive.json; Advanced › Restore picks a copy of the index (made by the Index backup schedule or Back up now), compares it with the index and restores it at the next start.
  • Scheduled jobs: Jobs › Scheduled (desktop) or admin panel › Jobs › Scheduled lists the system schedules (three on the desktop; five on the server, four on PostgreSQL). New schedule › Integrity check, Weekly Mon and Thu 02:30, create it, then Run now: the job appears in the Queue tab with a Scheduled pill; select the schedule (the panel: its name) for its runs. Turn Archive scan off and restart: no scan runs at start.
  • Logs: admin panel › Settings › Logs › File level Debug, Rotation Hourly › Save, then watch /data/logs get server-yyyyMMdd-HH.log with Debug lines, no restart; with CHRONOS_LOG_LEVEL set the two levels are read-only and their tooltip names the variable. Desktop: Settings › Advanced › Log level Debug, Rotation Hourly, then Logs › Open.
  • Admin panel Library: Library › filter by year, camera, status or tag, select cards (check box, Shift+click, or Space and Shift+Space) and try Tags…, Verify or Delete… (dry run first); open a sequence, open a photo (←/→, Esc), select 21 photos › Delete… (type their number), then the Library's Trash › Restore, or Empty… (type "empty") and watch the job end. Re-uploading a deleted photo from the Uploader or sync does not bring it back.
  • Web upload: Library › Upload › New sequence, drop a few JPEGs and a folder › Upload: one Folders skipped chip, progress per photo, Uploaded; upload them again: Already there; delete one and upload it again: Deleted before, whose Upload again files it on the next Upload. Esc does nothing while photos are sent.
  • Desktop trash: Archive › Maintenance › Trash… lists photo entries beside deleted sequences; Restore says why a photo stayed; Empty… measures the trash and asks for the number of entries before the Empty trash job.
  • Reorganize: desktop Archive › select a year › Reorganize… › Folders {year}/{date} {title}: the dry run lists every change, and Apply queues the Reorganize job (pause and resume it in Jobs). Admin panel: Library › select sequences › Reorganize… › Apply… › Reorganize › Open job; or Archive › change the file template › Save › Reorganize… in the toast.
  • Convert: desktop Archive › select a year › Convert… › Linear DNG, Replace › Apply › type the number of photos › Replace; when the job ends, Undo in its toast brings the originals back (later: Maintenance › Trash…). Admin panel: Library › select sequences › Convert… › JPEG, New sequence › Convert… › Convert › Open job: the copies appear as "… (JPEG)"; with Replace, type "replace", and the trash's Restore swaps the originals back.
  • Workspace: open a sequence from the Library: Open in workspace asks the project (Main, or New with a name) and the media (Proxies), with the copy's size and the free space; the editor opens once the Workspace copy job ends. Edit, then Ctrl+S, type a note, Enter: the chip says In sync and the Library's sequence takes the settings (Main). Ctrl+O lists the project in the picker's Workspace group. The title's ▾ › History… › Compare or Restore; ▾ › Remove local copy… shows its plan. Two workspace folders on one archive (Settings › Workspace › Change…) stand in for two PCs: change the same setting in both and Sync to see the conflict dialog.
  • Server home: sign in on Server to a server of this release; a server-only row offers Open in workspace (an older server shows it disabled). Choose a project (New, with a name): a Workspace copy job downloads the proxies and the editor opens. Edit, Ctrl+S, Enter: the chip says In sync, and the admin panel's sequence page lists the version under Projects. Rename the project there: the editor's project button takes the new name. Change a setting of Main from another PC (or an older Chronos) on the server while Main is open here: the chip says Server newer; Sync takes it. Render offers Send and render while changes are not sent, then renders on the server.
  • Project files: Export › Save project file writes a .chronos file; opening it (double-click or Chronos.exe <file>) opens the sequence with those settings in the running Chronos, given to its Main project in the workspace.
  • Notifications: minimise Chronos and insert a card or finish a job: a Windows notification appears; Ctrl+1…6 and Ctrl+, switch sections.
  • Edit: Ctrl+3 with no sequence open shows the picker (type to search, Enter opens); the title's ▾ or Ctrl+O chooses another sequence and Esc comes back. The step bar, Previous/Next (Ctrl+PgUp/PgDn) and Alt+1…8 move between steps; on Analysis each finding's button opens the step that deals with it.

Next steps

Owner reviews, in the owner's order (owner review 2 first, then the rest of owner review 1); each phase ends with a release (owner review 2, R12):

  1. Owner review 3, phase 1: release the ports fix as v0.1.0-rc.9.
  2. Owner review 2, phase 5b: settle the Server screen's row buttons and recapture the server-* baselines (and fix the TEMP path the capture shows), translate the new keys into the 36 other languages, then release v0.1.0-rc.10 (the PR green on Gitea Actions, squash-merge, tag, the Docker image and the Windows programs) and update the memory notes.
  3. Owner review 2, phase 5c: R8 originals, local render (WorkspaceRender), Remove local copy's clean-up and the workspace's trash, the size limit, moving the workspace folder, the rest of Settings › Workspace.
  4. Owner review 1, phase 4: R5 visual crop locked to the output's proportions, R6 mirroring, 90° rotations, straightening and colour filters (project settings in the workspace).
  5. Owner review 1, phase 5: R3 export panel and Render menu, R8 export options, R9 videos library.
  6. Owner review 1, phase 6: Docker, Unraid and deploy docs, BRIEF §24 amendments, full verification.

Phase 8 gate:

  1. Visibility: make the BalboSoft organisation (and its packages) public, or publish to a public RELEASES_REPO, so that people without an account can download releases, get update notices and pull the image.
  2. Windows runner: register an act_runner in host mode on a Windows PC (.NET SDK, Git for Windows, PowerShell 7) and set the repository variable WINDOWS_RUNNER to its label. The screenshot baselines in tests/visual/baselines were captured on the development PC (2026-11-04): register the runner on that PC, or accept a new set captured on the runner's PC (its README says how). From then on a visual change, or a screen without a baseline, fails the windows job.
  3. On Windows: install the latest pre-release's setup, upgrade over the previous version, uninstall (with and without user data), silent mode.
  4. Unraid: install the template as a user template (README › Server image, Compose and Unraid) with the official PostgreSQL template, check that its icon (the SVG of branding/) shows, reach the WebUI, and that the Dashboard shows the array's free space through Array view.
  5. Native-speaker review of the machine translations where users report wording (i18n export per language).