diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md index 705f3c81..8fff3b44 100644 --- a/docs/ARCHITECTURE.md +++ b/docs/ARCHITECTURE.md @@ -93,7 +93,7 @@ Dependencies point one way: `Core` ← `Core.Windows`, `Data`, `Protocol` ← `S | Host | Composition root | What it runs | |---|---|---| | Chronos (desktop) | `App/Infrastructure/AppServices` | SQLite index in `%LOCALAPPDATA%\Chronos` (or `.\data` when portable, unless the copy is in a OneDrive folder); `ArchiveService` with WIC first, then managed decoders; `ProcessingService` with Media Foundation, then managed encoders; one `JobEngine` with the handlers of both; thumbnails; `ServerSession`; `SyncHost` while signed in (sync engine and agent, upload and download handlers, metered hold, editors of server sequences); the render node while opted in and signed in; update check and download (`About/UpdateCheck`, `About/UpdateDownload`, `About/UpdateFlow`: the setup, or the portable zip for a portable copy, verified against `SHA256SUMS`, resumable, cancellable, failing after 60 s without data); diagnostics bundle; daily index backups and the restore staged in Settings › Advanced (`DatabaseBackups`) | -| Chronos Server | `Server/Hosting/ServerHost.Build` | Options from `server.json` + `CHRONOS_*`; PostgreSQL (or SQLite on Windows); `ArchiveModule` then `ProcessingModule` register job handler providers; `JobEngineHost` (renders only managed formats and MP4 jobs no render node can take, BRIEF §14.7); `RenderNodeService`/`RenderNodeMonitor`; `UploadService`; `EventHub` (WebSocket); embedded admin panel; LAN discovery beacon; Windows service host; daily backups of an SQLite index (`DatabaseBackupService`) | +| Chronos Server | `Server/Hosting/ServerHost.Build` | Options from `server.json` + `CHRONOS_*`; PostgreSQL (or SQLite on Windows); `ArchiveModule` then `ProcessingModule` register job handler providers; `JobEngineHost` (renders only managed formats and MP4 jobs no render node can take, BRIEF §14.7); `RenderNodeService`/`RenderNodeMonitor`; `UploadService`; `VolumeSpace` (free space of the archive, the space path and `/data`, file system and mount from `/proc/self/mountinfo`; tests replace it); `EventHub` (WebSocket); embedded admin panel; LAN discovery beacon; Windows service host; daily backups of an SQLite index (`DatabaseBackupService`) | | Chronos Uploader | `Uploader/App.xaml.cs` | `ChronosClient`, persisted queue, watch folders; no database | | Chronos Setup | `Setup/Program` | TPK1 payload extraction, registry, shortcuts, file types named in setup's language, silent mode, uninstaller; only what starts a program its log or payload lists is changed: Windows services of those programs stopped once the programs have closed, started again (also after a failure) or deleted through the Service Control Manager (an elevated `/SERVICES … /NAMES` step when needed), sign-in entries of those programs moved to the program an upgrade renamed or removed, shared shortcuts handed to the product that keeps the program; the Server only for all users inside Program Files; "Remove my data" limited to the programs no other installed product uses | diff --git a/docs/BRIEF.md b/docs/BRIEF.md index 7a181027..ec8fbe1e 100644 --- a/docs/BRIEF.md +++ b/docs/BRIEF.md @@ -683,22 +683,26 @@ player smoke test on Windows CI. │Edit│ content they act on; every command has a tooltip │ │ ▣ │ │ │Arch│ │ -│ ⚙ │ │ +│ ☰ │ │ │Jobs│ │ │ ☁ │ │ │Srv │ │ │ │ │ │ ⚙ │ │ │Set │ │ -│ ⓘ ├─────────────────────────────────────────────────────────────────────────────┤ +│ ├─────────────────────────────────────────────────────────────────────────────┤ │ │ 412 sequences · 618,204 photos · 9.4 TB · ☁ Connected to "Studio NAS" · 3 jobs │ ← status strip └────┴─────────────────────────────────────────────────────────────────────────────┘ ``` -- Left navigation rail (prototype pattern): full names in 200 px, collapsible to 48 px of - icons with ≡ or Ctrl+B (state saved at once; a collapsed icon's tooltip names its section - before describing it; amended 2026-10-16, R1), badge counts (warnings, running jobs), - hover tooltip with section description. +- Left navigation rail (prototype pattern): Library, Import, Edit, Archive, Jobs and Server + at the top, Settings alone at the bottom (About is the last page of Settings, §12.9; + amended 2026-10-26, R5); full names in 200 px, collapsible to 48 px of icons with ≡ or + Ctrl+B (state saved at once; a collapsed icon's tooltip names its section before + describing it; amended 2026-10-16, R1), badge counts (warnings, running jobs), hover + tooltip with section description. The Settings icon is a toothed gear (8 teeth, centre + hole), the same in Chronos, the Uploader and the admin panel; the circle with rays is the + Sun icon only (amended 2026-10-26, R4). - Fluent theme, system/dark/light, system accent; density "comfortable"; 8 px grid; one typeface (Segoe UI Variable, system fallback for CJK/Arabic/etc.). - Window chrome custom (dark title bar), min size 1200×760; per-monitor DPI. @@ -805,6 +809,16 @@ player smoke test on Windows CI. and profile; unknown cards prompt for a nickname (one field). - Plan before touching disk: sessions, folders to be created, first three file names, duplicates already in the archive (by hash), disk space check. +- A picked folder (`Folder…`, and Archive › Adopt folder › Copy into archive…) adds a + **Group** row: *Sessions* (as for a card) or *Whole folder* (amended 2026-10-26, R9). + Whole folder makes the folder (its subfolders too while Subfolders is on) one sequence + per file format: camera bodies and pauses are ignored, formats are not (RAW+JPEG of the + same shots stays two sequences, so no frame is doubled). Sessions, gap and minimum are + then disabled, their tooltips saying why. The title defaults to the folder's name (a + typed title wins; it also fills `{title}`). Each plan row shows the camera, or "n + cameras", and the format; Split in Show plan cuts a part off, Merge joins it back. A folder + starts on Sessions every time (folders have no profile); cards, drives and the admin + panel have no Group choice. - Copy with hash while streaming; verify by re-reading destination; only then delete or format (OS dialog); eject via `IOCTL_STORAGE_EJECT_MEDIA` after `FSCTL_LOCK_VOLUME`. - Destination "Server" streams frames through the client to the server (§14.4); the @@ -865,13 +879,19 @@ budget, spill folder, parallelism = photos the running job processes at once, pr with a level per job kind, encoders detected, hardware preference; amended 2026-10-16, R2), Formats (per format tier on this PC, codec install links), Server (last servers, trusted fingerprints, -render node), Updates (check on start), Advanced (portable mode, logs, database backup/ -restore, reset). Import/export settings as JSON. +render node), Updates (check on start; latest version: check now, download, releases page), +Advanced (portable mode, data folder, logs, diagnostics bundle, database backup/restore, +reset), About last (§12.9). Each action has one place in Settings (amended 2026-10-26, R5). +Import/export settings as JSON. ### 12.9 About -Version, build, licence/EULA link, third-party notice (none), diagnostics bundle button -(zips logs + environment report), update check. +The last page of Settings (§12.8), no longer an entry of the rail (amended 2026-10-26, R5): +version, build, runtime, system, licence/EULA link, third-party notice (none) and, in every +language but English, the machine-translation notice with its review link. Nothing is +offered twice: the update check, its notice and the releases page are on Updates, the data +folder and the diagnostics bundle button (zips logs + environment report) on Advanced. The +update check on start (§18) runs whatever screen is open. --- @@ -884,7 +904,14 @@ Version, build, licence/EULA link, third-party notice (none), diagnostics bundle inherit a "camera profile" (rules shared by all cards of that camera). - Session detection: gap > `SessionGapMinutes`; groups with < `MinimumSessionFrames` merge into the previous session (test shots); each session becomes a sequence; the user can - merge/split in the plan. + merge/split in the plan. A folder imported as **Whole folder** (§12.4) skips detection: + one session per file format whatever the bodies and pauses, broken only by the user's + splits. Its session key is `folder-` + the first 16 hex digits of SHA-256(PC name | full + path without trailing separator, upper-cased on Windows | format), plus + `-yyyyMMdd-HHmmss` of its first photo for a part split off; so an interrupted import + resumes into the same sequence and a later import of the folder adds to it. The PC name + is in the key because the server files uploads by session key for every user alike + (amended 2026-10-26, R9). - Duplicate handling: hash lookup against the archive index (skip/rename/overwrite); "already imported" state remembered per card + file (path, size, mtime) for fast re-inserts. @@ -964,7 +991,12 @@ the hash, moves the file into `originals/` under the layout templates (temp → rename), extracts metadata, appends to `sequence.json`, inserts the DB row, enqueues thumbs/proxies/light analysis, emits `sequenceChanged`. Frames without a target sequence are grouped by the same session rules (§13) into auto-created sequences. Card imports from -a connected client use exactly this path. +a connected client use exactly this path. `POST /uploads` answers 507 `insufficient_storage` +when `/data` lacks the upload's size plus a 64 MiB reserve; before its staging copy, +`complete` checks the archive's own volume (never the space path, §14.9) the same way and +answers 507 with the upload still receiving, so the client completes it again once there is +room; render uploads and render-node results are checked the same way at completion, and a +volume that cannot be measured refuses nothing (amended 2026-10-26, R2). ### 14.5 Sync @@ -1006,36 +1038,58 @@ available and says so in the job log. │ Users │ │ 9.4 TB │ │ 412 seq │ │ 3 jobs │ │ 2 nodes │ │ │ Archive │ │ of 16 TB │ │ 618k pho │ │ running │ │ online │ │ │ Jobs │ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │ -│ Settings │ Storage by year ▁▂▃▅▇█ Uploads last 30 days ▂▁▃▆▇▅▂ │ -│ Logs │ Recent: alberto uploaded 1,020 frames · node "studio-pc" rendered 4K HEVC │ -│ About │ │ +│ Logs │ Storage by year ▁▂▃▅▇█ Uploads last 30 days ▂▁▃▆▇▅▂ │ +│ │ Recent: alberto uploaded 1,020 frames · node "studio-pc" rendered 4K HEVC │ +│ Settings │ │ +│ (A) admin ⏻ │ │ └─────────────┴────────────────────────────────────────────────────────────────────────────┘ ``` Pages: Login · Dashboard · Users (table; create/edit/disable/reset/roles/quota) · Archive (path, templates, proxy policy, scan/rebuild/verify, stats) · Jobs (queue/history/nodes, -cancel/retry) · Settings (server name, ports, TLS mode + fingerprint, discovery, jobs: -parallelism and priority queue, limits, language, retention) · Logs (tail, download) · About. Same UI rules: tooltips only, light/ -dark, localised via `/api/v1/i18n`, keyboard accessible. The sidebar is 256 px and collapses -to its icons with ≡ or Ctrl+B like the desktop rail, the choice kept in the browser and the -links' tooltips then naming their page; on narrow screens it stays the top bar (amended -2026-10-16, R1). +cancel/retry) · Logs (tail, download) and, docked at the foot of the sidebar above the +account, Settings (server name, ports, TLS mode + fingerprint, discovery, jobs: parallelism +and priority queue, limits, language, retention). The last group of Settings, About, is +read-only: version, API version, database and uptime (the server name and the fingerprint +are in the groups above); an old `#/about` link opens Settings on it (amended 2026-10-26, +R4, R5). Same UI rules: tooltips only, light/dark, localised via `/api/v1/i18n`, keyboard +accessible. The sidebar is 256 px and collapses to its icons with ≡ or Ctrl+B like the +desktop rail, the choice kept in the browser and the links' tooltips then naming their page; +on narrow screens it stays the top bar, Settings at its end (amended 2026-10-16, R1; +2026-10-26, R4). Settings has the desktop's gear icon (§12.1). + +Storage (Dashboard and Archive) shows the space volume: the folder `CHRONOS_SPACE_PATH` +names (§14.9) when it can be measured, else the archive's own volume. When a space path is +in use and the archive's own volume (the write volume, where uploads land; on Unraid the +share's primary storage, often the cache) has other figures (another size, or free space +more than 64 MiB apart), a second line *Write volume* shows its free space. The figures' +tooltip names the volume and its file system (on Linux the mount's type from +`/proc/self/mountinfo`, so an Unraid share reads `fuse.shfs`); on such a share without a +space path it says the figures are the share's primary storage and to map the share's array +view (`/mnt/user0/`) to `/space`. The server's diagnostics report lists the archive, +the space path and `/data`, each with free space, file system and mount (amended +2026-10-26, R2). ### 14.9 Configuration and Docker Environment variables (also readable from `/data/server.json`): `CHRONOS_ADMIN_USER`, `CHRONOS_ADMIN_PASSWORD` (used only when no admin exists; forced change at first login), `CHRONOS_ARCHIVE_PATH=/archive`, `CHRONOS_DATA_PATH=/data`, +`CHRONOS_SPACE_PATH` (`SpacePath` in `server.json`; optional: a folder, e.g. `/space`, whose +volume's free space the admin panel shows instead of the archive's; one that cannot be +measured falls back to the archive's with one warning, logged at start and again only once +it has worked in between; uploads always check the archive's own volume, §14.4), `CHRONOS_DB=postgres|sqlite` (Linux: postgres only), `CHRONOS_DB_HOST`, `CHRONOS_DB_PORT=5432`, `CHRONOS_DB_NAME`, `CHRONOS_DB_USER`, `CHRONOS_DB_PASSWORD`, `CHRONOS_DB_SSLMODE=prefer`, `CHRONOS_HTTP_PORT=8080`, `CHRONOS_HTTPS_PORT=8443`, `CHRONOS_TLS_MODE=auto|pem|proxy`, `CHRONOS_TLS_CERT`, `CHRONOS_TLS_KEY`, `CHRONOS_SERVER_NAME`, `CHRONOS_LANG=en`, `CHRONOS_PARALLELISM` (photos the running job processes at once; `CHRONOS_WORKERS`, its former name, still sets it), `CHRONOS_PRIORITY_QUEUE=false`, `CHRONOS_DISCOVERY=true` (LAN UDP beacon), -`PUID`, `PGID`, `TZ`. (Amended 2026-10-16, R2.) +`PUID`, `PGID`, `TZ`. (Amended 2026-10-16, R2; 2026-10-26, R2.) Dockerfile: multi-stage on `mcr.microsoft.com/dotnet/sdk:10.0` → `aspnet:10.0`, non-root -user via `PUID/PGID` entrypoint, volumes `/archive` and `/data`, `HEALTHCHECK` on +user via `PUID/PGID` entrypoint, volumes `/archive` and `/data` (the optional read-only +`/space` bind mount is not a declared volume; amended 2026-10-26, R2), `HEALTHCHECK` on `/health`, `linux/amd64` + `linux/arm64`. `docker-compose.yml` with a PostgreSQL 17 service. Windows: `Chronos.Server.exe` runs as console or Windows Service (`sc create`), SQLite or PostgreSQL. @@ -1189,7 +1243,7 @@ container; the timings are printed at the end of the log. `obj/project.assets.json` lists no packages. The workflows use only shell (`run`) steps: no third-party actions at all (amended 2026-10-23, R3). -### 19.3 `release.yml` (tag `v*`, or manual re-publish of an existing tag; amended 2026-10-23, R3) +### 19.3 `release.yml` (tag `v*`, or manual re-publish of an existing tag; amended 2026-10-23, R3; amended 2026-10-26, R1) Job `release`, in the SDK container: the version from the tag (`vMAJOR.MINOR.PATCH[-PRERELEASE]`) passed as `-p:ChronosVersion`, with @@ -1203,14 +1257,23 @@ installers `Chronos-Setup-.exe` (components Chronos, Uploader, Server) and `Chronos-win-x64-portable-.zip` (with `portable.txt`); release notes (`Chronos.Tools changelog` from Conventional Commits) and `SHA256SUMS`; the Gitea release made by `Chronos.Tools gitea-release` (a draft first, every file uploaded and its size -verified, then published). Then job `image`, in the runner's default image with the docker -CLI and the host's daemon: it builds `linux/amd64` only (arm64 would need QEMU on the host) -and pushes `gitea.encke-hake.ts.net/balbosoft/chronos-server:`, plus `:latest` only -for the newest stable release. Pushing needs the repository secret `REGISTRY_TOKEN`, an -access token of a user who can write the owner's packages (scope "package: read and -write"): the workflow's own token (user `gitea-actions`) is refused by the organisation's -registry. Pre-releases (tags with a `-`) get no `:latest`, and the in-app update check -ignores them. +verified, then published). Then `Chronos.Tools release-channels` decides what the tag moves +(amended 2026-10-26, R1): it reads the target repository's published releases +(`releases?draft=false&limit=50`), stable and pre-releases alike, ignores drafts and tags +that are not `v` + SemVer 2.0, always counts the tag itself, takes a release Gitea flags as +a pre-release for one, and compares by SemVer 2.0 precedence (not Gitea's +`releases/latest`, which is the most recently created release; equal precedence counts as +highest). `latest` is true for the highest stable release and moves the releases +repository's content (§19.4); `image_latest` is true for the highest stable release or, +while no stable release exists, the highest pre-release, and moves `:latest`. Re-publishing +an older tag, or a pre-release once a stable release exists, moves neither. Then job +`image`, in the runner's default image with the docker CLI and the host's daemon: it builds +`linux/amd64` only (arm64 would need QEMU on the host) and pushes +`gitea.encke-hake.ts.net/balbosoft/chronos-server:`, plus `:latest` when `image_latest` +is true. Pushing needs the repository secret `REGISTRY_TOKEN`, an access token of a user who +can write the owner's packages (scope "package: read and write"): the workflow's own token +(user `gitea-actions`) is refused by the organisation's registry. Pre-releases (tags with a +`-`) are published as Gitea pre-releases; the in-app update check ignores them. Variables, all optional: `PUBLIC_URL` (default `https://gitea.encke-hake.ts.net`), `RELEASES_REPO` (§19.4), `REGISTRY` (default the host of `PUBLIC_URL`), `REGISTRY_USER` @@ -1249,15 +1312,22 @@ Nightly build of `main` (02:17 daily) to with the host's daemon and the `REGISTRY_TOKEN` secret as in §19.3 (amended 2026-10-23, R3); `deploy/docker/docker-compose.yml` for users (server + PostgreSQL + volumes), downloaded from `https://gitea.encke-hake.ts.net/BalboSoft/Chronos/raw/branch/main/deploy/docker/docker-compose.yml` -together with `.../deploy/docker/.env.example`. +together with `.../deploy/docker/.env.example`. `:nightly` is never a release: it carries +`main` as it was that night (version `0.0.0-nightly.`), for testing only; users follow +`:latest` or pin `:` (amended 2026-10-26, R1). ### 19.6 Unraid template (`deploy/unraid/chronos.xml`) -Community Applications XML: repository `gitea.encke-hake.ts.net/balbosoft/chronos-server:latest`, -WebUI `http://[IP]:[PORT:8080]/admin`, ports 8080/8443, paths `/archive` → -`/mnt/user/Timelapse`, `/data` → `/mnt/user/appdata/chronos`, variables from §14.9 (admin -user/password, DB host/port/name/user/password, TLS mode, PUID/PGID, TZ), description ≤ 2 -sentences. Registry and Project `https://gitea.encke-hake.ts.net/BalboSoft/Chronos`, +Community Applications XML: repository `gitea.encke-hake.ts.net/balbosoft/chronos-server:latest` +(the newest release: the highest stable release, or the highest pre-release until the first +stable one, §19.3; never `:nightly`, so the template finds an image from the first +pre-release on; amended 2026-10-26, R1), WebUI `http://[IP]:[PORT:8080]/admin`, ports +8080/8443, paths `/archive` → `/mnt/user/Timelapse`, `/space` → `/mnt/user0/Timelapse` +(*Array view*, read-only, optional: the same share seen on the array only, so the admin +panel shows the array's free space, §14.8), `/data` → `/mnt/user/appdata/chronos`, +variables from §14.9 (admin user/password, DB host/port/name/user/password, TLS mode, +*Space path* `CHRONOS_SPACE_PATH=/space` (advanced), PUID/PGID, TZ; amended 2026-10-26, R2), +description ≤ 2 sentences. Registry and Project `https://gitea.encke-hake.ts.net/BalboSoft/Chronos`, Support `https://gitea.encke-hake.ts.net/BalboSoft/Chronos/issues`, TemplateURL `https://gitea.encke-hake.ts.net/BalboSoft/Chronos/raw/branch/main/deploy/unraid/chronos.xml`, Icon `https://gitea.encke-hake.ts.net/BalboSoft/Chronos/raw/branch/main/branding/chronos-server.svg`; @@ -1442,6 +1512,11 @@ questions asked and the answers; DECISIONS rows give the reasons. | 2026-10-23 | Chronos on Gitea, R1 | whole brief, §23 | The product and its programs are named Chronos (Chronos, Chronos Server, Chronos Uploader) everywhere: projects and namespaces, files, settings, `CHRONOS_*` variables, `%LOCALAPPDATA%\Chronos`, `.chronos` project bundles and folders, the image `chronos-server`; the product name is no longer an open decision. | | 2026-10-23 | Chronos on Gitea, R2 | §3, §16, §18, §19.4, §19.6, §21, §22 | The repository is `BalboSoft/Chronos` on the self-hosted Gitea (`https://gitea.encke-hake.ts.net`): the update check reads the Gitea releases API of `ChronosReleasesUrl`; licence, issue and support links, the Unraid template and the ads manifest point to that repository; images go to the Gitea container registry; releases are published in the repository itself, a separate public releases repository is optional (`RELEASES_REPO`); `EULA.md` and `SECURITY.md` at the root, issue forms in `.gitea/ISSUE_TEMPLATE`. | | 2026-10-23 | Chronos on Gitea, R3 | §0.2, §18, §19.1, §19.2, §19.3, §19.5, §20.2, Appendix A | Gitea Actions on a Linux act_runner in Docker mode: CI jobs build, postgres, docker and yaml, plus a windows job once a Windows runner is registered; shell steps only, no artifacts, caches, job summaries or annotations; the release cross-compiles the Windows programs on Linux, checks them with `pe-check`, signs them with `osslsigncode` when secrets exist, publishes them with `gitea-release` and pushes a `linux/amd64` image with `REGISTRY_TOKEN`; Definition of Done is green on Gitea Actions, the Windows-only tests on a Windows runner or a Windows PC. | +| 2026-10-26 | Owner review 2, R1 | §19.3, §19.5, §19.6 | `:latest` follows the highest stable release, or the highest pre-release while none is stable, as decided by `Chronos.Tools release-channels` by SemVer 2.0 precedence; the releases repository's content and the update check still follow stable releases only; `:nightly` is the nightly build of `main`, never a release. | +| 2026-10-26 | Owner review 2, R2 | §14.4, §14.8, §14.9, §19.6 | `CHRONOS_SPACE_PATH` (`SpacePath`) names the volume whose free space the admin panel shows, the Unraid template mapping the share's array view `/mnt/user0/` read-only to `/space`; the archive's own volume shows apart as *Write volume* when it differs; the figures' tooltip names the file system (`fuse.shfs` from mountinfo); completing an upload checks the archive's own volume first (507, resumable). | +| 2026-10-26 | Owner review 2, R4 | §12.1, §14.8 | The Settings icon is a toothed gear in Chronos, the Uploader and the admin panel; the admin panel docks Settings at the foot of its sidebar (the end of the top bar on narrow screens). | +| 2026-10-26 | Owner review 2, R5 | §12.1, §12.8, §12.9, §14.8 | About is the last page of the desktop Settings and the last group of the admin panel's Settings, no longer a rail or sidebar entry; nothing is offered twice (update check and releases on Updates, data folder and diagnostics on Advanced); `#/about` opens the admin Settings on About. | +| 2026-10-26 | Owner review 2, R9 | §12.4, §13 | Import › Folder… can group the folder as *Whole folder*: one sequence per file format whatever the cameras and pauses, titled after the folder, with a session key per PC, folder and format so a repeated import adds to the same sequence; desktop only. | ## Appendix A — `CLAUDE.md` content (create verbatim in Phase 0, keep updated) diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md index 10f95f10..908d6ab5 100644 --- a/docs/CHANGELOG.md +++ b/docs/CHANGELOG.md @@ -5,6 +5,42 @@ commits follow Conventional Commits (release notes are generated from them by `C ## [Unreleased] +### Added +- Import › Folder…: **Group › Whole folder** imports the picked folder, with its subfolders when Subfolders is on, as + one sequence per file format, whatever the cameras and pauses (RAW+JPEG stays two sequences). The title defaults to + the folder's name, and an interrupted or repeated import of the folder continues the same sequence. Desktop only + (owner review 2, R9). +- Server: `CHRONOS_SPACE_PATH` (`SpacePath` in `server.json`) makes the admin panel show the free space of that + folder's volume instead of the archive's. The Unraid template maps the share's array view (`/mnt/user0/Timelapse`) + read-only to `/space` (*Array view*), so the dashboard shows the array's free space, not the cache's (owner review 2, + R2). +- Admin panel: the storage figures' tooltip names the volume and its file system, and on an Unraid share without a + space path explains that they are the share's primary storage; a *Write volume* line shows the archive's own volume + when it differs. +- Server diagnostics: the environment report lists the archive, space and data volumes with their free space, file + system and mount. +- `Chronos.Tools release-channels`: which channels a release tag moves (`latest=`, `image_latest=`), by SemVer 2.0 + precedence among the published releases. + +### Changed +- Server image: `:latest` now follows the highest stable release, or the highest pre-release while no stable release + exists, so the Unraid template and the compose file find an image from the first pre-release on. The public + releases repository still follows stable releases only, and re-publishing an older tag never moves either back. + `:nightly` stays the nightly build of `main`, for testing only (owner review 2, R1). +- Desktop: About is the last page of Settings and the rail keeps Settings alone at the bottom. *Check for updates* + and the Releases link are on Settings › Updates; the data folder and the diagnostics bundle are on Settings › + Advanced only (About's own copies of those buttons are gone) (owner review 2, R5). +- Admin panel: Settings sits at the foot of the sidebar, above your account (at the end of the top bar on narrow + screens), and About is the last section of Settings, without the server name and certificate fingerprint already + shown above it; old `#/about` links open it there (owner review 2, R4, R5). +- The Settings icon is a toothed gear in Chronos, the Uploader and the admin panel; it no longer looks like a sun + (owner review 2, R4). + +### Fixed +- Server: completing an upload, a render upload or a render node's result now checks the archive volume's free space + first. A full volume answers 507 `insufficient_storage` and the upload stays resumable, instead of the copy into + staging failing (owner review 2, R2). + ## [0.1.0-rc.2] — 2026-10-23 ### Fixed diff --git a/docs/DECISIONS.md b/docs/DECISIONS.md index 9016cf49..33df34ef 100644 --- a/docs/DECISIONS.md +++ b/docs/DECISIONS.md @@ -429,3 +429,15 @@ One line per decision: date · decision · alternative · reason. | 2026-10-23 | Update check: the client reads the published stable releases and takes the highest version, because Gitea's `releases/latest` is the most recently created release (a re-published older tag or a backport would become it); a pre-release build (`0.1.0-rc.1`) is offered the final release of its own version, which it used to call "up to date" forever; a 404 is a failed check, because Gitea answers 404 for a repository the client may not see (the `BalboSoft` organisation is private today) and that used to read as "up to date". The release workflow picks `:latest` the same way. `gitea-release` checks every file's size before it publishes, and when it replaces the files of a release clients can already see it removes the old `SHA256SUMS` first and uploads the new one last. (R2, R3; independent review of this change.) | Trust `releases/latest`; leave the pre-release rule as it was | The first release is a pre-release: its testers must be told when 0.1.0 is out; a download checked against the checksums of another build would be refused. | | 2026-10-23 | Timed tests (bulk insert, JPEG and RAW decode, resampler, light analysis, metadata robustness, scroll smoke, and the lease renewal test's timer periods) take their budget from `TestTiming.Budget`, stretched by `CHRONOS_TEST_TIME_FACTOR` (at least 1, default 1); ci.yml and release.yml set 3, perf.yml nothing. On the owner's runner, which shares its CPU and disks with Gitea and the server's other containers, the 100k-frame SQLite bulk insert took 10–19 s against 15 s from one run to the next. (R3.) | Raise the budgets; move the timed tests to perf.yml | The budgets stay what a developer's PC must meet and the weekly performance gates measure them unstretched; a CI run fails on a real regression, not on a busy host. | | 2026-10-23 | The update check builds the release page (`/releases/tag/`) and the download links (`/releases/download//`) from `ChronosReleasesUrl` and takes only the tags, names and sizes from Gitea's answer: Gitea writes `html_url` and `browser_download_url` with its ROOT_URL, the owner's being `http://192.168.30.23:3000`, so the first release's links were plain http on a LAN address and the https-only check ignored the release. Without a repository address (tests) the answer's links are used as before. (R2, after the first release.) | Ask the owner to set ROOT_URL to the public https name | The build already names the address its users reach; the client then works whatever Gitea's ROOT_URL is, and a ROOT_URL change stays the owner's choice. | +| 2026-10-26 | The server image's `:latest` follows the highest stable release, or the highest pre-release while no stable release exists; the releases repository's content and the in-app update check still follow stable releases only. `Chronos.Tools release-channels --tag --releases ` prints both answers (`latest=`, `image_latest=`) from Gitea's releases list (`releases?draft=false&limit=50`, saved by curl) by SemVer 2.0 precedence: drafts and tags that are not `v` + strict SemVer 2.0 are ignored, the tag itself always counts, a release Gitea flags `prerelease` counts as one whatever its tag, build metadata is ignored and equal precedence counts as highest; a body that is not a JSON array (a sign-in page, an API error) stops the release (exit 2). It replaces curl + grep + `sort -V` in release.yml and the 2026-10-23 rule "`:latest` only for the highest stable version". (Owner review 2, R1.) | Point the Unraid template and compose at `:nightly` or a pinned `:`; push `:latest` for every pre-release; keep `sort -V` over all releases | With only pre-releases published (v0.1.0-rc.1, rc.2) `:latest` never existed, so the template and compose found no image. Users should get the newest release, not the untested nightly build of `main`. A pre-release published after a stable one, or an older tag re-published, must not move `:latest`. `sort -V` ranks `1.0.0-rc.1` above `1.0.0`, so it cannot compare pre-releases with stable releases. | +| 2026-10-26 | The admin panel's free space comes from an optional space path (`SpacePath` in `server.json`, `CHRONOS_SPACE_PATH`): the Unraid template maps the share's array view `/mnt/user0/Timelapse` read-only to `/space` (*Array view*) and sets *Space path* to `/space` (advanced); empty means the archive's volume, as before. The archive's own volume, where uploads land, is shown apart as *Write volume*. `ArchiveStatsDto` keeps `FreeBytes`/`CapacityBytes` as the shown volume's figures and gains optional `WriteFreeBytes`, `WriteCapacityBytes`, `FileSystem` and `UsesSpacePath`. (Owner review 2, R2.) | Sum the array disks (`/mnt/disk*`) mapped into the container; read Unraid's emhttp state files; call Unraid's API | The container sees only what is mapped: one read-only mount of the same share's array view gives the array's figures with no host access, no external process and no Unraid-specific code. Only the server builds the stats and only the admin panel reads them, so the new members break no client. | +| 2026-10-26 | The file system type and mount of a folder come from `/proc/self/mountinfo` on Linux: the longest mount point that is the folder or one of its parents, of mounts stacked there the last listed, octal escapes (`\040`) decoded; elsewhere `DriveInfo.DriveFormat`. (Owner review 2, R2.) | `DriveInfo.DriveFormat` alone; `findmnt` or `stat -f` | `DriveFormat` calls a FUSE mount only "fuse", never `fuse.shfs`, which is what tells an Unraid share apart; external processes are not allowed at runtime. | +| 2026-10-26 | A space path that is missing or cannot be measured falls back to the archive's volume with one warning: at start, and again only after it has been measured in between. (Owner review 2, R2.) | Refuse to start; warn on every request | The template's default (`/space`) without the mapping must not stop the server or flood the log. | +| 2026-10-26 | The write volume is shown only when its figures differ from the space volume's: another total size, or free space more than 64 MiB apart. (Owner review 2, R2.) | Always show both; compare device ids | Two reads of one volume a moment apart differ by what was written in between; comparing figures also works on Windows. | +| 2026-10-26 | Completing a frame upload, a render upload or a render node's result first checks the archive root's volume for the upload's size + 64 MiB and answers 507 `insufficient_storage` with the upload still receiving; a volume that cannot be measured refuses nothing. The start keeps checking `/data` only. (Owner review 2, R2.) | Check only at upload start; fail the upload; check the space path | The staging copy lands on the archive's own volume (on Unraid the share's primary storage, often the cache); refusing before the state change keeps the part file, so the client can complete again once there is room. | +| 2026-10-26 | Free space comes from one injectable `VolumeSpace` service (`Server/Storage`, registered with `TryAddSingleton`; tests override `Measure`), also for the `/data` checks at upload start and for the diagnostics report, which lists the archive, the space path and `/data` with free space, file system and mount; the static `UploadRules.FreeBytes` is removed. (Owner review 2, R2.) | Keep a static helper | One source for every check, and tests can simulate a full volume. | +| 2026-10-26 | Admin panel menu in two groups: Dashboard, Users, Archive, Jobs and Logs from the top; Settings docked at the sidebar's foot above the account, or at the end of the top bar on narrow screens. `pages/about.js` is gone: About is the last, read-only group of Settings (version, API version, database, uptime counting on from when it was read), without the server name and certificate fingerprint rows that the Server and Network groups already show. `#/about` opens Settings on that group (focus on its heading) and rewrites the address to `#/settings`. (Owner review 2, R4, R5.) | Keep About as a page; an About dialog from the account box; repeat the name and fingerprint rows in About | One sidebar entry less, as the owner asked. Repeated rows on one page are noise, and the name row was stale after a save. Old bookmarks keep working. | +| 2026-10-26 | The Settings icon is an 8-tooth gear with a centre hole (outer radius 6.5, valleys on 4.6, teeth 0.6/0.85 half-width at tip/base, hole 1.7), drawn by `gear()` in `branding/ui-icons/icons.py`. The script now also writes the admin panel's `icons.js` (through a name map; the unused `about` icon dropped) and writes every file as UTF-8 with LF on every OS. (Owner review 2, R4.) | 6 teeth (crisper at 16 px but less familiar); wider hollow teeth (they merge at 16 px with 1.5 px strokes); radial stubs on a ring (close to the old sun); keep `icons.js` by hand | 8 narrow teeth close up into solid knobs at 16 px with open gaps, read as the usual settings gear at 20–32 px and stay distinct from Sun. One generator keeps the desktop and web paths identical. On Windows the script wrote `Icons.xaml` in the ANSI code page, garbling its header. | +| 2026-10-26 | Desktop About becomes the last Settings page (`SettingsPage.About`); `SectionKey.About` and `AboutView` are gone and the rail keeps Settings alone at the bottom. `AboutViewModel` (now `Chronos.App.About`) stays a view model owned by the shell (`Shell.About`), not a section, so the Updates page's bindings and the update check on start are unchanged. The page shows identity only (version, build, runtime, system, licence, third-party notice, translation notice outside English) and has no Reset section; the Releases link moved to Updates › Latest version; About's own diagnostics bundle and Open data folder buttons are removed (Advanced has both). (Owner review 2, R5.) | Move `UpdateFlow` into `SettingsViewModel`; embed the old AboutView inside Settings; repeat the data folder, diagnostics and update rows on About | Smallest change that keeps every `Shell.About` binding and the update check on start; one place per action avoids duplicates inside Settings, and saving space is what the owner asked for. Nothing navigated to the About section, so no link needed redirecting. | +| 2026-10-26 | Import › Folder… *Whole folder* (`ImportGrouping.WholeFolder`) makes one sequence per file format: camera bodies and pauses are ignored, formats are not; only the user's splits break it (the session splitter runs with no gap and a minimum of 1). The title defaults to the folder's name and fills `{title}`; a typed title wins. The plan row shows "Canon EOS R5 · CR3" or "2 cameras · JPEG", and a split part merges back into the part before it of the same format. Switching the grouping clears the user's splits and merges. (Owner review 2, R9.) | One sequence holding every file; one sequence per camera body | A folder shot RAW+JPEG would otherwise hold every instant twice, doubling the time-lapse; formats also decode and render differently. Bodies are ignored because the owner asked for the folder's sequence "in its entirety". | +| 2026-10-26 | A whole folder's session key is `folder-` + the first 16 hex digits of SHA-256 of "PC name, full path (trailing separator trimmed, upper-cased on Windows), format", plus `-yyyyMMdd-HHmmss` of the first photo for a part the user split off. The grouping is not stored in card profiles: a folder starts on Sessions, and cards and drives are always planned by sessions. (Owner review 2, R9.) | Hash of path and format only; remember the grouping per folder | The same key for the same folder lets an interrupted or repeated import continue its sequence through the existing session-key lookup. The server files client uploads by session key without user scope, so the same `D:\Photos\Trip` on two PCs must not land in one sequence; renaming the PC starts a new one (hash duplicate detection still prevents doubled frames). Folder sources have no profile today, so the simplest safe default applies. | diff --git a/docs/STATUS.md b/docs/STATUS.md index bd66700d..466ebfd0 100644 --- a/docs/STATUS.md +++ b/docs/STATUS.md @@ -14,8 +14,9 @@ by its `windows` job once a Windows runner is registered (`WINDOWS_RUNNER`), and | 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: 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; their server images wait for the `REGISTRY_TOKEN` secret. | +| 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/` 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) @@ -48,10 +49,21 @@ src/Chronos.App/bin/Release/net10.0-windows/Chronos.exe --capture out/screenshot - 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: About › *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. +- 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/` 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. @@ -65,19 +77,38 @@ src/Chronos.App/bin/Release/net10.0-windows/Chronos.exe --capture out/screenshot 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 (Phase 8 gate) +## Next steps -1. Server image: create an access token with *package: read and write*, save it as the repository secret - `REGISTRY_TOKEN`, then re-run the *Server image* job of the `v0.1.0-rc.2` release run (Actions › Release). -2. 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. -3. 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 - ` 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. -4. On Windows: install the `v0.1.0-rc.2` setup, upgrade over the previous version, uninstall (with and without user - data), silent mode. -5. 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. -6. Native-speaker review of the machine translations where users report wording (`i18n export` per language). +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: + +12. 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. +13. 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 ` 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. +14. On Windows: install the latest pre-release's setup, upgrade over the previous version, uninstall (with and without + user data), silent mode. +15. 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*. +16. Native-speaker review of the machine translations where users report wording (`i18n export` per language). diff --git a/docs/requests/2026-10-26-owner-review-2.md b/docs/requests/2026-10-26-owner-review-2.md index c93efef6..eebb080c 100644 --- a/docs/requests/2026-10-26-owner-review-2.md +++ b/docs/requests/2026-10-26-owner-review-2.md @@ -69,7 +69,7 @@ | Phase | Content | State | Commit | |---|---|---|---| -| 1 | R1 `:latest`, R2 array space, R4 gear and Settings at the bottom, R5 About inside Settings, R9 whole-folder import | in progress | | +| 1 | R1 `:latest`, R2 array space, R4 gear and Settings at the bottom, R5 About inside Settings, R9 whole-folder import | implemented 2026-10-26: BRIEF §12.1, §12.4, §12.8, §12.9, §13, §14.4, §14.8, §14.9, §19.3, §19.5, §19.6, §24; 12 DECISIONS rows dated 2026-10-26 (R1 `:latest` and `release-channels`; R2 space path, mountinfo file system, fall-back warning, write volume, 507 at completion, `VolumeSpace`; R4/R5 admin menu and About group; R4 gear icon and `icons.py` generating `icons.js`; R5 desktop About page; R9 whole-folder grouping and its session key); CHANGELOG [Unreleased]; STATUS 8.3. `:latest` appears with the next pre-release: re-publishing `v0.1.0-rc.2` builds the tag's `Chronos.Tools`, which lacks `release-channels` | | | 2 | R11 log settings, R10 scheduled jobs (migration 0007) | todo | | | 3 | R6 library on the panel, photo delete and trash (migration 0008), R3 web upload | todo | | | 4a | R7 Reorganize after import | todo | |