Project text was indented with Environment.NewLine, so the same project
read as CRLF text on Windows and LF text on the Linux server and its
content hash differed. A Windows desktop pushing to a Linux server got
spurious Merge and External versions, Modified/Behind states with no
edits, empty commits, and renders and sends taken for other settings.
Every build now writes the project JSON with LF (ProjectJson and
IndentedJson). Versions already stored keep their CRLF text and hash, so
SameChoices reads CRLF as LF (lossless: raw line ends are JSON
whitespace) and the places that ask whether a text is a given version
use the new ProjectContent.MatchesHash, true for the hash of the LF or
the CRLF form. Integrity checks of stored and pushed versions stay exact.
Tests pin the LF default hash, cover both comparisons both ways, and
push versions with the other OS's line ends to an archive home and into
a workspace: no outside change, in sync, nothing to commit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Originals are now judged by their bytes, never by the media index: a removal
or clean-up hashes every file under media/originals and deletes it only when
the home holds that SHA-256; every other file, named or not, goes to the
workspace trash. Trash entries are filled under a staging name that Empty
never lists. A ledger can only name files inside exports/.
Jobs follow the workspace: a copy, render or send resolves the folder that
holds its project now (a moved workspace, a retry after a move) and waits
while a move has not switched yet. A clean-up failure after the switch is a
warning that keeps the journal for a later resume; entries that changed
since they were copied are kept, and a same-volume rename refused across
volumes falls back to copy and verify.
Sends map a replayed version by content hash, or go with the project only,
and note an old server that drops provenance. The media index (format 2) and
project file (format 3) refuse older readers while they hold originals.
Metered connections also hold sync downloads and server copies. The editor
gains Send again, the Settings page can resume a stopped move, the disabled
tooltips say why, and unused strings are pruned.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The local render, the send home, the clean-up, the settings page and the
folder move were built apart; together they left gaps:
- A local render to an image sequence writes a folder, which the send
took for a missing file. The archive home now files the folder whole
(checked by its listing hash, as the render recorded it) and the
clean-up removes a sent folder; a server, which takes one file per
render, refuses it with Errors.Workspace.SendSequence.
- Rename, delete and Remove local copy are refused while the folder is
being moved, so no project folder changes under the move.
- Settings > Workspace shows the folder, usage, Move... and Change...
again when a move ends (WorkspaceHost.MoveEnded).
- Empty... uses the Settings typed confirmation; the separate trash
dialog, never shown, is removed. The move plan counts unsent renders
with the clean-up's helper.
- Tests: the follow-up send now runs in the render tests; an end-to-end
archive-home test (originals, version on render, local render, send
with project and version, clean-up) and an image-sequence send test.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Phase 5c P3. A render made in a workspace must reach its home with the project
and version it was rendered from, and transfers with a server must respect a
metered connection, downloads into the workspace included.
- WorkspaceSendJobHandler: per unsent ledger entry, hash the file again
(missing or changed: marked failed, file left in place), push the named
version first when the home lacks it (failure fails the job, entry pending),
then file it in this PC's archive (staged copy read back against its SHA-256,
project and version checked against the sequence) or upload it to the server
with ProjectId/ProjectVersionId; mark it sent. Idempotent by render id. A send
to a server waits while HoldTransfers says so.
- SyncTransfers: extract FileRenderAsync, the lease-held filing of a staged
render into a sequence's exports, shared by GetExportsAsync and the send.
- ISyncConnector.ProjectHome (default null; SyncHost already implements it) so
the send can push a version to a server home.
- Server: RenderUploads checks the project fields at start and completion
(422 project_mismatch) and records them; RenderDto carries them.
- UploadHold also pauses WorkspaceCopy and WorkspaceSend jobs naming a server;
Server screen checkbox reads "Pause metered transfers".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Phase 5c (owner review 2, R8) is built by six packages in parallel. This
commit settles everything they share, so each one touches its own files:
- job kinds WorkspaceRender (21), WorkspaceSend (22) and WorkspaceMove (23)
with their wire names, default priorities, notices and parameter records;
their handlers are registered as skeletons that throw until their
package lands
- WorkspaceJobOptions and a new CreateHandlers overload; the earlier ones
stay and default the options
- originals in the media index (an index of phase 5b reads as proxies
only), their file names, and the exports/renders.json ledger of local
renders, written atomically
- the optional project and version of an uploaded render
- the workspace settings (size limit, default media, version on render,
clean-up age, project to open) and when each project was opened, which
Reset and Import keep and Export leaves out
- WorkspaceHost split into partial files, with stubs for usage, trash and
the folder move, removal hooks for unsent renders and last originals,
and a guard that holds work while the workspace moves
- every new string of the phase in English and Italian, with tooltips
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>