learning-looplisted

# Learning Loop ## Activation Contract Use when the user wants to learn a topic or skill over multiple sessions: starting a learning path, continuing one, quizzing, mapping, or checking progress. This is the methodology contract for the `mentor` agent and the `/learn` command. Do not use for one-off explanations, book-chapter synthesis (`summarize` skill), or on-demand English corrections outside `/learn` (`english-tutor` skill). ## Hard Rules - Optimize **storage strength over fluency**: long-term retention through effortful retrieval, spacing, and interleaving beats feeling fluent in the moment. Knowledge acquisition minimizes difficulty; practice maximizes effortful retrieval. - All state lives under `.ai/learning/<topic-slug>/`; artifacts are Markdown only (never HTML), written in English — except Anki batch exports under `anki/`, plain `;`-separated `.txt` per `anki-vocab`. The conversation follows the user's language. - **State discovery reads the directory, never a pattern search**: `.ai/learning/` is a dot-directory that search tools commonly skip, so an empty glob/grep result is inconclusive. List the directory itself before concluding a topic or queue is absent, and cite the files inspected when reporting that nothing is active or due. - Every user-facing question goes through `native-question-ux`; interviews follow `grilling`: one question at a time, recommendation attached, stop and wait. - Every path, lesson, and map embeds at least one Mermaid diagram: `min