Say the Fabric changes were run, and write them the way this codebase writes

Two things the pre-push audit turned up, neither of them a defect in behaviour.

status.md said all three of the window's fixes were re-checked in the running
application. Two were. The third needs a second install into a real Minecraft,
which has not been done; what covers it is tests over the merge itself. Now said
that way.

The adapter changes were compiled and not run, which the commits said accurately
but which left the standing gate unexercised over three behavioural changes to
the coordinator. It has now been run: 158 chunks enqueued, none dropped, no
snapshot failures, all seven corpus shapes present, and a fingerprint
byte-identical to the committed reference.

The rest is prose. Comparing the added lines against the codebase found the
" -- " aside used at roughly seven times the rate this project uses it, which is
a voice that is not its own. Rewritten into colons, commas and full stops; what
remains in these files is the author's own from before.

Author: TonyLu786

adapters/fabric/src/client/java/org/worldledger/fabric/WorldLedgerRuntime.java

@@ -110,8 +110,8 @@ public static void onBiomeUpdate(ClientboundChunksBiomesPacket packet) {
 	 *
 	 * <p>Nothing this mod does is worth that. Capture is a passenger: it records
 	 * what the client was shown, and a session that records nothing is a session
-	 * that recorded nothing. A player losing their connection -- or their
-	 * afternoon -- because a chunk could not be read is the one outcome that is
+	 * that recorded nothing. A player losing their connection, or their
+	 * afternoon, because a chunk could not be read is the one outcome that is
 	 * worse than not capturing at all.
 	 *
 	 * <p>Errors are not caught. An OutOfMemoryError or a linkage failure is not

adapters/fabric/src/main/java/org/worldledger/fabric/CaptureNotices.java

@@ -116,7 +116,7 @@ public static String reloaded(String contributor, boolean sessionRunning) {
 			// The one case where being vague would matter most. A player who
 			// blanks their name mid-session is asking to stop, and this used to
 			// answer "capture stays off" flatly while the running session kept
-			// recording under the name it took at join -- the setting changed,
+			// recording under the name it took at join. The setting changed,
 			// the session's copy of it did not.
 			//
 			// The session is now ended for them, so the sentence is true when it

cmd/worldledger/export.go

@@ -258,8 +258,8 @@ func (r worldRequest) write(snapshot epoch.Snapshot, prepared []anvil.PreparedCh
 	for _, path := range report.RegionFiles {
 		fmt.Printf("  %s\n", path)
 	}
-	// Said even when it is none, because the question it answers -- what
-	// happened to what was already in that world -- is one somebody has whether
+	// Said even when it is none. The question it answers, what
+	// happened to what was already in that world, is one somebody has whether
 	// or not the answer is reassuring.
 	if report.Kept > 0 {
 		fmt.Printf("%d chunk(s) already in those files were left as they were\n", report.Kept)

cmd/worldledger/translate.go

@@ -93,7 +93,7 @@ func translateForTarget(prepared []anvil.PreparedChunk, dimensionID string, opti
 	// Refusal was decided inside the translator, which only sees blocks, biomes
 	// and the build range. Block entities are dropped out here, so a conversion
 	// whose only loss was every chest, sign and furnace in the world reported
-	// them and then wrote the world anyway -- under the one policy whose entire
+	// them and then wrote the world anyway, under the one policy whose entire
 	// purpose is to write nothing and tell you what would have gone.
 	if report.Policy == translate.PolicyReport && droppedBlockEntities > 0 {
 		return nil, 0, fmt.Errorf(

desktop/internal/api/installing.go

@@ -230,7 +230,7 @@ func saveManifest(dir string, manifest installer.Manifest) string {
 	// usually one step. Replacing the record with that one step is how Remove
 	// came to remove a single jar and report "Your Minecraft is back to what it
 	// was" while the Fabric profile, the launcher entry, Fabric API and
-	// capture.properties all stayed -- and the play screen sends people back to
+	// capture.properties all stayed. The play screen sends people back to
 	// Set up for exactly the case that causes it, a launcher that replaced the
 	// mods folder.
 	if previous, err := os.ReadFile(path); err == nil {
@@ -258,7 +258,7 @@ func saveManifest(dir string, manifest installer.Manifest) string {
 // Where both touched the same file the two halves come from different places,
 // and getting that backwards undoes the wrong thing. The digest has to be the
 // new one, because that is what is on disk now and an uninstall compares against
-// it before removing anything -- keeping the old digest would make every
+// it before removing anything. Keeping the old digest would make every
 // reinstalled file look changed by somebody else and be left behind. The backup
 // has to be the oldest one, because that is what was there before this
 // application first touched the file; the later backup is a copy of our own

desktop/internal/api/manifest_merge_test.go

@@ -9,7 +9,7 @@ import (
 
 // A plan only contains steps for what is missing, so a second set-up is usually
 // one step. Writing that over the record is how Remove came to remove a single
-// jar and report "Your Minecraft is back to what it was" -- and the play screen
+// jar and report "Your Minecraft is back to what it was", while the play screen
 // sends people back to Set up for exactly the case that causes it, a launcher
 // that replaced the mods folder.
 

desktop/internal/api/status.go

@@ -63,7 +63,7 @@ type Server struct {
 	// The page never sent one, so export, moments and travel all defaulted to
 	// the overworld while this count summed every dimension. A player whose
 	// evening was in the Nether was told "800 places recorded" and then, on the
-	// next screen, that there was nothing recorded at that moment -- three
+	// next screen, that there was nothing recorded at that moment. Three
 	// screens disagreeing about the same archive, and none of them ever saying
 	// the word "overworld".
 	Dimensions []Dimension `json:"dimensions"`
@@ -184,7 +184,7 @@ func readSpoolState() *SpoolState {
 		}
 		// A folder that cannot be read is not an empty folder. Returning zero
 		// counts made the play screen say "Nothing new since last time" about a
-		// folder it had failed to open -- while the import screen, given the
+		// folder it had failed to open, while the import screen, given the
 		// same folder, said so honestly. Two screens disagreeing about one
 		// directory, and the reassuring one was wrong.
 		return &SpoolState{Dir: dir, Unreadable: err.Error()}

desktop/internal/installer/apply.go

@@ -335,8 +335,8 @@ func removeLauncherEntry(path, versionID string) error {
 // without saying so.
 //
 // So an existing file is edited: the contributor line is set wherever it is, and
-// every other line -- settings, comments, blank lines, whatever somebody added
-// of their own -- is passed through as it stands. Only an absent or contributed
+// every other line is passed through as it stands: settings, comments, blank
+// lines, whatever somebody added of their own. Only an absent or contributed
 // file gets written from scratch.
 func captureProperties(contributor string, existing []byte) []byte {
 	if len(bytes.TrimSpace(existing)) == 0 {

docs/status.md

@@ -101,13 +101,13 @@ The window is now told to draw at the display's real resolution. It never declar
 
 And the path ended without saying what had happened. It ended in one green line where the whole screen had been — no count, no folder, no files, nothing about what was already in that world. The last screen now answers the four questions that are actually asked there: what went in, what was already there and survived, where it is, and what to do next. On the same run, the install had also refused *after* the person had typed a name, read five file paths and agreed to all five, because a build from source carries no address for the mod; that refusal now happens before the asking, since consent collected for something that cannot happen is worse than not asking.
 
-**Three more the window had, found by looking for the same shapes again.** None of them fails anything, and all three are now fixed with the running application checked afterwards.
+**Three more the window had, found by looking for the same shapes again.** None of them fails anything. Two were re-checked in the running application afterwards and the third, which needs a second install into a real Minecraft, is covered by tests over the merge itself and is marked as such below.
 
 Reloading the page broke the application, and in browser mode killed it. The token arrives in the address and is stripped immediately so it does not reach history — and it lived only in a variable, so pressing F5 left the page with no token, every call answering 401, and the keepalive silenced, which ended the process forty-five seconds later. F5 on a screen that looks stuck is the most natural recovery action there is. The token now survives in `sessionStorage`, which is not what the original note was about: it empties when the tab closes and is shared with no other tab, and a token only ever works for the server that minted it. Checked in the running application: after a reload the address carries no token, the token is recovered, `/api/status` answers 200 and the page draws.
 
 Those four rejections were also the only failures in the application that came back as bare text, so the page could say "the application answered 401" and had nothing to suggest. All four now carry a problem and a next step, with a test over every one.
 
-A second set-up destroyed the record of the first. A plan holds steps only for what is missing, so a second run is usually one step, and the record was written over rather than added to — leaving Remove able to delete one jar while reporting "Your Minecraft is back to what it was", with the Fabric profile, the launcher entry, Fabric API and `capture.properties` all still there. The play screen sends people to Set up for exactly the case that causes it. Records merge now: the digest from the newer install, because that is what an uninstall compares against, and the backup from the older one, because that is what was there before this application first touched the file.
+A second set-up destroyed the record of the first. A plan holds steps only for what is missing, so a second run is usually one step, and the record was written over rather than added to — leaving Remove able to delete one jar while reporting "Your Minecraft is back to what it was", with the Fabric profile, the launcher entry, Fabric API and `capture.properties` all still there. The play screen sends people to Set up for exactly the case that causes it. Records merge now: the digest from the newer install, because that is what an uninstall compares against, and the backup from the older one, because that is what was there before this application first touched the file. Reproducing that end to end means installing into a real Minecraft twice, which has not been done; what is covered is the merge itself, by tests, including that a first install is unchanged by passing through it.
 
 And the whole application only ever meant the overworld. The page sent no dimension, so export, moments and travel all defaulted to it while the server's chunk count summed every dimension — so an evening in the Nether showed "800 places recorded" on one screen and "nothing recorded at that moment" on the next, with the word overworld appearing nowhere. The status now reports each dimension and its count, and both screens have a World chooser beside the server one.
 

internal/anvil/export.go

@@ -366,8 +366,8 @@ func readObject(source ObjectSource, ref model.BlobRef) ([]byte, error) {
 // The temporary name is unique rather than the target's with ".tmp" on the end.
 // A fixed name is only safe while one writer exists at a time, and there is no
 // such guarantee here: the desktop application's export lock is in-process, so a
-// command line export and the window running together -- or two exports into the
-// same world -- opened the same temporary with O_TRUNC, interleaved their bytes,
+// command line export and the window running together, or two exports into the
+// same world, opened the same temporary with O_TRUNC, interleaved their bytes,
 // and both renamed the mixture over a region file in somebody's save.
 //
 // The contents are forced to disk before the rename. This writes into a world