The fourth verification round of the matches work found 18 defects in the merge, Integrate and Matches surfaces. This commit fixes them: - An Integrate job now carries the planning account's id, so its re-plan decides ownership the way the dialog did. - A merge skips only a project the kept sequence holds a real copy of (name, offset head and history content) and re-points its renders to that copy. - A merge runs its trash checks before the Links stage and records an undo, so an abandoned merge gives the other sequence back its link, session keys and pairs. - The metered hold adopts automatic transfers that were paused before a restart. - Apply in the Compare dialog re-plans when the plan is pending or stale. - The Library's Two versions... lists the second versions a Union merge leaves, each with Drop... (dry run, confirmation, verified partner). A merge job's Open shows that list. - The merge's typed confirmation is the invariant count, and the prompt names it in all 38 languages. - Italian text uses Principale and Gemello. The Main project is named through WorkspaceText in the Projects part and in the twin tooltip. - The session keys tooltip is split into two keys, and To trash... and Delete on server... say why they are disabled. - The capture restores the editor account before the Matches scenes. - Upload again follows SyncHost.CanSendSync (Upload with Edit). - Matches rows trim archive names in the middle on a rebalanced grid; the Projects part rows trim, with the full text in the tooltip. - The sample project targets use ProjectTransplant.FreeName. DECISIONS, CHANGELOG, STATUS 8.7, the request doc and the 16 changed capture baselines are updated. Refs #73 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Screenshot baselines
The approved look of every screen, one PNG per --capture screenshot (<screen>-<theme>.png, as Chronos.exe,
Chronos.Uploader.exe and Chronos.Setup.exe --capture <dir> write them). CI compares each new screenshot with the
file of the same name here (BRIEF §20.2, visual regression with a pixel-diff tolerance):
dotnet run --project src/Chronos.Tools -- screenshots diff out/screenshots --out out/screenshot-diff
- A pixel differs when one of its channels moves by more than
--tolerance(default 8 of 255); a screen fails when more than--max-diffof its pixels differ (default 0.0005, that is 0.05 %), when its size changed, or when a baseline here has no screenshot any more. - A screenshot without a baseline fails as soon as this folder holds any PNG: a pull request that adds a screen adds its baselines too.
- While this folder holds no PNG nothing is compared: the step passes, with a warning in the log saying that no visual change can fail it.
out/screenshot-diffgets<screen>-diff.pngfor every screen with differing pixels (the baseline faded to grey, the differences magenta) andsummary.md; they stay in the work folder of the Windows runner (Gitea Actions keeps no artifacts here), and the job log lists every screen that failed.
The pictures are reproducible
The capture runs on sample data whose clock stands at SampleData.Now (2026-10-02 10:18 UTC), in English with English
formats and with animations off, so the same code draws the same pixels on any day. What the screens measure on
the machine is shown as fixed sample values while the clock is frozen (AppClock): free space (1.2 TB), the
server's response time (12 ms) and the time and duration of the last sync comparison. The capture's data folder is a
new one in the machine's temporary folder, but the screens show it as a sample user's (C:\Users\Studio\AppData\Local\Chronos,
its sample archive as D:\ChronosArchive: AppEnvironment.Shown; the videos folder is set to D:\Videos\Chronos), so neither the temporary folder nor the user name
reaches a picture; a path typed over a shown one goes back to the temporary folder (AppEnvironment.Actual), so the
capture writes nowhere else. Two captures made with different TEMP folders are identical. Two things still come from the
machine: the time zone (times are shown in local time; the baselines are made in the development PC's, Europe/Rome,
which the Windows runner must share) and the fonts and scaling of Windows itself.
Adding or updating baselines
Capture them on the development PC, the one where the Windows runner is registered (fonts, scaling and the time zone differ per machine), from a Release build of the branch that changes the screens:
dotnet build Chronos.slnx -c Release
src/Chronos.App/bin/Release/net10.0-windows/Chronos.exe --capture out/screenshots
src/Chronos.Uploader/bin/Release/net10.0-windows/Chronos.Uploader.exe --capture out/screenshots
src/Chronos.Setup/bin/Release/net10.0-windows/Chronos.Setup.exe --capture out/screenshots
dotnet run --project src/Chronos.Tools -- screenshots diff out/screenshots
dotnet run --project src/Chronos.Tools -- screenshots accept out/screenshots
screenshots accept <dir> copies every PNG of <dir> here. Commit only the screens whose change is intended, and delete
the baseline of a screen that no longer exists. If the Windows runner is ever registered on another PC, accept a new
set captured there in one commit.
The first baselines
The first set (156 screens) was captured on the development PC on 2026-11-04 (owner review 3, R2), at SampleData.Now,
and is committed with the ports fix of v0.1.0-rc.9. Until a Windows runner is registered, CI skips the windows job
and nothing compares them: run screenshots diff locally before a pull request that touches a screen.