Files
Chronos/docs/STATUS.md
T

16 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 implemented; review and release pending: :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). Next: phase 2, log settings (R11) and scheduled jobs (R10).
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 daily backup, compares it with the index and restores it at the next start.
  • 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.
  • 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 2, phase 1: its new strings in the 36 machine-translated languages (only en and it have them), review, merge and release (a new pre-release, whose image also moves :latest).
  2. Owner review 2, phase 2: R11 log settings, R10 scheduled jobs (migration 0007).
  3. Owner review 2, phase 3: R6 library on the admin panel, photo delete and trash (migration 0008), R3 upload from the admin panel.
  4. Owner review 2, phase 4a: R7 Reorganize after import.
  5. Owner review 2, phase 4b: R7 mass conversion.
  6. Owner review 2, phase 5a: R8 workspace and projects with a local home (migration 0009).
  7. Owner review 2, phase 5b: R8 server home.
  8. Owner review 2, phase 5c: R8 originals, local render, clean-up, Workspace settings.
  9. 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).
  10. Owner review 1, phase 5: R3 export panel and Render menu, R8 export options, R9 videos library.
  11. 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. Then arm the screenshot diff: from the ci-screenshots commit of the first green windows job of a pull request, run dotnet run --project src/Chronos.Tools -- screenshots accept <dir> and commit the PNGs to tests/visual/baselines (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).