maintain-rightmemorylisted

- If the user specifies an exact root, use it. Otherwise run `rightmemory status` from the task's working directory, or `rightmemory --profile <name> status` when the user specifies a profile, and use the reported `root:`. If no root is reported, stop and ask the user; do not infer or guess it. Never call `rightmemory update`, submit candidates, or invoke another RightMemory model role. - Run `rightmemory validate --root <root>` before reading RightMemory state. Never follow or read a path it reports as non-regular; treat other findings as maintenance evidence. - Read the package-owned schema and Memory rules with `rightmemory reference schema` and `rightmemory reference memory`, then read available regular `<root>/MEMORY.md`, `<root>/PURSUITS.md`, relevant reachable backings, and relevant Git history or `update_records/*.json`. Before judging corresponding content, read `rightmemory reference pursuit`, `rightmemory reference agent-correction`, `rightmemory reference edit-correction`, or `rightmemory reference shared-view`; never edit immutable update records. Inspect the complete reachable state and identify concrete organization, consolidation, and cleanup that would make future retrieval and maintenance more coherent and useful. - During cleanup, delete trivial items instead of compacting them. - Before writing, present a concise proposal split into `Strongly recommended` items that materially affect correctness, coherence, or future use and `Optional` items that are discr