nx_companion_persona.nx

nx_companion_persona.nx -- the CompanionPersona object (RENAMED from nx_companion_memory.nx 2026-07-21 to end a NAME COLLISION with runtime/nx_companion_memory.nx, which is a DIFFERENT episodic-memory module (nx_registry/nx_tabrec); nx_cc `find runtime -name` was resolving the wrong file after a sibling session removed the _hdl_build copy = a multi-agent-contention casualty). A companion's persona (data-driven elara_persona.txt) + persistent conversation memory (append-log elara_mem.log, cwd-relative) + reply cleaning (strips the model's <think> block). Bodies are the exact CompanionMemory object from the OO decomposition, behaviour-preserving. license_tier: ORIGINAL CC4 THE SWIPE LOOP (2026-08-30, companionchat): the log stays APPEND-ONLY and becomes BRANCH-AWARE. Row kinds (role <TAB> content <NL>, one record per line, exactly as before): user opens a turn assistant the turn's first reply (sibling 0) swipe a REGENERATED sibling reply of the current turn -- never overwrites, sibling k select the turn's displayed sibling becomes <n>; persists; an out-of-range n is IGNORED and counted, never guessed edit the displayed reply's text becomes <text>; ADDITIVE -- the original row stays in the log Displayed reply of a turn = the latest edit if any, else sibling[latest select], else the LAST sibling (a fresh swipe shows by default, as the field expects). The model's context carries only the displayed reply per turn, so a branch the user swiped away from never leaks into the next turn. A plain user/assistant log loads to the byte-identical legacy shape. Contract symbol: go_chat_swipe (companionchat CC4) is carried by the orchestrator's routes; the mechanism is here. Gate: nx_chat_swipe_gate (fixture log under /tmp/<gate>/, in-process).