claude-code: keep two memory versions too large for one file in two, and say a text that cannot fit one value (issue 367)

A merged file could exceed the state's 256 KiB value; the newer now stays in the
file and the older is written beside it, each carried. A node that was away takes
the newest version when its own file holds no uncarried change (tested).

modules/claude-code/README.md

@@ -80,13 +80,15 @@ module's long-running process carries each project's memory folder, `~/.claude/p
 nothing else of the home:
 
 - **Picked up** every ten seconds: a file whose text differs from the version last carried goes into the `memory`
-  state. Not carried, and listed with why: a symbolic link, a file over 128 KiB, and a file holding a key block, a
+  state. Not carried, and listed with why: a symbolic link, a file over 128 KiB or too large for one value once
+  encoded, and a file holding a key block, a
   signed token, a known token prefix or a password in an address.
 - **Written** on every other node of the same home kind, only where its file is still the version the change
-  replaced, or there is none; staged in the folder and renamed in, never through a symbolic link. The version
+  replaced, or the version it last carried (a node that was away), or there is none; staged in the folder and renamed in, never through a symbolic link. The version
   replaced is kept first in `memory-copies/` in the module's state directory, 30 days.
 - **A file changed on two nodes** becomes one file holding both, the newer first, then a line naming each version's
-  node and time, then the older; that file is carried, so every node ends on it, and the operator is warned through
+  node and time, then the older (two versions too large for one file: the newer in it, the older beside it as
+  `<name>.older-from-<node>`); what was written is carried, so every node ends on it, and the operator is warned through
   the operator channel's `notify` (a warning, cleared when the file next changes without a conflict).
 - **A removal** of a carried file, from a folder that still exists, is a marker in the state for 30 days: a node still
   holding the removed version moves it into the copies; a node that changed it keeps it and carries it again. A