session-learningslisted

## What This Does Reviews the current session conversation **plus today's diary** (`/diary` decisions + SessionEnd baseline) to extract: - **Observations:** factual findings about how the system behaved - **Anti-patterns:** behaviors or approaches that caused waste or errors - **Rule suggestions:** concrete improvements to existing rules or new constraints needed - **Next actions:** deferred tasks that should be picked up in a future session Writes to `~/worklogs/learnings/YYYY/MM/YYYY-MM-DD-<slug>.yaml` (date-sharded for efficient lookup). Updates `~/worklogs/learnings/INDEX.yaml` with the new entry. ## When to Use **Trigger:** - `/session-learnings` command (manual invocation) - End of any substantive session (implementation, debugging, refactoring) - After a circuit-breaker halt that was resolved **Skip:** - Sessions that were purely exploratory with no findings - Sessions shorter than ~15 minutes with no significant discoveries ## How to Use 1. Read today's diary — the durable record of this day's decisions and outcomes: `cat ~/worklogs/diaries/$(date +%Y/%m)/$(date +%Y-%m-%d)-$(printf "%s" "$PWD" | (md5 -q 2>/dev/null || md5sum | awk '{print $1}') | cut -c1-8).yaml` Missing file → skip, conversation is the only source. Present → its `decisions`, `worked`, `failed`, and `signals` are facts; mine them for observations and anti-patterns before reading the conversation. 2. Review conversation for observations, anti-patterns, and rule friction points. 3. Ge