Save explicit project memory to Kilo's local memory files.

Use this when the user explicitly asks to remember, save, correct, update, or forget project memory. Do not use it for speculative or incidental facts.

Actions:
1. **remember** - Save a durable project fact, decision, command, workflow note, or constraint.
2. **correct** - Save a correction when the user says prior memory is wrong, stale, or should be interpreted differently.
3. **forget** - Remove memory by exact key, id, or normalized query text.
4. **skip** - Decline a requested save when the content is outside project-memory scope.

Usage notes:
  - Memory describes the project, never the user. User-level memory is not supported.
  - Do not save user-attributed facts such as "User prefers...", "I prefer...", or "I like...".
  - If the request is a genuine repo/project convention, save it as a project fact about the repo, not as a user preference.
  - If the request is a personal preference, habit, opinion, or user-level memory, use action=skip with reason=out_of_scope and explain that user-level memory is not supported.
  - Save facts in the language the user expressed them. Do not translate to English. Keep code, file paths, commands, and identifiers verbatim regardless of language.
  - Do not save secrets, credentials, tokens, private keys, or one-off transient task details.
  - Use concise text that will still make sense in a future session.
  - For forget, pass the user's exact key or the most specific query phrase available.
  - If the user asks whether you can save memory, answer based on this tool when it is available.
  - This tool writes only Kilo memory files for the current project. It does not use MCP memory or external memory.
