Owner review 6 asks Chronos to recognise the same time-lapse on a server
and on this PC, show the differences and let the user keep the two apart
or integrate and sync them. The request file keeps the owner's words, the
reading R1-R8, the eight answers and the delivery plan; the brief now
describes matches, the Compare dialog, Integrate, the merge of two local
sequences, the automatic photos of integrated pairs, the photo lookup and
uploads into a target, and amends 14.5 so other projects cross only through
Integrate or a merge. DECISIONS records the design choices and those taken
while building it; the changelog, status, architecture and design notes
follow, and the version moves to 1.2.0.
Refs #73
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Windows hands-on test of v1.1.0 on the development PC (#70).
- The App suite runs whole on Windows again. Five stale screen smoke tests are brought up to date.
- The Reorganize capture gives the sample sidecars.
- Forget fits in the Bulgarian certificate rows.
- The job log shows local time. It stays UTC on disk, and lines are dated backwards from the job's end.
- The Jobs and Server › Jobs Type column takes a 1* share (90–170 px).
- Builds without a tag say 1.1.1.
Closes#70
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
Builds without a release tag say 1.0.0; CHANGELOG [1.0.0] and [0.1.0-rc.14]; STATUS, DECISIONS and the request files record rc.14 and 1.0.0.
Closes#23
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
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>
F5 in VS Code now starts Titano, the Uploader and the server under the C#
extension's debugger, as well as the --capture runs, Titano.Tools and the test
programs. Each configuration builds in Debug first and starts the program's
.exe rather than its .dll, because the programs read Environment.ProcessPath
(Setup's payload, the Run keys and tray icons). The server's session keeps its
data and archive in out/debug/server instead of %ProgramData% and
C:\TitanoArchive.
The build tasks use no reused MSBuild nodes, whose cached drive-letter case
made every F5 build restore and C# Dev Kit reload, and keep MSB3026 (a copy
that succeeds on a retry) a warning so a file held for a moment no longer
stops F5.
Design-time builds skip the icon generation, which on a fresh clone ran a
Titano.Tools.dll that did not exist yet (MSB3073 in VS Code), and log WPF's
MC1000 about projects not built yet as a message.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
RF-3: the anonymous usage counts checkbox (Welcome and Settings › General) promised a
daily ping that does not exist; BRIEF §21 puts that consent inside monetization, which
ships disabled until the human flips TitanoAdsEnabled=true. Directory.Build.props now
defines the property (default false) and stamps it into every assembly as metadata;
ProductFeatures.AdsEnabled reads it, and both checkboxes and the Settings search
keyword follow it. The unused Shell.Welcome.Consent sentence is removed from every
culture.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
- Titano.Ui: DESIGN.md tokens (dark/light), generated 16-px icon set,
styles for all standard controls, custom chrome window with snap
layouts, rail, job bar, Auto/manual slider, chips, toasts.
- Titano desktop shell with sections, Settings (language, theme),
About and a --capture screenshot mode.
- Titano Server skeleton: env/server.json configuration, self-signed
TLS with fingerprint, /health, /server/info, i18n endpoint and the
embedded admin panel; in-process server tests.
- Docker image (multi-arch, PUID/PGID, health check), compose file,
Unraid template; CI, release and nightly workflows; changelog tool.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC