Commit Graph
5 Commits
Author SHA1 Message Date
Alby96andClaude Opus 5.5 bc4d8e0768 fix(app): captures show no machine paths, Server row actions stay on one line
The capture's data folder lives in the machine's temporary folder, so 8
baselines showed %TEMP% and the user name and differed on any other machine.
AppEnvironment.Shown now shows a capture's folders as a sample user's
(C:\Users\Studio\AppData\Local\Chronos, the sample archive as D:\ChronosArchive)
in Settings > Storage, Workspace and Advanced, the Rebuild index dialog and the
cache's Clear confirmation; AppEnvironment.Actual maps a typed path back, so the
capture still writes only to its temporary folder. Two captures with different
TEMP folders are identical.

On the Server screen the row actions column is at least 400 px wide, so a
remote row's three actions (an older server's disabled Open in workspace after
Open with proxies and Download originals, as BRIEF 12.7 asks) fit one 40 px
line at the capture size instead of wrapping.

Baselines recaptured: server, server-sync, server-conflict, server-signedout
(column layout; the disabled action of phase 5b), settings-storage,
settings-workspace, settings-advanced and archive-rebuild (sample paths), light
and dark.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-04 13:54:26 +01:00
Alby96andClaude Opus 5.5 7273eec2bb feat: screenshot baselines from the development PC, fixed capture values, ports strings in all languages
The owner chose to capture the baselines on the development PC (owner
review 3, R2): 156 screens go to tests/visual/baselines and CI no longer
pushes a ci-screenshots branch. While --capture freezes AppClock, free
space, a server's latency and the last sync are fixed sample values; they
moved the Server and Import screens past the diff tolerance at random.
The 22 new or changed Admin strings are translated into the 36 other
languages, and the request file records the owner's text and answers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-04 11:04:23 +01:00
Alby96andClaude Opus 5.5 f2b58522b9 refactor!: rename Titano to Chronos and move CI and releases to Gitea (#6)
CI / Build and test (push) Successful in 8m14s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 7s
Release / Build, test and publish (push) Successful in 13m19s
CI / PostgreSQL 16 integration (push) Successful in 4m49s
CI / PostgreSQL 17 integration (push) Successful in 5m28s
CI / Docker image (push) Successful in 53s
Release / Server image (push) Failing after 10s
The owner renamed the product and moved the repository to the self-hosted
Gitea (https://gitea.encke-hake.ts.net/BalboSoft/Chronos) for more control,
and asked for Actions and a first automatic release with the server package
and the Windows exe (docs/requests/2026-10-23-chronos-gitea.md).

- Chronos everywhere: a byte-exact rename of contents and paths, then a
  per-language review of the forms the old name's ending had dictated.
- Gitea instead of GitHub: the update check, licence, issue and support
  links read ChronosReleasesUrl; the update check takes the highest stable
  version, offers a pre-release build its final release and reports a
  repository it cannot see as a failed check. EULA, security policy and
  Gitea issue forms live at the repository root.
- Gitea Actions for the Linux act_runner (.gitea/workflows): CI, release,
  nightly image and performance gates in the .NET SDK container with git
  checkout and the system SQLite. The release cross-compiles the Windows
  programs, checks their icon, version and DPI manifest, packs installers
  and zips, publishes the Gitea release and pushes the server image
  (REGISTRY_TOKEN). Windows-only tests run in an opt-in job on a Windows
  runner (WINDOWS_RUNNER).
- New Chronos.Tools commands: zip, gitea-release, postgres-ci (replaces the
  docker-exec script, which Gitea's service containers do not allow; the
  throw-away server runs without durability) and pe-check.
- Timed tests take their budget from TestTiming (CHRONOS_TEST_TIME_FACTOR,
  3 on the shared runner; the weekly performance gates keep theirs).

BREAKING CHANGE: programs, settings, data folders, file types, environment
variables and the Docker image use the new name; nothing is migrated from
Titano, which never had a release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
2026-10-23 12:45:18 +02:00
Claude 2c643fba96 fix(tools): screenshot diff fails a screen without a baseline once any is committed
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
2026-10-12 10:34:25 +00:00
Claude e583b6ed74 feat(tools): screenshot diff against committed baselines, reproducible captures
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
2026-10-12 10:05:49 +00:00