A screenshot without a baseline only warned, so with no baseline committed every
screen was "new" and the CI step could not fail, and a screen added after the
first baselines could stay ungated for good. Now the baseline folder is armed as
soon as it holds a PNG: from then on a screen without its own baseline fails
(Verdict.Unbased, an error annotation). Before the first baselines the run says
plainly, in its warning and in bold in the job summary, that it compared nothing
and that no visual change can fail it.
The baselines README explains why the existing ci-screenshots pictures cannot
serve (captured before the clock was fixed: times and dates follow the capture
moment) and how the first set is accepted from the first green windows-latest
run of the reproducible capture.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
BRIEF §20.2 asks for visual regression of the --capture screenshots with a
pixel-diff tolerance; CI only published them. `Titano.Tools screenshots diff
<dir>` compares every PNG with tests/visual/baselines: a pixel differs when a
channel moves by more than --tolerance (8 of 255), and a screen fails when more
than --max-diff of its pixels differ (0.05 %), when its size changed or when a
baseline lost its screen; a screen without a baseline only warns. It writes a
diff image per screen with differing pixels (the baseline faded, the differences
magenta) and a Markdown summary, also to the GitHub job summary.
`screenshots accept <dir>` copies screenshots over the baselines. The baselines
folder starts with its README; the pictures come later from ci-screenshots.
The captures were not reproducible: the sample's jobs, renders, transfers,
cards, trash and remote sequences were dated from the clock, the Library
timeline and the Archive heatmap laid out around today, the Uploader captured
in the computer's language and an indeterminate bar animated. The sample now
dates everything from SampleData.Now, --capture freezes the new AppClock there,
formats are English, and the new Motion attached property (off in the captured
windows) keeps the indeterminate sweep still in the middle.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC