remake: replays keep their writers

A remake's replay writes each value as the user who wrote it,
splitting where several users wrote under a path, so replays are
judged as the original writes.

Auth plan M6 (remakes, 2.4).

1 files changed, 3 insertions, 1 deletions

diff --git a/docs/remakes.md b/docs/remakes.md
index 7b21b9e..cad429f 100644
--- a/docs/remakes.md
+++ b/docs/remakes.md
@@ -305,7 +305,9 @@ The swarm stays writable throughout.
 * **Last writer wins**: a write is carried over only if nothing newer touched its path,
   a path above it or one below it, in the new epoch; newer by the times the writers'
   clocks gave their changes. A carried-over write keeps the time it was made, so a
-  later carry-over judges by that. A write that loses is left out, logged (`Writes not
+  later carry-over judges by that, and the user it was made for (`GET /admin/changes`);
+  the carrying node commits it. Another member's own entry (its alive stamp, its
+  links) is carried over by that member only. A write that loses is left out, logged (`Writes not
   replayed: newer ones touched their paths`), or with `--superseded-writes quarantine`
   kept in the quarantine. Clocks that disagree (beyond `--clock-skew-warn`) can make
   the older write win.