claude-code: a session's memory follows the operator to every node (issue 367, ADR 0343) #276

Merged

mesh-admin merged 4 commits from fix/367-memory-follows-the-operator into main 2026-10-13 14:26:59 +00:00

Conversation 8 Commits 4 Files Changed 5

+2070 -3

4 Commits

Author	SHA1	Message	Date
jschoubben	305601d25e	claude-code: memory carrying never leaves a memory folder, never takes the unreadable for gone, and screens every write (issue 367, review of #276) ... A value in the state could name a project such as ../../.. and be written outside the memory folder; a file or folder that could not be read was carried as a removal; text kept over a removal or merged in a conflict reached the state unscreened; and a conflict whose file could not be written was merged into the state again on every look. Names are judged before any file is touched, what cannot be read is kept and listed, every state write is screened, a conflict is written to the file before the state and warns once when it cannot be, a file changed between reading and writing is not written over, non-UTF-8 text is not carried, and a node that was away takes a removal it holds no change against (ADR 0343 §9, as clarified).	2026-10-13 16:20:02 +02:00
jschoubben	910bc58fe0	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).	2026-10-13 16:03:37 +02:00
jschoubben	0096beeff9	claude-code: say a memory conflict in the operator's plain words, and skip a look the state does not answer (issue 367) ... The warning now opens with what the operator is needed for and names no path, agent or session (ADR 0253's plain rule); clause references follow ADR 0343 as reviewed.	2026-10-13 16:01:16 +02:00
jschoubben	6aa30eae66	claude-code: carry each project's memory folder between nodes (issue 367, ADR 0343) ... A session started on another node began without what the sessions elsewhere had learned, because Claude Code keeps project memory on one node. The module's own process now carries the memory folders through its kept memory state: a change is written elsewhere only over the version it replaced, a file changed on two nodes keeps both (newer first) with a warning, and every replaced or removed version is kept. No tool writes memory.	2026-10-13 15:57:44 +02:00