m_savelisted

# m_save Write a **complete, self-contained snapshot** of the current work to `.m_last_task.md` in the project root. This is the standing "last task" file — always one file, always overwritten. Its counterpart `/m_go` reads it in a fresh session and continues. ## Inputs - `$ARGUMENTS` (optional): extra notes to include verbatim in the snapshot (e.g. "stop after step 3", a hint for the next session). ## Rules - **Write for a stranger.** The next session has NONE of this conversation. No "as discussed above", no shorthand invented mid-chat. Every file mentioned gets its full repo-relative path; every command is copy-pasteable. - **One standing file.** Always `.m_last_task.md` at the project root. Overwrite what's there — do not append, do not create dated copies. (If the current file describes a *different unfinished task*, mention that in one line under "Previous task" so it isn't silently lost.) - **No secrets.** Never write tokens, passwords, keys, or prod credentials into the file — reference the secret's *name/location* (env var, vault entry) instead. - **Gitignore:** if `.m_last_task.md` is not covered by `.gitignore`, append it (create `.gitignore` if missing) — this file is personal working state, not repo content. Skip silently if already ignored. - If an `.m_plan/<slug>/` run is active, don't duplicate its content — link the slug and state which step/`V-*` row you're on; `09_verification.md` stays the oracle. ## Snapshot format ```markdown # Last task — <one-lin