videos-board is new; videos, videos-list, the Export footer and the Render
menu changed with the preset-first card line and sizes kept whole (#28).
Refs #29#28
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Translate the 40 keys of the work board, the archive folder structure and
the Create archive prompt. STATUS gets how to try rc.14; BRIEF §14.9 and the
Dockerfile say releases publish linux/amd64 only, as release.yml does.
Refs #29#31#22
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Settings no longer makes a folder an archive on its own: a typed or
picked folder without archive.json is made one only after a
confirmation naming it, and Settings > Import keeps this PC's archive
folder and never creates one. A half-typed path or another PC's drive
letter could otherwise get .chronos and sidecars written unasked.
The server's structure check creates nothing in a root that lost its
archive.json (an unmounted disk's empty mount point) and reports it
unavailable; /health re-checks when its last check is over 10 s old,
so a fix on the host shows without a dashboard read.
The admin board reads the server newest first with Order off, counts
Published over the server's total, and a Shift range runs along the
lane picked in. Admin sizes keep number and unit together. A sent
workspace render whose file left exports/ is no longer listed as
missing. Desktop Board cards put their actions under the text while
the player is open. Start-up range errors name the CHRONOS_* variable;
the deploy guide documents the parallelism clamp and the log rule.
Refs #29#31
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The phase 6 docs were written before the board, no-usage and archive
layout parcels landed: the BRIEF section 24 rows now name the sections
actually amended, sections 7, 12.10 and 14.8 describe the board and the
archive's root folder tree, and the Docker guide explains the start-up
layout and the "Archive incomplete" warning. The phase 5 changelog moves
under rc.13 and [Unreleased] carries the rc.14 work.
Refs #29#30#31#22
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Videos section and the admin Videos page gain a Board view with two
lanes, newest first, each with a count and the list's filters: Published
(library and server renders, including those sent from a workspace) and
Workspace (workspace exports, unsent ones plus sent ones marked Sent).
Cards show the sequence, project and version when known, preset, kind,
date and state chips, and reuse the existing actions; no new store.
Video cards now start with the preset ("4K archive · HEVC · 0:41 · 1.4 GB")
and Formatting.Bytes keeps number and unit together with a no-break space
(#28). The capture tool adds the videos-board scene in both themes.
Refs #29
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The owner asked (2026-11-06) that whatever path is given as the archive
root, on the server in Docker or on Windows, Chronos creates inside it
every folder the archive keeps. Until now only .chronos was made up
front; locks, journal, staging, trash and its photos and videos areas
appeared on first use, and an archive copied or made by an older build
could lack them.
ArchiveStructure.Ensure (Core) creates the missing folders of BRIEF §7
idempotently, never touching existing folders or files, and reports why
it could not (drive or share unavailable, permission denied, read-only,
a file in the way) as one localized sentence. ArchiveService runs it
when it creates an archive (refused with the reason when the tree cannot
be made) and at every open. The server checks it at start-up and on
each dashboard read: it logs a warning, the dashboard shows an "Archive
incomplete" chip with the reason, and /health reports archive
"incomplete". The desktop runs it when an archive is created, adopted or
opened at start, and a folder typed in Settings that is not an archive
yet becomes one in place, as Welcome's Create does; a writable archive
whose tree cannot be completed is refused with the reason.
Refs #31
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 1 phase 6 asks for Docker, Unraid and deploy documentation. docs/deploy/
now covers the image tags, volumes, every CHRONOS_* variable with its default, ports and
public ports (the owner's host 8087/8444 mapping), TLS modes and the fingerprint,
upgrades and forward-only migrations, backup and restore, PostgreSQL, troubleshooting,
and the desktop Setup, portable mode and update channel.
The owner review 4 request (2026-11-06) is recorded with its interpretation and plan;
BRIEF §14.9 lists CHRONOS_TRUSTED_PROXIES, which the server already read, §19.6 points
to the Unraid guide, and §24 gains the rows of owner review 4 and phase 6. STATUS shows
both in progress for v0.1.0-rc.14, then v1.0.0.
Refs #22
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The owner does not want Chronos to send data about its use, and nothing
ever sent the counts the consent promised. The first-run checkbox, the
Settings > General row, the AnonymousUsageCounts setting and its three
strings in every culture are gone; a settings file that still carries the
member loads and is saved without it. BRIEF §21, the EULA and the Welcome
mockup now say Chronos sends nothing about its use; the diagnostics
bundle stays, saved only locally.
Refs #30
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The documentation the project started from (then called Titano), frozen under
docs/reference/original for history; the current docs win where they differ.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>