fix(projects): same project text on every OS; compare stored CRLF versions line-end-insensitively

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>
This commit is contained in:
Alby96andClaude Opus 5.5 committed 2026-11-04 22:48:27 +01:00
1 parent 863c6cf27b
commit 787f030060
15 files changed
+174 -25

No files matched your search

@@ -217,7 +217,10 @@ internal sealed class WorkspaceSendJobHandler(ChronosDatabase db, ArchiveService
if (entry.SettingsHash is { Length: > 0 } hash)
{
var history = await home.HistoryAsync(projectId, null, ReplayedLookBack, ct).ConfigureAwait(false);
same = history.FirstOrDefault(v => string.Equals(v.ContentHash, hash, StringComparison.OrdinalIgnoreCase));
// Of the same content whatever its line ends: a version stored by a Windows build before every build wrote LF
// holds the CRLF text and its hash.
same = history.FirstOrDefault(v => string.Equals(v.ContentHash, hash, StringComparison.OrdinalIgnoreCase)
|| (v.SettingsJson is { Length: > 0 } text && ProjectContent.MatchesHash(text, hash)));
}
if (same is not null)
{