Owner review 2, R8, phase 5b: a Chronos Server becomes a project home, as a PC's archive already is (phase 5a).
What changes
Server:/api/v1/sequences/{id}/projects (list, create, rename, delete, versions with paging, head, push with fast-forward / idempotent / project_diverged / hash checks), the projects capability and the projectChanged WebSocket event. Settings written by older clients, analyses, linked-copy sync or conversions become a new Main version. A settings PATCH also writes project.json under the sequence's lease.
Desktop:Open in workspace for a server's sequences (Edit and the Server screen), proxies downloaded into the workspace (hash-checked, resumable), and Save version, Sync, conflicts, History, Restore, New, Rename, Delete and Remove local copy against the server. Projects keep working offline and show Server newer / Not on server.
Renders can target a project version; the server and render nodes record it.
Admin panel: the sequence page lists projects and versions, with Rename and Delete for projects other than Main.
Translations: 119 new strings in all 38 languages.
Review
One adversarial round with 21 findings, 19 fixed, then a checker pass (P1–P4 fixed). F3 (History downloads every version's settings) is partly fixed and listed under known limitations in the CHANGELOG.
How to try it
Update the server (chronos-server:0.1.0-rc.10) and the desktop (installer from the release).
In Chronos, go to Server › a sequence › Open in workspace, then pick Main or a new project.
Edit, use Save version, then Sync. The admin panel's sequence page shows the new version.
Checks
dotnet build -c Release: 0 warnings.
i18n check: 4451 keys, 38 cultures, 0 warnings.
Local suites: Core 1368, Data 844, Server 317, App 774 passed, 0 failed (App without the classes that hang on this PC).
Owner review 2, R8, phase 5b: a Chronos Server becomes a project home, as a PC's archive already is (phase 5a).
## What changes
- **Server:** `/api/v1/sequences/{id}/projects` (list, create, rename, delete, versions with paging, head, push with fast-forward / idempotent / `project_diverged` / hash checks), the `projects` capability and the `projectChanged` WebSocket event. Settings written by older clients, analyses, linked-copy sync or conversions become a new Main version. A settings `PATCH` also writes `project.json` under the sequence's lease.
- **Desktop:** *Open in workspace* for a server's sequences (Edit and the Server screen), proxies downloaded into the workspace (hash-checked, resumable), and Save version, Sync, conflicts, History, Restore, New, Rename, Delete and Remove local copy against the server. Projects keep working offline and show *Server newer* / *Not on server*.
- **Renders** can target a project version; the server and render nodes record it.
- **Admin panel:** the sequence page lists projects and versions, with Rename and Delete for projects other than Main.
- **Translations:** 119 new strings in all 38 languages.
## Review
One adversarial round with 21 findings, 19 fixed, then a checker pass (P1–P4 fixed). F3 (History downloads every version's settings) is partly fixed and listed under known limitations in the CHANGELOG.
## How to try it
1. Update the server (`chronos-server:0.1.0-rc.10`) and the desktop (installer from the release).
2. In Chronos, go to Server › a sequence › *Open in workspace*, then pick Main or a new project.
3. Edit, use *Save version*, then *Sync*. The admin panel's sequence page shows the new version.
## Checks
- `dotnet build -c Release`: 0 warnings.
- `i18n check`: 4451 keys, 38 cultures, 0 warnings.
- Local suites: Core 1368, Data 844, Server 317, App 774 passed, 0 failed (App without the classes that hang on this PC).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The owner's Uploader could not connect: the panel showed the container's
listening ports (8080/8443) as if clients used them, the public ports were
only environment variables (CHRONOS_PUBLIC_HTTP_PORT not even in the Unraid
template), and the clients mapped a bare host to 443, where another service
answered.
- Public HTTP/HTTPS ports are settings (server.json, or locked by
CHRONOS_PUBLIC_*) and apply at once; ServerSettingsDto gains appended
PublicHttpPort, PublicHttpsPort and InContainer members.
- In a container the listening ports are fixed by the template: locked in the
panel, and saved values from earlier versions are ignored with a warning.
- Settings > Network and TLS shows the client address with a Copy button; the
discovery tooltip says a container needs network type Host.
- ChronosAddress (shared by Chronos and the Uploader): no scheme and no port is
https on 8443, https:// keeps 443, a typed port is kept, IPv6 is bracketed.
- GetInfoAsync throws NotChronosServerException for answers that are not a
Chronos server; another service's certificate is never offered for trust
and no credentials are sent to it. Both clients name the address asked.
- Unraid template, compose file, user guide, README, BRIEF, DECISIONS,
CHANGELOG (with an Unraid upgrade note) and ARCHITECTURE updated; en/it
strings added.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review fixes on top of the public ports change (owner review 3):
- Settings > Network and TLS: opened over HTTPS, the client address uses the port
the page came through (a container's 8443 published as 8444 with Public HTTPS
port still empty showed the wrong 8443), and a "Use <port>" button fills that
port in. Saving a Public HTTPS port other than the page's asks first, since the
HTTPS redirect follows it at once and a typo would lock the panel's link out.
- GetInfoAsync tells Chronos from other services by stricter rules on both the
trusted and the untrusted-certificate path: any redirect, any answer that is not
JSON, more than 1 MB, or an error without the X-Chronos-Api header is not
Chronos. Another service's certificate is no longer offered for trust after a
cross-scheme redirect, an error page or a JSON 401/403/404, and a JSON 401 over
HTTP no longer reads as a wrong password.
- The HTTP port typed without a scheme (TLS to a plain HTTP port) now gives the
not-Chronos error instead of "the server did not answer".
- The Uploader's certificate question names the address with its port.
- A link-local IPv6 address with a zone index is refused instead of losing it.
- In a container, the first save of the settings removes HttpPort/HttpsPort from
server.json, so the start-up warning stops; the warning says so.
- Guide, README, compose and template: with network type Host the mappings do
nothing and CHRONOS_HTTP_PORT / CHRONOS_HTTPS_PORT move the listening ports off
ones another service uses; the template overview is back to two sentences.
- BRIEF, DECISIONS and CHANGELOG updated; en/it strings added.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The identity check reads Chronos's error body to tell it from another
service; GetInfoAsync then read it again and threw ObjectDisposedException.
The identity now carries the parsed error and GetInfoAsync throws it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
Owner review 2, phase 5b (R8): a server is a project home. A workspace can
list a sequence's projects, make, rename and delete them, read their
versions and push new ones through /api/v1/sequences/{sid}/projects. The
endpoints run on the archive's ProjectService exactly as a desktop's archive
does (sidecars first, then the index, under the sequence's lease), so no
version is stored apart and a desktop sharing the archive sees the same
projects.
- Protocol: project, version, create, rename, version page, push answer
(outcome, stored version, head, plus code and message on 409/422) and
home frames DTOs, the projectChanged event, the "projects" capability and
the ChronosClient calls; a push returns its outcome without throwing on
409 or 422. ProjectWire maps them to and from the model for both sides.
- Server: Read lists and reads, Edit makes, renames and pushes, Delete (the
sequence's owner, the project's maker or an admin) deletes; refusals with
stable codes, 503 while the sequence is busy, offline or moved; the
pushing account becomes the version's author; creations, renames and
deletions audited, pushes logged.
- ProjectService tells the host what each call changed, compared under the
lease, so projectChanged also follows Main's external versions; a Main
version mirrored into the settings sends sequenceChanged too, for older
clients. ProjectCatchUp takes settings a PATCH, an analysis or a
conversion wrote into Main at once, for sequences that have a Main.
- Renders of a project version: POST /jobs checks the project and version
against the sequence and pins a project alone to its head; render nodes
get the version's settings placed on the frames they claim; the render
records the project and version.
- Admin panel: the sequence page lists its projects (Main marked, head,
last change, versions on demand) with Rename and Delete for the others,
live on projectChanged. It edits no settings.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 2, R8, phase 5b (client part), ported onto the final phase 5a.
A Chronos Server with the "projects" capability is now the home of
workspace projects. A server sequence is edited in the workspace like a
local one, not inside the library, and its versions sync with the server
"like git".
- Data: ServerProjectHome is an IProjectHome over ChronosClient.
- These are HomeUnavailableException, so the workspace shows Offline: a
server out of reach, an expired sign-in, a 503 (lease, offline archive,
projects_unreadable), a 409 folder_in_use, and a server without projects.
- 404 sequence/project/version and refused names are ProjectException;
other refusals keep their meaning.
- A deleted project's head is 404 project, so final 5a's HeadAsync NotFound
rule reads it as Gone. The original 5b's IsLiveAsync and
WorkspaceStatus.Gone are dropped. IProjectHome gains rename and delete.
- Data: WorkspaceJobs.CopyFromServer downloads into the workspace, through
the desktop's session, the proxies of one frames version (or the
thumbnails standing in for them), with the aliases of the server's
conversions. It is rebuilt on final 5a's copy handler:
- the copy:frame:fv:folder checkpoint, EnsureSpace (from the server's proxy
sizes), WritingMedia, and the cancelled-copy clean-up;
- the editor's current file is never overwritten;
- each file is hashed as it arrives and checked on disk, four at a time.
It never writes this PC's archive. Originals are still refused until 5c.
- Data: SyncAgent passes on the server's projectChanged events, and after a
lost event stream it reports that changes may have been missed.
- App: SyncHost gives the server home over one session client. The Server
screen offers Open in workspace, disabled with its reason on older
servers, whose sequences keep opening with proxies.
- App: Edit opens or checks out server projects with final 5a's refusals:
unreadable copies, a disabled damaged or newer Main, a refused folder. The
"sequence left the index" refusal now applies only to projects of this
PC's archive.
- App: the picker and the chip follow projectChanged (Server newer, Not on
server). Every state, conflict, delete, remove and failure text uses its
".Server" form when one exists (WorkspaceText.ForHome). That includes 5a's
newer-format conflict, the save conflict, the taken-values toast, Gone and
version-too-large.
- App: a render of a server project first offers to send what is not on the
server, then renders the version the server holds. Offline, Gone, Damaged
and missing media hold the render. Analyses and renders run as server jobs
(ServerJobs, shared with RemoteSequenceSource).
- Pruning keeps final 5a's rule: a version is pruned only after HoldsAsync
reads it back.
- Strings in en and it; ARCHITECTURE, DECISIONS and CHANGELOG.
Tests:
- ServerProjectHome error mapping, using a fake handler.
- Against the in-process server:
- two workspaces on one project: fast-forward, replay and merge, keep mine,
take server, save both, restore;
- the copy job verifying, resuming and following new frames;
- a project deleted on the server (Gone from its head; a push sends
nothing);
- an offline server.
- SyncAgent project events.
- App tests for the host, the project menu and renders of a server home.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The projects table sits in a min-width-0 host so fitColumns can drop columns.
A live refresh re-reads only the changed, expanded projects and keeps as many
versions as were shown (Load more included). Version pages ask for the summary
form, so the panel no longer downloads settings it never shows.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The agent told "changes may have been missed" as soon as the stream dropped,
so a workspace re-read before the server's events could reach it again and
missed changes made in between. The signal now waits for the reconnected
stream and the refresh that follows it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- An unplaced sequence (no photos) lists no projects and refuses to create one
with sequence_empty, instead of writing sidecars at the archive root.
- A push accepts a full-size version; a 413 is reported as too_large.
- Version pages are capped in bytes and say when more follow; the summary form
leaves settings out; server homes page on.
- Deleting by its maker needs the same account, not just the same username.
- A settings PATCH writes project.json under the sequence lease, so Main's
later birth no longer wipes it.
- Reconcile, read-only catch-up and a Main flip publish projectChanged.
- Server homes read the frames stamp and check a version is really stored.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each behavioural fix of the previous commit gets a test that fails without it:
an empty sequence writes nothing and refuses projects, a 24 MiB version is
stored and one over the limit is too_large, a page of large versions stops
short and a server home pages on, a reused username deletes nothing, a PATCH
made after project.json stays Main's head, HoldsAsync is false for a missing
file or a deleted project, and a full rescan tells the rename it found.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A pull and the server's renamed event write the home's name into the copy, so
a rename made on the server reaches the workspace. A copy from a server marks
a thumbnail taken for a missing proxy before moving it into place; a resumed
run reads the marker and fetches the proxy the server has now, instead of
recording the thumbnail as one. Tests also cover the frames stamp (frames read
only when it moves), an older server's copy refusal and a viewer's 403 push.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An account without Edit is offered Open with proxies on a server that keeps
projects and checks nothing out, since it could never push. The editor of a
server's workspace project connects with the sign-in in use at each call, so a
project opened signed out renders once signed in; SyncHost tells every session
start and stop so workspace projects read their state again.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Phase 5b had only module rows and the review's DECISIONS and CHANGELOG lines.
The brief now describes the server home as the code does after the review
fixes: the projects API, projectChanged, the capability, the settings PATCH
under the lease, renders of a project version, the panel's Projects section,
and the desktop's server projects (open, copy, sync, chip, renders, viewers).
DECISIONS gains the phase's own rows; the 5b rows are dated 2026-10-26 like
the other review-2 phases, and three 5a rows are marked partly superseded.
CHANGELOG, STATUS, the request's 5b row and ARCHITECTURE follow the code
(frames stamp, stored reads, the .thumb marker, followed renames, the
editor's sign-in).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Before phase 5b the server's settings PATCH wrote the index alone, and every
desktop edit of a linked sequence arrives as one, so an upgraded server holds
sequences whose index settings are newer than their project.json. Main's birth
read project.json first and mirrored it over the index; sequenceChanged then
carried the loss to the desktops' linked copies.
ArchiveServiceOptions.IndexSettingsMayLead, set by the server, keeps both: Main
is born with project.json's settings as version 1 and the index's as version 2,
in force and mirrored (on a read-only archive both go to the index only). A Main
the sidecars already hold, met with no mirror known, keeps index settings that
none of its versions hold as an External version below what project.json gives
(the head again as a Restore, a merge, or the file's). The desktop is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The name follow after a pull caught only the home's own exceptions, so a 403
or any other error from the home's list (or a bundle in use) made a pull that
had already pulled and replayed report a failure. It is now logged as a
warning and the name is followed at the next pull; a cancellation still passes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
DECISIONS: IndexSettingsMayLead (Main's birth and meeting on a server keep the
index's settings), the name follow that never fails a pull, the capture's
sample paths and the Server actions column; the rows on the Main meeting, the
settings PATCH and the name follow point to them. CHANGELOG: the fix wording
is now true for servers upgraded from an earlier release, with an upgrade note;
BRIEF's Main mirror rule and STATUS follow.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 119 new phase 5b strings are translated into the 36 machine-translated
languages. The changelog separates what shipped in 0.1.0-rc.9 (ports and
baselines) from the unreleased phase 5b work, and the index settings decision
names the rare cases where a newer project.json is kept as version 1.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Alby96
merged commit 81c303f484 into main2026-11-04 14:58:18 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Owner review 2, R8, phase 5b: a Chronos Server becomes a project home, as a PC's archive already is (phase 5a).
What changes
/api/v1/sequences/{id}/projects(list, create, rename, delete, versions with paging, head, push with fast-forward / idempotent /project_diverged/ hash checks), theprojectscapability and theprojectChangedWebSocket event. Settings written by older clients, analyses, linked-copy sync or conversions become a new Main version. A settingsPATCHalso writesproject.jsonunder the sequence's lease.Review
One adversarial round with 21 findings, 19 fixed, then a checker pass (P1–P4 fixed). F3 (History downloads every version's settings) is partly fixed and listed under known limitations in the CHANGELOG.
How to try it
chronos-server:0.1.0-rc.10) and the desktop (installer from the release).Checks
dotnet build -c Release: 0 warnings.i18n check: 4451 keys, 38 cultures, 0 warnings.🤖 Generated with Claude Code
Owner review 2, phase 5b (R8): a server is a project home. A workspace can list a sequence's projects, make, rename and delete them, read their versions and push new ones through /api/v1/sequences/{sid}/projects. The endpoints run on the archive's ProjectService exactly as a desktop's archive does (sidecars first, then the index, under the sequence's lease), so no version is stored apart and a desktop sharing the archive sees the same projects. - Protocol: project, version, create, rename, version page, push answer (outcome, stored version, head, plus code and message on 409/422) and home frames DTOs, the projectChanged event, the "projects" capability and the ChronosClient calls; a push returns its outcome without throwing on 409 or 422. ProjectWire maps them to and from the model for both sides. - Server: Read lists and reads, Edit makes, renames and pushes, Delete (the sequence's owner, the project's maker or an admin) deletes; refusals with stable codes, 503 while the sequence is busy, offline or moved; the pushing account becomes the version's author; creations, renames and deletions audited, pushes logged. - ProjectService tells the host what each call changed, compared under the lease, so projectChanged also follows Main's external versions; a Main version mirrored into the settings sends sequenceChanged too, for older clients. ProjectCatchUp takes settings a PATCH, an analysis or a conversion wrote into Main at once, for sequences that have a Main. - Renders of a project version: POST /jobs checks the project and version against the sequence and pins a project alone to its head; render nodes get the version's settings placed on the frames they claim; the render records the project and version. - Admin panel: the sequence page lists its projects (Main marked, head, last change, versions on demand) with Rename and Delete for the others, live on projectChanged. It edits no settings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>Owner review 2, R8, phase 5b (client part), ported onto the final phase 5a. A Chronos Server with the "projects" capability is now the home of workspace projects. A server sequence is edited in the workspace like a local one, not inside the library, and its versions sync with the server "like git". - Data: ServerProjectHome is an IProjectHome over ChronosClient. - These are HomeUnavailableException, so the workspace shows Offline: a server out of reach, an expired sign-in, a 503 (lease, offline archive, projects_unreadable), a 409 folder_in_use, and a server without projects. - 404 sequence/project/version and refused names are ProjectException; other refusals keep their meaning. - A deleted project's head is 404 project, so final 5a's HeadAsync NotFound rule reads it as Gone. The original 5b's IsLiveAsync and WorkspaceStatus.Gone are dropped. IProjectHome gains rename and delete. - Data: WorkspaceJobs.CopyFromServer downloads into the workspace, through the desktop's session, the proxies of one frames version (or the thumbnails standing in for them), with the aliases of the server's conversions. It is rebuilt on final 5a's copy handler: - the copy:frame:fv:folder checkpoint, EnsureSpace (from the server's proxy sizes), WritingMedia, and the cancelled-copy clean-up; - the editor's current file is never overwritten; - each file is hashed as it arrives and checked on disk, four at a time. It never writes this PC's archive. Originals are still refused until 5c. - Data: SyncAgent passes on the server's projectChanged events, and after a lost event stream it reports that changes may have been missed. - App: SyncHost gives the server home over one session client. The Server screen offers Open in workspace, disabled with its reason on older servers, whose sequences keep opening with proxies. - App: Edit opens or checks out server projects with final 5a's refusals: unreadable copies, a disabled damaged or newer Main, a refused folder. The "sequence left the index" refusal now applies only to projects of this PC's archive. - App: the picker and the chip follow projectChanged (Server newer, Not on server). Every state, conflict, delete, remove and failure text uses its ".Server" form when one exists (WorkspaceText.ForHome). That includes 5a's newer-format conflict, the save conflict, the taken-values toast, Gone and version-too-large. - App: a render of a server project first offers to send what is not on the server, then renders the version the server holds. Offline, Gone, Damaged and missing media hold the render. Analyses and renders run as server jobs (ServerJobs, shared with RemoteSequenceSource). - Pruning keeps final 5a's rule: a version is pruned only after HoldsAsync reads it back. - Strings in en and it; ARCHITECTURE, DECISIONS and CHANGELOG. Tests: - ServerProjectHome error mapping, using a fake handler. - Against the in-process server: - two workspaces on one project: fast-forward, replay and merge, keep mine, take server, save both, restore; - the copy job verifying, resuming and following new frames; - a project deleted on the server (Gone from its head; a push sends nothing); - an offline server. - SyncAgent project events. - App tests for the host, the project menu and renders of a server home. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>