Maintain Rightmemory

---
name: maintain-rightmemory
description: "Use when the user explicitly asks to inspect or maintain RightMemory Memory, Agent Corrections, edit feedback, or supporting references. Pursuit map editing is outside this workflow."
---

- 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`, relevant reachable backings, and relevant Git history or `update_records/*.json`. Read Pursuit as context for Memory meaning and references, not as content to reorganize. 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 affected reachable state for concrete organization, consolidation, and cleanup that would improve future use.
- During cleanup, delete trivial items instead of compacting them.
- Preserve consequential context gaps or ambiguity found within the requested scope as Open Context Questions; in read-only reviews, report them without editing.
- An explicit request to change these surfaces authorizes the requested maintenance. Read-only inspection does not authorize edits. Resolve ordinary local details from the current state, and ask only when a missing target or materially different interpretation prevents a safe change; do not add a routine preview-and-approval ceremony.
- Before writing, require the active root to be clean, capture its branch and HEAD, and create a dedicated temporary Git worktree and branch from that HEAD. Do not stash, discard, or absorb unrelated changes.
- Apply the requested changes in the worktree to Memory, its F#/M#/S# backings, Agent Corrections, RightMemory Edit Feedback, and supporting references. Keep Agent Corrections separate from root `corrections.md`. Preserve ids referenced from Pursuit and leave the Pursuit document tree unchanged. Explicit map changes belong to the separate `maintain-pursuit-map` workflow; do not invoke it or queue map work from this skill.
- Run `rightmemory validate --root <worktree>` and require a successful exit immediately before committing with subject `maintain: <concise maintenance summary>` and a `Validation:` body.
- Before landing, require the active root to remain clean, on the captured branch, and at the captured HEAD; otherwise stop and report the changed state. Land the exact validated commit with `git merge --ff-only`, without creating another commit, then require `rightmemory validate --root <root>` to pass. Remove the temporary worktree and branch; push when sync is configured.
- Report the applied changes, validation result, landed commit hash, and push result, or `no commit`.