resumelisted

# /mneme:resume — Orient in the current task graph, then stop Read-only ORIENTATION. It reads the current git branch, finds the branch's active run in mneme's event log, reconstructs the phase map (closed / ready / blocked / paused-on-boundary) plus the staged-but-unaccepted notes, and SUGGESTS the `/mneme:dev` continuation in REAL syntax — slug + `until`, with boundary candidates per the shared GRAPH-MAP convention — but it NEVER continues and NEVER mutates anything. It answers "where am I", not "carry on". The internal read-only posture is borrowed from `/mneme:arch`. The difference from `/mneme:dev` with no argument is the whole point: dev CONTINUES (it calls `workflow_step` and drives the loop); resume ORIENTS and STOPS. See `### RESUME-VS-DEV`. ## Arguments `/mneme:resume` — no argument. It orients on the CURRENT git branch's active run. There is nothing to pass; the branch selects the run. ## Permissions (VIOLATION = ABORT) — ORIENT-ONLY - Read / Grep: YES — the branch, the event log, and the phase files are all read-only inputs. - `workflow_start` / `workflow_step` / any submission: FORBIDDEN — resume NEVER drives the engine. It does not start, sync, advance, retry, or submit anything. - Edit / Write / Bash / any change on disk: FORBIDDEN — resume changes nothing, anywhere. - `recall` / `remember` / any memory tool: FORBIDDEN. This is ORIENT-ONLY: resume builds a map and STOPS. Acting on the map is `/mneme:dev`'s job, on the user's next move — never resume's.