session-memorylisted

# Session Memory Keep structured session notes at `session.md` in the project directory moh supplies in the prompt environment (`Session notes:` line under `## Environment`). Use exactly that path — never recompute the project slug from the working directory. ## Path setup Read the `Session notes:` path from the prompt environment. If it is not available, ask the user for the intended session file rather than recreating the slug calculation manually. ## Structured template When creating a new file, use **exactly** this template: ```markdown # Session Title _Descriptive 5-10 words, info-dense, no filler_ # Current State _What is being worked on RIGHT NOW. Pending, incomplete tasks. Immediate next steps._ # Task Specification _What the user asked for. Design decisions and explanatory context._ # Files and Functions _Important files: what they contain and why they are relevant._ # Workflow _Bash commands usually used and in what order. How to read the output._ # Errors & Corrections _Errors encountered and how they were resolved. What the user corrected. Failed approaches not to repeat._ # Learnings _What worked? What didn't? What to avoid? Do not duplicate other sections._ # Key Results _If the user asked for a specific output (table, answer, document), include the exact result here._ # Worklog _Step-by-step: what was attempted/done. Terse one-line summary per step._ ``` ## Update rules Always respect these rules when updating the file: 1. **Preserve structure*